Received: from mail-bw0-f61.google.com ([209.85.214.61]:48567) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RWTat-00075t-Ha; Fri, 02 Dec 2011 05:56:10 -0800 Received: by bkbzt19 with SMTP id zt19sf2889513bkb.16 for ; Fri, 02 Dec 2011 05:55:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf: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:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=L8mUA/WcLPtvfDnnNSUDkPG3AoM3WLJ0JlTWJu3WXK0=; b=zSw59QWV1kQ2/NFCRb0amYured092SqxiH8JGeOIPjDibNO1thElVm5C8tUTmfSMa2 wIHeYzoGWmm1QV6+KJFcuO0GNq4tPG1V95+EagrLtc5c33XTTSEBRHdVCGmy7mXnDILg JR88lkVB28AYTcQR8u3jO2LgfNdexB0tb2p/I= Received: by 10.204.41.201 with SMTP id p9mr1193358bke.18.1322834153278; Fri, 02 Dec 2011 05:55:53 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.204.130.207 with SMTP id u15ls19656740bks.0.gmail; Fri, 02 Dec 2011 05:55:52 -0800 (PST) Received: by 10.204.145.80 with SMTP id c16mr72275bkv.2.1322834152185; Fri, 02 Dec 2011 05:55:52 -0800 (PST) Received: by 10.204.145.80 with SMTP id c16mr72273bkv.2.1322834152160; Fri, 02 Dec 2011 05:55:52 -0800 (PST) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by gmr-mx.google.com with ESMTPS id 6si3348855bkv.1.2011.12.02.05.55.52 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Dec 2011 05:55:52 -0800 (PST) Received-SPF: pass (google.com: domain of mturniansky@gmail.com designates 209.85.214.54 as permitted sender) client-ip=209.85.214.54; Received: by mail-bw0-f54.google.com with SMTP id t2so5720416bka.27 for ; Fri, 02 Dec 2011 05:55:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.154.130 with SMTP id o2mr11161172bkw.138.1322834151888; Fri, 02 Dec 2011 05:55:51 -0800 (PST) Received: by 10.204.224.11 with HTTP; Fri, 2 Dec 2011 05:55:51 -0800 (PST) In-Reply-To: References: <20111126154114.GC27177@gonzales> <20111126182915.GC15113@gonzales> <20111126214806.GB19833@gonzales> <20111129030444.GA26300@gonzales> <20111129225808.GA19818@gonzales> <20111201021703.GL2886@gonzales> Date: Fri, 2 Dec 2011 08:55:51 -0500 Message-ID: Subject: Re: [lojban] semantic parser - tersmu-0.1rc1 From: Michael Turniansky To: lojban@googlegroups.com X-Original-Sender: mturniansky@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mturniansky@gmail.com designates 209.85.214.54 as permitted sender) smtp.mail=mturniansky@gmail.com; dkim=pass (test mode) header.i=@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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=0015175d0796b8581f04b31c53e5 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --0015175d0796b8581f04b31c53e5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2011/12/1 Jorge Llamb=EDas > On Wed, Nov 30, 2011 at 11:17 PM, Martin Bays wrote: > > > I'm not seeing any solutions other than either (a) choosing one of (i) > > and (ii), and declaring the other disallowed; (b) just accepting this a= s > > an ugly exception to the wide "scope" of description sumti. > > > > I don't like either of these. > > > > Any better ideas? > > Define better where the quantifier that binds a variable implicitly > goes. Is "da" just equivalent to "su'o da" in the same position where > it first occurs (in which case the scope of "su'o" is determined by > this position only) or is "da" bound by a quantifier with scope wide > enough to encompass all following occurrences of "da" (in which case > it may not be equivalent to "su'o da" in the same position)? The two > criteria give the same results for very simple cases, but different > results for slightly more complicated ones. I don't think anyone ever > bothered to define a proper rule for this. > > My personal opinion is that, in the absence of an explicit prenex, "da" should probably be considered "su'oda" and the scope of that definition of da is all physcially following bridi in that sentence that are on the same level or below (including bridi tails, if it was used in the main bridi), and (if used in the main bridi) all subsequent sentences that are linked by an .i{X}bo.... but I am probably wrong. --gejyspa --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den. --0015175d0796b8581f04b31c53e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


2011/12/1 Jorge Llamb=EDas <= ;jjllambias@gmail.com>
On Wed, Nov 30, 2011 at 11:17 PM, Martin Bays <mbays@sdf.org> wrote:

> I'm = not seeing any solutions other than either (a) choosing one of (i)
> = and (ii), and declaring the other disallowed; (b) just accepting this as > an ugly exception to the wide "scope" of description sumti.<= br>>
> I don't like either of these.
>
> Any bette= r ideas?

Define better where the quantifier that binds a varia= ble implicitly
goes. Is "da" just equivalent to "su'o da" in the s= ame position where
it first occurs (in which case the scope of "su&= #39;o" is determined by
this position only) or is "da" bo= und by a quantifier with scope wide
enough to encompass all following occurrences of "da" (in which c= ase
it may not be equivalent to "su'o da" in the same posi= tion)? The two
criteria give the same results for very simple cases, but= different
results for slightly more complicated ones. I don't think anyone everbothered to define a proper rule for this.
=A0
=A0 My personal opinion is that, in the absence of an explicit=A0prene= x, "da" should probably be considered "su'oda" and = the scope of that definition of da is all physcially following =A0bridi in = that sentence=A0that are on the same level or below (including bridi=A0tail= s, if it was used=A0in the main bridi), and (if used in the main bridi) all= subsequent sentences that are linked by an .i{X}bo.... but I am probably w= rong.
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 --gejyspa
=A0

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--0015175d0796b8581f04b31c53e5--