Received: from mail-pz0-f61.google.com ([209.85.210.61]:62781)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCOTEtqyUDhDviq31BBoE2oNo7Q@googlegroups.com>)
	id 1RJwZU-00079p-53; Fri, 28 Oct 2011 17:14:54 -0700
Received: by pzk4 with SMTP id 4sf6081173pzk.16
        for <multiple recipients>; Fri, 28 Oct 2011 17:14:41 -0700 (PDT)
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=PEg09jYw/gIi30Ua10r3sRNz3RBWw6QXn6NVdseJTSI=;
        b=proX4PGfrVUyOj9kaWyGmHIqqd6/fggUhmauOXNBXN2RjyCo4JN4dYv/SCsMVqCvAb
         Tm01Lagdr4btzlc60X+zj/641IOzU2b3cs6YIbLLJgbBuIjJ66J9J0t0NgbUyML37YUh
         WTra4vrZJ9k5Q/biD9lCBWHh9ki7o9Mto2DEQ=
Received: by 10.68.12.36 with SMTP id v4mr539266pbb.4.1319847279433;
        Fri, 28 Oct 2011 17:14:39 -0700 (PDT)
X-BeenThere: lojban@googlegroups.com
Received: by 10.68.74.5 with SMTP id p5ls9498856pbv.7.gmail; Fri, 28 Oct 2011
 17:14:38 -0700 (PDT)
Received: by 10.68.0.170 with SMTP id 10mr1588264pbf.2.1319847278838;
        Fri, 28 Oct 2011 17:14:38 -0700 (PDT)
Received: by 10.68.0.170 with SMTP id 10mr1588263pbf.2.1319847278826;
        Fri, 28 Oct 2011 17:14:38 -0700 (PDT)
Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19])
        by gmr-mx.google.com with ESMTPS id l5si12430195pbe.2.2011.10.28.17.14.38
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 28 Oct 2011 17:14:38 -0700 (PDT)
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 p9T0Eb4c007207
	for <lojban@googlegroups.com>; Sat, 29 Oct 2011 00:14:38 GMT
Received: from martin by gonzales.homelinux.org with local (Exim 4.75)
	(envelope-from <mbays@sdf.org>)
	id 1RJwZJ-0002Yk-HA
	for lojban@googlegroups.com; Fri, 28 Oct 2011 20:14:37 -0400
Date: Fri, 28 Oct 2011 20:14:37 -0400
From: Martin Bays <mbays@sdf.org>
To: lojban@googlegroups.com
Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable
Message-ID: <20111029001437.GA5535@gonzales>
References: <4EA5ACD4.4030106@gmail.com>
 <20111024184651.GC3062@gonzales>
 <4EA5F890.6070501@gmail.com>
 <20111025002558.GA27114@gonzales>
 <4EA60BBC.1040707@gmail.com>
 <20111025021504.GB27114@gonzales>
 <4EA68224.1080406@gmail.com>
 <20111026033114.GB3119@gonzales>
 <4EA7BF06.5050103@gmail.com>
 <4EAA8AC9.2010000@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z"
Content-Disposition: inline
In-Reply-To: <4EAA8AC9.2010000@gmail.com>
X-PGP-Key: http://mbays.freeshell.org/pubkey.asc
X-PGP-KeyId: B5FB2CD6
X-cunselcu'a-valsi: bolci
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: /


--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Friday, 2011-10-28 at 11:58 +0100 - And Rosta <and.rosta@gmail.com>:

> Martin Bays, On 26/10/2011 04:31:
>  > * Tuesday, 2011-10-25 at 10:32 +0100 - And Rosta<and.rosta@gmail.com <=
mailto:and.rosta@gmail.com>>:
>  >> Martin Bays, On 25/10/2011 03:15:
>  >>> * Tuesday, 2011-10-25 at 02:07 +0100 - And Rosta<and.rosta@gmail.com=
 <mailto:and.rosta@gmail.com>>:
>  >>> If Lion X is equal to Lion Y, then they satisfy the same predicates.=
 So
>  >>> if we can agree that Lion X is called Nigel while Lion Y is called
>  >>> Samantha, or if X likes to eat gazelles while Y prefers humans, then=
 we
