From lojban-out@lojban.org Wed Nov 06 13:42:02 2002 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 6 Nov 2002 21:41:59 -0000 Received: (qmail 53143 invoked from network); 6 Nov 2002 21:41:57 -0000 Received: from unknown (66.218.66.217) by m9.grp.scd.yahoo.com with QMQP; 6 Nov 2002 21:41:57 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta2.grp.scd.yahoo.com with SMTP; 6 Nov 2002 21:42:00 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.05) id 189Xw0-00088D-00 for lojban@yahoogroups.com; Wed, 06 Nov 2002 13:42:00 -0800 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.05) id 189Xvu-00087r-00; Wed, 06 Nov 2002 13:41:54 -0800 Received: with ECARTIS (v1.0.0; list lojban-list); Wed, 06 Nov 2002 13:41:53 -0800 (PST) Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root) by digitalkingdom.org with esmtp (Exim 4.05) id 189Xvp-00087h-00 for lojban-list@lojban.org; Wed, 06 Nov 2002 13:41:49 -0800 Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1]) by cs6668125-184.austin.rr.com (8.12.3/8.12.3) with ESMTP id gA6LlaiR063012 for ; Wed, 6 Nov 2002 15:47:36 -0600 (CST) (envelope-from fracture@cs6668125-184.austin.rr.com) Received: (from fracture@localhost) by cs6668125-184.austin.rr.com (8.12.3/8.12.3/Submit) id gA6LlaaT063011 for lojban-list@lojban.org; Wed, 6 Nov 2002 15:47:36 -0600 (CST) Date: Wed, 6 Nov 2002 15:47:36 -0600 To: lojban-list@lojban.org Subject: [lojban] Re: importing ro Message-ID: <20021106214736.GA62605@allusion.net> References: <3DC92B49.9060908@newmail.net> <20021106154952.GA60620@allusion.net> <3DC95DD8.9050509@newmail.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <3DC95DD8.9050509@newmail.net> User-Agent: Mutt/1.4i X-archive-position: 2468 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: fracture@allusion.net Precedence: bulk X-list: lojban-list X-eGroups-From: Jordan DeLong From: Jordan DeLong Reply-To: fracture@allusion.net X-Yahoo-Group-Post: member; u=116389790 X-Yahoo-Profile: lojban_out --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 06, 2002 at 08:22:16PM +0200, Adam Raizen wrote: > la djorden. cusku di'e [...] > >"naku ro pavyseljirna cu blabi" is not a true statement, because > >it makes more claims than you are giving it credit for, and you > >only contradicted one of them. In fact, it's not even a true > >statement with a nonimporting universal quantifier, if we keep our > >negation boundary rules unchanged (more on this below). >=20 > "naku ro pavyseljirna xirma cu blabi" is the negation of "ro=20 > pavyseljirna xirma cu blabi", and so one of them must be true and the=20 > other false; that is simply the definition of negation. If ro has=20 > existential import, as the book seems to claim at first glance, then "ro= =20 > pavyseljirna xirma cu blabi" is false, and its negation is true. This is= =20 > not just Logic, but also what CLL says (15.2): "The most important rule=20 > about bridi negation is that if a bridi is true, its negation is false,=20 > and vice versa." [twice, a few paragraphs apart] (bridi negation is=20 > demonstrated to be putting 'na' in front of the selbri, which is=20 > elsewhere explained to be equivalent to putting 'naku' before the whole=20 > bridi.) Like I said, you're only negating one of the bridi. > >It should be noted, btw, that: > > > > no pavyseljirna cu blabi > > > >is a false statement because no imports also, since it can be moved > >around. >=20 > If it is indeed false, then either 'su'o pavyseljirna' is not importing=20 > (probably not the best option), or 'no pavyseljirna' !=3D 'naku su'o=20 > pavyseljirna', which is extremely counterintuitive, no matter how=20 > intuitive an importing ro might be. With a *nonimporting* ro, naku ro pavyseljirna !=3D su'o pavyseljirna naku (and the book says this is equal). I think you misunderstood what I said about "no". "no da" imports if "ro da" imports, because of the negation boundary rules: no pavyseljirna =3D=3D naku su'o da poi pavyseljirna =3D=3D ro da poi pavyseljirna ku'o naku This supports AndR's view that it isn't *ro* that imports (i.e. ro can =3D 0 in things like lo'i [ro] broda, which is both useful and intuitive), but it's the "da" which is present in the "ro da" claims which imports. None of this contradicts itself, *or* (more importantly) the book (which is consistent here, though not fully explained). > >Actually the more I think about this the more I like importing > >universals for lojban. Take a look at the generalization of what > >you were talking about: > > > > naku ro da poi gerku cu broda > > > >Now; imagine that ro *doesn't* import. The above sentence, then, > >can't have the negation boundary moved: > > > > su'o da poi gerku naku broda > > > >which claims there is at least one gerku. >=20 > If ro doesn't import, then your first sentence would use an importing=20 > "not all", since with the empty set for the set of gerku the sentence=20 > without "naku" is vacuously true, and thus its negation would be false.=20 > Therefore, there is no problem with equating that with the second=20 > sentence; both are importing. So with a nonimporting "ro da" we'd keep "naku ro da ..." as importing? This is a lot less elegant than the way AndR suggests, which is consistant with the book and quite usable (it allows "roda" to import while also allowing "lo'i broda" to refer to an empty set). > >So what's really going on is what AndR says here, I think: It is > >"da" that imports, not ro. Which is both consistent with book and > >makes sense (and i'm even starting to like it better than nonimporting > >foo). >=20 > It can be made consistent, but then we would have to drop the ability to= =20 > move negation across quantifiers while switching the quantifier, which=20 > is also inconsistent with the book. You have yet to show any inconsistency. Just repeating that one is there doesn't do much. --=20 Jordan DeLong - fracture@allusion.net lu zo'o loi censa bakni cu terzba le zaltapla poi xagrai li'u sei la mark. tuen. cusku --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9yY34DrrilS51AZ8RAr1QAJ4l4/l8NWsKGI0jund3jfTD1DdvnQCgnWyz ArzOe9srzkbhz5p3LQvbWCo= =pA10 -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--