Received: from mail-pz0-f61.google.com ([209.85.210.61]:63329) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RGib6-0004ic-Im; Wed, 19 Oct 2011 19:43:17 -0700 Received: by pzk4 with SMTP id 4sf2494420pzk.16 for ; Wed, 19 Oct 2011 19:43:02 -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=0RSfLusEQ42GW/pOMcfVUW3lkONZAoU4LYuvJY1gfz4=; b=lcQd/I3x9BO7QK+tO2SU8IgPXrdJ9VyHRlQMipkQdSXnAk8mAHqLA5y6oRxm3OXRE4 5yTzUtRTC8NnlW00I9GALKvJLOS6Dv1p0iNlcT2HCh6TybrCqzhokEjc3zY7eXe4P6mM B9+Rheww2bhy6fq6cbj256rTOc+Omzmv9ef2M= Received: by 10.68.27.201 with SMTP id v9mr1380632pbg.5.1319078494300; Wed, 19 Oct 2011 19:41:34 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.68.33.200 with SMTP id t8ls8159348pbi.4.gmail; Wed, 19 Oct 2011 19:41:33 -0700 (PDT) Received: by 10.68.35.68 with SMTP id f4mr6193971pbj.5.1319078493599; Wed, 19 Oct 2011 19:41:33 -0700 (PDT) Received: by 10.68.35.68 with SMTP id f4mr6193970pbj.5.1319078493590; Wed, 19 Oct 2011 19:41:33 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19]) by gmr-mx.google.com with ESMTPS id l3si4825773pbd.0.2011.10.19.19.41.33 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Oct 2011 19:41:33 -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 p9K2fWo2006046 for ; Thu, 20 Oct 2011 02:41:33 GMT Received: from martin by gonzales.homelinux.org with local (Exim 4.75) (envelope-from ) id 1RGiZY-0000OI-En for lojban@googlegroups.com; Wed, 19 Oct 2011 22:41:32 -0400 Date: Wed, 19 Oct 2011 22:41:32 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable Message-ID: <20111020024132.GH5010@gonzales> References: <1318906003.98760.YahooMailRC@web81305.mail.mud.yahoo.com> <20111018044730.GB30548@gonzales> <20111018054425.GP21114@gonzales> <20111019184449.GC5010@gonzales> <1319076660.7053.YahooMailRC@web81305.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNpeiK4tTqhYOExY" Content-Disposition: inline In-Reply-To: <1319076660.7053.YahooMailRC@web81305.mail.mud.yahoo.com> X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: kicne 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: 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: / --PNpeiK4tTqhYOExY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Wednesday, 2011-10-19 at 19:11 -0700 - John E Clifford : > U\I'm not going to worry about {loi} etc. until I am sutre about {lo} and= then=20 > see what is lefyt over that needs dealing with. {lo cipnrdodo) refers > to all the dodos there ever were (suppose that is right for this > context), all of which are thus in the domain of discourse and also in > the extension of {cipnrdodo}. What problem are you having; I just > don't see it? Hmm. So you'd want every dodo which ever lived to now cipnrdodo - even if it doesn't zasti, nevermind jmive? That might work for some cases, but what if we want to say "people in glass houses should install proper insulation"? Even if the people in question (who mostly don't zasti in this possible world, nevermind now) were to ca ca'a prenu, they surely couldn't ca ca'a nenri su'o blaci zdani; nor is there any other world in which they all do. So the bunch of them doesn't satisfy {prenu gi'e nenri su'o blaci zdani} - since there's only one bunch, we would need that the bunch satisfies this in some given world. It doesn't. But each atom (person, in this case) in the bunch does satisfy {prenu gi'e nenri su'o blaci zdani}. So for {lo prenu poi nenri su'o blaci zdani} to get the bunch, we'd need the quantifier over worlds to go inside a quantifier over the bunch. The gadri seems the right place to specify this. Martin > ----- Original Message ---- > From: Martin Bays > To: lojban@googlegroups.com > Sent: Wed, October 19, 2011 1:44:49 PM > Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plur= al=20 > variable >=20 > * Tuesday, 2011-10-18 at 01:44 -0400 - Martin Bays : >=20 > > * Tuesday, 2011-10-18 at 00:47 -0400 - Martin Bays : > >=20 > > > * Monday, 2011-10-17 at 19:46 -0700 - John E Clifford=20 > : > > > > ----- Original Message ---- > > > > From: Martin Bays > > > > > Maybe I finally understand what you mean with your "kinds =3D max= imal > > > > > bunches" idea. Let's see. > > > > >=20 > > > > > I've been implicitly assuming that in {lo broda}, the tense insid= e the > > > > > description is by default copied from outside it. So {mi ca ca'a = nelci > > > > > lo pavyseljirna} =3D=3D {mi ca ca'a nelci lo ca ca'a pavyseljirna= }, which is > > > > > false if there are no unicorns. > > > >=20 > > > > I suppose the tense (if there is one) is as contextual as everythin= g else=20 > >about=20 > > > > > > descriptions. The same as the bridi surely is a good guess in gene= ral, but=20 > >may=20 > > > > > > be obviously wrong in other circumstances. For example, in general= ities,=20 > >the=20 > > > > > > tense (if that is the right notion) is probably past, present, futu= re and=20 > > > > possible. > > >=20 > > > Right, so I think I do understand you. > > >=20 > > > Does this work? > >=20 > > But there's something of a problem: if the plural referent of {lo broda} > > is meant to satisfy broda, what tense can give us e.g. all dodos ever? > > The plural referent of {lo pu cipnrdodo} must satisfy {pu cipnrdodo}, > > i.e. must have satisfied {cipnrdodo} at some point in the past. But that > > means we're picking up some dodos all of which existed at the same time. > >=20 > > So it seems we'd have to have the rule be that {ro lo broda cu broda}, > > rather than {lo broda cu broda}, for this to work. >=20 > ...and then it might make sense to have {loi broda} be the same as {lo}, > except that the plural referent is required to broda (rather than the > atoms below it brodaing). So while {lo pu cipnrdodo} could get the bunch > (aka plurality) of all dodos ever, {loi pu cipnrdodo} would have to get > a bunch all of which cipnrdodod at the same past time (which might imply > that they were all alive at the same time, or if dead at least not too > far decomposed...). >=20 > So this contains some of the essence of the historical meaning of {loi}, > and is usefully distinct from (the understanding under discussion of) > {lo}. >=20 > Martin >=20 > --=20 > You received this message because you are subscribed to the Google Groups= "lojban" group. > To post to this group, send email to lojban@googlegroups.com. > To unsubscribe from this group, send email to lojban+unsubscribe@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?hl=3Den. --PNpeiK4tTqhYOExY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk6filwACgkQULC7OLX7LNbGNACgnxc9YflcZPD6K34GCxddZN2m ZxsAn3IKoSUsUm0sG9ABMOdEkdOurHsN =tquh -----END PGP SIGNATURE----- --PNpeiK4tTqhYOExY--