>  >>> must agree that there are at least two lions. Right?
>  >>
>  >> So not one lion that changes its name and dietary preferences?
>  >
>  > The use of the present tense was intended to rule that out.
>=20
> But you will presumably also say that the definition of {cinfo} also
> specified criteria for distinguishing between two stages of the same
> lion and stages of two different lions, and that the distinction
> cannot be left lingustically unencoded.

I'm saying that the definition of {cinfo} is
"x1 is a lion/[lioness] of species/breed x2", and that I wouldn't want
to change this.

If I understand you correctly, that does mean that I am saying what you
say I'm saying.

>  > OK. So in John's lion-hunting context, after his having shot the left
>  > lion, you'd say "lo pa cinfo noi zu'a se cmene zo samantas.uu cu zu'a
>  > morsi gi'e ku'i ri'u pu'o zi gunta .ii mi'o"?
>  >
>  > I can see that John might be dangerously confused. Perhaps there are
>  > sound evolutionary reasons for natural language making sharper
>  > distinctions between lions and Lion than you seem to want lojban to?
>=20
> Speakers should make the distinctions when necessary, using the
> resources of the language. When being approached by lions, it is
> especially important to know their spetial distribution. In other
> contexts, such as the daily lion, there is no such need to agonize
> over whether they're all the same lion. For other predicates, e.g.
> Barbie ("We both got given Barbie for Christmas") and Father Christmas
> ("F. C. has a white beard"), identity criteria are more insensitive to
> spatial distribution.

I still don't think I understand your setup. Do you have different
entities to handle these different cases? e.g. would you actually use
multiple lions in the lion-hunting example, rather than Lion doing
different things in different places? But use Lion for the daily lion?

If so, that is sounding closer to my understanding of xorxes' setup.

>  > Is it arbitrary to treat Obama as a single entity but lions as multiple
>  > entities? Does it involve treating time differently from space? To an
>  > extent, I suppose it does - at least, I don't see a wholly coherent way
>  > to rationalise the counting by reference to just the topology of the
>  > subset of space-time at which there is Obama or Lion or whatever. But =
in
>  > a language that's meant to be speakable by humans, I don't find time vs
>  > space asymmetry too objectionable.
>=20
> Rather than "speakable by humans" I think you mean "speakable by
> Martin". But anyway, I think that when one thinks about how to
> implement your vision of lojban, assuming it's agreed that it should
> be able to express world-vviews other than your own, the solution
> would accommodate equally well the views of all participants in this
> discussion. For every current predicate with X places, there will be
> X * Y new predicates, where Y is the number of sets of criteria for
> discriminating between individuals (i.e. for deciding, given F(a) and
> F(b), whether or not a=3Db). Now it's hard to see how these extra
> predicates could be achieved other than by the use of appropriate
> cmavo dedicated to the purpose. And in that case, the way of both
> lojban and common sense would be to stipulate that when the
> individuative cmavo are omitted, the semantic criteria for
> individuating are unexpressed. Thus, the version with individuative
> cmavo used would allow you to express what you want to express,=20
> while the version witouth individuative cmavo used would express how
> things are in me and xorxes's vision.

So your individuative cmavo would be something like classifiers?

Those would certainly be helpful if we're to have kinds in the language.

But really, it seems that we are literally disagreeing on the meaning of
{cinfo} - whether it means "is a lion", or "is Lion", or is ambiguous
between the two. So wouldn't the most natural and lojbanic solution be
to decide on one of the two as the meaning of {cinfo}, and have
a tanru/lujvo ({cinfo pavrolza'i} or {cinfo dacti}, perhaps) for the
other?

Whichever were chosen for {cinfo} itself, it would still be possible to
declare that {lo cinfo} explicitly selects one or the other, or is
ambiguous between the two, as preferred.

Martin

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

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

iEYEARECAAYFAk6rRW0ACgkQULC7OLX7LNaa0gCgyI+ED3IaUcXTKgiI26LhUGEw
FTkAoIYrPyJNBKwNcDvp8DzSHQJA4CkZ
=OuvM
-----END PGP SIGNATURE-----

--Nq2Wo0NMKNjxTN9z--