Received: from mail-qa0-f64.google.com ([209.85.216.64]:56014) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XnXJm-0007TP-8Z; Sun, 09 Nov 2014 10:34:38 -0800 Received: by mail-qa0-f64.google.com with SMTP id i13sf922469qae.29 for ; Sun, 09 Nov 2014 10:34:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=cd2YTvP3xwsw1E4XRvqbN99fMQb5ev6BwQF3GZOgkzU=; b=ZzYDbGUMQmE0hMUNxXUvtd6ERrGTUac5x+8fvOMH0oREK7iUPm6WNABWM7RYgIMyTI cIPEIz/RjmVYQtNByurrOlcgk6OauzX1sbN52tIOVtdaa2+aHG8o3qUbKedMjvvi7PBe wSHPN0bELQgWZmFi4ggOGOojyxk7wZ1oc+aHervIJrG1BCOiDg2DOaUOzYD0KI8IGY3s v7DCgeZTFAXRVkT8BVM/YTWnqQicmgilY3H8Cy30z6yOd3FUX3F3RN0rK+UM08uzEUq6 98r15Wb3nkDM1xE/3FCmI6mWbjS23hutTn4KqhOI2LCcFlK1VuWk9VXsIMV3VWq5gd2f mqQQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=cd2YTvP3xwsw1E4XRvqbN99fMQb5ev6BwQF3GZOgkzU=; b=dROwQRDfnvocA+K/mDqOvhLdm4i2JrhiDIRQUR6qZJjzoAzWN0M9SmxCcFSzvWhAbv /sChKxNgYN1AoQ+TdyT1FDFjp8b/J4qm5RvBVK4ercTeZ1byOPWN2YEI1CDzfQH3t8zE Gr2Vs6ATA/wHNQNOkkcjGU+iIjvqAEqdSK9KkuV17dkia1pHaT+ynO/jSg8XKRH9o48n j3Nsyo+beCzW5q3lBf3kA2j7Q32pOfsoFsGWDR4XmldWO5i0Sq7WCifFf+wO3QCeQu52 KGe563hPqevcoOBwJIyr2Z6gXZj6g85CeOYMTDNjcjWvWHlhmjEM/8jHjafxR/KeFbkk V7CA== X-Received: by 10.140.40.20 with SMTP id w20mr404677qgw.2.1415558063419; Sun, 09 Nov 2014 10:34:23 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.140.102.11 with SMTP id v11ls1583143qge.74.gmail; Sun, 09 Nov 2014 10:34:23 -0800 (PST) X-Received: by 10.140.19.110 with SMTP id 101mr3155qgg.9.1415558063283; Sun, 09 Nov 2014 10:34:23 -0800 (PST) Date: Sun, 9 Nov 2014 10:34:22 -0800 (PST) From: mukti To: bpfk-list@googlegroups.com Cc: ozymandias.haynes@gmail.com Message-Id: In-Reply-To: References: <20141018011419.GF12268@mercury.ccil.org> <97AABFB42A204E5D97A4EDFEA57A8508@gmail.com> <20141019012930.GF12991@mercury.ccil.org> <676B49242B0D4F6A986D6AFEA1EB3B3C@gmail.com> <20141019170808.GJ12991@mercury.ccil.org> <20141109004632.GL6360@mercury.ccil.org> Subject: Re: [bpfk] {ro}, existential import and De Morgan MIME-Version: 1.0 X-Original-Sender: shunpiker@gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_2550_108090981.1415558063010" X-Spam-Score: -2.0 (--) X-Spam_score: -2.0 X-Spam_score_int: -19 X-Spam_bar: -- Content-Length: 9410 ------=_Part_2550_108090981.1415558063010 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sunday, November 9, 2014 9:42:50 AM UTC-3, And Rosta wrote: > > 1. What does ro mean, and does it have EI? (A question settled a dozen=20 > years ago.) > 2. Should there be a non-EI universal quantifier? > 3. Should there be an EI universal quantifier? This is the question John= =20 > seems to be addressing.=20 > 4. In any bpfk revision of the CLL specification, which meaning should be= =20 > paired with the phonological form /ro/? > I believe that #1 and #4 are the question I'm trying to ask -- which=20 hopefully have the same answer -- and I'm sorry if I invited the detour=20 into other questions. CLL 16.8 says: sumti of the type =E2=80=9Cro da poi klama=E2=80=9D requires that there are= things which=20 =E2=80=9Cklama=E2=80=9D It's not entirely explicit in the section what the consequences when the=20 requirements of the sumti are not met. I have assumed that according to=20 this requirement, {ro da poi klama cu pavyseljirna} is then considered to= =20 be false in the case of {no da klama}. (If it has another truth value which= =20 is neither true nor false, then I'm barking up the wrong tree!) However, if such sentences are considered to be false, then the definition= =20 of {ro} is incompatible with the description of how negation boundaries=20 work. Supposing, for old time's sake, a universe without unicorns: {su'o pavyseljirna na ku cu blabi} =3D> There is at least one unicorn, such= =20 that it is not white. =3D> FALSE. Now we move the boundary, and "invert" the quantifier, while preserving the= =20 truth value of the statement: {na ku ro pavyseljirna cu blabi} =3D> It is not true that all unicorns are= =20 white. =3D> FALSE. But then we negate that and get: {ro pavyseljirna cu blabi} =3D> All unicorns are white. =3D> TRUE. The {ro} derived from these transformation is not one that "impl[ies] the= =20 corresponding existential claims". Either that definition of {ro} is=20 invalid, or the derivation of {ro} from {su'o} by moving negation=20 boundaries is. It's not just faulty examples at stake. The rules don't work= =20 together.=20 When I started this thread, I was under the impression that the BPFK=20 section on "Inexact Numbers"=20 took no clear= =20 position on this problem. I now see that there is indeed a commitment to=20 preserving the negation boundaries formula, although it is buried in the=20 formal definitions and obscured by bad formatting. The part I'm looking at= =20 is this: ro da =3D da'ano da =3D no da naku =3D naku su'o da naku If this definition holds, then {ro pavyseljirna cu blabi} has the same=20 truth value as {na ku su'o pavyseljirna na ku cu blabi}. If {ro} were held= =20 to import, then both sentences would be false. Wouldn't that commit us to= =20 hold the negation of the second sentence to be true? =20 {su'o pavyseljirna na ku cu blabi} =3D> "There is at least one unicorn, suc= h=20 that it is not white." If I have made a mistake in my reasoning, please point it out. Otherwise, I= =20 will assume that BPFK has settled questions #1 and #4 per the equivalence= =20 for {ro da} =3D=3D {naku su'o da naku} on the "Inexact Numbers" page. mi'e la mukti mu'o --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. ------=_Part_2550_108090981.1415558063010 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sunday, November 9, 2014 9:42:50 AM UTC-3, And Rosta wr= ote:

