Received: from mail-we0-f188.google.com ([74.125.82.188]:35443) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TyUet-00041B-JN; Thu, 24 Jan 2013 13:48:51 -0800 Received: by mail-we0-f188.google.com with SMTP id t44sf264518wey.5 for ; Thu, 24 Jan 2013 13:48:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf :x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to: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:content-type; bh=BiunYLd8IZ0Hxz8JcsFIIo39+OE2CO71JeqxKDTNU3U=; b=AQiKn87NZsnmGNH9wvF8Tyf9q1TOyyxbk/nfdr0ysiR3263USQ50CkOllGbB/lrGIL SlqsTYGB9URu3+1tpqEuKIm/eGDZ2TovRlj6FZ8Yb6H5dcXQ9t+Bvh1NfMu9zVfOks9n RGpsgZNTFEq4nQByODFAJjVMq0yTs7QZl3W+w5Lb5oZuzH0t8RXyJi76m7Q0EEbXGfFI jboC5oOtkv9T5i2SZ8IW0e5iN458rEtepaOuq3n8XBUdaV/s/gGQtoihcB6sFc7hfFIy pzSFpAoRdoKzEmV6fGRp3rP5ZD6MhU+yNf1dnjgPTRNymjsVmp/0agp6Gwxwn+2z8WFp Y4wQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:x-received:received-spf :x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to: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:content-type; bh=BiunYLd8IZ0Hxz8JcsFIIo39+OE2CO71JeqxKDTNU3U=; b=JljOuoVoqe7MEkDJ/e9tFE9/oV7ozzFDyzIIHcbox/Nqz/mFZ8DX45FwyiVDEY25zf k5NVcNr7edpuAm2r9t6ka4iK4xk4bt+tBl4zNwUDxpgqsCeCdfNJnBweL/Nb2awQYGV5 Qwohg08Yd8+FDSXfU221OCKO+bJLvLAajhM8jv80GjLAtxpdV706ykOURNnODv6OmK/1 +HPbx20hSE2DSh16nsL73D3Mtw5rY0/38b3UIxX3Pgxi3smBP7bh/F+HvZtUr/xcMRJm 9aSB8z3khKhkBRAP3S6jxb0kaa16xE8qqG+E3ewtgdknhFFkYW+vo0XyML6QuFDju+Ja q0Yg== X-Received: by 10.180.94.194 with SMTP id de2mr942624wib.2.1359064101219; Thu, 24 Jan 2013 13:48:21 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.77.133 with SMTP id s5ls802869wiw.35.canary; Thu, 24 Jan 2013 13:48:19 -0800 (PST) X-Received: by 10.204.146.25 with SMTP id f25mr194298bkv.1.1359064099536; Thu, 24 Jan 2013 13:48:19 -0800 (PST) X-Received: by 10.204.146.25 with SMTP id f25mr194297bkv.1.1359064099510; Thu, 24 Jan 2013 13:48:19 -0800 (PST) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by gmr-mx.google.com with ESMTPS id 14si411127bky.0.2013.01.24.13.48.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 13:48:19 -0800 (PST) Received-SPF: pass (google.com: domain of nictytan@gmail.com designates 209.85.217.182 as permitted sender) client-ip=209.85.217.182; Received: by mail-lb0-f182.google.com with SMTP id gg6so7470151lbb.13 for ; Thu, 24 Jan 2013 13:48:19 -0800 (PST) X-Received: by 10.152.144.164 with SMTP id sn4mr3136045lab.57.1359064099105; Thu, 24 Jan 2013 13:48:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.68.46 with HTTP; Thu, 24 Jan 2013 13:47:59 -0800 (PST) In-Reply-To: References: From: Jacob Errington Date: Thu, 24 Jan 2013 16:47:59 -0500 Message-ID: Subject: Re: [lojban] Re: Advanced Place Stucture Mangling To: lojban@googlegroups.com X-Original-Sender: nictytan@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nictytan@gmail.com designates 209.85.217.182 as permitted sender) smtp.mail=nictytan@gmail.com; dkim=pass header.i=@gmail.com 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: , Content-Type: multipart/alternative; boundary=e89a8f22c4afdaad3f04d40fc4f2 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --e89a8f22c4afdaad3f04d40fc4f2 Content-Type: text/plain; charset=ISO-8859-1 On 24 January 2013 16:07, ianek wrote: > I'm sure I've talked about this here before. > It's true that {da de broda be di} is equivalent to {da broda di de}, but > it's not true that {broda be di} has different place structure than > {broda}. It's just that the second place is already filled, so {de} takes > the next unoccupied place. Meanwhile, {da fe de broda be di} is equivalent > to {da broda de fe di}, so there are two sumti for the second place > (possibly equivalent to {da broda de jo'u di} or something). > At least that's how it is now, I'm not sure whether you're talking about > current Lojban or proposing new things. > > I don't know if you could really call it "the way Lojban is now" because stuff like this is extremely rare. What I'm trying to do here is provide a comprehensive analysis of what happens on the selbri level when linked arguments are used. The conclusion that I reached is that {be} is a selbri operator much like {se} that will indeed *modify* the place structure. {broda} and {se broda} are indeed different selbri, even though one is clearly derived from the other. Similarly, {broda be ko'a} and {broda} are *different* selbri. (I have put parentheses around the selbri in places where isolating it aids comprehension.) With that said, it shouldn't be unusual that the place structures be different. Because using {be} drops a place from the structure, the other places should move forward. {ko'a ko'e (broda be fo'a)} is equivalent to {ko'a (broda be fo'a) ko'e} because we are allowed to move sumti from the head into the tail freely. The sumti that are linked directly into the sumti are invisible to the formal structure sumti. This becomes more obvious when we isolate the selbri and write this out in {me'au} notation. {me'au} is an experimental cmavo that allows function abstractions (i.e. {ka}-abstractions) to become selbri. e.g. {mi do (me'au lo ka ce'u cinba ce'u)} -> {mi cinba do} (Formally, {me'au} is of selma'o ME.) Do demonstrate the effect of be operating on a selbri level, using me'au helps, such that {broda be ko'a} as a selbri is equivalent to {lo ka [ce'u] broda ko'a [ce'u] ...} Therefore, {.i fo'a fo'e (broda be ko'a)} -> {.i fo'a fo'e (me'au lo ka ce'u broda ko'a ce'u)} Using {fe} on the top level therefore has no effect, as it is operating on the formal place filling level and not the selbri-internal level, where {ko'a} resides in the example just above. {.i fo'a fe fo'e (broda be ko'a)} -> {.i fo'a fe fo'e (me'au lo ka ce'u broda ko'a ce'u)} which is equivalent to {.i fo'a fo'e me'au lo ka ce'u broda ko'a ce'u}. The {fe} indeed has no effect of double-assigning a place, in this case. Another way of looking at it would be to say that using be moves the sumti directly into the selbri, which is outside the scope of top-level FA. Even if at this point it were still debatable, saying that it causes double assignment would be less productive, I think, as double assignment in general is unuseful. (I don't think it's entirely pointless; it's one solution to the problem of using {sei} and splitting quotes: {.i lu coi pendo li'u selsku lo verba fa lu .i do mo li'u}) .i mi'e la tsani mu'o -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. Visit this group at http://groups.google.com/group/lojban?hl=en. For more options, visit https://groups.google.com/groups/opt_out. --e89a8f22c4afdaad3f04d40fc4f2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 24 January 2013 16:07, ianek <janek37@gmail.com> wrote:
I'm sure I've talked about this here before.
It's true that = {da de broda be di} is equivalent to {da broda di de}, but it's not tru= e that {broda be di} has different place structure than {broda}. It's j= ust that the second place is already filled, so {de} takes the next unoccup= ied place. Meanwhile, {da fe de broda be di} is equivalent to {da broda de = fe di}, so there are two sumti for the second place (possibly equivalent to= {da broda de jo'u di} or something).
At least that's how it is now, I'm not sure whether you're talk= ing about current Lojban or proposing new things.


