Received: from mail-yw0-f61.google.com ([209.85.213.61]:62639) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RN2mn-00082Z-DF; Sun, 06 Nov 2011 05:29:31 -0800 Received: by ywa17 with SMTP id 17sf5394811ywa.16 for ; Sun, 06 Nov 2011 05:29:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :x-ymail-osg:x-mailer:references:message-id:date:from:subject:to :in-reply-to:mime-version: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:content-type :content-transfer-encoding; bh=JUg+YumhJlMVveWTSczRvGRyesZHN68IEd9SCmPrBQE=; b=FPJNTgIjW6aLqDahZnwRujQjDFXQ+eSHGBKWptm+72Sb/qXsjEQD+al/N6iA/aEUA6 AIlUfy13lg/GRcKN0IB27kUuBhqBGFqmSh/uLvORIL8wU5IJMbA/AuBQo1SZGMUy3MuH aH3v2aCpnyYiTQVFEZ3Krg5z5dX3CW5U1pLb0= Received: by 10.236.161.165 with SMTP id w25mr6208732yhk.15.1320585374171; Sun, 06 Nov 2011 05:16:14 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.101.167.19 with SMTP id u19ls1744772ano.7.gmail; Sun, 06 Nov 2011 05:16:13 -0800 (PST) Received: by 10.101.110.14 with SMTP id n14mr5686126anm.39.1320585373338; Sun, 06 Nov 2011 05:16:13 -0800 (PST) Received: by 10.101.110.14 with SMTP id n14mr5686125anm.39.1320585373323; Sun, 06 Nov 2011 05:16:13 -0800 (PST) Received: from nm5-vm0.access.bullet.mail.mud.yahoo.com (nm5-vm0.access.bullet.mail.mud.yahoo.com. [66.94.237.155]) by gmr-mx.google.com with SMTP id s16si9310335ane.3.2011.11.06.05.16.13; Sun, 06 Nov 2011 05:16:13 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.237.155 as permitted sender) client-ip=66.94.237.155; Received: from [66.94.237.126] by nm5.access.bullet.mail.mud.yahoo.com with NNFMP; 06 Nov 2011 13:16:13 -0000 Received: from [66.94.237.100] by tm1.access.bullet.mail.mud.yahoo.com with NNFMP; 06 Nov 2011 13:16:12 -0000 Received: from [127.0.0.1] by omp1005.access.mail.mud.yahoo.com with NNFMP; 06 Nov 2011 13:16:12 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 870389.44364.bm@omp1005.access.mail.mud.yahoo.com Received: (qmail 13039 invoked by uid 60001); 6 Nov 2011 13:16:12 -0000 X-YMail-OSG: 3WuQkd0VM1nfbpSPQoGN5RuYM4yn.G3p7jS5mIkBi9pm6NN kVZIX3pYZcQaOQmGpRk7JeHBbcn6zKSZVZ_bfIfjw7pNo7D7fTXvOHpm5q82 Mm16IhBTDDIjOlD1pwIFDE4o8DBZW_qzdYC3bVHdrTHCnvHvxgGoldcl62O9 GTNSMH38sbG6GqDAuTJ4JN5hBQ8IMwuYIwshUSrk_CdWqOnzJpHDIXntUCja 1BQek1IO5mXRzUdBo5WJ9fd.4pEXwQmoX6wRCKbVPyb72ZgLkUX_vh.X61U_ fXEF4L8MoRGVcMabhHYZ5zfcVS9pHqMkrYg6atxC9JGf9eQdFoEU4kU.t8e8 6U.UZMvdwP87Bk_V4U3d.120qy2wyRq1W6A5NFKJjDHKX5fF7_gHyvTgyFCN kkFnnME9e07A7KixDWGbJduif_cfSlt.EnZhUBWiixZFNiw-- Received: from [99.92.108.41] by web81301.mail.mud.yahoo.com via HTTP; Sun, 06 Nov 2011 05:16:12 PST X-Mailer: YahooMailRC/574 YahooMailWebService/0.8.114.317681 References: <20111104233756.GB24058@gonzales> <4EB4A123.7030305@gmail.com> <20111105061247.GE24058@gonzales> <4EB526B7.7070008@gmail.com> <20111105172216.GI24058@gonzales> <20111105201536.GB835@gonzales> <20111105233402.GA2831@gonzales> <20111106033146.GC2831@gonzales> Message-ID: <1320585372.5586.YahooMailRC@web81301.mail.mud.yahoo.com> Date: Sun, 6 Nov 2011 05:16:12 -0800 (PST) From: John E Clifford Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable To: lojban@googlegroups.com In-Reply-To: <20111106033146.GC2831@gonzales> MIME-Version: 1.0 X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.237.155 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.com 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: , Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / Le'see. I think I understand what is going on here. Let me say it out for= =20 corrections and then I can get on (though I will comment on this understand= ing=20 now). Somebody (the layered responses without summaries makes it difficult= to=20 figure out who is advocating what) holds that, in a given conversation, {c= info}=20 (for example) may mean any of at least: Lion, lions, lion, lion segments=20 (temporally defined), lion kinds, lionness. And which {cinfo} means in tha= t=20 conversation in no way determines what, say, {xanti} (or whatever "elephant= " is=20 ) means in that same conversation. Somebody else holds that this makes Loj= ban=20 predicates ambiguous (at least across conversations -- the listed definitio= ns=20 are merely suggestive, not to be taken literally, or, if so, at least liber= ally)=20 and, further, that it does not work because, in fact, most conversations tu= rn=20 out to involve shifts from one meaning to another, with corresponding chang= es in=20 the domain, and with disastrous logical consequences (AE implies EA, for=20 example).=20 The first idea seems to rest on 1) a desire to show that Lojban is not SAE= =20 metaphysically, but rather can be viewed as of several different types in= =20 different contexts and 2) the looseness of English (and presumably Spanish = and=20 most other familiar languages, possibly excepting Chinese) usage, which doe= s in=20 fact shift among these various meanings unmarked. Unfortunately, goal 1)= =20 misses, since all that is shown is how wide the notion of thing is, not tha= t NPs=20 in Lojban refer to other than things. Source 2) is, of course, just=20 irrelevant. The fact that English (etc.) is sloppy does not mean that Lojb= an=20 is. Lojban has expressions for most of the distinctions here suggested and= can=20 easily fill in any gaps (there may be a infinite number of ways to slice th= e=20 baloney, but at any given point only a finite number have been used, and we= can=20 cover that number). Lojban can, of course, be telegraphic, dropping qualif= iers=20 that are not needed in context (indeed, Gricean rules require this), but th= e=20 semantics (and, probably, the pragmatics) are up to handling this and so th= is=20 need not change the underlying nature of what is going on. As for the other position, I confess that I cannot follow the arguments, wh= ich=20 seem to me to involve illegitimate (or at least misleading) uses of quantif= iers=20 and a lot of technical mumble-jumble that does not obviously serve the poin= t=20 (side one seems to do quite a bit of this, too, and side two may be merely= =20 repeating that). =20 In short, this seems to me a tempest in a teacup -- without any real ripple= s=20 even -- and of no real significance to Lojban. Stepping back to the official topic here for a moment. The notion that {zo= 'e}=20 means "what I have in mind or would have it I thought about it" leads to th= e=20 paradoxical (but not contradictory) situation: A: xu do klama le zarci. B:= na=20 go'i . mi klama le zarci. That is, B went to the store, but not from A's= =20 intended starting point or not along A's intended path or not using A's int= ended=20 mode of transportation. But rather using B's intended starting point, path= and=20 mode. Taking {zo'e} to be just {da} cleverly disguised avoids this problem but cr= eates=20 others of its own, in terms scope and negation problems (which happen to wo= rk=20 out alright here) ----- Original Message ---- From: Martin Bays To: lojban@googlegroups.com Sent: Sat, November 5, 2011 10:31:46 PM Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural= =20 variable * Saturday, 2011-11-05 at 22:28 -0300 - Jorge Llamb=EDas : > On Sat, Nov 5, 2011 at 8:34 PM, Martin Bays wrote: > > * Saturday, 2011-11-05 at 18:18 -0300 - Jorge Llamb=EDas=20 >: > > > >> I think I do get it. I just don't think it has anything to do with > >> logical structure. > > > > Well that's a matter of definitions. > > > > But note e.g. that the classic example of scope ambiguity in english, > > "someone loves everyone", can be looked at this way: > > > > A: "Someone loves everyone." > > B: "Oh yeah? Who? > > A: "Their mother." > > > > A: {su'o prenu cu prami ro prenu} > > B: {ma prami ro prenu} > > A: {lo mamta} > > > > (Lojban can't seem to get at the "their" in "their mother", but that's > > not really important) > > > > (and yes, I know by now that you would consider A to be breaking your > > favoured domain conventions by having both mundane people and Mother as > > a person in the same domain; but (a) that's an informal rule, which > > appears to be flexible (you broke it in the xabju example), and (b) it'= s > > not important to the essence of the example that prenu is being used on > > both sides) >=20 > I still don't think that's a matter of logical structure. It's A > tricking B into one interpretation to get an effect once the "right" > interpretation is presented. That's how many jokes work. Well, I presented it in joke form - which was possibly foolish as I didn't intend to trivialise the issue! Really, I don't see that the situation is significantly better than it is in english. A search for "quantifier scope ambiguity examples" yields various examples of the issue in english, most of which appear to go through directly in kindful lojban. Another clear example: "A professor talked to all the students" {su'o ctuca cu tavla ro le tadni} could mean only that each student was talked to by a professor - formally, just because the kind Professor ctucas; or if we apply your informal rule that quantification indicates that there should be multiple things at the same level involved, then because it could be that they were all talked to by a logic professor. > >> Consider "a beret is a type of hat". I would say "lo ranmapku cu klesi > >> lo mapku". > > > > In reality, I'd just say {ro ranmapku cu mapku}. >=20 > What about "berets and bowler hats are different types of hats"? > "lo ranmapku jo'u lo bolmapku cu ficysi'u lo ka klesi lo mapku" Again we could avoid kinds, and just say {su'o da ranmapku .o nai bolmapku}. Or we could use properties rather than kinds, and say {lo ka ranmapku na du lo ka bolmapku}, or copy your approach with {lo ka ranmapku ku jo'u lo ka bolmapku cu ficysi'u lo ka kairni'i lo ka mapku} (where ro da poi selkai ku'o ro de poi selkai zo'u go da de kairni'i gi ro di ckaji da na.a de) (although {go'e fi lo ka ma kau ckaji} might make more sense). > > But if you forced me to use kind terminology, I'd want a second > > predicate for "x1 is a subkind of x2". From the gimste definitions, I'd > > be more likely to use {klesi} for that than "x1 is an instance of x2", > > which is closer to {mupli}. In fact, {mupli} seems to want a property i= n > > x2, so maybe this could be {klemupli}. >=20 > (I would rather re-define "mupli" into "x1 is an instance of x2", but any= way.) >=20 > ... > > But maybe it's true that kinds are useful enough that the language > > should have special facilities for handling them - e.g. allowing {lo > > mapku} to get a kind. We just need to have ways to disambiguate. >=20 > "klesi" allows us to disambiguate between two levels. Disambiguating > between a potentially infinite number of levels is trickier. As the > old Lojban saying goes: the price of infinite precision is infinite > verbosity Can you give an example where we might want to go up two levels from mundanes (as opposed to their stages or whatever)? I wouldn't be surprised if there were such, and maybe you've given examples before, but none spring to mind (other than artificial examples like "kinds of kinds of garment" - unless you can think of natural cases where we'd want to talk about those). > > The "imaginaries" terminology of the other thread gives one plausible > > approach to this - treating kinds as analogous (and, in a sense, dual) > > to bunches. {su'o} would get neither bunches nor imaginaries, but {lo} > > could get either. > > > > I suspect that a system based on this could explain e.g. most if not al= l > > of the sentences in your alis, while also being sufficiently > > disambiguable to satisfy me. > > > > Would you reject such a solution out of hand? >=20 > I think that covers most needs, but I suspect there are cases when we > may want to quantify over kinds. Hmm. That didn't sound like a rejection! For quantifying over kinds: if the rule is that {lo} gets a bunch of imaginaries which are all imaginaries with respect to the same equivalence relation aka differentiation criterion (i.e., to import one more piece of model theoretic parlance, a bunch of imaginaries from the same "imaginary sort"), I see nothing wrong with using e.g. {ca lo prulamnicte mi citka vo lo cidja poi do nelci}. I would also want it to be possible to specify that we are fa'u are not talking about imaginaries (with respect to a non-trivial equivalence relation, i.e. one coarser than equality), perhaps with {lio} fa'u {loi}. (No that wasn't a typo! The PEG morphology allows {lio} as a cmavo form, right?) I'd also want to be able to specify the equivalence relation in question in the former case, i.e. as per And's (iii) of the other thread. I don't know how to do that... maybe with inner quantifiers? {re lo fi'u vei ni'e ka skari ma kau ve'o mapku cu vi zvati} for "two colours of hat are here", or {so'o lo fi'u vei ni'e ka danlu ma kau ve'o cinfo ba zi morsi} for "several species of lion will soon become extinct"? With {lio broda} being (blissfully) short for {lo fi'u vei ni'e co'e ve'o broda}? And {lo fi'u ro cinfo} being the wholly singularised lion, i.e. Lion (rather than an infinitesimal amount of lion)? Martin --=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@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.