Received: from mail-bw0-f61.google.com ([209.85.214.61]:48752) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RZOls-0000yj-AC; Sat, 10 Dec 2011 07:23:32 -0800 Received: by bkat2 with SMTP id t2sf8399376bka.16 for ; Sat, 10 Dec 2011 07:23:20 -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=XqOraIBwGY6Bnmic34wGZXdSDSPWu1n5I2vtJAL4Sik=; b=L3XuFMuDmNpnmveQRKAU+qWRSUjS4zUeKt7cXYGbpd+FROCWL+wwspw+bJxENOmmns ObGQHm6PlsyMVBhHbas3Fm45rRB9CA8kt13+HvfgdO5MGIOIGafBFRi2EQqjy2ZEkYVl bLT3FmEgHt+Ig1+v+qmS7pA8JKlW/4Ce9poso= Received: by 10.204.152.143 with SMTP id g15mr1594148bkw.10.1323530598086; Sat, 10 Dec 2011 07:23:18 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.204.130.207 with SMTP id u15ls11909846bks.0.gmail; Sat, 10 Dec 2011 07:23:17 -0800 (PST) Received: by 10.205.132.133 with SMTP id hu5mr820379bkc.4.1323530596986; Sat, 10 Dec 2011 07:23:16 -0800 (PST) Received: by 10.205.132.133 with SMTP id hu5mr820378bkc.4.1323530596969; Sat, 10 Dec 2011 07:23:16 -0800 (PST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by gmr-mx.google.com with ESMTPS id c11si6849747bke.3.2011.12.10.07.23.16 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Dec 2011 07:23:16 -0800 (PST) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.215.44 as permitted sender) client-ip=209.85.215.44; Received: by laah2 with SMTP id h2so1160533laa.17 for ; Sat, 10 Dec 2011 07:23:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.134.10 with SMTP id pg10mr7698470lab.3.1323530596609; Sat, 10 Dec 2011 07:23:16 -0800 (PST) Received: by 10.152.19.198 with HTTP; Sat, 10 Dec 2011 07:23:16 -0800 (PST) In-Reply-To: <857BF1E4-628A-4E05-BC02-A90D15C6895E@yahoo.com> References: <1323373742.18817.YahooMailRC@web81306.mail.mud.yahoo.com> <857BF1E4-628A-4E05-BC02-A90D15C6895E@yahoo.com> Date: Sat, 10 Dec 2011 12:23:16 -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.44 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 Fri, Dec 9, 2011 at 2:07 PM, John E. Clifford wro= te: > On Dec 9, 2011, at 9:24 AM, Jorge Llamb=EDas wrote= : >> On Thu, Dec 8, 2011 at 8:39 PM, John E. Clifford = wrote: >> >>> Except that quantifiers, unlike negations, introduce references to thin= gs. >> >> In the sense that they need a domain of quantification? Yes. And the >> domain of quantification should be maintained for quantifier "terms" >> that are shared by eks or giheks. > > Not domain, instances are the problem. Quantifiers do not introduce any reference to instances. That's just not what quantifiers do. Quantifiers don't refer. They count. And when a "quantifier term" is shared by two branches of a conjunction, the count must of course be the same for each branch, and the domain must of course be the same for each branch, but that's all. That's just like when a quantifier is under the scope of another. "ro da su'o de" is not much different from "(... .e ... .e ... .e ...) su'o de", and not much different from "ro da (... .a ... .a ... .a ...)" and not much different from "(... .e ... .e ... .e ...) (... .a ... .a ... .a ...)". (Of course there are important differences, such as the connective form requiring individual names for each member of the domain, or the quantifier form allowing for an indefinite number of members in the domain. But these differences don't affect the issue at hand, which is what has scope over what.) Quantifiers don't refer. Quantifiers count. I don't know why this point needs to be made over and over again. > Well, of course, I don't think donkey sentences are problems; we know exa= ctly how to handle them and always have. =A0they do present problems for ru= les of your sort which try to take items one at a time and in order, rather= than a more global (at least context-sensitive) approach. =A0As soon as yo= u assign a {su'o} to all "floating" variables, you have eliminated the poss= ibility of donkey sentences, which may or may not cripple your results, but= seems rather arbitrary, given how natural languages work. I don't agree donkey anaphora are to be equated with implicitly bound variables. In any case, I refuse to discuss donkey anaphora before we settle the (in my opinion trivial) issue of the expansion of eks and giheks, and the movement of "quantifier terms" and "negation terms" to the prenex in the first place, and the (not so trivial but still realtively easy) issue of implicitly bound variables. Trying to discuss donkey anaphora without those two prior issues settled is in my opinion pointless. > Again, this is a theoretical ( even aesthetic) comment. =A0The needs of a= speakable language override logical clarity. =A0If the crude rules always = give the right results, what's the problem? Even a little braggadocio does = no harm. =A0But a bit of concern with justifying the rules by something oth= er than their results wouldn't hurt either. The unpacking rules I propose are not based on their results, although of course their giving the desired result is obviously a plus. The rules are based on the observation that quantifiers and connectives are ultimately at some level the same kind of logical construct, and should therefore be treated basically in the same way. (I just said I wouldn't discuss donkey anaphora before settling eks and giheks, but I can't refrain from pointing out that donkey anaphora can turn up with connectives as easily as they do with quantifiers, as in for example: "Everyone who loves either Mary or Jane wants to marry her.") 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.