Received: from mail-qk0-f188.google.com ([209.85.220.188]:32976) by stodi.digitalkingdom.org with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1btOZq-000455-QZ for lojban-list-archive@lojban.org; Sun, 09 Oct 2016 17:36:28 -0700 Received: by mail-qk0-f188.google.com with SMTP id n189sf3663532qke.0 for ; Sun, 09 Oct 2016 17:36:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=sender: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-spam-checked-in-group :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=U2+pYouz8OmYMkoI8jJVl2GsYQ7DhdTgtf4Y3KMsmwM=; b=sZ/6GPQdszgIci0/X3n/HosDUF9109opFL7Vr6uPMAFZP66FNwyhD5mSw48VTOWEvl mSqSA1BY5tENyNhxsXBSA3FmzNgCNKbTW7E4U5W34Dnjwxv9x4e4K4+HkW8MxEWEHazO 7qaD3vLoKHQIcWP/mA71/GSremJ9PEPoXApT0BnMYTJG4FFiV7OGba0PEaOZMfnJk4Je ztmxkTvCFUxZu9AttrjeLmsP24QVXVdGctUGujNZtmOct94R/ydCLW5M5BHr4T38LZ5y YkAhzxAUxBRHm6aJjrCIsZJ6ZKXj6Qgx4XAvAc1MNcSDJrUTq+sFyuPbQDwpqCsxww2c g6Cw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=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-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=U2+pYouz8OmYMkoI8jJVl2GsYQ7DhdTgtf4Y3KMsmwM=; b=tQqulVcUr4NODrmyO8rpSFMSBiiTtcNczv+I6/3OhrB6n0ximG1v44qtQU19V4OPRR wlkbz3/Yt5wSVRCOigXrcbUAhwkbuF77ysamZq5B99/wztfQ/xtOhIdqlQ4BOBrYLdAD C8xAzLWjZEKSfDwJYG/ZjgolunrrmONKr7iuNnMkg8OGsVoZdlft7kYUQK2NXkLjgcxY AfW6Qk3eVWvBhpCqVnZJJrEM1lo4IarUPLHsmzsG+TWkzh2AoDQhmC7OXuLRTy2lct2y ydkWt1fFbb+m8vys08K1sNXf9stxlHY5kweELxP7Xr28Osf2FyLpTu8s8Fk1mgl/nrgw D1Cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=sender:x-gm-message-state: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-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=U2+pYouz8OmYMkoI8jJVl2GsYQ7DhdTgtf4Y3KMsmwM=; b=dQ/JINfugyloJV2rkQWkBZKtIkflYoLpK2qOsMXRMpYINyKGqizlUD7LmRoCdH/WW5 V3tF+U56kOo+p7u9Rga6oEXJC/tL89fkVSStyg6ZsJ9f+ZP7cBPJfd5GQ2cv91jn43Tj sAQIYyu7riCS4ffJ39pawbkVxV0fBe+2LE/YIKqaM7lrmV3T1Lw/HmIkHXHcR5Px41cY xHR5srswm99OkVffmT/fDXJ2eBZxCqdWC/oG80dXpvCsIpKfuDEDq51zHyZ/FAfTFclU /mkKB8m7iP7zVz3inhnjwAS8a1sAQGPBe7Av9ALMIijOl2qHSQqkwjqzbWfeqiGxY8+g L4sA== Sender: lojban@googlegroups.com X-Gm-Message-State: AA6/9RmjdP1RStK5MUZagq5x99j1bATECgl4cV8yqFqPnt4dEMD0lKRC+kdJOaNphe2khw== X-Received: by 10.36.50.145 with SMTP id j139mr302344ita.9.1476059776861; Sun, 09 Oct 2016 17:36:16 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.36.238.68 with SMTP id b65ls2711594iti.13.canary; Sun, 09 Oct 2016 17:36:15 -0700 (PDT) X-Received: by 10.107.146.9 with SMTP id u9mr7657975iod.66.1476059775474; Sun, 09 Oct 2016 17:36:15 -0700 (PDT) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com. [2607:f8b0:400d:c09::230]) by gmr-mx.google.com with ESMTPS id y17si963439ywy.1.2016.10.09.17.36.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Oct 2016 17:36:15 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2607:f8b0:400d:c09::230 as permitted sender) client-ip=2607:f8b0:400d:c09::230; Received: by mail-qk0-x230.google.com with SMTP id n189so87167224qke.0 for ; Sun, 09 Oct 2016 17:36:15 -0700 (PDT) X-Received: by 10.55.138.66 with SMTP id m63mr30530298qkd.159.1476059775070; Sun, 09 Oct 2016 17:36:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.38.226 with HTTP; Sun, 9 Oct 2016 17:36:14 -0700 (PDT) In-Reply-To: <99931644-56cd-b50f-401d-af57df7e64b0@gmx.de> References: <3cb1fc04-c3d0-3535-099e-30b8b120f219@gmx.de> <99931644-56cd-b50f-401d-af57df7e64b0@gmx.de> From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= Date: Sun, 9 Oct 2016 21:36:14 -0300 Message-ID: Subject: Re: [lojban] A Simpler Quantifier Logic (blog article) To: lojban@googlegroups.com Content-Type: multipart/alternative; boundary=94eb2c060f228f7c7f053e77f27e X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2607:f8b0:400d:c09::230 as permitted sender) smtp.mailfrom=jjllambias@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-Spam-Checked-In-Group: lojban@googlegroups.com X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.8 (-) X-Spam_score: -1.8 X-Spam_score_int: -17 X-Spam_bar: - --94eb2c060f228f7c7f053e77f27e Content-Type: text/plain; charset=UTF-8 On Sun, Oct 9, 2016 at 12:49 PM, selpahi wrote: > On 08.10.2016 02:23, And Rosta wrote: > >> >> Each argument place is either >> distributive or collective? Would you not also want an "unspecified as >> regards distributivity"? And wouldn't this mean that where the xorxesian >> underspecification of distributivity would have one predicate with, say, >> three argument places, yours would have 2^3 or 3^3 predicates? This >> looks so untenable that I conclude I must be misunderstanding you. >> > > This would indeed be untenable, but I do not believe that you need every > version of every predicate. For example, I believe that a distributive > {citka} is enough. Very often, a non-distributive version is either not > distinct from the distributive version, or includes some added meaning of > "doing it together while possibly some of them only watch" (things like > {kansi'u lo ka citka}). There is a lot more to be said here, but I'd rather > first hear any additional points from you. > I don't believe a distributive "citka" is all that useful. I want to be able to say "the children ate the whole cake" without having to introduce any roundabouts. It's also a simplification to say that there are only two kinds of distributivity (fully distributive and fully collective). Those are just the two extremes. In many cases we can have partial distributivity. For example, I can say "the children took the chairs to the garden", when one of the children took one chair, another one took two, and two other children took one chair together. If you make "take" distributive, you make it hard to say something simple like "the children took the chairs to the garden" when you don't know or don't care about how the action was distributed among children and chairs. If you say you can use the collective version for that, then you can use it for everything, since in that case "non-distributive" doesn't really mean "all together at once". > Unspecified distributivity in an argument place is a form of ambiguity at > the definitional level of a predicate. No, it's just a form of vagueness, where you don't specify what you don't want or need to specify. > It makes it very difficult to ever answer "what does it mean to {broda}", > because there are by definition multiple potentially non-overlapping > answers. That's true with or without distributivity. Very few predicates can be defined so precisely that they won't admit of multiple potentially non-overlapping definitions. (I cannot possibly count the hours that went into discussing {bevri lo > pipno} over the years without ever getting to a conclusion. This sort of > stuff is hard to sort out!) > But don't we already know what it means? At least to the extent that we can use it without creating any kind of confusion? Why wouldn't a definition similar to "support and move (someone or something) from one place to another." work? There are other ways (for example, in the realm of pragmatics) to deal with > vague distributivity, outside of the definition of argument places, and I > prefer those ways. I'm not too sure how stringent you want to be with defining distributivity into all predicate places. For some places it's reasonable that it be part of the definition of the predicate ("pavmei" might be an example). For other predicates, I don't see how forcing a fixed distributivity helps, since there are things that can just as well be done separately or together. mu'o mi'e xorxes -- 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 email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at https://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --94eb2c060f228f7c7f053e77f27e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Oct 9, 2016 at 12:49 PM, selpahi <seladwa@gmx.de> = wrote:
On 08.10.2016 02:23, And = Rosta wrote:

