Received: from mail-vc0-f185.google.com ([209.85.220.185]:45462) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XnE77-0000qM-6C for lojban-list-archive@lojban.org; Sat, 08 Nov 2014 14:04:17 -0800 Received: by mail-vc0-f185.google.com with SMTP id ij19sf745343vcb.22 for ; Sat, 08 Nov 2014 14:04:02 -0800 (PST) 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=ura8q05u0HWnqhGG2VjjYy+B2glXITNKaDKtXNnezoo=; b=ER8LozKlYfkhozVczWhgLeNbJ5jdYltWQljD1nUAbCl42ZFgcNKaiqT37TyjnSnJvJ XjaxUo4B8sYa0m1hZ2G6LMivweleqXssCF2C3iMF1IMQ3pAKmaK5T1heZk5X4j2v9Z1B dQMJ6wDxNNVeZ8MlVBJCMzAS+FzerQsrr0p3Tqtwip0rqvmBgcn6ocE+e1m3RsTBWZCq cR4nObXudQYraM84Y4dC9cipygPX/v0EOGVe5GXomegeKExEsBuhjnaFgWlxO+obVabv oF8mDMcDPozhBzel9Yfizh9wJHdePm6+8++Aa9QqKY4TsW4rnDJ9Dg6Tt1V6vfqvAbaU /UEw== X-Received: by 10.140.94.81 with SMTP id f75mr321075qge.5.1415484242750; Sat, 08 Nov 2014 14:04:02 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.140.94.193 with SMTP id g59ls1356500qge.75.gmail; Sat, 08 Nov 2014 14:04:02 -0800 (PST) X-Received: by 10.52.52.84 with SMTP id r20mr16587918vdo.5.1415484242386; Sat, 08 Nov 2014 14:04:02 -0800 (PST) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id jq13si720718pbb.1.2014.11.08.14.04.02 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Nov 2014 14:04:02 -0800 (PST) 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 sA8M3hM1002610 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sat, 8 Nov 2014 22:03:44 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XnE5x-0003Gd-Sh for lojban@googlegroups.com; Sat, 08 Nov 2014 17:02:57 -0500 Date: Sat, 8 Nov 2014 17:02:57 -0500 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141108220257.GA31242@gonzales> References: <20141104010958.GA27496@gonzales> <20141105035457.GA7768@gonzales> <20141106232818.GB1433@gonzales> <20141108030052.GC8542@gonzales> <20141108171036.GA10866@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: trati 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: - --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Saturday, 2014-11-08 at 18:02 -0300 - Jorge Llamb=EDas : > On Sat, Nov 8, 2014 at 2:10 PM, Martin Bays wrote: > > * Saturday, 2014-11-08 - Jorge Llamb=EDas : > > > So following CLL, without logical connectives "broda .i [tag] bo brod= e" > > > makes three independent claims: > > > > > > (1) broda > > > (2) brode > > > (3) lo nu broda cu xo'i [tag] (for tense tags) > > > lo nu brode cu xo'i [tag] (for non-tense tags) > > > > I read CLL as explicitly claiming a relation between events > > corresponding to the two sides, not leaving one of them up to context > > like this. So I read it as having > > (3') {[tag] le nu broda kei brode} (tense) > > {[tag] le nu brode kei broda} (non-tense) >=20 > Agreed, but that means the role of the brode event for tenses and the bro= da > event for non-tenses is left up to context, since the tag only guarantees > the x1 role of its underlying relation. Of course for many tags the role > for the other event will often also be quite obvious, but it's not a part > of the general logic of tags. With (3) I wanted to indicate that, but (3') > also works. But tags can have semantics which go beyond having something appearing in the x1 role of an underlying relation, with the rest left up to context. That may be all a fi'o tag does, but e.g. if ko'a is an event, then {ba ko'a brode} is an explicitly tensed claim of brode in the future of ko'a. {[tag] [[sumti]]} is a modal operator, whose precise semantics are entirely up to the definition of the tag. We called this "(i)" upthread. We agree on this really, don't we? > > > (a) mi na klama lo zarci .i ba'i bo mi stali lo zdani > > > I don't go to the market. Instead, I stay home. > > > > > > (a1) mi na klama lo zarci > > > (a2) mi stali lo zdani > > > (a3) lo nu mi stali lo zdani cu basti (lo nu mi (ja'a!) klama lo zarc= i) > > > > > > That works fine, because the change from "na" to "ja'a" is not part of > > > anything explicit in (3). > > > > This doesn't work with (3'), and hence not with CLL as I'm reading it. >=20 > (3') gives: >=20 > ba'i lo nu mi stali lo zdani kei mi na klama lo zarci > With replacement my staying at home: it is not the case that: I go to the > market. >=20 > I don't think it's too unreasonable for ba'i to provide a relation such > that basti1 relates to the negation of basti2 rather than to basti2 > directly, since this relation has to be contextual anyway. So I wouldn't > say it doesn't work with (3'), at worst it takes more work than just > assuming that "lo nu mi na klama lo zarci" has to take the basti2 role. I don't see what reasonable general definition of {ba'i ko'a broda} would make this work. If for any broda it implies the negation of broda, then {ba'i ko'a na broda} has to imply broda. If it's only for "positive" broda that it implies the negation of broda, then we'd have to have a notion of "positive"... and I doubt there's a good one. > > > But what if we wanted to say "mi stali lo zdani" first. Do we say: > > > > > > (b) mi stali lo zdani .i se ba'i bo mi klama lo zarci > > > (c) mi stali lo zdani .i se ba'i bo mi na klama lo zarci > > > > > > Neither (b) nor (c) seems to work well with (1), (2), (3), so we eith= er > > > have to discard (2), amend (3) somehow. > > > > Meanwhile with (1)+(2)+(3'), this definition of {ba'i} gives an > > immediate contradiction between (1) and (3'). >=20 > And here we have no escape because the role of lo nu mi na klama lo zarci > has to be basti2. >=20 > > > or dictate that tags like "se ba'i" don't make sense as bridi > > > connectives. CLL says that tags like "bau" don't make much sense, > > > which is reasonable because a bridi doesn't really describe > > > a language, but if "se ba'i" were not to make sense it would be for > > > a very different reason. > > > > Yes. Another option, if we do want to keep (1), which given the surface > > form would I agree be nice, would be to take it as part of the semantics > > of non-tense tags that {[tag] [[sumti]] broda} implies {broda}. That > > would rule out this use of {ba'i} entirely. >=20 > Or we could still have {[tag] [[sumti]] broda} implying {broda}, but then > (3') not always equivalent to (3) and it would be plain (3), or possibly >=20 > (3'') lo nu broda cu xo'i [tag] do'e lo nu brode (for tense tags) > lo nu brode cu xo'i [tag] do'e lo nu broda (for non-tense tags) >=20 > that expands the tag connective. There doesn't seem to be a strong reason > to disallow (a). Using anything like {do'e} would be a move of last resort for me... > > Evidence in CLL is very slim for non-je tensed logical connections. The > > only example I know of is the rather strained {mi bevri le dakli .ebake > > le gerku .acabo le mlatu} (10:17). I think what's there reads most > > naturally as being a case of "TT-skimming" as described earlier, but > > I don't think it's enough to force this interpretation. >=20 > I don't remember the details of TT-skimming. Was it something like that t= he > tag only kicks in when both connectands are true, and is otherwise ignore= d? Exactly that, yes. It's main advantage is being relatively simple. > > >>>>>> ca ro nu mi xagji kei mi klama lo zarci .e ba bo lo zdani > > >>>>>> -> ca ro nu mi xagji kei da poi nu mi klama lo zarci zo'u ge > > >>>>>> da fasnu gi ba da mi klama lo zdani > > > ca ro nu mi xagji kei ko'a fasnu > > > .i ko'a nu ge ko'e fasnu gi ko'i fasnu ba ko'e > > > .i ko'e nu mi klama lo zarci > > > .i ko'i nu mi klama lo zdani > > > > > > Every time I'm hungry, X happens. > > > X is Y happening and Z happening after Y > > > Y is my going to the market > > > Z is my going home > > > > I don't see that this helps at all. Now I have to ask: if ko'e is > > a constant (kind of an) event, what does {ko'i fasnu ba ko'e} mean? >=20 > Oh, I see I didn't expand it enough. OK: >=20 > ca ro nu mi xagji kei ko'a fasnu > ,i ko'a nu ge ko'e fasnu gi ko'i fasnu > ;i ko'i nu ko'o balvi ko'e > .i ko'e nu mi klama lo zarci > .i ko'o nu mi klama lo zdani OK... now I have to ask what {ko'o balvi ko'e} means! I expect it to be time-independent - if it holds at some time, then it holds at all times. But then your expansion doesn't have the intended meaning. Martin --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRekxEACgkQULC7OLX7LNbkKwCg4XWbGGbS4ndPcMg5h5sS2XW0 zlMAoN8Yt3vMxo6Vi7qpdwYxlWdnY5ua =tnPx -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o--