Received: from mail-ia0-f183.google.com ([209.85.210.183]:65339) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TrvS2-0003AG-UG; Sun, 06 Jan 2013 11:00:21 -0800 Received: by mail-ia0-f183.google.com with SMTP id r13sf11225813iar.10 for ; Sun, 06 Jan 2013 11:00:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf :mime-version: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; bh=e5q7fVZEPAyDaCAgEdVTtGg+QW2n6cklV+BqU7AEpPI=; b=eG5GgB7edsABL7TkCLZ+0u7vuse2VFd/6x53URaBsXeBhq68BRjKYxDAtaqyOR+8h9 jOGEQ0bGiYWxE178Wklgnl5Dpom5cqmNyjp496oRO27V+kxzR94FZqzwrr2yujUFI5eL kOjT+qR6jXlSCSVNci0Fixwnkf8kl1y9TJSbasxzZwzpCeu6g2gpUDk9sAKkLcheWsMz 38ntbfBbwqLuta9LOgpEDmlWzVTUssatFrcHXZEWP6ZOHbunBuTf5ozTgEJ6Bpo5T8vX z47Pn9bTJnz8rxAd7YOn8aWSyHRjSv/etYX8zGLzyPDjCksY9l1WpQIJJE40W0o/PAtH Cecg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:x-received:received-spf :mime-version: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; bh=e5q7fVZEPAyDaCAgEdVTtGg+QW2n6cklV+BqU7AEpPI=; b=Nd5Yu+e/ropnGjBNdH4HF/a4djIkM3RxX4kAX/9M+oRSI6MOq6lLztfTUG4AdN5zQ5 bt/ZQtCGtZmw7g0CPcChlqAw7L5Jp/Bo9og0gzUFseUX4X2OnyBvANXmrOiYkbVUjyps 0G8SzNhDmwKJP4qKyoEShspQTI25xYvMh2FE9xbogMqsyZ8UBuQTI9RX9IEZIz2xt8eq wBxHEP2uY3mqp2yT60Eb2uSZv8yjhbo0LBq17Z8+SF52VzYU/HwymdIcarOWoWAMEsGF aQvel3sfh6xSqzD4+X9+bVzT/HtHj7RxKymyv5viJpui25LQrz8QtNB3Xu7YqM7FaUVt Uyxg== X-Received: by 10.49.72.169 with SMTP id e9mr10048318qev.3.1357498800197; Sun, 06 Jan 2013 11:00:00 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.87.227 with SMTP id bb3ls8138043qeb.3.gmail; Sun, 06 Jan 2013 10:59:58 -0800 (PST) X-Received: by 10.52.99.129 with SMTP id eq1mr24185200vdb.4.1357498798933; Sun, 06 Jan 2013 10:59:58 -0800 (PST) X-Received: by 10.52.99.129 with SMTP id eq1mr24185198vdb.4.1357498798919; Sun, 06 Jan 2013 10:59:58 -0800 (PST) Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by gmr-mx.google.com with ESMTPS id d17si16653993vdt.1.2013.01.06.10.59.58 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Jan 2013 10:59:58 -0800 (PST) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 209.85.220.169 as permitted sender) client-ip=209.85.220.169; Received: by mail-vc0-f169.google.com with SMTP id gb23so18966126vcb.0 for ; Sun, 06 Jan 2013 10:59:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.151.142 with SMTP id c14mr80357582vcw.16.1357498798806; Sun, 06 Jan 2013 10:59:58 -0800 (PST) Received: by 10.220.13.197 with HTTP; Sun, 6 Jan 2013 10:59:58 -0800 (PST) Date: Sun, 6 Jan 2013 13:59:58 -0500 Message-ID: Subject: [lojban] Quantifier exactness From: Ian Johnson To: lojban@googlegroups.com X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 209.85.220.169 as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass 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=f46d043be06aaf95c104d2a35115 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --f46d043be06aaf95c104d2a35115 Content-Type: text/plain; charset=ISO-8859-1 The issue of quantifier exactness has come up a few times already. The most recent example was "context and precision" which was forked by aionys from another thread. You can look at that thread On IRC today, playing around with functions we stumbled upon a combination of a sentence and situation such that one stance on quantifier exactness makes the sentence false while the other makes it true. Here's the setup: There are 4 people, mi, do, la alis, la bab; the latter two are grouped under {lo re prenu}. I like la alis a little bit, but hate la bab. You like la alis and la bab a lot. Now consider {mi zmadu do lo ni ce'u nelci pa lo re prenu} (If the ni confuses you, pretend it's ka, as that part's not important here. We can talk about ka-ni elsewhere.) If quantifiers are exact, this is true. {do nelci pa lo re prenu} is completely false (you like *two* of them, not one), while {mi nelci pa lo re prenu} is true, if only a little bit, so I do exceed you in that aspect. Note that the CLL says this is how the language works, but if you look at the previous discussions you'll find that this is clumsy fairly frequently. If quantifiers are not exact, this is false or at least false-ish, since {ro da poi me lo re prenu zo'u do zmadu mi lo ni ce'u nelci da}. I thought this example warranted discussion primarily because it does *not*arise because of annoying, semi-ontological issues related to the universe of discourse. Instead there's only two people being quantified over, but the two interpretations still differ with respect to this (relatively simple) sentence. .i do ma jinvi .i mi'e la latro'a mu'o -- 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. --f46d043be06aaf95c104d2a35115 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The issue of quantifier exactness has come up a few times already. The most= recent example was "context and precision" which was forked by a= ionys from another thread. You can look at that thread On IRC today, playin= g around with functions we stumbled upon a combination of a sentence and si= tuation such that one stance on quantifier exactness makes the sentence fal= se while the other makes it true. Here's the setup:

There are 4 people, mi, do, la alis, la bab; the latter two are grouped= under {lo re prenu}.
I like la alis a little bit, but hate la bab.
Y= ou like la alis and la bab a lot.
Now consider
{mi zmadu do lo ni ce&= #39;u nelci pa lo re prenu}
(If the ni confuses you, pretend it's ka, as that part's not import= ant here. We can talk about ka-ni elsewhere.)

If quantifiers are exa= ct, this is true. {do nelci pa lo re prenu} is completely false (you like <= i>two of them, not one), while {mi nelci pa lo re prenu} is true, if on= ly a little bit, so I do exceed you in that aspect. Note that the CLL says = this is how the language works, but if you look at the previous discussions= you'll find that this is clumsy fairly frequently.
If quantifiers are not exact, this is false or at least false-ish, since {r= o da poi me lo re prenu zo'u do zmadu mi lo ni ce'u nelci da}.
<= br>I thought this example warranted discussion primarily because it does not arise because of annoying, semi-ontological issues related to the = universe of discourse. Instead there's only two people being quantified= over, but the two interpretations still differ with respect to this (relat= ively simple) sentence.

.i do ma jinvi

.i mi'e la latro'a mu'o

--
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.
--f46d043be06aaf95c104d2a35115--