Received: from mail-qc0-f189.google.com ([209.85.216.189]:54298) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XiwYO-00037T-FF for lojban-list-archive@lojban.org; Mon, 27 Oct 2014 19:30:41 -0700 Received: by mail-qc0-f189.google.com with SMTP id b13sf683744qcw.26 for ; Mon, 27 Oct 2014 19:30:29 -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=+10MCIJKG/v4TCKrkNhemWCyKV+1Jau9PFthbfC7UkM=; b=FjciQT4tvz/7T27VGk+ieW7D07jnXuzhYhUetBUBtm6xZcOeufH1A3V6zyDOgbBSu+ P8gCNU9wPGzGfuqIWLSvJV/WeY7RgDqEHza6OeiaWTMQnYEFybt309oSp3yueNGNX8QV SGESS9fYQVv2VgQAaIHiHp5fCfozBv+Cq/D/QbOZEbAM4Nkdjb9jjHMiQAGaCkUfRICP Wd0gVrTkVWfpChdPsMKjXRQQgq7lRjJtqkaWLlIjXYSbELzdQeNB03AaVNcrZqIpmIMH f9LRF4jVPYIH/1aNrO4EKT3N38xV3FLzsaYeALSBTgmbDMEem6qjFe1GY/rOaFNgIEJt 4mnA== X-Received: by 10.140.20.175 with SMTP id 44mr7441qgj.4.1414463429492; Mon, 27 Oct 2014 19:30:29 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.20.141 with SMTP id 13ls15466qgj.58.gmail; Mon, 27 Oct 2014 19:30:29 -0700 (PDT) X-Received: by 10.224.30.133 with SMTP id u5mr382575qac.8.1414463429153; Mon, 27 Oct 2014 19:30:29 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id qm4si18529pdb.2.2014.10.27.19.30.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Oct 2014 19:30:29 -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 s9S2UMt3012809 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Tue, 28 Oct 2014 02:30:23 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XiwXZ-0002Ee-HQ for lojban@googlegroups.com; Mon, 27 Oct 2014 22:29:45 -0400 Date: Mon, 27 Oct 2014 22:29:45 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141028022945.GA6097@gonzales> References: <20141018180946.GF20049@gonzales> <20141018233648.GA29040@gonzales> <20141021010639.GB11705@gonzales> <20141022002214.GD25753@gonzales> <20141022230855.GG2128@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: kelci 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: - --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Wednesday, 2014-10-22 at 20:38 -0300 - Jorge Llamb=EDas : > On Wed, Oct 22, 2014 at 8:08 PM, Martin Bays wrote: >=20 > > > > ba gi broda gi zajba =3D=3D broda .i ba bo zajba > > bai gi broda gi zajba =3D=3D zajba .i bai bo broda > > > > Which reminds me - which way should > > broda .i ba je bai bo zajba > > work, or should it be some mix? If a mix, how about with {joi}? >=20 > I guess it would be: "ba je se bai gi broda gi zajba" and the same for > "joi", but we should unify all tags to work the same way. That would be nice! I'm not sure that using {se} like this is robust, though. There's no formal reason that [BAI] gi bakni gi zajba should be equivalent to se [BAI] gi zajba gi bakni , even if it often is, right? > > > I think it might also make sense to analyse tag-connectives as if > > > they were ordinary tags on the second connectand, with the first > > > connectand acting as their complement, so: > > > > > > broda .i [jek tag] bo brode > > > -> broda .i [jek] brode [(se} tag] lo nu broda > > > > But if broda doesn't occur, what is {lo nu broda} referring to here? >=20 > In that case the complement would have to be "lo nu na broda". So: >=20 > broda .i [jek tag] bo brode > -> broda .i [jek] brode [(se} tag] lo nu xu kau broda >=20 > where "lo nu xu kau broda" is whichever of "lo nu broda" and "lo nu na > broda" is true. I don't immediately see exactly what that would mean, so let me back up and think abstractly about events, tenses and modal operators. A lojban statement is interpreted as a proposition in the corresponding logic, and by default the illocutionary force is to assert the truth of the proposition. Often the assertion is spatiotemporally restricted, and we can say that an event (of the proposition being true) is being asserted to occur. Again, for this discussion I'll pretend (or note?) that this is the only case to consider. In lojban, and I suppose in human cognition, events are things. They can be counted and measured in various ways, and can satisfy predicates.=20 A tag is interpreted as mapping an optional term to a modal operator - something which takes formulae to formulae. The semantics of these operators are highly miscellaneous; {ba}, {no roi}, {ja'e}, {bau} all have quite distinct flavours. Now to return to tag connectives, and to correct some mistakes I made earlier in this thread, let me first think through again the simple case of {[tag] gi broda gi brodu}. Earlier I implied that this could be handled symmetrically, but that was just wrong-headed; e.g. in {no roi gi broda gi brodu}, we're claiming an event of broda occurs, but not so for brodu. So it must be something like "an event E of broda occurs; {[tag] E brodu}". I think it must actually be: [tag] gi broda gi brodu <=3D> su'o da tu'e da fasnu gi'e nu broda .i [tag] da brodu , or maybe that but with {su'oi} in place of {su'o}. (For this to make sense, {fasnu} must behave the with respect to tense the way "occurs" does, e.g. an event which occurred in the past fasnued then but doesn't fasnu now.) Evidence for this being the right thing: we can rule out any "lo-style" semantics, where some definite nu broda are involved, by considering how the construction works in negated scope: na ba gi broda gi brodu should make sense, and be true, if no events of broda occur. So {lo ge nu broda gi fasnu} can't be involved, nor is it about a specific contextually specified nu broda, nor the kind, nor anything similar that I can think of. Universal quantification would be silly. So by elimination of the other natural choices, it has to be existential quantification. In particular, {broda .i brodu [tag] lo nu broda} may be a handy shorthand reformulation, but it isn't actually equivalent. Now: > broda .i [jek tag] bo brode > -> broda .i [jek] brode [(se} tag] lo nu xu kau broda =2E For simplicity, let's assume the tag is a tense (so there's no {se}). Again, if this is to work in embedded scopes, I think we need to recast it in terms of quantification over events. Annoyingly, I can't see a way to do that that's uniform over the possible jeks. But e.g. for {jo}, I guess it would have to be: da zo'u ge da fasnu gi ga ge da nu broda gi [tag] da brode gi ge da nu na broda gi [tag] da na brode Is that faithful to your intention? Is there a way to abbreviate it using {xu kau}? I don't really know how this kind of use of q-kau works, but I'm guessing it jumps scope like actual questions do, so can't really be used here for this kind of thing. Anyway, this does seem like a reasonable semantics. To compare with the TT-skimming approach I suggested: {broda .i na ja ba brode} still means "if broda then then brode"; {do ba prije gi'o ja'e bo snada} adds that failure will be caused by non-wisdom; in the CLL example {ba tu'e mi bevri le gerku .ijacabo mi bevri le mlatu} the truth conditions seem to be the same without the {ca}, but then I think that's how it has to be read in CLL too (so it isn't a very good example, really.), and this is also the case with TT-skimming. Martin --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRO/5kACgkQULC7OLX7LNbkeACfVx/rwBXSBOqFLx9taHk2/NUE /b4AoIcrrvfP9gynZhhsSbElOjnq7AT+ =oIws -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu--