Received: from mail-iy0-f189.google.com ([209.85.210.189]:47404) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RNA0O-0004U1-8z; Sun, 06 Nov 2011 13:12:00 -0800 Received: by iage36 with SMTP id e36sf8766555iag.16 for ; Sun, 06 Nov 2011 13:11:45 -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=6SyXW4PvzPne4xDzDMUD5gGkWHOZhYOrUKwjwgYJCI0=; b=m4CBg8zQiRxcP1qbxiRuzDlz33Dx1Hj7FhbFhtgAslzWlXePLQ0OpcqFn23c09A9KR e6TLuniU+pJGYmzWDAk0zgAeiWeP2G5l7fUqClbvIS2FykEHmWr74FfYh/Oa7LQnGTah Bug8m2swzJJUgDO2TtbkgenyVZ29j0mFwzayA= Received: by 10.50.155.196 with SMTP id vy4mr2925664igb.4.1320613902864; Sun, 06 Nov 2011 13:11:42 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.231.63.137 with SMTP id b9ls13128787ibi.0.gmail; Sun, 06 Nov 2011 13:11:42 -0800 (PST) Received: by 10.42.133.135 with SMTP id h7mr37190070ict.4.1320613902108; Sun, 06 Nov 2011 13:11:42 -0800 (PST) Received: by 10.42.133.135 with SMTP id h7mr37190069ict.4.1320613902097; Sun, 06 Nov 2011 13:11:42 -0800 (PST) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19]) by gmr-mx.google.com with ESMTPS id l5si13727290pbe.2.2011.11.06.13.11.41 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Nov 2011 13:11:41 -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 pA6LBf8Q006784 for ; Sun, 6 Nov 2011 21:11:41 GMT Received: from martin by gonzales.homelinux.org with local (Exim 4.75) (envelope-from ) id 1RNA0D-00088L-15 for lojban@googlegroups.com; Sun, 06 Nov 2011 16:11:41 -0500 Date: Sun, 6 Nov 2011 16:11:41 -0500 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable Message-ID: <20111106211140.GC2703@gonzales> References: <20111105172216.GI24058@gonzales> <20111105201536.GB835@gonzales> <20111105233402.GA2831@gonzales> <20111106033146.GC2831@gonzales> <20111106182701.GA2703@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="S1BNGpv0yoYahz37" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: so'i 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: / --S1BNGpv0yoYahz37 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2011-11-06 at 17:15 -0300 - Jorge Llamb=EDas : > On Sun, Nov 6, 2011 at 3:27 PM, Martin Bays wrote: > > * Sunday, 2011-11-06 at 12:56 -0300 - Jorge Llamb=EDas : > >> On Sun, Nov 6, 2011 at 12:31 AM, Martin Bays wrote: > >> That says something quite different though. It doesn't even preclude > >> the possibility that every ranmapku is bolmapku as long as there is > >> one bolmapku that is not ranmapku. > > > > Does ficysi'u? >=20 > Hmm... I think so, yes. >=20 > If you are quantifying over mundane hats, then saying that at least > one of them is either a beret or a bowler but not both is not much > like saying that berets and bowler hats are different kinds of hats. I > think you would need to say that everything is either a beret, a > bowler, or neither. (And the double exclusive or is hard!) Hmm? Why not just {no da ranmapku gi'e bolmapku}? > And even so, mere set disjointness doesn't seem to get at the heart of > the matter, which is probably in the x3 of klesi: >=20 > "lo ranmapku jo'u lo bolmapku cu ficysi'u lo ka ce'u klesi lo mapku ma ka= u" Yes, good. So I'd want to add three characters: {lo ranmaplei jo'u lo bolmaplei cu ficysi'u lo ka ce'u klesi lo maplei ma k= au} > >> Why is beret - hat - garment artificial? > > But they're all on the same level, no? > As kinds? A beret is a kind of hat, and a hat is a kind of garment. I'm only seeing two levels there - one containing berets and hats, and one containing kinds of hat and kinds of garment. > > It's true that it isn't clear what a valsi is. I do believe that this > > should be clarified. My take would be that a valsi is an abstract > > entity, as are jufras and selskus; that {zo mupli} has a single > > referent, like (qkauless) {lo ka broda}; and that what these pixels > > glowing on your monitor are doing is sinxaing valsis. The valsis > > themselves may sinxa concepts, and we can skip a level and say that the > > pixels sinxa the concepts. > > > > I suppose you would have the pixel-valsis sinxaing the abstract-valsis, > > but also valsiing whatever it is the abstract-valsis valsi? >=20 > I would want to say "mi kancu lo valsi poi dei vasru ku'o li pa pa". Well, I would probably be pernickety and demand {valsi nunsku} in place of {valsi}. This does not give you licence to call me pernickety when I demand {mapku klesi} ;) Martin --S1BNGpv0yoYahz37 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk62+AwACgkQULC7OLX7LNacewCgolsZk3FqnmlCf4PbVcZA0HwC mWgAoI/xcD/Ej7jwPdofOgddiLKGawMA =hpCl -----END PGP SIGNATURE----- --S1BNGpv0yoYahz37--