1. What does ro mean, and does it have EI? (A question settled a dozen year= s ago.)
2. Should there be a non-EI universal quantifier?
3. Should there be an EI universal quantifier? This is the question John se= ems to be addressing. 

4. In any bpfk revision of the CLL specificati= on, which meaning should be paired with the phonological form /ro/?

I believe that #1 and #4 are the question I'm trying to ask -= - which hopefully have the same answer -- and I'm sorry if I invited the de= tour into other questions.

CLL 16.8 says:

sumti of the type =E2=80=9Cro da poi klama=E2=80=9D requires th= at there are things which =E2=80=9Cklama=E2=80=9D
It's not entirely explicit in the section what the consequence= s when the requirements of the sumti are not met. I have assumed that accor= ding to this requirement, {ro da poi klama cu pavyseljirna} is then conside= red to be false in the case of {no da klama}. (If it has another truth valu= e which is neither true nor false, then I'm barking up the wrong tree!)

However, if such sentences are considered to be false= , then the definition of {ro} is incompatible with the description of how n= egation boundaries work. Supposing, for old time's sake, a universe without= unicorns:

{su'o pavyseljirna na ku cu blabi} =3D> T= here is at least one unicorn, such that it is not white. =3D> FALSE.

Now we move the boundary, and "invert" t= he quantifier, while preserving the truth value of the statement:

{na ku ro pavyseljirna cu blabi} =3D> It is not true that all= unicorns are white. =3D> FALSE.

B= ut then we negate that and get:

{ro pavyseljirna cu bla= bi} =3D> All unicorns are white. =3D> TRUE.
The {ro} derived from these transformation is not one that "im= pl[ies] the corresponding existential claims". Either that definition of {r= o} is invalid, or the derivation of {ro} from {su'o} by moving negation bou= ndaries is. It's not just faulty examples at stake. The rules don't work to= gether. 

When I started this thread, I was un= der the impression that the BPFK section on "Inexact Numbers" too= k no clear position on this problem. I now see that there is indeed a commi= tment to preserving the negation boundaries formula, although it is buried = in the formal definitions and obscured by bad formatting. The part I'm look= ing at is this:

ro da =3D da'ano da = =3D no da naku =3D naku su'o da naku

If this definition holds, then {r= o pavyseljirna cu blabi} has the same truth value as {na ku su'o pavyseljirna na ku cu blabi}. If {ro} were = held to import, then both sentences would be false. Wouldn't that commit us= to hold the negation of the second sentence to be true?  

{su'o pavyselji= rna na ku cu blabi} =3D> "There is at least one unicorn, such that it is= not white."

If I have made a = mistake in my reasoning, please point it out. Otherwise, I will assume that= BPFK has settled questions #1 and #4 per the equivalence for {ro da} =3D= =3D {naku su'o da naku} on the "Inexact Numbers" page.

=
mi'e la mukti mu'o

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