Received: from mail-pz0-f56.google.com ([209.85.210.56]:56295)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCOTEtqyUDhCagsT2BBoEZ0wt9g@googlegroups.com>)
	id 1RUJsZ-0005oA-7c; Sat, 26 Nov 2011 07:09:39 -0800
Received: by pzk6 with SMTP id 6sf1479014pzk.1
        for <multiple recipients>; Sat, 26 Nov 2011 07:09:16 -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=5kxkifkhszRs12KuFffgdcQKHUlY47bgrI/rbSVbzcg=;
        b=YXeDWvm/B+nic2eQCYpyr1p4qr7jjp5iE88DHYxOoJJurh6JhVcmPLygO9Q4SMyit+
         KXHIGIhIwpqDk0wC0h2tds9abzpZMxbtB/Kla4kSXR0RZ9W4UsUOZuIbBhjnEuNiWlaf
         Tk+nSU7tT5watevD6fW/sT9sqUIx0oEGV87/g=
Received: by 10.68.1.66 with SMTP id 2mr1696649pbk.15.1322320154446;
        Sat, 26 Nov 2011 07:09:14 -0800 (PST)
X-BeenThere: lojban@googlegroups.com
Received: by 10.68.74.199 with SMTP id w7ls4398413pbv.7.gmail; Sat, 26 Nov
 2011 07:09:13 -0800 (PST)
Received: by 10.68.35.68 with SMTP id f4mr15729834pbj.5.1322320153702;
        Sat, 26 Nov 2011 07:09:13 -0800 (PST)
Received: by 10.68.35.68 with SMTP id f4mr15729833pbj.5.1322320153693;
        Sat, 26 Nov 2011 07:09:13 -0800 (PST)
Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19])
        by gmr-mx.google.com with ESMTPS id j5si6582956pbi.0.2011.11.26.07.09.13
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sat, 26 Nov 2011 07:09:13 -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 pAQF9CRv006465
	for <lojban@googlegroups.com>; Sat, 26 Nov 2011 15:09:13 GMT
Received: from martin by gonzales.homelinux.org with local (Exim 4.75)
	(envelope-from <mbays@sdf.org>)
	id 1RUJsO-0007gF-PW
	for lojban@googlegroups.com; Sat, 26 Nov 2011 10:09:12 -0500
Date: Sat, 26 Nov 2011 10:09:12 -0500
From: Martin Bays <mbays@sdf.org>
To: lojban@googlegroups.com
Subject: Re: [lojban] semantic parser - tersmu-0.1rc1
Message-ID: <20111126150912.GB27177@gonzales>
References: <20111124044118.GF6112@gonzales>
 <CAO7tK2cfhJtrvLX1S6Mga_CJU2nLyt96_4DR=ygJksH3ixaamg@mail.gmail.com>
 <20111125195038.GA29512@gonzales>
 <CAO7tK2ezxrDKHEDQx1k7O1+E_FsviPXYOK=R8aU3xVy2C4kb6g@mail.gmail.com>
 <20111126012512.GA6702@gonzales>
 <CAO7tK2euHY7snwkb2L68spGHYpX=mAiVXYYjXs0Aws+3=JZdEQ@mail.gmail.com>
 <20111126040757.GA17974@gonzales>
 <CAO7tK2dJc8y14v8iVZ-3Y7WxW55JJ5-qv4f841aVy=AmxnqJ-w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="eAbsdosE1cNLO4uF"
Content-Disposition: inline
In-Reply-To: <CAO7tK2dJc8y14v8iVZ-3Y7WxW55JJ5-qv4f841aVy=AmxnqJ-w@mail.gmail.com>
X-PGP-Key: http://mbays.freeshell.org/pubkey.asc
X-PGP-KeyId: B5FB2CD6
X-cunselcu'a-valsi: lujvo
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.0 (/)
X-Spam_score: -0.0
X-Spam_score_int: 0
X-Spam_bar: /


--eAbsdosE1cNLO4uF
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Saturday, 2011-11-26 at 10:52 -0300 - Jorge Llamb=EDas <jjllambias@gmail.=
com>:

> On Sat, Nov 26, 2011 at 1:07 AM, Martin Bays <mbays@sdf.org> wrote:
> > It seems related to donkey anaphora -  consider
> > {ro te cange poi ponse su'o xasli noi ke'a xi re darxi cu broda}.
>=20
> Right, it's the same thing. The grammar allows both ke'a and ri to see
> as its antecedent something that in principle it should have no
> business seeing as its antecedent, and so we have to cope somehow.

Well... in the case of true donkey anaphora, I think I'll be happiest
declaring them semantically anomalous.

