Received: from mail-qa0-f59.google.com ([209.85.216.59]:51368) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XYGwI-0002xH-Nj for lojban-list-archive@lojban.org; Sun, 28 Sep 2014 09:03:18 -0700 Received: by mail-qa0-f59.google.com with SMTP id w8sf125454qac.24 for ; Sun, 28 Sep 2014 09:03:04 -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=8GCKbZD0EQqUCzzXO6oK1uh1umqh1npwXLH1hsjYVPs=; b=F9gepQGDQbgYVwkjtxknQJ6WQpS/3ElSom60Zy6WCNyjuDIaU/qcBWhqyV5gMWZ9ee UlWCAC8zOxHxshk7byPaUGM1c4OEAXotKj4FLkaCLQhfb8l7yytlO+RsKNqS1gOsqemQ zR2kTQQtTPkB79GvxPDbnH7X3NoFEnylk6LXvmi+CH4E+0Jt+BaY36cEcfTdaw+7QPG3 zBbR39ts9IS8mK5bI1z9tfCS8JXPRuAua//NEl0Tennk0B5p/Fdk9RryFC3S9pbtDW7P Gz4Ek5BOTbkFQfKrroUHq07bQHEPhgsyhIx++z7Gou8AVemhWRAIUPDaIYB7KsVt2hKB Hy/Q== X-Received: by 10.182.165.8 with SMTP id yu8mr24400obb.9.1411920184362; Sun, 28 Sep 2014 09:03:04 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.182.213.37 with SMTP id np5ls535429obc.84.gmail; Sun, 28 Sep 2014 09:03:04 -0700 (PDT) X-Received: by 10.182.85.165 with SMTP id i5mr30281535obz.42.1411920184039; Sun, 28 Sep 2014 09:03:04 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id pz1si639769pbb.0.2014.09.28.09.03.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Sep 2014 09:03:03 -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 s8SG30Lv028850 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sun, 28 Sep 2014 16:03:02 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XYGve-0006CY-6o for lojban@googlegroups.com; Sun, 28 Sep 2014 12:02:30 -0400 Date: Sun, 28 Sep 2014 12:02:30 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: {da poi} (was: Re: tersmu 0.2 Message-ID: <20140928160229.GD28734@gonzales> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+b2GFy/wpzNn/yIF" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: burcu 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: - --+b2GFy/wpzNn/yIF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2014-09-28 at 12:35 +0100 - And Rosta : > On 28 Sep 2014 12:04, and.rosta@gmail.com wrote: > > On 28 Sep 2014 02:34, "Martin Bays" wrote: > > > the compositionality of restrictive clauses (which admittedly is > > > already broken in some other cases, e.g. {da poi broda}). > > > > I agree {da poi} looks broken. What are the remedies? (1) To allow > > noncompositional idioms? (2) To define /poi/ as an allomorph of /noi/ in > > this syntactic environment? (3) To accept that, given the internal logi= c of > > the language, {da poi} as habitually used is simply wrong? (4) To seek = and > > find a consistent definition for {poi} and {noi} such that {da poi} usa= ge > > becomes correct? Some other possibilities: (5) change the grammar to match the semantics, taking variable out of sumti6, and having restrictive relatives allowed only where there's a matching place for a quantifier; (6) note that doing (5) wouldn't actually render anything ungrammatical, so treat the existing grammar as a kind of shorthand for that in (5), and so consider current handling to be "effectively compositional". Other than indicators and frees, the {ro bu'a} hack, and {ma poi broda} which is arguably magic in the same way {da poi broda} is, I can't think of any place the semantics doesn't match the grammar. Not too bad. > I realize I was too hasty. Modifying a constant, X poi/noi broda both mean > "me X" & "broda", differing in the scopal position of "broda", local for > poi and outermost (in the entire logical form) for noi. I think {ko'a noi broda} really involves the claim {ko'a broda}, not {lo me ko'a cu broda}. > Modifying a variable, that cannot be the difference. I had been > assuming that noi modifying a variable would have outermost scopal > position within the domain in which the variable is bound. Hmm, that makes some sense. I have been taking, ever since xorxes told me off for doing otherwise in the first release, incidentals to be truly incidental, having no effect on the truth value of the main proposition. So a {noi} on a variable yields a side claim entirely outside the scope of the corresponding quantifier, so involving an unbound variable, which I'm currently (fairly arbitrarily) handling by universally quantifying it out over whatever domain it was originally quantified over, so e.g. {du su'o da poi broda zi'e noi brode} -> {ro da poi broda zo'u da brode .i su'o da poi broda zo'u du da}. > But I haven't studied the matter long enough to be sure that there is > no other equally coherent definition for poi & noi. >=20 > At any rate, none of this is in CLL, so at best is part of the lore of wh= at > should go into a revised CLL. Yes. --+b2GFy/wpzNn/yIF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQoMRUACgkQULC7OLX7LNYT3gCfc1knPhLCM0L+k4X14dX9zUJx /iEAniC0rZW6B28wbbfaF77J2QUtpJPK =4Oy0 -----END PGP SIGNATURE----- --+b2GFy/wpzNn/yIF--