Received: from mail-oi0-f63.google.com ([209.85.218.63]:38958) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Xn9YC-00082B-J4 for lojban-list-archive@lojban.org; Sat, 08 Nov 2014 09:11:56 -0800 Received: by mail-oi0-f63.google.com with SMTP id e131sf692793oig.18 for ; Sat, 08 Nov 2014 09:11:42 -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=d/1OHWv3ykDS8voJWWi5Hk6ZIXd8QAKTOE7j2gjv/pU=; b=Whltz8nl5WrWGixfAfaiF1x3aTHTAEKE3OiLExGKc3Qc88nldaV8obo9LGNvi57e2K Gz0FxQC9cItRJIBiVbsrkFmLV+F8Kr2kT/ZSDc9tGEw4/3oto5Q+ENrUWSVYdwtouoAF GeK9B6CAwZdzXhj2/gSHmB/hcWMwNkBDpzJCFWV/UIgZ1Y/fXT7xESuBf4ojtaQhkMEM HK0WJr5VF88ZyLv4uQk8e2d2+dknpbS4maCj5Ok/cckRK7/D4nDctoAlKdkxy7VC0Lnx CHT5a1eQx5BfTKOe33FvT+6Uy5065qZBtzgLfWgIdbgo1+t9kT4S4kccCTLo559DAVif SVhQ== X-Received: by 10.50.112.67 with SMTP id io3mr132876igb.14.1415466701998; Sat, 08 Nov 2014 09:11:41 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.107.3.10 with SMTP id 10ls953717iod.87.gmail; Sat, 08 Nov 2014 09:11:41 -0800 (PST) X-Received: by 10.66.102.42 with SMTP id fl10mr15036297pab.45.1415466701232; Sat, 08 Nov 2014 09:11:41 -0800 (PST) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id ax5si932129pbd.0.2014.11.08.09.11.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Nov 2014 09:11:41 -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 sA8HBN53011050 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sat, 8 Nov 2014 17:11:24 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1Xn9X2-0003qZ-Q1 for lojban@googlegroups.com; Sat, 08 Nov 2014 12:10:36 -0500 Date: Sat, 8 Nov 2014 12:10:36 -0500 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141108171036.GA10866@gonzales> References: <20141030013306.GO4023@gonzales> <20141104010958.GA27496@gonzales> <20141105035457.GA7768@gonzales> <20141106232818.GB1433@gonzales> <20141108030052.GC8542@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: latmo 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: - --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Saturday, 2014-11-08 at 11:28 -0300 - Jorge Llamb=EDas : > On Sat, Nov 8, 2014 at 12:00 AM, Martin Bays wrote: >=20 > > * Friday, 2014-11-07 at 17:58 -0300 - Jorge Llamb=EDas > >: >=20 > > On Thu, Nov 6, 2014 at 8:28 PM, Martin Bays wrote: > > > > * Wednesday, 2014-11-05 - Jorge Llamb=EDas : > > > > > I was speculating on what the second proposition would be when > > > > > a logical connective is involved. Nothing really makes much > > > > > sense though. > > > > Is it so bad for it to be {brode}, completing the symmetry with > > > > the tense case? > > > It's unintuitive for me, it doesn't really fit the surface form. > > > > I see what you mean. But CLL is clear that brode is claimed, so I'll go > > with that. >=20 > So following CLL, without logical connectives "broda .i [tag] bo brode" > makes three independent claims: >=20 > (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) > CLL analyzes the relatively easy cases (causals) where the tag-claim > presupposes the subordinate claims in any case, Implies rather than presupposes, I'd say (the distinction matters in embedded contexts). Because CLL only considers such cases, I think in the non-tense case we can feasibly read it as only claiming (2) and (3'), with (1) being an implication of (3') in the cases it considers. Reading its account of the distinction between 9:7.1 and 9:7.7, where the former is of form (3') and the latter is a non-tense connection, it seems quite clearly to be saying that all it adds to (3') is a claim of form (2). CLL also doesn't consider embedded contexts, so I think we can expect to have to change its use of {le nu} to something other than {lo nu}. > but this may be problematic for other tags such as "se ba'i" or "se > cau", where the negation of one of the subordinate claims would have > to be presupposed. So for example: >=20 > (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. >=20 > (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 zarci) >=20 > 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. > But what if we wanted to say "mi stali lo zdani" first. Do we say: >=20 > (b) mi stali lo zdani .i se ba'i bo mi klama lo zarci >=20 > (b1) mi stali lo zdani > (b2) mi klama lo zarci (?!) > (b3) lo nu mi klama lo zarci cu se basti (lo nu mi stali lo zdani) >=20 > or do we say: >=20 > (c) mi stali lo zdani .i se ba'i bo mi na klama lo zarci >=20 > (c1) mi stali lo zdani > (c2) mi na klama lo zarci > (c3) lo nu mi na klama lo zarci cu se basti (lo nu mi stali lo zdani) (?= !) >=20 > Neither (b) nor (c) seems to work well with (1), (2), (3), so we either > 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'). > 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. > In any case, all of that applies to ".i [tag] bo". ".i [jek tag] bo" is > related, but has to be analyzed separately. >=20 > "broda .i brode" makes two independent claims. > "broda .i [jek] brode" makes one claim. > "brode .i [tag] bo brode" makes three independent claims according to CLL > (I would prefer it rather made two.) >=20 > How many independent claims does "broda .i [jek tag] bo brode" make, and > what is it or what are they? >=20 > I'd like it to make just one claim, the jek-logical connection between (1) > and (3) above. CLL seems to say that it makes two independent claims: > "broda .i [jek] brode" and (3). But this doesn't work very well when "jek" > is anything other than "je". 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. > > > > > 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 g= e da > > > > > > fasnu gi ba da mi klama lo zdani > > > > > > > > > > ca ro nu mi xagji kei ge ko'a goi lo nu mi klama lo zarci cu > > > > > fasnu gi ba ko'a mi klama lo zdani > > > > But if ko'a is a constant (kind of an) event, what does {ba ko'a mi > > klama lo zdani} mean? > > > > I understand the original sentence as having multiple pairs of goings, > > with a time relationship claimed for each pair. >=20 > 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 >=20 > 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? > We could, instead of saying that X, Y and Z happen every time, talk about > many different instances such that each happens once, but I think that > introduces a lot of (sub)entities that are not obviously there in the > original sentence. I'm not seeing an alternative. Martin --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlReTowACgkQULC7OLX7LNbnRwCaAwrx9NaohELUGS/m14pyFCIr t+oAoN3dQvUwh1si2D3lILc/USzyd8bD =4BB1 -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--