I don't know if you could really call it "the= way Lojban is now" because stuff like this is extremely rare. What I&= #39;m trying to do here is provide a comprehensive analysis of what happens= on the selbri level when linked arguments are used. The conclusion that I = reached is that {be} is a selbri operator much like {se} that will indeed *= modify* the place structure. {broda} and {se broda} are indeed different se= lbri, even though one is clearly derived from the other. Similarly, {broda = be ko'a} and {broda} are *different* selbri.=A0

(I have put parentheses around the selbri in places whe= re isolating it aids comprehension.)

With that sai= d, it shouldn't be unusual that the place structures be different. Beca= use using {be} drops a place from the structure, the other places should mo= ve forward. {ko'a ko'e (broda be fo'a)} is equivalent to {ko= 9;a (broda be fo'a) ko'e} =A0because we are allowed to move sumti f= rom the head into the tail freely. The sumti that are linked directly into = the sumti are invisible to the formal structure sumti. This becomes more ob= vious when we isolate the selbri and write this out in {me'au} notation= . {me'au} is an experimental cmavo that allows function abstractions (i= .e. {ka}-abstractions) to become selbri.

e.g. {mi do (me'au lo ka ce'u cinba ce'u)} = -> {mi cinba do}
(Formally, {me'au} is of selma'o ME.)=

Do demonstrate the effect of be operating on a se= lbri level, using me'au helps, such that {broda be ko'a} as a selbr= i is equivalent to {lo ka [ce'u] broda ko'a [ce'u] ...}

Therefore, {.i fo'a fo'e (broda be ko'a)} -= > {.i fo'a fo'e (me'au lo ka ce'u broda ko'a ce'= u)}
Using {fe} on the top level therefore has no effect, as it is= operating on the formal place filling level and not the selbri-internal le= vel, where {ko'a} resides in the example just above.
{.i fo'a fe fo'e (broda be ko'a)} -> {.i fo'a fe fo= 'e (me'au lo ka ce'u broda ko'a ce'u)} which is equival= ent to {.i fo'a fo'e me'au lo ka ce'u broda ko'a ce'= ;u}. The {fe} indeed has no effect of double-assigning a place, in this cas= e. Another way of looking at it would be to say that using be moves the sum= ti directly into the selbri, which is outside the scope of top-level FA. Ev= en if at this point it were still debatable, saying that it causes double a= ssignment would be less productive, I think, as double assignment in genera= l is unuseful. (I don't think it's entirely pointless; it's one= solution to the problem of using {sei} and splitting quotes: {.i lu coi pe= ndo li'u selsku lo verba fa lu .i do mo li'u})

.i mi'e la tsani mu'o

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
--e89a8f22c4afdaad3f04d40fc4f2--