Received: from mail-pz0-f61.google.com ([209.85.210.61]:33121) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RECyt-0006gc-W4; Wed, 12 Oct 2011 21:33:28 -0700 Received: by pzk32 with SMTP id 32sf972695pzk.16 for ; Wed, 12 Oct 2011 21:33:13 -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=MsUAaKJF+HCn3o3OlsQhoDNDaxKJaOwFg+mlLpSuVH0=; b=tuLbSQSpOsTBToKXjOX1rR2tVrJ9Z0kGxTYHwWvKQYv6ROnfb+3Rg/9YQ0FaC3MtE7 gJSgu2NtZxwnCRsHoUVGuILiMSNNxC94DPhleVjdjT2qKGu4S2bY98g6JgXnaQ/W0IBl HuMN2vxr3tLqAYqCy5DhBL5Y2KGRiWG6yvkAo= Received: by 10.68.75.230 with SMTP id f6mr936459pbw.12.1318480390631; Wed, 12 Oct 2011 21:33:10 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.68.33.200 with SMTP id t8ls5674074pbi.4.gmail; Wed, 12 Oct 2011 21:33:09 -0700 (PDT) Received: by 10.68.46.193 with SMTP id x1mr4077970pbm.7.1318480389675; Wed, 12 Oct 2011 21:33:09 -0700 (PDT) Received: by 10.68.46.193 with SMTP id x1mr4077967pbm.7.1318480389655; Wed, 12 Oct 2011 21:33:09 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19]) by gmr-mx.google.com with ESMTPS id r5si2699207pbe.1.2011.10.12.21.33.09 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Oct 2011 21:33:09 -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 p9D4X86k010098 for ; Thu, 13 Oct 2011 04:33:09 GMT Received: from martin by gonzales.homelinux.org with local (Exim 4.75) (envelope-from ) id 1RECyi-0007Dm-G4 for lojban@googlegroups.com; Thu, 13 Oct 2011 00:33:08 -0400 Date: Thu, 13 Oct 2011 00:33:08 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable Message-ID: <20111013043308.GD3367@gonzales> References: <1318202744.44997.YahooMailRC@web81306.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sXc4Kmr5FA7axrvy" Content-Disposition: inline In-Reply-To: <1318202744.44997.YahooMailRC@web81306.mail.mud.yahoo.com> X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: troci 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: / --sXc4Kmr5FA7axrvy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2011-10-09 at 16:25 -0700 - John E Clifford : > OK, that helps. You want not just quantified variables, but restrictivel= y=20 > quantified variables, with the restrictions to be gotten from contexts in= at=20 > least some cases. And the restriction is to be such that it has only one = item=20 > (atom or plurality) meeting it. I just don't see the point of this. Why= bring=20 > quantification, with the attendant problems of scopes, when all that is n= eeded=20 > is a constant (one of the virtues of Skolem functions is just that they g= et rid=20 > of some quantification -- why bring it back?) My point was that constants (or, more accurately, Skolem functions) are handled as an extreme case of the "tight existential quantification over a glorked domain", namely where the glorked domain is a singleton. Of course if this were the only relevant case, it would be perverse to consider it as quantification over a singleton domain. In other words: I'm converting your binary ambiguity - between the Skolem function "some things I (would) have in mind" and the existential quantifier ranging over the whole universe - into a vagueness, the glorked domain C interpolating between the two extremes. > Nor do I see the point of trying to bring together anaphora (typically > syntactic. occasionally semantic), deixis (always pragmatic, I think) > and the "whatever I have in mid" sense (probably pragmatic), as well > as the unfettered quantifiers of the indifferent gaps. It does provide > for something that looks like a uniform explanation for the various > treatment of gaps, but I think it would be better to admit that the > treatment is a mistake and try to replace it than to fadge up > a dubious coverup job. I don't know if it's a mistake. I don't see it as being much more conceptually repugnant that the binary ambiguity it interpolates, and it explains more uses. It is, however, incomplete as an explanation of unfilled places, because unfilled places are often more like generics - e.g. in "adjectival" predications like {ko'a se cinri} or {ko'a jdari}. > Careful about the order of thing; if resolution of {zo'e} comes after ana= phora=20 > (as it usually would, given your ideas), them {P(zo'e zo'e)} would not be= the=20 > same as {P(zo'e ri)} because each occurrence of {zo'e} is evaluated on it= s own. Yes, I think I was wrong to suggest that anaphora can be cleared up before interpreting the {zo'e}s and {lo}s. The real story is likely to be tricky. To take a simple example: when the {lo} is read generically, what does {lo remna cu prami ri} mean? There are two obvious possibilities - "humans love humans" (both generic) and "humans love themselves". The first is natural only if we admit kinds. (For nastier a example, consider the apparently classic {ro te cange poi ponse lo xasli cu darxi ri}... although I'd be happy simply considering this to be meaningless) > On Oct 9, 2011, at 13:03, Martin Bays wrote: >=20 > > * Sunday, 2011-10-09 at 12:11 -0400 - John E. Clifford : > >=20 > >> On Oct 9, 2011, at 0:27, Martin Bays wrote: > >>=20 > >>> * Saturday, 2011-10-08 at 19:56 -0400 - John E. Clifford=20 > >>>: > >>>=20 > >>>> It seems the only logically sensible out is to allow unfilled > >>>> spaces only for variables (the general case) and require something > >>>> more specific for the rest,preferably the appropriate pronouns in > >>>> those case and {zo'e} on the last, though I suppose that in most > >>>> cases {zo'e} could do for all three. > >>>=20 > >>> But unless I'm misunderstanding what you mean by variables, the other > >>> three cases (which are arguably really just one case) are just special > >>> cases of the variable case - namely, where the glorked domain of the > >>> existential quantification is a singleton (whose single element might= be > >>> a plurality, of course). > >>>=20 > >> Here is the problem, then. In standard semantics, the universe or > >> domain of discourse is a given and all variables range over the items > >> in that domain. There is no case of a special domain to be used for > >> just one variable, separate from the domain that applies to all the > >> others (there are complications here but none that bear on this > >> point). I suppose some mechanism could be worked out to do something > >> like this, but it seems a lot of work for no apparent gain. > >>=20 > >>> So I'm understanding you as having {zo'e} force the domain to be > >>> a singleton, but otherwise to work like an unfilled place > >>=20 > >> No. Domains don't change like that. {zo'e} is simply a constant. Is > >> this strange ad hoc domain what you mean by "close-scope"? Rather > >> than its effect in the structure of the sentence? > >=20 > > I didn't mean to do anything funny with the domain of discourse. By > > 'domain', I meant the domain of this particular quantification - so in > > {da poi broda}, the set of (atomic) brodas is the domain of that > > quantification. > >=20 > > So having {zo'e} give existential quantification over a glorked > > singleton domain is equivalent to having it give a constant. > >=20 > > To be more precise about how I'm suggesting zo'e works / should work: > >=20 > > If we have a predication P(zo'e noi broda, zo'e noi brode), it resolves > > as: > > EX (X1,X2). (C(X1,X2) /\ P(X1,X2)) > > where C is a context-glorked relation which depends on any quantifiers > > (including ones over worlds) which the current predication is in the > > scope of, and which is such that C(X1,X2) implies broda(X1)/\brode(X2). > >=20 > > (X, X1, X2 all plural mundane variables, i.e. not allowed to take kinds, > > but not restricted to atoms) > >=20 > > (Here I've made C a relation rather than a set, which is a subtle > > difference but I think an improvement) > >=20 > > Furthermore, I'm suggesting that at least some uses of {lo} follow this > > pattern - i.e. that P(lo broda, lo brode) means the above, at least > > sometimes. > >=20 > > Something else which might not be obvious: I think this resolution > > of zo'e-terms happens *after* most other processing, in particular after > > resolution of anaphora. So e.g. {broda zo'e ri} is just equivalent to > > {broda zo'e zo'e}. > >=20 > > More generally, I think we can split semantic analysis of lojban into > > two broad stages - a pre-pragmatic stage, in which there is no > > vagueness, ambiguity or glorking, but which leaves behind tanru, > > zo'e-terms, non-anaphoric prosumti like {ti}, and perhaps some other > > such things; and a pragmatic stage which applies glorking to handle > > those leftovers. We're talking here about how the pragmatic stage > > handles zo'e-terms. > >=20 > > The prepragmatic stage should return a sentence in a logic something > > like Montague's IL, but with basic terms and relations having some > > structure, like zo'e-terms and abstractions and tanru. I think this is > > quite doable, and that doing it is the best way to specify the logical > > parts of lojban. > >=20 > > But that's branching from the point. > >=20 > >>> It seems reasonable to want a word for that. Maybe it should be {zo'e= }, > >>> I'm not sure. If it were, we'd need to find another word with the > >>> meaning of an unfilled place, say {zo'e'e} - if only because {lo brod= a} > >>> would then be {zo'e'e noi broda} rather than {zo'e noi broda} (to > >>> whatever extent that equivalence ever works). > >>>=20 > >>>> So, back to the question case: the appropriate negative responses to > >>>> the question { xu do klama le zarci} are {na}(or should that > >>>> be{naku}?), {na go'i}, {mi na klama zy} ( or some more official > >>>> pronoun), and the basic {mi na klama le zarci}, with {mi na klama > >>>> zo'e} as a marginal possibility. > >>>=20 > >>> And {mi na klama} as a definite possibility, yes? > >>=20 > >> I would say, no, because that would have me going nowhere, not merely > >> not to the store. > >=20 > > Right. But I don't think having the quantification always be over the > > whole domain of discourse, rather than a glorked portion thereof, is > > very usable. For example, one arguably is always klamaing somewhere - > > even if just to the place one already is at. > >=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. --sXc4Kmr5FA7axrvy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk6WagQACgkQULC7OLX7LNairwCeMQbyiOA1zyt8wpR9SpWu+lOR KPoAoN4CAQI+A5suUSseE7y3lRER8UW9 =54lX -----END PGP SIGNATURE----- --sXc4Kmr5FA7axrvy--