Received: from mail-ee0-f61.google.com ([74.125.83.61]:56291) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XczdK-000560-CL for lojban-list-archive@lojban.org; Sat, 11 Oct 2014 09:35:14 -0700 Received: by mail-ee0-f61.google.com with SMTP id t10sf519247eei.16 for ; Sat, 11 Oct 2014 09:34:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=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:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=/UmFz3J2x90Gi28kB2M5oKOaC/rw7p4LiClF0vPf+uA=; b=yNUBG20URd8M2apyqMk/NHMU6AqAYVI7Y0GONlSEtA8VngwL8pKHegcFu3QllnfTsG Y81DDaXaXR4dSubmgM2AhnXUBLlWG1sHVpMVUgwwUhH7ujYyt5TPO7jP05jfHjYFCJVS vZ0KtvzXhbQBU33QZEn3AihbN7fjvEiUjPxlQJnZAU93iS7xI8FyAbqXUCtbA3f7gnTJ KHKLyAtg87A2licAhEayLA2wDgq3R30VSOoo07ZwC51Ns+9PXiSvtzTKnu+u/TATbXMo 8Dbdo8yLtLbXTgGRtKT2wi7h7u2yCIdbI2HDtq5chSyNpeptrhd0ABirRsr3xEo3LOTG XZBw== X-Received: by 10.152.19.97 with SMTP id d1mr182466lae.1.1413045298933; Sat, 11 Oct 2014 09:34:58 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.152.2.67 with SMTP id 3ls366308las.63.gmail; Sat, 11 Oct 2014 09:34:57 -0700 (PDT) X-Received: by 10.112.132.37 with SMTP id or5mr2268895lbb.2.1413045297787; Sat, 11 Oct 2014 09:34:57 -0700 (PDT) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [2a00:1450:4010:c04::235]) by gmr-mx.google.com with ESMTPS id rb5si139029lbb.0.2014.10.11.09.34.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Oct 2014 09:34:57 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c04::235 as permitted sender) client-ip=2a00:1450:4010:c04::235; Received: by mail-lb0-f181.google.com with SMTP id l4so4537440lbv.26 for ; Sat, 11 Oct 2014 09:34:57 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.27.40 with SMTP id q8mr3499123lag.92.1413045297701; Sat, 11 Oct 2014 09:34:57 -0700 (PDT) Received: by 10.114.61.107 with HTTP; Sat, 11 Oct 2014 09:34:57 -0700 (PDT) In-Reply-To: <20141011143749.GD23876@gonzales> References: <20141008015245.GB17866@gonzales> <20141009010533.GF18854@gonzales> <20141009233031.GC1592@gonzales> <20141010234033.GG22868@gonzales> <20141011021201.GH22868@gonzales> <20141011143749.GD23876@gonzales> Date: Sat, 11 Oct 2014 13:34:57 -0300 Message-ID: Subject: Re: [lojban] Re: tersmu 0.2 From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c04::235 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=089e0158c5aa0566f30505283fce X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --089e0158c5aa0566f30505283fce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Oct 11, 2014 at 11:37 AM, Martin Bays wrote: > * Saturday, 2014-10-11 at 08:58 -0300 - Jorge Llamb=C3=ADas < > jjllambias@gmail.com>: > > > On Fri, Oct 10, 2014 at 11:12 PM, Martin Bays wrote: > > > > (So then tu'a needing opacity is no longer an argument that the rest = of > > > LAhE should get it...) > > > > Well... > > By which you mean it kind of still is, because it's best to minimise > what irregularity we're forced into? Perhaps so. No longer a strong > argument, anyway. > It's still the case that "tu'a" places the operators at the minimum of the three scopes available to it, so it's reasonable for the others to place them at the minimum of the two scopes they have available. Also for "na'e bo" and for "lu'a" the minimum scope seems to be the more useful one. If based just on usefulness LAhE would have to be split into different classes with different logical behaviors. Or perhaps we need to reevaluate the definition of some of these LAhEs. I wouldn't mind for example making "lu'i A .e B" the set of those things that are both among A and among B, which would require redefining "lu'i" as "lo selcmi be ro me", with three potential scope levels just as "tu'a" has, and with the minimum being the correct one. Regarding {lo}: could it be the "down" operator which extracts a kind > from a predicate? I'm not seeing any other options, if it is "definite" > and if \iota is out. > That kind of presupposes that among all the various operators that linguists/logicians/etc have defined, described, explored there has to be one that matches "lo". I don't know enough about the subject to give an opinion one way or the other. mu'o mi'e xorxes --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --089e0158c5aa0566f30505283fce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Sat, Oct 11, 2014 at 11:37 AM, Martin Bays <mbays@sdf.org> wr= ote:
* Saturday, 2014-10-11 at 08:58 -030= 0 - Jorge Llamb=C3=ADas <jjllamb= ias@gmail.com>:

> On Fri, Oct 10, 2014 at 11:12 PM, Martin Bays <mbays@sdf.org> wrote:

> > (So then tu'a needing opacity is no longer an argument that t= he rest of
> > LAhE should get it...)
>
> Well...

By which you mean it kind of still is, because it's best to mini= mise
what irregularity we're forced into? Perhaps so. No longer a strong
argument, anyway.

It's still the ca= se that "tu'a" places the operators at the minimum of the thr= ee scopes available to it, so it's reasonable for the others to place t= hem at the minimum of the two scopes they have available. Also for "na= 'e bo" and for "lu'a" the minimum scope seems to be = the more useful one. If based just on usefulness LAhE would have to be spli= t into different classes with different logical behaviors.=C2=A0
=
Or perhaps we need to reevaluate the definition of some of t= hese LAhEs. I wouldn't mind for example making "lu'i A .e B&qu= ot; the set of those things that are both among A and among B, which would = require redefining "lu'i" as "lo selcmi be ro me", = with three potential scope levels just as "tu'a" has, and wit= h the minimum being the correct one.

Regarding {lo}: could it be the "down" operator which extracts a = kind
from a predicate? I'm not seeing any other options, if it is "defi= nite"
and if \iota is out.

That kind of presup= poses that among all the various operators that linguists/logicians/etc hav= e defined, described, explored there has to be one that matches "lo&qu= ot;. I don't know enough about the subject to give an opinion one way o= r the other.

mu'o mi'e xorxes

<= div class=3D"gmail_extra">=C2=A0=C2=A0

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--089e0158c5aa0566f30505283fce--