Received: from mail-vc0-f190.google.com ([209.85.220.190]:42350) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XPfUl-0001x7-2k for lojban-list-archive@lojban.org; Thu, 04 Sep 2014 15:27:11 -0700 Received: by mail-vc0-f190.google.com with SMTP id im17sf2164258vcb.17 for ; Thu, 04 Sep 2014 15:27:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=+hz5heTdQw3EX2Z1YuLwNtwQKLDUzPunmXrw4QFu1E8=; b=mQ/1VA8NJVu/kHfCYxsNS/Wl7C3EwLUlBmQb2OL/BA8Ft3bZX4Bd+PXCAKxCYqMAn/ bNRO6MGQ7yjcVlwxNXO/b4AtaVFb4NfpwISVej/Qa3xXaZzshWldUIJKiKPik5FwU4NZ rmnN22LLfcEQpd6Svus0qd6tfmQhUeI2EcCuV8WeHAZHke0DwYe1NKmWfDcwx55i/Rvz R8gGCtbhcyPV6WOKX4LlrMIUNuOkq/Qa4wfTYYIjNRiZfdoTQOH+1mABLD98on8ax0am 5Vl46g36deMfSEqL71WwZSKl5BB5gU2H0R67qgcTSeenvryf4wInGqmU6R9oxT1j37mZ J4jQ== X-Received: by 10.50.77.51 with SMTP id p19mr142452igw.17.1409869624220; Thu, 04 Sep 2014 15:27:04 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.57.8 with SMTP id e8ls4082199igq.15.canary; Thu, 04 Sep 2014 15:27:03 -0700 (PDT) X-Received: by 10.42.90.209 with SMTP id l17mr2971372icm.34.1409869623971; Thu, 04 Sep 2014 15:27:03 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id pk7si47294pbc.2.2014.09.04.15.27.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Sep 2014 15:27:03 -0700 (PDT) Received-SPF: none (google.com: mbays@sdf.org does not designate permitted sender hosts) client-ip=192.94.73.24; Received: from thegonz.net (d24-141-9-29.home.cgocable.net [24.141.9.29]) (authenticated (0 bits)) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s84MQmSE028885 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Thu, 4 Sep 2014 22:26:50 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XPfUG-0000Cq-NB for lojban@googlegroups.com; Thu, 04 Sep 2014 18:26:40 -0400 Date: Thu, 4 Sep 2014 18:26:40 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] unquantified sumti with restrictive relative clauses in xorlo Message-ID: <20140904222640.GD29601@gonzales> References: <20140904043953.GA29601@gonzales> <54083D4C.5000809@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mSxgbZZZvrAyzONB" Content-Disposition: inline In-Reply-To: <54083D4C.5000809@gmx.de> X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: ku'a User-Agent: Mutt/1.5.22 (2013-10-16) X-Original-Sender: mbays@sdf.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: mbays@sdf.org does not designate permitted sender hosts) 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: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Note: SpamAssassin invocation failed --mSxgbZZZvrAyzONB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Thursday, 2014-09-04 at 12:22 +0200 - selpa'i : > la'o me. Martin Bays .me cusku > > Recall the following production: > > > > sumti5 <- quantifier? sumti6 [relative-clauses] > > > > I want to understand the semantics of this in the case that there is no > > quantifier, and there is a restrictive clause among the relative clause= s. > > {ko'a poi broda}, in other words. > > [...] > > I can see six broad approaches to interpreting such expressions, i.e. t= hose of > > the form {ko'a poi broda}. > > > > (i) Consider it an error, or just ignore any restrictives. >=20 > I don't like this option, because it would be an exception. I believe=20 > {poi} can be defined in such a way that the same rule handles both=20 > quantified and unquantified sumti. >=20 > > (ii) Declare that in this case (and this case alone), there is an impli= cit > > quantifier after all. >=20 > This is certainly how if feels at times, but it's probably not necessary= =20 > for it to actually be the case at a formal level. >=20 > By the way, the case of {lo broda poi brode ku'o ku} needs to be looked= =20 > at as well. An outer quantifier wouldn't affect the {poi} clause here,=20 > but it still needs to be defined what it means and how it differs from=20 > {noi}. Yes, true. Relatedly: any option other than (i) or (ii) or (iv) has a limitation: if {ko'a poi broda} is a referring expression in itself, one might expect {ro ko'a poi broda} to mean (1) {ro da poi me ko'a poi broda}, but instead we have a separate rule which makes it (2) {ro da poi me ko'a gi'e broda}, and (1) and (2) agree only in case (iv). They almost agree in case (v), and I'm tempted to amend case (v) to have it give {ro ko'a poi broda} meaning (1) rather than meaning (2). > > (iii) Have it pick out some referents such that they satisfy the restri= ctives: > > ko'a poi broda -> zo'e noi me ko'a gi'e broda >=20 > This is pretty much my take on it. I like the general definition of {poi= =20 > broda} =3D=3D {je poi'i* broda} because it works in all cases, both with= =20 > sumti and with selbri, and it doesn't matter if there are quantifiers=20 > present. (it is equivalent to your definition, but works better in real= =20 > life as an afterthought, not that that's very relevant here) Yes, this is definitely attractive in its simplicity. It's much looser than restrictive relatives in english, though; if I point at some assorted fruit and say {ti poi plise}, with (iii) there's no reason to think that I'm referring to all the apples rather than only one. > > (iv) Have it pick out those referents which each satisfy broda: > > ko'a poi broda -> > > zo'e noi ro da zo'u go da me ke'a go ge da me ko'a gi broda >=20 > I think this doesn't fit with the current system where the argument=20 > places of predicates aren't defined as distributive or collective Agreed. > (they should be in my opinion). >=20 > If you want distributive satisfaction, {ko'a poi ro ke'a broda} works. Almost - but assuming we work with (iii), that doesn't get the idea that *every* individual among ko'a which satisfies broda is a referent of ko'a poi broda, as (iv) states. > > (v) Something along the lines of (iv), but more in line with plural log= ic / > > mereology, perhaps by requiring the obvious maximality condition, = i.e. > > ko'a poi broda -> > > zo'e noi ge ge me ko'a gi broda gi ro da poi ge ge ke'a xi re = me ke'a gi > > ke'a me ko'a gi ke'a broda cu du ke'a > > , perhaps making it an error if there is no unique such maximum, or > > perhaps taking all the maxima together (i.e. taking the join). >=20 > This is also a bit too specific, like (iv). >=20 > > (vi) Something along the lines of (v), but with no formal rule - just a= n idea > > that the intended referents of {ko'a poi broda} are picked out amo= ng the > > referents of {ko'a} by virtue of their brodaing. >=20 > Isn't this similar to (iii) as well? Not the way I meant it. I meant it as a translation of the english "those of ko'a which broda" - which is rather more specific than (iii), which is more like "some of ko'a, that broda,". (v) was also an attempt at translating that english phrase. This just reminded me of [Chierchia98]; using his notation, (v) (with error when there's no unique maximum) can be expressed: {ko'a poi broda} -> \iota { x | x <=3D ko'a /\ broda(x) }. It seems a reasonable translation of english restricted relatives. I just had a quick look at some semantics papers, and I have the impression that this is indeed a standard way to handle them - but I'm not confident I'm reading the literature right. > > The usage I've seen could fit any of (iii)-(vi), I think. So, taking va= rious > > degrees of liberty, could CLL's use of restrictives - although of cours= e they > > had implicit quantifiers, so are not really relevant. >=20 > There is definitely a lot of contrasting usage between {ko'a poi} and=20 > {ko'a noi}, with meaningful distinctions being felt by the speakers.=20 > That, and the fact that I think the general definition of {poi} in terms= =20 > of {je} (or gi'e) works made me believe that something like (iii) is the= =20 > most practical solution. >=20 > We could try to write up a table of all the cases: >=20 > [snip] >=20 > lo broda poi brode > lo broda je poi'i broda / zo'e noi broda gi'e brode >=20 > [snip] > > So a lot of these are equivalent as long as no quantifier is added, but= =20 > they all use the same expansions which work whether or not there is a=20 > quantifier (or so I hope, let's look for mistakes!). They look reasonable to me. Taking {lo broda poi brode} to be have the same referents as {lo broda ku poi brode} would also be an option. > PA broda noi brode > PA da (to ri broda toi) poi ke'a broda >=20 > Some of this depends on {ri}'s ability to repeat {da} and quantified=20 > terms. Writing {PA da (to da broda toi)} would be weird, as the {da}=20 > could just as well be a new variable. Yeah, I don't think that's really legitimate. Pretending that {ri} can pick up the {da} at all (and actually I believe it just skips over it to the previous sumti), I'd say the bracketed phrase there has an unbound ("donkey") variable, and we should either consider it an error or universally quantify it out to give {PA broda noi brode} -> {PA da poi broda zi'e noi brode} -> {to da brode toi PA da poi broda} * -> {to ro da brode toi PA da poi broda} or, perhaps, remembering the domain of the variable and only universally quantifying over that, giving {to ro da poi broda brode toi PA da poi broda} ; but that's a bit of a pain in practice, since the clause giving the domain could itself mention unbound variables, and you have to recurse. Martin --mSxgbZZZvrAyzONB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQI5yAACgkQULC7OLX7LNaxOACffH9oxjZER4cG4JWHYWX2KOLj gAcAnA4n6tee4FpZepqo3uhWch4xPb5Z =8w/5 -----END PGP SIGNATURE----- --mSxgbZZZvrAyzONB--