Received: from mail-bw0-f61.google.com ([209.85.214.61]:46280) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RWEZY-0000Ey-6j; Thu, 01 Dec 2011 13:53:47 -0800 Received: by bkbzt19 with SMTP id zt19sf2280653bkb.16 for ; Thu, 01 Dec 2011 13:53:32 -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 :content-transfer-encoding; bh=gzp3ESDkqMQI+mSxeDwipDHkVyW0u8PVuaSHlZKbH7s=; b=CWxs056eBo+59avefjEV2/qowNVoIptNsqnCDxfZLJ1mZ3vMVU5FDB/DKyfXREgm8o 6UYgzIbaDJcAS61ttyTKKUx6TujRNPXWvAmsDKH3nzVgTV9PWNiy+lHuq3yQ4R/syALo 3jA82mHxlBOCNJmBn06VVzFt1YOXl7L4GbUEE= Received: by 10.204.157.19 with SMTP id z19mr1025789bkw.24.1322776409925; Thu, 01 Dec 2011 13:53:29 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.204.152.154 with SMTP id g26ls18460987bkw.3.gmail; Thu, 01 Dec 2011 13:53:29 -0800 (PST) Received: by 10.205.138.133 with SMTP id is5mr666677bkc.0.1322776408881; Thu, 01 Dec 2011 13:53:28 -0800 (PST) Received: by 10.205.138.133 with SMTP id is5mr666676bkc.0.1322776408867; Thu, 01 Dec 2011 13:53:28 -0800 (PST) Received: from mail-lpp01m010-f41.google.com (mail-lpp01m010-f41.google.com [209.85.215.41]) by gmr-mx.google.com with ESMTPS id w8si5274655bkd.0.2011.12.01.13.53.28 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 13:53:28 -0800 (PST) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.215.41 as permitted sender) client-ip=209.85.215.41; Received: by lahi5 with SMTP id i5so1172473lah.0 for ; Thu, 01 Dec 2011 13:53:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.102.138 with SMTP id fo10mr6096597lab.44.1322776408479; Thu, 01 Dec 2011 13:53:28 -0800 (PST) Received: by 10.152.19.198 with HTTP; Thu, 1 Dec 2011 13:53:28 -0800 (PST) In-Reply-To: <20111201021703.GL2886@gonzales> References: <20111126154114.GC27177@gonzales> <20111126182915.GC15113@gonzales> <20111126214806.GB19833@gonzales> <20111129030444.GA26300@gonzales> <20111129225808.GA19818@gonzales> <20111201021703.GL2886@gonzales> Date: Thu, 1 Dec 2011 18:53:28 -0300 Message-ID: Subject: Re: [lojban] semantic parser - tersmu-0.1rc1 From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 209.85.215.41 as permitted sender) smtp.mail=jjllambias@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: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / On Wed, Nov 30, 2011 at 11:17 PM, Martin Bays wrote: > > Actually, there's an issue here, and I'm not sure how to resolve it. This is why I avoid relying on implicit quantifiers. > I think we agreed that > (i) if {lo broda be da} occurs not in the scope of a quantification of > =A0 =A0{da}, the resulting existential quantifier has scope only within t= he > =A0 =A0lo-phrase - i.e., referents are claimed to satisfy > =A0 =A0EX x. broda(_,x) . That's how I would deal with "lo broda be su'o da". > Meanwhile, > (ii) if {da} is already quantified, then {lo broda be da} is interpreted > =A0 =A0as a skolem function. If da is bound by a quantifier and "lo broda be da" occurs within the scope of the quantifier, yes. > But then how to handle > {ge broda da gi brode vau lo brodi be da} ? The two options seem to be: (1) ge broda su'o da gi brode vau lo brodi be su'o de (2) su'o da zo'u ge broda da gi brode vau lo brodi be da I would personally choose (1), but I'm sure someone will want to argue for = (2). > The same problem occurs with {da .e ko'a lo broda be da}, if my > understanding of the interaction between sumti connectives and > quantifiers is correct. Right, again it's one of: (1) su'o da .e ko'a lo broda be su'o de (cu brode) (2) su'o da zo'u da .e ko'a lo broda be da (cu brode) But I don't think you need to bring "lo" into this. We already have the same issue with "ge da gi ko'a da broda", which could be either of: (1) ge su'o da su'o de zo'u da de broda gi su'o de zo'u ko'a de broda (2) su'o da zo'u ge da da broda gi ko'a da broda > 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. > > 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. mu'o mi'e xorxes --=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.