Received: from mail-qg0-f64.google.com ([209.85.192.64]:36923) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XYCli-0005s0-7b for lojban-list-archive@lojban.org; Sun, 28 Sep 2014 04:36:05 -0700 Received: by mail-qg0-f64.google.com with SMTP id e89sf2115000qgf.19 for ; Sun, 28 Sep 2014 04:35:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :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:content-type; bh=9ODIQko1hWOoUDeDolAQNrm+dYBAPfLlP/hWOk3mhLs=; b=fnVdIOG+kfcgqwP3G9oJR3FuHkAkS8jLqYEi3/u6ClT20ai9p1zfpwtpdI/CppG+En gd5emFdLMKHVDXLVKroKonYw3sB8NgthFkMa1+ywle1tDJ93kdY6F4xaev9Kje/EQNiy u3moZc4y1GurKnXKweioR52ezuHyqjDpQ5zwjCioT95dackhp7CUItwFA0oHlvp9YZha 05sOtbzdS5MH47pmnHdIBLoC4MrKJe5/r/9sM+ijtmGMFZhCkHxPm8WwMhVEDdRCSY8g UE/NeaIS2k6AzsrWGLfpCd20VkvhGrsNo6mUfgrg3Iup1zG0NxnCDjRjkzgUeYMlsfay 5JaA== X-Received: by 10.182.4.1 with SMTP id g1mr479579obg.3.1411904151450; Sun, 28 Sep 2014 04:35:51 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.182.213.37 with SMTP id np5ls520938obc.84.gmail; Sun, 28 Sep 2014 04:35:51 -0700 (PDT) X-Received: by 10.182.66.68 with SMTP id d4mr27606902obt.39.1411904151066; Sun, 28 Sep 2014 04:35:51 -0700 (PDT) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [2607:f8b0:400e:c03::229]) by gmr-mx.google.com with ESMTPS id hz1si586714pbc.1.2014.09.28.04.35.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Sep 2014 04:35:51 -0700 (PDT) Received-SPF: pass (google.com: domain of and.rosta@gmail.com designates 2607:f8b0:400e:c03::229 as permitted sender) client-ip=2607:f8b0:400e:c03::229; Received: by mail-pa0-f41.google.com with SMTP id eu11so399145pac.14 for ; Sun, 28 Sep 2014 04:35:51 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.68.68.193 with SMTP id y1mr31104262pbt.70.1411904150905; Sun, 28 Sep 2014 04:35:50 -0700 (PDT) Received: by 10.70.37.198 with HTTP; Sun, 28 Sep 2014 04:35:50 -0700 (PDT) Received: by 10.70.37.198 with HTTP; Sun, 28 Sep 2014 04:35:50 -0700 (PDT) In-Reply-To: References: Date: Sun, 28 Sep 2014 12:35:50 +0100 Message-ID: Subject: [lojban] Re: {da poi} (was: Re: tersmu 0.2 From: And Rosta To: lojban@googlegroups.com X-Original-Sender: and.rosta@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of and.rosta@gmail.com designates 2607:f8b0:400e:c03::229 as permitted sender) smtp.mail=and.rosta@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com 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: , Content-Type: multipart/alternative; boundary=001a1137fbc85f2c1a05041e8d1a X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --001a1137fbc85f2c1a05041e8d1a Content-Type: text/plain; charset=UTF-8 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 logic 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} usage becomes correct? 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. 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. But I haven't studied the matter long enough to be sure that there is no other equally coherent definition for poi & noi. At any rate, none of this is in CLL, so at best is part of the lore of what should go into a revised CLL. --And. -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --001a1137fbc85f2c1a05041e8d1a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 28 Sep 2014 12:04, and.rosta@gmai= l.com wrote:
>
>
> On 28 Sep 2014 02:34, "Martin Bays" <mbays@sdf.org> wrote:
> > the compositionality
> > of restrictive clauses (which admittedly is already broken in som= e other
> > cases, e.g. {da poi broda}).
>
> I agree {da poi} looks broken. What are the remedies? (1) To allow non= compositional idioms? (2) To define /poi/ as an allomorph of /noi/ in this = syntactic environment? (3) To accept that, given the internal logic 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} usage becom= es correct?

I realize I was too hasty. Modifying a constant, X poi/noi b= roda both mean "me X" & "broda", differing in the s= copal position of "broda", local for poi and outermost (in the en= tire logical form) for noi. Modifying a variable, that cannot be the differ= ence. I had been assuming that noi modifying a variable would have outermos= t scopal position within the domain in which the variable is bound. But I h= aven't studied the matter long enough to be sure that there is no other= equally coherent definition for poi & noi.

At any rate, none of this is in CLL, so at best is part of t= he lore of what should go into a revised CLL.

--And.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--001a1137fbc85f2c1a05041e8d1a--