Received: from mail-vw0-f61.google.com ([209.85.212.61]:39965) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RRFyp-0003Fi-S1; Thu, 17 Nov 2011 20:23:16 -0800 Received: by vbbez10 with SMTP id ez10sf70448vbb.16 for ; Thu, 17 Nov 2011 20:23:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from:to: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=okSwAk61+mXO90VyoOe7Pb443bYrSQYK5coJwE6Uv7c=; b=TyaNzEB+spHlBc4SsbXe94k9rYWqiRzEbSt8nDYYLFDL/qL29LPy6Ft6HlJjmBMsKG 4xXtN2bujdxgUctZmv7rmAxk391D7EPxTL2z0qexJB5dMWYSKge45UnuvaUtew4Qr4dt QAAoDL+yHO5fp28OVMqHwxKD+XjxCneG4P0u0= Received: by 10.52.92.232 with SMTP id cp8mr720974vdb.13.1321590182705; Thu, 17 Nov 2011 20:23:02 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.220.149.17 with SMTP id r17ls3170782vcv.0.gmail; Thu, 17 Nov 2011 20:23:01 -0800 (PST) Received: by 10.52.30.195 with SMTP id u3mr2891285vdh.3.1321590181490; Thu, 17 Nov 2011 20:23:01 -0800 (PST) Received: by 10.52.30.195 with SMTP id u3mr2891283vdh.3.1321590181481; Thu, 17 Nov 2011 20:23:01 -0800 (PST) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by gmr-mx.google.com with ESMTPS id en7si5601188vdb.1.2011.11.17.20.23.01 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 20:23:01 -0800 (PST) Received-SPF: pass (google.com: domain of maikxlx@gmail.com designates 209.85.220.182 as permitted sender) client-ip=209.85.220.182; Received: by mail-vx0-f182.google.com with SMTP id fy13so3162489vcb.27 for ; Thu, 17 Nov 2011 20:23:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.24.210 with SMTP id w18mr1716107vdf.21.1321590181380; Thu, 17 Nov 2011 20:23:01 -0800 (PST) Received: by 10.52.181.167 with HTTP; Thu, 17 Nov 2011 20:23:00 -0800 (PST) In-Reply-To: References: <1321501066.64722.YahooMailRC@web81306.mail.mud.yahoo.com> Date: Thu, 17 Nov 2011 23:23:00 -0500 Message-ID: Subject: Re: [lojban] Lions and levels and the like From: maikxlx To: lojban@googlegroups.com X-Original-Sender: maikxlx@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of maikxlx@gmail.com designates 209.85.220.182 as permitted sender) smtp.mail=maikxlx@gmail.com; dkim=pass (test mode) header.i=@gmail.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.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / 2011/11/17 Jorge Llamb=EDas > > On Thu, Nov 17, 2011 at 9:22 PM, maikxlx wrote: > > 2011/11/17 Jorge Llamb=EDas : > >> "ka'e" is "fi'o se cumki". The connection with "kakne" is just mnemoni= c. > > > > Is this a newish development? =A0{ka'e} is also a rafsi of {kakne}, > > often a strong sign of relatedness. > > Almost all CV(')V cmavo have the same form of a rafsi of something. My > guess is the ones that are related to that something are in =A0the > minority. "ka'e" was obviously taken from "kakne", yes, but the > connection is kind of malglico. Similarly "pe'i" comes from "pensi", > "ti'e" from "tirna", and thare are other mnemonics that go through > malglico glosses. > Right, but with e.g. {pi'o}, it's a no-brainer that the cmavo has nothing to do with pianos despite sharing {pipno}'s rafsi's form. With {ka'e}, one would not think it was such an accident. In principle of course no cmavo need to be related to the gismu with that cmavo's form. > > >=A0Meanwhile, vlasisku, BPFK section > > CAhA, cmavo.txt and the CLL say nothing about {cumki} wrt {ka'e}. > > In jbovlaste "ka'e" is defined as "fi'o se cumki". But since I wrote > that definition I guess I can't count that as evidence. :) > It's only in the Lojban record! Side note: which should I rely on more, vlasisku or jbovlaste? I find vlasisku's cross linking and more complete search results to be superior. If someone rolled in the BPFK definitions and CLL sections, it would be almost ideal. > > Also, while {cumki} does express possibility, {ka'e}, from the given > > definitions, seems to be more about ability than possibility. > > But whose ability? Each of the arguments of the relation modified by > "ka'e"? The x1? The agent (assuming there is one)? > You're asking me?! Well since you asked, from what I see, I would definitely assume the x1, given the glosses, proposed keywords, and examples in the CLL and BPFK. In particular the CLL examples indicate very clearly that {ka'e} and related CAhA are some sort of short-scope selbri modifiers and emphatically _not_ true modal operators with scope over the whole bridi. > >=A0In > > order to say things like "it possibly brodas" and "it necessarily > > brodas" I have to believe that these concepts should have their own > > words, without mixing ability into it. > > I agree that the word "ability" should not appear in the definition of > CAhAs, since events don't really have abilities. > It's not just "ability" that seems off, it's also the ambiguous "can" and "innate capability" as well as the conspicuous absence of "may", "might" and above all "POSSIBLE". > >=A0These primitive logical > > operators strike me as vastly worth assigning two disyllables from > > cmavo space, especially in light of some of the other things > > available. Just my 2 cents. > > I agree. I have said before that it is extremely weird that a logical > language doesn't have a word for the "necessarily" operator. > The fact that there is no necessity operator strongly suggests that the language designers did not have the foggiest notion of modal logic when they created {ka'e}. It's clear to me from the evidence that {ka'e} is at best roughly related, but not identical, to the possibility operator. At the very least, it seems muddled and contaminated with malglico. I do not read a ton of Lojban, but I find it very doubtful that common usage is substantially better than the flawed CLL examples. Therefore I would respectfully suggest considering two new uncontaminated cmavo to act as true and contaminated, wide-scope modal-logical operators: ci'a =3D "it is possible that; possibly; may/might" (looks vaguely like 'c= umki') ne'e =3D "it is necessary that; necessarily; must" (looks vaguely like 'necessary') > mu'o mi'e xorxes > mu'o mi'e .maik. --=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.