Received: from mail-yk0-f192.google.com ([209.85.160.192]:43366) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Xataz-00075h-Jv for lojban-list-archive@lojban.org; Sun, 05 Oct 2014 14:44:06 -0700 Received: by mail-yk0-f192.google.com with SMTP id 9sf672871ykp.29 for ; Sun, 05 Oct 2014 14:43:55 -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=3CSBaqDDy9jOKqSp0lZr+6LH/ebXZUZ6RBqpuOYPwUI=; b=F0ezltj1DpBh7eAXyKwhvHiLAwejWhC2EW0sjr4xt1H0CBG8uOW9IquXJ4A0LBDDhh IGcYoAH4PXyvR51sb/725DB+WYguDtrx4h4QU9q889uw2+UUf/3Qr1Zwz0/otLto6rqc kHLZUu6mtZ3ELKMVUa1khGfWLKn2LoX7VAPsqqEoq5OWte1BgGatiGo/C401lzZAPMFO B9myAI4FvmKZB8JwbWJ4Mt6nD6hwkamOq795aZdup43yT2DkvfgXRw/n8limkXjX9eh8 jHwsdhyhQ3ZyUqMptS2smTgIiunFI/1tdz+kH+ASngKQirJjVQv+oiuQb/tOXtiBqukT GJaw== X-Received: by 10.50.122.2 with SMTP id lo2mr88839igb.4.1412545434945; Sun, 05 Oct 2014 14:43:54 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.13.40 with SMTP id e8ls2008614igc.7.canary; Sun, 05 Oct 2014 14:43:54 -0700 (PDT) X-Received: by 10.70.37.225 with SMTP id b1mr10048103pdk.1.1412545434542; Sun, 05 Oct 2014 14:43:54 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id hz1si1653549pbc.1.2014.10.05.14.43.54 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Oct 2014 14:43:54 -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 s95LhpCR007332 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Sun, 5 Oct 2014 21:43:52 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1Xatao-00048j-Fy for lojban@googlegroups.com; Sun, 05 Oct 2014 17:43:50 -0400 Date: Sun, 5 Oct 2014 17:43:50 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141005214350.GC1974@gonzales> References: <5349359c-f884-4976-a3e1-b0610eabeff6@googlegroups.com> <20140928013358.GB28734@gonzales> <20140928152915.GB7320@gonzales> <20141004141407.GG32481@gonzales> <20141005153531.GA1974@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L6iaP+gRLNZHKoI4" 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: - --L6iaP+gRLNZHKoI4 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2014-10-05 at 14:10 -0300 - Jorge Llamb=EDas : > On Sun, Oct 5, 2014 at 12:35 PM, Martin Bays wrote: >=20 > > * Saturday, 2014-10-04 at 13:07 -0300 - Jorge Llamb=EDas > > > Does it unwrap "li mo'e lo broda" in any way? > > Only in that it parses the sumti, yielding > > broda(c0); [Fragment: [c0]] > > cy no broda .i li mo'e cy no te'u lo'o >=20 > Shouldn't "li mo'e cy no te'u lo'o" reduce to "cy no"? Probably - but I'm considering performing such reductions a separate problem, one I'm ignoring for now. > 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", and > "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 broda li mo'e ko'a .e ko'e -> EQ(3) x1:(({ko'a}) >=3D (_)). broda( ,[x1]) ci da poi ke'a me ko'a me'u ku'o zo'u broda li mo'e da te'u lo'o > > Uhoh. > > So if there are five contextually relevant apples, you would never > > understand {lo plise goi ko'a} to be referring to just one of them? >=20 > How would I know which one? What if you could guess from context? e.g. only one is red, and I say {lo plise cu xunre}. You seem to be saying that this must involve a universe shift to exclude the other four? > I may perhaps understand it as referring to them as if they were one, i.e. > I could abstract away the different instances of Apple as I can abstract > away the temporal dimension and consider all the different temporal > instances as one, in cases where the different positions that Apple is > taking are not relevant. >=20 > No description will ever be enough to pick the referent out uniquely in an > absolute sense. The universe of discourse is not something that we have as > a given, it's something that we have to construct and negotiate as the > discourse proceeds. If you tell me that we already know for sure that the > universe of discourse contains five things that satisfy "plise", then I > would say that "lo pise" can only be "lo mu plise". 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? Martin --L6iaP+gRLNZHKoI4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQxu5YACgkQULC7OLX7LNbrTgCfc+j8Lz5pd0LdLUeja8oyJBDf mFIAn3PwOkQ9NDBs+YGN8NRaX6BBtOPw =OBpn -----END PGP SIGNATURE----- --L6iaP+gRLNZHKoI4--