Each argument place is either
distributive or collective? Would you not also want an "unspecified as=
regards distributivity"? And wouldn't this mean that where the xor= xesian
underspecification of distributivity would have one predicate with, say, three argument places, yours would have 2^3 or 3^3 predicates? This
looks so untenable that I conclude I must be misunderstanding you.

This would indeed be untenable, but I do not believe that you need every ve= rsion of every predicate. For example, I believe that a distributive {citka= } is enough. Very often, a non-distributive version is either not distinct = from the distributive version, or includes some added meaning of "doin= g it together while possibly some of them only watch" (things like {ka= nsi'u lo ka citka}). There is a lot more to be said here, but I'd r= ather first hear any additional points from you.

<= /div>
I don't believe a distributive "citka" is all that = useful. I want to be able to say "the children ate the whole cake"= ; without having to introduce any roundabouts.

It&= #39;s also a simplification to say that there are only two kinds of distrib= utivity (fully distributive and fully collective). Those are just the two e= xtremes. In many cases we can have partial distributivity. For example, I c= an say "the children took the chairs to the garden", when one of = the children took one chair, another one took two, and two other children t= ook one chair together. If you make "take" distributive, you make= it hard to say something simple like "the children took the chairs to= the garden" when you don't know or don't care about how the a= ction was distributed among children and chairs. If you say you can use the= collective version for that, then you can use it for everything, since in = that case "non-distributive" doesn't really mean "all to= gether at once".=C2=A0
=C2=A0
Unspecified distributivity in an argument place is a form of ambiguity at t= he definitional level of a predicate.

No, i= t's just a form of vagueness, where you don't specify what you don&= #39;t want or need to specify.
=C2=A0
It m= akes it very difficult to ever answer "what does it mean to {broda}&qu= ot;, because there are by definition multiple potentially non-overlapping a= nswers.

That's true with or without dis= tributivity. Very few predicates can be defined so precisely that they won&= #39;t admit of multiple potentially non-overlapping definitions.
=
(I cannot possibly count the hours that went in= to discussing {bevri lo pipno} over the years without ever getting to a con= clusion. This sort of stuff is hard to sort out!)

=
But don't we already know what it means? At least to the ext= ent that we can use it without creating any kind of confusion? Why wouldn&#= 39;t a definition similar to "support and move (someone or something) from one plac= e to another." work?

There are other ways (for example, in the realm of pragmatics) to deal with= vague distributivity, outside of the definition of argument places, and I = prefer those ways.

I'm not too sure how= stringent you want to be with defining distributivity into all predicate p= laces. For some places it's reasonable that it be part of the definitio= n of the predicate ("pavmei" might be an example). For other pred= icates, I don't see how forcing a fixed distributivity helps, since the= re are things that can just as well be done separately or together.

mu'o mi'e xorxes

=

--
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= s://groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--94eb2c060f228f7c7f053e77f27e--