Received: from mail-pb0-f61.google.com ([209.85.160.61]:60101) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1WqDQy-0004Fv-5w for lojban-list-archive@lojban.org; Thu, 29 May 2014 20:24:52 -0700 Received: by mail-pb0-f61.google.com with SMTP id rq2sf308216pbb.26 for ; Thu, 29 May 2014 20:24:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:cc: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=+HLw4QUduoKxjgC+jfT9AvrfPY05pGI3oqrGeNhGFLU=; b=QLvpZ8ubD2Yhq/iB9FnWea0SXdozjVztqIgeHadezh9JtTBxNU4XrDz5VXNzA9OLl2 eePDXVcDuBWWobJzbH4ayVpXCA5BH+qo91el50VJsPq+ErhHSkkjmnRDmvf4qT7psB5l DPwk1AmcninAb4IqCzMby88/e2s1NpgZQW746oc0PMdtkmKjSDbufDpOSWnCy9ihGDuF DmU0o7/O2Xvu2oCCcdb9cWSbKjMSGIoSLJvs2zRgZVouDRT5u18eCmmpkfgJvdouEcN4 exQP0mQZdnj0gmj7EN4dlDHkd73sk6j6/kF3Am3sIVoIgxi2ycLPAtJRstdzQaeN9HS6 fRAQ== X-Received: by 10.140.38.199 with SMTP id t65mr4505qgt.17.1401420278154; Thu, 29 May 2014 20:24:38 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.24.42 with SMTP id 39ls820312qgq.26.gmail; Thu, 29 May 2014 20:24:37 -0700 (PDT) X-Received: by 10.236.140.42 with SMTP id d30mr4659882yhj.2.1401420277703; Thu, 29 May 2014 20:24:37 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id bu7si737541pad.0.2014.05.29.20.24.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 May 2014 20:24:37 -0700 (PDT) Received-SPF: none (google.com: mbays@sdf.org does not designate permitted sender hosts) client-ip=192.94.73.24; Received: from mbays.mdns.org (c-50-131-238-175.hsd1.ca.comcast.net [50.131.238.175]) (authenticated (0 bits)) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s4U3O4qQ019141 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Fri, 30 May 2014 03:24:05 GMT Received: from martin by mbays.mdns.org with local (Exim 4.80.1) (envelope-from ) id 1WqDQo-0002FH-U7; Thu, 29 May 2014 20:24:34 -0700 Date: Thu, 29 May 2014 20:24:34 -0700 From: Martin Bays To: lojban@googlegroups.com Cc: gusni.kantu@gmail.com Subject: Re: [lojban] Individuals and xorlo Message-ID: <20140530032434.GA20211@gonzales> References: <750f9b01-a747-4b12-80ba-e31b7e7bd20e@googlegroups.com> <570dae9f-cda3-42c4-a861-1c7974fe5bfd@googlegroups.com> <20140525194906.GA885@gonzales> <20140527025346.GJ885@gonzales> <20140527204250.GL885@gonzales> <462524b8-28de-49f3-a938-4cc42543c28f@googlegroups.com> <20140528171446.GN885@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: mei 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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , X-Spam-Score: -0.0 (/) X-Spam_score: -0.0 X-Spam_score_int: 0 X-Spam_bar: / --jI8keyz6grp/JLjh Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Thursday, 2014-05-29 at 15:42 -0700 - guskant : > Le jeudi 29 mai 2014 02:14:50 UTC+9, Martin Bays a =E9crit : > > > > * Tuesday, 2014-05-27 at 19:21 -0700 - guskant > >:=20 > > > > > Regarding {zo'e} as the outmost constant in a prenex of a statement i= s a=20 > > > special case of {zo'e} as Skolem functions. As for the example=20 > > >=20 > > > {ro da broda lo brode},=20 > > > that is=20 > > > Ax B(x,f(x)),=20 > > >=20 > > > it says nothing about whether {lo brode} as a Skolem function f(x) is= =20 > > > constant for all x or not. That is to say, xorlo allows both=20 > > > interpretations "EYAx B(x,Y)" and "AxEY B(x,Y)" as a statement before= =20 > > > Skolemization, while CLL-lo restricts the interpretation to "AxEy=20 > > B(x,y)"=20 > > > (small y is a singular variable).=20 > > > > Assuming I understand you correctly as wanting {lo broda se broda ro da= }=20 > > to have only the "EYAx" interpretation, this is in direct conflict with= =20 > > the gadri BPFK section, which says=20 > > "Any term without an explicit outer quantifier is a constant, i.e. not= =20 > > a quantified term. This means that it refers to one or more individuals= ,=20 > > and changing the order in which the constant term appears with respect= =20 > > to a negation or with respect to a quantified term will not change the= =20 > > meaning of the sentence.".=20 > =20 >=20 > Then your assumption is false. I don't want {lo broda cu se broda ro da} = to=20 > have only "EYAx B(x,Y)" interpretation. See the table at=20 > http://guskant.github.io/lojbo/skolem.png Aha, thanks. I hadn't realised you were suggesting this only as a special role for terms in the prenex. > Le jeudi 29 mai 2014 05:21:56 UTC+9, xorxes a =E9crit : > > On Wed, May 28, 2014 at 2:14 PM, Martin Bays wrote: > >> The statement "there exists a function f(x) such that for all x, > >> P(x,f(x))" is logically equivalent to "for all x, there exists y such > >> that P(x,y)".=20 > > There is, however, a difference between these two metalinguistic=20 > > statements: > > > > "There exists a function f(x) such that the speaker of the sentence is= =20 > > claiming that for all x, P(x, f(x))" and "the speaker of the sentence = is=20 > > claiming that there exists a function f(x) such that for all x, P(x, f(= x)". > > > > CLL-lo uses the second interpretation when interpreting such sentences. > mi'usai Agreed. To return to the question of whether the referent of {zo'e} can be non-constant wrt {da} in {ro da broda zo'e}: I understood xorxes as adopting the contrary position when we discussed these things some years ago (using generics as the constant values to make sense of things like your S1), but perhaps that is out-dated or I over-interpreted. In any case, the semantics you suggest seem sensible to me. As for ways to specify that a {zo'e} is constant: an alternative to your suggestion of introducing new rules for prenexes would be to pull tricks like: su'oi da zo'u ro de broda lo du be da (which may or may not be equivalent to lo du be su'oi da se broda ro da ). A bit long-winded for something so important, though. Meanwhile, a question. Under these semantics, the second (and only the second!) {zo'e} in ro zo'e zo'e broda depends functionally on the quantifier. But in ro zo'e ro zo'e broda it doesn't make sense to say that each {zo'e} depends functionally on the quantifier on the other. This seems to complicate matters? Martin --jI8keyz6grp/JLjh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlOH+fIACgkQULC7OLX7LNb5xgCeMUzAopH+uLZJxz1PQRCMHl8b cI0AnjwCb1Wfw+dXfCZUNZcWZlmgX/X1 =1tSp -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--