Received: from mail-yx0-f189.google.com ([209.85.213.189]:47986) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RW9RO-0006KX-4C; Thu, 01 Dec 2011 08:24:59 -0800 Received: by yenm12 with SMTP id m12sf2105297yen.16 for ; Thu, 01 Dec 2011 08:24:47 -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:from :date:message-id:subject: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; bh=dI01ygnFUImPG1wpYe9FqBAgpuk336vTDOv+kz4M9SQ=; b=XjUVMGuVPM6YI4byDpxP0bHjd2Lp7AhQGcrUo7f+OFT9GfdICRZ+l/RcLb1jwsd4D8 MX0Tgh/b0VK/5fhIPTbFPOog5s1L68xPs8Z/ESR9Fjh884e+FDHYXrBWBZCwwT+as2Ud 6ENYwOdZlnBR7UVG3lH1HJohZcC12MplK25io= Received: by 10.236.176.103 with SMTP id a67mr3724644yhm.7.1322756685037; Thu, 01 Dec 2011 08:24:45 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.100.236.2 with SMTP id j2ls12146268anh.0.gmail; Thu, 01 Dec 2011 08:24:44 -0800 (PST) Received: by 10.236.124.80 with SMTP id w56mr13422712yhh.0.1322756684337; Thu, 01 Dec 2011 08:24:44 -0800 (PST) Received: by 10.236.124.80 with SMTP id w56mr13422710yhh.0.1322756684327; Thu, 01 Dec 2011 08:24:44 -0800 (PST) Received: from mail-gx0-f177.google.com (mail-gx0-f177.google.com [209.85.161.177]) by gmr-mx.google.com with ESMTPS id n75si2192604yhe.3.2011.12.01.08.24.44 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 08:24:44 -0800 (PST) Received-SPF: pass (google.com: domain of lukeabergen@gmail.com designates 209.85.161.177 as permitted sender) client-ip=209.85.161.177; Received: by ggki1 with SMTP id i1so2372488ggk.36 for ; Thu, 01 Dec 2011 08:24:44 -0800 (PST) Received: by 10.101.94.15 with SMTP id w15mr1883830anl.117.1322756684148; Thu, 01 Dec 2011 08:24:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.14.2 with HTTP; Thu, 1 Dec 2011 08:24:23 -0800 (PST) In-Reply-To: <20111201160359.GE22210@stodi.digitalkingdom.org> References: <20111130173647.GO8581@stodi.digitalkingdom.org> <20111130195612.GF2886@gonzales> <20111201041638.GZ8581@stodi.digitalkingdom.org> <20111201153201.GN2886@gonzales> <20111201160359.GE22210@stodi.digitalkingdom.org> From: Luke Bergen Date: Thu, 1 Dec 2011 11:24:23 -0500 Message-ID: Subject: Re: [lojban] Rant (baby related): dasni, taxfu, and all their friends. To: lojban@googlegroups.com X-Original-Sender: lukeabergen@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lukeabergen@gmail.com designates 209.85.161.177 as permitted sender) smtp.mail=lukeabergen@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: multipart/alternative; boundary=0016e6d3e22d486f2d04b30a4aeb X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --0016e6d3e22d486f2d04b30a4aeb Content-Type: text/plain; charset=ISO-8859-1 > > > If it was up to me, I'd define certain places as being ka'e-able: > that is, "this place is normally filled by X [where in the case of > botpi X would be "what the bottle currently contains"], but even if > there is no current or obvious X, the capability is sufficient for > the semantics of this word; zi'o should only be used if the > capability has been lost". > > -Robin > > I don't know if I agree with that. I think a {broda zi'o} isn't necessarily a {broda} that cannot have an x2 but rather a {broda} that in this instance does not have an x2. i.e. there's no reason that {ko'a simlu lo ka barda zi'o} COULDN'T have an observer, only that in this instance it does not. Or... maybe that's the chief difference between noda and zi'o? I'll be honest, my grasp of what zi'o is/does in a technical sense is fairly weak. -- 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@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --0016e6d3e22d486f2d04b30a4aeb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

If it was up to me, I'd define certain places as being ka'e-a= ble:
that is, "this place is normally filled by X [where in the case of
botpi X would be "what the bottle currently contains"], but even = if
there is no current or obvious X, the capability is sufficient for
the semantics of this word; zi'o should only be used if the
capability has been lost".

-Robin


I don't know= if I agree with that. =A0I think a {broda zi'o} isn't necessarily = a {broda} that cannot have an x2 but rather a {broda} that in this instance= does not have an x2. =A0i.e. there's no reason that {ko'a simlu lo= ka barda zi'o} COULDN'T have an observer, only that in this instan= ce it does not. =A0Or... maybe that's the chief difference between noda= and zi'o? =A0I'll be honest, my grasp of what zi'o is/does in = a technical sense is fairly weak.

--
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.
--0016e6d3e22d486f2d04b30a4aeb--