Received: from mail-yw0-f61.google.com ([209.85.213.61]:58830) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RMmeZ-0002K4-VV; Sat, 05 Nov 2011 13:15:57 -0700 Received: by ywa17 with SMTP id 17sf4674180ywa.16 for ; Sat, 05 Nov 2011 13:15: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=50WqPAVHuDUlEC5P/4zAqevxNgykpLJQ9LZiP6GmKq4=; b=AqQlJ2IbvQP1ZfLsW/D/sb4LAXd0Ahxl1E8jgccLCA3IdVAglE2LlffLNjkDjdQjs/ Gy7I7cE4xpRdaAYWjlkTaex3qf2vBZ+32/NM9uWlRqGareR63xuD/qo5DYeYoy09vLcf dIpgcplcYEBGehK6qTHDbjYrEszk6cYpigmRY= Received: by 10.236.124.105 with SMTP id w69mr5973743yhh.5.1320524138880; Sat, 05 Nov 2011 13:15:38 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.150.114.13 with SMTP id m13ls7041474ybc.3.gmail; Sat, 05 Nov 2011 13:15:37 -0700 (PDT) Received: by 10.236.46.130 with SMTP id r2mr29120676yhb.7.1320524137379; Sat, 05 Nov 2011 13:15:37 -0700 (PDT) Received: by 10.236.46.130 with SMTP id r2mr29120674yhb.7.1320524137368; Sat, 05 Nov 2011 13:15:37 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19]) by gmr-mx.google.com with ESMTPS id r5si10020068pbe.1.2011.11.05.13.15.37 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 Nov 2011 13:15:37 -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 pA5KFaup021388 for ; Sat, 5 Nov 2011 20:15:36 GMT Received: from martin by gonzales.homelinux.org with local (Exim 4.75) (envelope-from ) id 1RMmeO-0002CV-6S for lojban@googlegroups.com; Sat, 05 Nov 2011 16:15:36 -0400 Date: Sat, 5 Nov 2011 16:15:36 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable Message-ID: <20111105201536.GB835@gonzales> References: <20111029172822.GC9385@gonzales> <4EAC5B24.4000604@gmail.com> <20111103234955.GA3758@gonzales> <4EB43035.6040407@gmail.com> <20111104233756.GB24058@gonzales> <4EB4A123.7030305@gmail.com> <20111105061247.GE24058@gonzales> <4EB526B7.7070008@gmail.com> <20111105172216.GI24058@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZfOjI3PrQbgiZnxM" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: bradi 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: / --ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Saturday, 2011-11-05 at 15:18 -0300 - Jorge Llamb=EDas : > On Sat, Nov 5, 2011 at 2:22 PM, Martin Bays wrote: > > > > To reiterate the point: allowing cinfo to be ambiguous between levels > > is, by the definition of 'level', effectively equivalent to allowing the > > logical structure of sentences which involve quantifying over cinfo to > > be ambiguous. >=20 > No, that's not true. Sorry, make that "effectively ambiguous", or "meta-ambiguous" or somesuch. I meant the "effectively" of "effectively equivalent" to carry over to "ambiguous", but should have been clearer. I think I've made clear by now the sense in which it is effectively ambiguous; if not, I can try to be clearer. > Just because "ro broda cu brode" can have different meanings in > different contexts does not mean that there is anything ambiguous > about its logical structure. Its logical structure has nothing to do > with the meaning of "broda" or of "brode". All the logical structure > tells us is that any thing from the domain of discourse that satisfies > the predicate broda, also satisfies the predicate brode. It tells us > nothing about what things are in the domain of discourse or about what > things satisfy broda or about what things satisfy brode. Sure. But if it isn't enough to stick to one domain when understanding some lojban text, then it isn't enough to stick to one domain when considering what counts as (effectively) ambiguous lojban text. > > So where does this leave Blobularism? I fear it leaves it needing to > > find a way to specify the levels its carving the Blob to. Sorry. >=20 > There are some level-mixing predicates. The ones that come to mind are > "klesi", "krefu" and "rapli". The x1 of klesi is at a lower level than > the x2. The x1 of krefu is at a lower level than the x2. In the case > of rapli, there is only one level for its arguments, but x2 counts > things that are at a lower level than x1. I wonder how you handle > these predicates in Ready-Made. Assuming that is how {klesi} works (I find the gimste definition rather unclear), we would have e.g. that a type of hat selkle su'o mapku gi'e nai mapku. > Presumably in Ready-Made there is only one level of events, so what > does it mean for an event to rapli any number other than one? With events, something like Blobularity might well be appropriate - the crucial point being that we have the tense system to specify carvings. So a nu broda is like a quantity of water - you can carve it up however you like and still get a nu broda. (By "carving" here, I mean taking the restriction of the event to a subset of the set of space-time(-possibility) associated to the original event - or if we shouldn't literally be talking about sets (c.f. the "distribution-theoretic" approach in the other subthread), whatever is the correct analogue of that.) The only obvious alternative would be to say something like that an atomic nu broda corresponds to a connected component of the subset of space-time at which {broda} holds, and that events with multiple connected components are bunches. But I feel that might be too restrictive - any examples to show that it is? Martin --ZfOjI3PrQbgiZnxM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk61mWgACgkQULC7OLX7LNYrFwCeKQ7hIMOifZsGDcWkk8gghrLH UMUAnAzqwLppC11UPlLJSMiGCDhJBQhd =zJn6 -----END PGP SIGNATURE----- --ZfOjI3PrQbgiZnxM--