Received: from mail-pz0-f61.google.com ([209.85.210.61]:49898)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCOTEtqyUDhCxkur2BBoEswc1zw@googlegroups.com>)
	id 1RWwNn-0001Uk-D3; Sat, 03 Dec 2011 12:40:32 -0800
Received: by dajx4 with SMTP id x4sf2831954daj.16
        for <multiple recipients>; Sat, 03 Dec 2011 12:40:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=beta;
        h=x-beenthere:received-spf:date:from:to:subject:message-id:references
         :mime-version:content-type:content-disposition:in-reply-to:x-pgp-key
         :x-pgp-keyid:x-cunselcu'a-valsi:user-agent: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;
        bh=6GqZrftd64AGd6L9AWTwFUOvCwu5DN1TCACu/M5DUZI=;
        b=OQRmbVvZrrBw+9d7Eeq5yu8XuBRJyKMmbl5TlP1Z638Xh2po99ESVs7yAyPPBeA/3T
         r+3r6KLyCu0eRYc/FRHt1k/x+f9zpaRjUZ+c31fY9QJz9YZ1d1QduIZl6Z4qj91FFh1U
         NFmWS+RDItqk7aGsFqd0AXGMOQ84eWkBmeRrM=
Received: by 10.68.38.200 with SMTP id i8mr1826749pbk.13.1322944817291;
        Sat, 03 Dec 2011 12:40:17 -0800 (PST)
X-BeenThere: lojban@googlegroups.com
Received: by 10.68.121.5 with SMTP id lg5ls19321376pbb.5.gmail; Sat, 03 Dec
 2011 12:40:16 -0800 (PST)
Received: by 10.68.31.165 with SMTP id b5mr12091486pbi.1.1322944816813;
        Sat, 03 Dec 2011 12:40:16 -0800 (PST)
Received: by 10.68.31.165 with SMTP id b5mr12091484pbi.1.1322944816806;
        Sat, 03 Dec 2011 12:40:16 -0800 (PST)
Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19])
        by gmr-mx.google.com with ESMTPS id j5si6742009pbi.0.2011.12.03.12.40.16
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sat, 03 Dec 2011 12:40:16 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of mbays@sdf.org designates 192.94.73.19 as permitted sender) client-ip=192.94.73.19;
Received: from gonzales.homelinux.org (root@sverige.freeshell.org [192.94.73.4])
	by sdf.lonestar.org (8.14.5/8.14.3) with ESMTP id pB3KeFqh020455
	for <lojban@googlegroups.com>; Sat, 3 Dec 2011 20:40:16 GMT
Received: from martin by gonzales.homelinux.org with local (Exim 4.75)
	(envelope-from <mbays@sdf.org>)
	id 1RWwNb-0001N3-QW
	for lojban@googlegroups.com; Sat, 03 Dec 2011 15:40:15 -0500
Date: Sat, 3 Dec 2011 15:40:15 -0500
From: Martin Bays <mbays@sdf.org>
To: lojban@googlegroups.com
Subject: Re: [lojban] semantic parser - tersmu-0.1rc1
Message-ID: <20111203204015.GA11790@gonzales>
References: <CAO7tK2fSavtz6QA1dJB0Nh7ZWC9_ucLMWdkC4Kzk2aQK9xpVrQ@mail.gmail.com>
 <20111126214806.GB19833@gonzales>
 <CAO7tK2cu1S5eGm9F21kDd6rN548CXdPqeTwEU5X4tD=OjctEfA@mail.gmail.com>
 <20111129030444.GA26300@gonzales>
 <CAO7tK2f3vj9sesm1XEOm4KArdxuKgAT84Whpn-D4HiaTFQXPWQ@mail.gmail.com>
 <20111129225808.GA19818@gonzales>
 <20111201021703.GL2886@gonzales>
 <CAO7tK2fH0ACodKJe7Hhwi8t_ivjiANg7d5cqEukudq6fRTZJXQ@mail.gmail.com>
 <20111203175028.GC12482@gonzales>
 <CAO7tK2eDAX-HZMubt9k5coxY=AjnxbQj67t8-2TF-sTcsnrtug@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW"
Content-Disposition: inline
In-Reply-To: <CAO7tK2eDAX-HZMubt9k5coxY=AjnxbQj67t8-2TF-sTcsnrtug@mail.gmail.com>
X-PGP-Key: http://mbays.freeshell.org/pubkey.asc
X-PGP-KeyId: B5FB2CD6
X-cunselcu'a-valsi: sirxo
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Original-Sender: mbays@sdf.org
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 best guess record for domain of mbays@sdf.org designates 192.94.73.19 as
 permitted sender) 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: <lojban.googlegroups.com>
