Received: from mail-yk0-f183.google.com ([209.85.160.183]:64191) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XfYSK-0007OP-5p for lojban-list-archive@lojban.org; Sat, 18 Oct 2014 11:10:27 -0700 Received: by mail-yk0-f183.google.com with SMTP id 20sf389735yks.0 for ; Sat, 18 Oct 2014 11:10:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=5WYcfSP3k3yWcZ6QGW16gnIt813DM+4RMK/kHyS8Sss=; b=fBtX5XqJrsUqaYvkF0itgRP2MZfyXpzAEwGiZL8WVrroP4uhghwbIeh8Rb7V/K6AvO ltpvaBelmyd9H1L3pAnxmsXa/wWg3yJcp5PfGUpm+x1kaSObaXgQZ1RH4CyRohNqVC8S UDzwFrltrYb8rbvVtoSyaXFPia7RoU3AfG4Fse1tOuzO8rGTZgDNUyzzLMW9BiDN5jr+ 3PJkcMkfTr/UUhQXZamM/WVs9jqkgCyG3pVewSipuCMZ63isU+5eROqix0NlNP3hSSTw vlWG0ue7Es0vvXVXek1VDA/Xi07OhXGl8hPTTMr44oMx9pGUk8uOiXlHexzvwWk3Gp30 vApg== X-Received: by 10.140.85.111 with SMTP id m102mr234026qgd.3.1413655813624; Sat, 18 Oct 2014 11:10:13 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.18.143 with SMTP id 15ls1589094qgf.70.gmail; Sat, 18 Oct 2014 11:10:13 -0700 (PDT) X-Received: by 10.236.17.233 with SMTP id j69mr10775622yhj.47.1413655813382; Sat, 18 Oct 2014 11:10:13 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id yr4si491607pab.1.2014.10.18.11.10.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Oct 2014 11:10:13 -0700 (PDT) Received-SPF: none (google.com: mbays@sdf.org does not designate permitted sender hosts) client-ip=192.94.73.24; Received: from thegonz.net (d24-141-9-29.home.cgocable.net [24.141.9.29]) (authenticated (0 bits)) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s9II9aQV026395 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sat, 18 Oct 2014 18:09:37 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XfYRm-0005qi-EM for lojban@googlegroups.com; Sat, 18 Oct 2014 14:09:46 -0400 Date: Sat, 18 Oct 2014 14:09:46 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141018180946.GF20049@gonzales> References: <20141012012427.GF23876@gonzales> <20141012173533.GG23876@gonzales> <20141014010742.GF19061@gonzales> <20141015005542.GC3713@gonzales> <20141018004531.GE20049@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FeAIMMcddNRN4P4/" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: xampo User-Agent: Mutt/1.5.22 (2013-10-16) X-Original-Sender: mbays@sdf.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: mbays@sdf.org does not designate permitted sender hosts) smtp.mail=mbays@sdf.org Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --FeAIMMcddNRN4P4/ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Saturday, 2014-10-18 at 13:12 -0300 - Jorge Llamb=EDas : > On Fri, Oct 17, 2014 at 9:45 PM, Martin Bays wrote: > > I don't see it that way at all. It's the same rule. It's just that the > > rule is applying to the implicit sub-bridi of the description clause; in > > general it applies to the immediately enclosing bridi (just like any > > other bridi operator, e.g. tenses). > > > > (I'm not particularly happy with this "bridi" and "sub-bridi" > > terminology, btw, though I hope you can see what I mean by it; feel free > > to suggest alternatives) >=20 > Well, we know for sure how the operator "ko'a .e ko'e" operates when it > occupies the place of an argument of an atomic predicate: It outputs the > conjuntion of the two atomic formulas created by using "ko'a" and "ko'e" > respectively as the argument of the atomic predicate. (Since we were talking about terminology, let me be picky: it isn't just a matter of atomic formulas, since e.g. in {ko'a .e ko'e ro da broda} ~=3D {ge ro da zo'u ko'a da broda gi ro da zo'u ko'e da broda}, the formulae being conjoined aren't atomic.) > When "ko'a .e ko'e" occupies some other place (e.g. the argument of a > function LAhE) we cannot apply the above rule directly. We need to either > say how "ko'a .e ko'e" operates when it occupies the argument of an atomic > function (which to me implies a new rule, even if the rule is very similar > to the rule for when it occupies the place of an atomic predicate While, if you'll excuse me reiterating, I would say that given the profusion of logical connectives and other bridi operators throughout the language, it's better to give abstract rules which cover many cases uniformly rather than think in terms of specific rules for each situation; so in this case I would explain the situation with two rules: (i) a bridi operator operates on the bridi immediately under construction, i.e. the lowest in the tree; (ii) a logical connective acts as a bridi operator, connecting the two formulae obtained by substituting each connectand in turn for the connected element. > ) or we can say that there are no atomic functions, all functions are > in fact built out of predicates. In this case, we just need to express > the function in terms of a predicate, and then apply the rule we > already have for "ko'a .e ko'e" as a pseudo-argument of an atomic > predicate. If I understand correctly, (i) and (ii) also explain these semantics; the only difference is in whether LAhE introduces a bridi of its own. > > So it does... I guess to get the "lo (re lo mlatu .e ci lo gerku)", you > > have to use > > lo tu'o boi re lo mlatu .e ci lo gerku > > ? >=20 > I suppose. I guess with ".a" it would make more sense: "lo po'i ga re mei > gi'e me lo mlatu gi ci mei gi'e me lo gerku". Hmm... hold on, in {lo tu'o boi re lo mlatu}, we have to parse {re lo mlatu} first as {re da poi me lo mlatu}. So I don't think any remei are really involved. If we assume that {lo [quantifier]} does introduce a sub-bridi, I guess I'd expect lo tu'o boi re lo mlatu .a ci lo gerku -> lo poi'i me re lo mlatu .a ci lo gerku -> lo poi'i ga me re lo mlatu gi me ci lo gerku -> lo poi'i ga re da poi me lo mlatu zo'u ke'a me da gi ci da poi me lo gerku zo'u ke'a me da (which is a rather bizarre thing to refer to!). > > > I have no idea what the rules for mekso are in detail, so I don't know > > > whether for example "li na'u sinso mo'e ko'a .e ko'e" is supposed to = be > > > equivalent to "lo sinso be ko'a .e ko'e" or to "li na'u sinso mo'e ko= 'a > > > lo'o .e li na'u sinso mo'e ko'e".=20 > > > > What is the operand {mo'e ko'a .e ko'e} such that sine of it is > > something which is sine of both ko'a and ko'e? >=20 > Is "mo'e ko'a .e ko'e" an operand, or just a pseudo-operand > (morphologically an operand, but logically not an operand, like "ko'a .e > ko'e" is morphologically a sumti, but logically not a sumti)? >=20 > We cannot claim that the rule for operand-3 always returns true logical > operands, in the way that we could claim that sumti-6 (almost) always > returns true logical sumti. "gek operand gik operand-3" is an operand-3, > for example. I would say that 'sumti' always returns a term, and so does 'operand', where "term" is meant in the sense of logic, and where "returning" is something that only makes sense in the context of the full parsing algorithm, but is such that e.g. {ko'a .e ko'e} returns what ko'a is bound to to one branch, while returning what ko'e is bound to to the other branch - where these "branches" are what are created by the semantics of logical connectives as in (ii) above. Similarly, {ro da} returns the variable quantified over by the quantifier it introduces. > So, I would not want to insist that "mo'e ko'a .e ko'e" is a logical > operand, and indeed in my example I was not taking it as one. Since > sumti and operands are logically the same thing, I was just ignoring > "mo'e" and "li", and the question was whether "ko'a .e ko'e" operates > on the predicate "sinso" or on the predicate containing the li-clause > as its argument. OK; so in other words you're taking {mo'e} to be transparent, i.e. not to introduce a sub-bridi, but for the production 'mex' to be opaque and to introduce a sub-bridi corresponding to the predicate "is the result of applying [operator] to [operands]"? So this handling of {mo'e ko'a .e ko'e} involves a "new rule"? > > > > > Do we even know what "na ku zo'u broda .i bo brode" means? > > > > I believe it's the same as "na ku ge broda gi brode". > > > I suppose that's one choice, although it's not a necessity that > > > juxtaposition be equated with conjunction, or that the negation of two > > > separate propositions has to be the negation of their conjunction. > > Is there a plausible alternative? >=20 > Well, I'm not advocating this but we know that "na ku zo'u broda" express= es > the negation of the proposition expressed by "broda", so it would not be > out of the question to say that "na ku zo'u tu'e broda .i brode tu'u" > expresses the negations of both propositions, rather than just the negati= on > of their conjunction. The operator "na ku zo'u" is only well defined when > applied to a single proposition. When applied to multiple propositions at > once, who knows how we want it to act. Maybe it should be distributive. I guess it could! Yet another thing to be decided. Do you think it might be a bad idea to decide that it's equivalent to "na ku go broda gi brode"? --FeAIMMcddNRN4P4/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRCrOoACgkQULC7OLX7LNaEQACg3k2Md2R7HA5+fi6VUfHheyfg BxIAn0M+WYfQ3P56Jc3xBbRqez945bQv =KTmG -----END PGP SIGNATURE----- --FeAIMMcddNRN4P4/--