Received: from mail-iy0-f189.google.com ([209.85.210.189]:44563) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RND2K-0006Gk-U5; Sun, 06 Nov 2011 16:26:13 -0800 Received: by iage36 with SMTP id e36sf9010537iag.16 for ; Sun, 06 Nov 2011 16:25:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to:x-pgp-key :x-pgp-keyid:x-cunselcu'a-valsi:user-agent:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe; bh=Z0Khtn8PK7iKYr54qPB4UTSoZleSxGtw+ULCdSW08CY=; b=ODlCDVxf8HF7l9J21qN6jx+aC4epqXMQhtTXml6PfKh+VuedOiNsZeL3bh0zmSrSWm izAj0wve5Uru71Ilb8QABlJQTKpAXH/D2nAn5E7Z01eC4hLbSIay0RNgw7HLMalSWrKF Li1W1LEhfvJjCSPYxxVtjua5X9NSyLQ8jI+j8= Received: by 10.50.155.169 with SMTP id vx9mr3063538igb.12.1320625555881; Sun, 06 Nov 2011 16:25:55 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.231.63.137 with SMTP id b9ls13397088ibi.0.gmail; Sun, 06 Nov 2011 16:25:55 -0800 (PST) Received: by 10.42.155.2 with SMTP id s2mr38084004icw.5.1320625555110; Sun, 06 Nov 2011 16:25:55 -0800 (PST) Received: by 10.42.155.2 with SMTP id s2mr38084002icw.5.1320625555099; Sun, 06 Nov 2011 16:25:55 -0800 (PST) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.19]) by gmr-mx.google.com with ESMTPS id l3si14197531pbd.0.2011.11.06.16.25.55 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Nov 2011 16:25:55 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of mbays@sdf.org designates 192.94.73.19 as permitted sender) client-ip=192.94.73.19; Received: from gonzales.homelinux.org (root@sverige.freeshell.org [192.94.73.4]) by sdf.lonestar.org (8.14.5/8.14.3) with ESMTP id pA70Prhs012153 for ; Mon, 7 Nov 2011 00:25:54 GMT Received: from martin by gonzales.homelinux.org with local (Exim 4.75) (envelope-from ) id 1RNCgn-0000nb-1y for lojban@googlegroups.com; Sun, 06 Nov 2011 19:03:49 -0500 Date: Sun, 6 Nov 2011 19:03:49 -0500 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] self-referential goi Message-ID: <20111107000348.GA17040@gonzales> References: <20111106215741.GD2703@gonzales> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: rirni User-Agent: Mutt/1.5.21 (2010-09-15) X-Original-Sender: mbays@sdf.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of mbays@sdf.org designates 192.94.73.19 as permitted sender) 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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , X-Spam-Score: -0.0 (/) X-Spam_score: -0.0 X-Spam_score_int: 0 X-Spam_bar: / --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sunday, 2011-11-06 at 19:58 -0300 - Jorge Llamb=EDas : > On Sun, Nov 6, 2011 at 6:57 PM, Martin Bays wrote: > > I thought this was cute, and it seems to be allowed by the BPFK section > > definition of {goi}: > > > > {ko'a goi li pa lo'o ce'o ko'a ce'o ke li re lo'o ce'o ko'a zo'u pa > > cimni je terkancu cu mleca lo se zilkancu be lu'i ko'a} > > > > It's the continuum hypothesis ;) >=20 > I don't really quite know how either "lu'i" or "ce'o" are meant to work, = but... >=20 > Assuming ko'a is a set, wouldn't "lu'i ko'a" be a singleton, and so > "lo se zilkancu be lu'i ko'a" be just one? >=20 > And doesn't ko'a have only three members: 1, ko'a, {2, ko'a}? Well, I was making up semantics for {lu'i} and {ce'o} which make this work. Probably I shouldn't do that. The goi phrase was meant to be read as A =3D=3D ((1,A),(2,A)) . As for lu'i... actually, I guess it doesn't work. Also there's no reason that A should be the *smallest* infinite binary tree, which is needed for the continuum hypothesis bit. Anyway, the real point was that self-referential goi is cool. If anyone can see an actual use for them, that would be even cooler. This does raise the more important question of how {ce} and {ce'o} should work. If we want {.a bu ce'o by ce'o cy} to get (a,b,c), doesn't that involve following LISP et al and defining (a,b,c) =3D <,c>? And if we want {.a bu ce by ce cy} to get {a,b,c}, rather that {{a,b},c}, doesn't that involve blatant cheating? Is this what "considered jointly" in the bpfk definitions is meant to handle? It doesn't seem very clear. Maybe it would be cleaner to explicitly have a ce b :=3D a \cup {b} if A is a set {a,b} otherwise , and similarly for ce'o? --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk63IGQACgkQULC7OLX7LNYuVQCgkbq5fxowPaFtFfN7CS6e0tRn /bsAn1+0Qtcqr7rkajfvlIizfTeXCI1p =HgPW -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--