X-Google-Group-Id: 1004133512417
List-Post: <http://groups.google.com/group/lojban/post?hl=en_US>, <mailto:lojban@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:lojban+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/lojban?hl=en_US>
Sender: lojban@googlegroups.com
List-Subscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:lojban+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:lojban+unsubscribe@googlegroups.com>
X-Spam-Score: -0.7 (/)
X-Spam_score: -0.7
X-Spam_score_int: -6
X-Spam_bar: /


--0F1p//8PRICkK4MW
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Saturday, 2011-12-03 at 15:51 -0300 - Jorge Llamb=EDas <jjllambias@gmail.=
com>:

> On Sat, Dec 3, 2011 at 2:50 PM, Martin Bays <mbays@sdf.org> wrote:
> > * Thursday, 2011-12-01 at 18:53 -0300 - Jorge Llamb=EDas <jjllambias@gm=
ail.com>:
> >> On Wed, Nov 30, 2011 at 11:17 PM, Martin Bays <mbays@sdf.org> wrote:
> >> > Meanwhile,
> >> > (ii) if {da} is already quantified, then {lo broda be da} is interpr=
eted
> >> > =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.
> >
> > Thinking about it, I'm no longer so convinced that this is important.
> >
> > I can't think of nor find any examples of uses of {lo broda be da} where
> > the itended meaning wouldn't be given more clearly by using {ro} or
> > {piro}/{ro'oi}, or occasionally some other quantifier.
>=20
> What about things like: "ro da poi verba cu prami lo mamta be da"?

Ah, you mean because {ro mamta be da} would get everything which is
motherly towards {da}, when we might want to specifically mean the
biological mother but not want to waste a couple of syllables by making
it {ro rorci mamta be da}?

I suppose that is an example. Although the complication in semantics
involved seems rather large compared to this two-syllable saving...
generally, those situations in which it's reasonable to leave the nature
of a function to pragmatics seem to coincide with those in which it's
easy to actually express it. But maybe it seems that way only because
the examples I'm considering are too simple.

> > It would certainly be conceptually neater to do away with this "Skolem
> > function" possibility for description sumti - declare them to be
> > *literally* constants, with any {da} in the description assumed not to
> > be bound outside, and any anaphora to exterior variables (or connected
> > terms) considered erroneous.
> >
> > See any compelling arguments against that?
>=20
> I don't really see a problem with functions. (I don't think they are
> Skolem functions though, just the usual functions of first order
> logic.)

Yes, I'm not sure why I'm still calling them Skolem functions! It's
a relic from my previous (mis)understanding that there was some actual
quantification going on somewhere, rather than pure pragmatics.

> >> 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
> >
> > Hmm. I have it as
> >
> > (3) ge su'o da zo'u da da broda gi su'o da zo'u ko'a da broda
> >
> > , i.e. handling the two arms of the connective separately. This
> > algorithm seems most natural to me. Do you dislike this possibility for
> > some reason other than the {lo broda be da} issue?
>=20
> I find it weird that for one conjunct the second "da" is the same
> variable as the first "da", and for the other conjunct it's a
> different variable.

Yes; it's the algorithm I find natural, not the results!

> As I said, I don't think bridi connected with eks share words.

I wouldn't think of it as sharing words. They share the interpretation
of the term {da} - but that's just a variable.

> > (1) seems reasonable. It looks like it could be implemented (in all
> > cases) by having the binding of a {da} in a connectand to the bound
> > variable it creates survive only within the connectand. I think I might
> > like it.
>=20
> That's what makes sense to me, but of course it goes against CLL.

Really? Explicitly?

> >> 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)?
> >
> > Interesting idea. This is how you derive (2)?
>=20
> That's the only way I can make sense of CLL's rule for implicit
> quantifiers jumping out of their "natural" scope.
>=20
> > But having such a preprocessing step before scope can be decided
> > - meaning that in speech, the scope of a heard {da} can't be determined
> > until the statement is finished - strikes me as something to be avoided
> > if possible.
>=20
> How else can you process CLL's implicit quantifiers having scope over
> several bridi?

I'm not sure what you're getting at here. As I read CLL, the first {da}
in a statement/subsentence is "exported" to the prenex, creating
a generalised quantifier corresponding to the quantifier on the {da}, or
an existential quantifier if it's a bare {da}. It has scope over the
whole statement/subsentence, within the scope of any previous
quantifiers/connectives/tags.

Martin

--0F1p//8PRICkK4MW
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk7aiS8ACgkQULC7OLX7LNawSwCgsFclrOBwJg2gufErd1eYGD7w
PfkAni5V7dj4bU20nKuPEWTbYqOEDdYB
=WmgK
-----END PGP SIGNATURE-----

--0F1p//8PRICkK4MW--