Received: from mail-vc0-f189.google.com ([209.85.220.189]:48738) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XavZ3-0007fj-Ua for lojban-list-archive@lojban.org; Sun, 05 Oct 2014 16:50:14 -0700 Received: by mail-vc0-f189.google.com with SMTP id hy10sf694295vcb.26 for ; Sun, 05 Oct 2014 16:50:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :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; bh=dxOfF5nPJ0HZRoxZ962tYpAI1xL7TbQVsFDNryVnk+E=; b=WsNhGGHfwXc7+hZwoyViBJASa7yOqivPMfqscSu5iW7IBTX90OhMjNWtx7cCL+6QCy MOyyf1TCQzy6G5/bDQoEkSpiqQEfTE1i2O1VxpBI1DJ+nJUO6YOYM665Kmqj9G7G9SpJ kQZPyCpYomS1uKgQMPPhHfRAGmCICS4SiMJWShFq+6z2zqF+SbUujQ2szLIacCS6G4q5 1Vnkmr3zJQMq2XCcIozLuc1J1UKiProrwG02exwOQU2szSiablMnxmdcxucOjYEZ4Rlx +cOkGUd/9y8MnfsSymUWRODyNtyLAIfNbqza7zF8zpWf8os39ZE9KyixDIY0bgCS+kxY Z0eQ== X-Received: by 10.140.34.208 with SMTP id l74mr211929qgl.1.1412553003314; Sun, 05 Oct 2014 16:50:03 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.91.230 with SMTP id z93ls1948489qgd.99.gmail; Sun, 05 Oct 2014 16:50:03 -0700 (PDT) X-Received: by 10.236.207.101 with SMTP id m65mr8737311yho.41.1412553002995; Sun, 05 Oct 2014 16:50:02 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id bj5si824792pdb.1.2014.10.05.16.50.02 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Oct 2014 16:50:02 -0700 (PDT) Received-SPF: none (google.com: mbays@sdf.org does not designate permitted sender hosts) client-ip=192.94.73.24; Received: from thegonz.net (d24-141-9-29.home.cgocable.net [24.141.9.29]) (authenticated (0 bits)) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s95Nnx13011619 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sun, 5 Oct 2014 23:50:00 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XavYs-00058v-SX for lojban@googlegroups.com; Sun, 05 Oct 2014 19:49:58 -0400 Date: Sun, 5 Oct 2014 19:49:58 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141005234958.GD1974@gonzales> References: <20140928013358.GB28734@gonzales> <20140928152915.GB7320@gonzales> <20141004141407.GG32481@gonzales> <20141005153531.GA1974@gonzales> <20141005214350.GC1974@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KdquIMZPjGJQvRdI" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: cumki User-Agent: Mutt/1.5.22 (2013-10-16) X-Original-Sender: mbays@sdf.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: mbays@sdf.org does not designate permitted sender hosts) smtp.mail=mbays@sdf.org 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: , X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --KdquIMZPjGJQvRdI Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2014-10-05 at 19:38 -0300 - Jorge Llamb=EDas : > On Sun, Oct 5, 2014 at 6:43 PM, Martin Bays wrote: > > * Sunday, 2014-10-05 at 14:10 -0300 - Jorge Llamb=EDas : > > > I guess "li mo'e sumti-6 te'u lo'o" has to be equivalent to "sumti-6", > > > but I don't know what happens when a quantifier or a logical > > > connective gets involved. Maybe "li mo'e ci ko'a" =3D "lo ci ko'a", a= nd > > > "li mo'e ko'a .e ko'e" =3D "ko'a jo'u ko'e". > > > > I don't see how you get those. I get: > > > > broda li mo'e ko'a e ko'e -> > > (broda( ,[{ko'a}]) /\ broda( ,[{ko'e}])) > > ge broda li mo'e ko'a te'u lo'o gi broda li mo'e ko'e te'u lo'o >=20 > That's assuming that "li mo'e ko'a .e ko'e" =3D "li mo'e ko'a je mo'e ko'= e" =3D > "li mo'e ko'a .e li mo'e ko'e". The second one is a parse error, but yes, I have the other two being equivalent. I wouldn't use anything like that as a derivation, though, it's just that I have logical sumti connection working the same way wherever the sumti occurs. > That would mean, for example, that "li (expression)" does not always refer > to the value of the expression but can be some operation transforming the > bridi in which it occurs as an argument. My take is that sumti-6 is > generally just a constant (or a function if it contains internally unbound > variables). I'm not sure if that's the correct interpretation, but it see= ms > to be the simplest. (There are also some weird cases like "ko", "ma", and > "zi'o" that need to be treated separately.) My take is that sumti-6 indeed returns a term, but in the process of parsing some logical operations may take effect. My way of thinking about this is entangled with the details of the Haskell implementation (monadic values), but I'll try to describe it in English! So {ro da} returns the variable which subsequent {da} will return, but it also causes a quantification; {ko'a .e ko'e} returns ko'a resp ko'e, but it also causes a fork in processing, each side getting one of the return values ko'a and ko'e, with the two sides then logically connected. For this to make sense, you need a way of interpreting these logical operations of quantification and connection. They apply in the obvious ways to propositions and to predicates, and I think we agree that this is how things work when parsing a sumti at main-bridi level or within a description. If I understand you correctly, you want special rules for what happens when we parse a sumti with such logical information during the parsing of a value: so rather than passing the actions of quantification and connection up to the logic, they should be caught at the level of the value and evaluated there. Right? I imagine that could be made to work, but I worry that any such rules for how the logical operations work on values would be rather arbitrary and non-obvious. Having them pass up and operate in the usual logical way seems much more natural to me. Something analogous happens with sumtcita. Do you consider broda ca ro da to mean something other than ro da zo'u broda ca da (which is how tersmu currently handles it)? > > > Uhoh. > > So are you saying that {lo plise} *always* refers to Apple? Such that > > it isn't really a matter of presuppositions after all, but rather of > > ensuring our universes are equipped with kinds? >=20 > I don't think so. What things are or are not in the universe of discourse > is a matter of interpretation, and doesn't really affect the logical form. OK, phew! > The presupposition is that when you use "lo plise" there's something you > are talking about, and that something is identified by their satisfying t= he > predicate "plise". Kinds may be one candidate interpretation, especially > with so little context. What is the logical content of this presupposition? Not actually a matter of uniqueness, presumably? Some sort of maximality? Martin --KdquIMZPjGJQvRdI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQx2SYACgkQULC7OLX7LNZP0ACdGuWf2KzvYJFxOwzo6OMiqg83 BWUAn0cRs+n8MQmuA8pTDMOYV5AlOIPp =52AF -----END PGP SIGNATURE----- --KdquIMZPjGJQvRdI--