(I don't consider something like {la alis goi ko'a cu nixli .i ko'a
fanza} to be a true donkey anaphora, although it has the grammatical
form of one and therefore is not handled by my current code)

> > Also, note that the scope-respecting rules sometimes are the most
> > intuitive - e.g. in {ro da prami de noi se prami da}. I'm not sure what
> > the scope-breaking rules would make of that; I guess something
> > nonsensical.
>=20
> In principle as nonsensical as "no da prami de noi se prami da".
>=20
> But what you call scope-respecting rules are the rules for "poi", not "no=
i".

Yes, in the case of an existential quantifier I am making no distinction.

> >> I think it's "broda be na ku" that must force tight scope.
> >
> > I don't see why.
>=20
> Mainly because that's what the sytntax suggests. It's when we go
> against the syntax that we end up with problem cases.

How can the syntax be suggesting that linkargs but not selbri tags get
tighter scope than tailterms?

> > But in {broda da gi'e brode da}, the first {da} is to the left of the
> > {gi'e}. So why shouldn't the {gi'e} be in the scope of the {[su'o] da}?
>=20
> Because "gi'e" connects two bridi-tails, and so each bridi-tail is
> subordinate to it. It's for the same reason that in "na broda gi'e na
> brode" the first "na" is in the scope of "gi'e" and not the other way
> around.

I agree; my point was only that the scope rules don't always respect
textual order, which you were appealing to.

> > So do you also have {da broda .i je da brode} -> {ge da broda gi da
> > brode}? If so: that's clearly contrary to CLL (and much usage).
>=20
> Yes, as I said, that's what I would have. I find the CLL rule somewhat
> strange.

OK. Then I'm not worried that we disagree on this.

I intend to stick with the CLL as far as coherence allows for the first
pass.

I hope that having rigorously implemented semantics for one form of
lojban will make it easier to develop alternatives.

> >> >> =A0 ko'a .e ko'e broda su'o da
> >>
> >> How does that work for ".e"? It seems that if you do what I do, you
> >> end up exporting "su'o da" to newly created preneces.
> >
> > In a sense, yes; e.g.
> >
> > da ko'a .e ko'e de broda
> > Prop: EX x1. (EX x2. broda(x1,ko'a,x2) /\ EX x2. broda(x1,ko'e,x2))
> >
> > ; but I think of this as exporting the connective to the prenex, and
> > then the inner existential to that same prenex within the scope of the
> > connective.
>=20
> Same with "gi'e".

I understand.

If it helps: my code is such that switching to your preferred gihek and
ijek handling is easy to do.

> Presumably in "su'o da .e su'o de" you have the first "su'o" within
> the scope of ".e", yes?

Yes, certainly. And I have that being equivalent to {da .e da} (which
may be more controversial, but I think must be right).

> > Basically: when parsing, we always have a notion of 'current prenex',
> > which corresponds to the closest instance of 'statement' or
> > 'subsentence' we're below. All sumti connectives, termset connectives,
> > quantifiers and tagged terms (currently just {naku}) export to that
> > prenex, in order.
>=20
> Yes, but I'm just parsing gi'e, na and selbri tags before tail terms
> rather than leaving them for last. That's what the syntax suggests,
> and I just don't see the advantage of doing otherwise.

For giheks and ijeks, an argument might be that they are afterthought
connectives, so should be usable in situations where you had not
considered when starting the sentence that you were going to want to add
the connective. If you introduce a quantifier (or sumti connective)
during the first connectant, you may want it to scope over the second
connectant - and since you hadn't planned on expressing the second
connectant at all, you won't have had the foresight to put the
quantifier in a prenex.

As for having {na broda da} work differently from {na ku broda da}...
one argument would simply be that it allows you to efficiently get at
meanings which would otherwise be complicated to express. e.g. suppose
we want to add negations to modify
{broda da gi'e brode vau de}
to have the first conjunct be
EX x1. EX x2. !broda( ,x1,x2) .

With your {na} rule, it seems you would have to make it
{broda da gi'e nai brode vau de na ku} .
With mine, it's just
{na broda da gi'e brode vau de} .


Another argument would involve your agreeing with me that

broda je brode da
Prop: EX x1. (broda( ,x1) /\ brode( ,x1))

is correct... do you?

Martin

--eAbsdosE1cNLO4uF
Content-Type: application/pgp-signature

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

iEYEARECAAYFAk7RARgACgkQULC7OLX7LNaYvQCdEqBwCPnQXAQLHKoY1WkgaitY
puIAoKju5zqcNhl/vVH+hwwYiD9SmDZR
=6RbD
-----END PGP SIGNATURE-----

--eAbsdosE1cNLO4uF--