Received: from mail-ye0-f185.google.com ([209.85.213.185]:54575) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1U4V9I-0000Q9-5O; Sun, 10 Feb 2013 03:33:06 -0800 Received: by mail-ye0-f185.google.com with SMTP id l3sf1810527yen.12 for ; Sun, 10 Feb 2013 03:32:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :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=K/VDajBzM/ZjVeF/7IlHWciNZXBDpPqC647QYPRqAbU=; b=Fa5e/+bySf7C/T9Qqq/iIemEgFullyGaO0QjtdIvuenEp0UpAoyhdRHKvkFfQSRFrl pMB56Z1VdxjgZxHOj9zpEaNoEUshPVqk7f1/qdyPn9aOmFv6n1zqJdysFUFSyyHW4SNJ S82TGiWLpcODDSopwGaTabRGiOIILdiZcflMUe4vr/xtKn1j+t6VIo9FlFB6Ep8OpP2C SF6/9GYMC8EKR8ASsRg4kKvdcwl1F5q5SeN6HlIdKgFJABncEZN2HM90X4g8gJNQv0D3 wQ6piVkGYC95XV2k74O9qOenSqor0g1wiybLoWi85laPuap17SsxEYISQYtuIITJbB5W r7LQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :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=K/VDajBzM/ZjVeF/7IlHWciNZXBDpPqC647QYPRqAbU=; b=HqC7yVbkIyo1UWR07ptP284ZXDZZGyooj4x8pvVupAltXlAtoHlRNRO7C5dojZguoI t1US58joXdyI0DpC9Zq7aEsRkza4HUg9vJfcM+ng9z6OVVRXmZqvKro8uvnzCCenfh+X r6zKtCBJuRhs2yCEHeuAI1zd3V/SxZa448wYtLFZubRcgV5qp8F7M3dfi+0S86QLcqRT wpdMXx6gcPhARHS9+fBW694/ieu+eA3nPwB3aowdkQTVyybU6wSJrvUvUArfM0Eo0lLG wjyaXqTva25RtCTxXWL6CM3mt9a7T3JJ5upds06B9G6Jl6sIQt9ljcFr79tU43HMunIW A4lQ== X-Received: by 10.49.15.100 with SMTP id w4mr787579qec.26.1360495955711; Sun, 10 Feb 2013 03:32:35 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.2.225 with SMTP id 1ls1557262qex.77.gmail; Sun, 10 Feb 2013 03:32:34 -0800 (PST) X-Received: by 10.49.1.43 with SMTP id 11mr771238qej.29.1360495954069; Sun, 10 Feb 2013 03:32:34 -0800 (PST) Date: Sun, 10 Feb 2013 03:32:32 -0800 (PST) From: la gleki To: lojban@googlegroups.com Message-Id: <710074ba-dfaa-4789-b735-37122a78b1d5@googlegroups.com> In-Reply-To: References: <84d88820-8c7d-436b-a0cc-222666747afd@googlegroups.com> <2625542.LcrIRrlWQu@caracal> <0c6ecd5d-9e9b-4180-b719-c92d16a4bdfa@googlegroups.com> Subject: Re: [lojban] strange behaviour of {cortu} MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@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="----=_Part_73_4862496.1360495952768" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_73_4862496.1360495952768 Content-Type: text/plain; charset=ISO-8859-1 On Saturday, February 9, 2013 9:08:46 PM UTC+4, .asiz. wrote: > > On 9 February 2013 13:50, la gleki > > wrote: > > > > > > On Saturday, February 9, 2013 6:21:29 PM UTC+4, .asiz. wrote: > >> > >> I still don't see the problem. And, while I agree with most of tsani's > >> stance on use > >> of abstractions, I think he went too far here. The locus of pain IS a > >> concrete object, > >> and the fact that it is usually described with a part-whole relation > >> doesn't mean that > >> it has to be always like that. Consider > >> {mi cortu lo xunre} > >> > > > > Well, he said he was semi-serious. Next, IMO this is not lojban but a > > dialect of it. Lastly, this shows how this problem could be solved. > > > > Again, I don't see the problem. Restricting cortu2 to involve a > part-of-body > relation would be a problem. Of course. I didn't suggest that. The problem is that two arbitrary sumti from one jufra may not be equal. E.g. there can be semi-abstractions like in the case with {mi kakne lo ka citka lo plise} where {kakne2} mustn't contain anything but this semi-abstraction where one inner sumti is automatically replicated from kakne1. This is something that just wasn't built into the design of Lojban. That's why such questions as "I don't see a problem" arise (e.g. long long ago I used to think that all languages must have verbs and nouns, which Lojban proved wrong to me). Saying that unfilled places are {zo'e} and can be easily derived from context makes Lojban not so intuitive for computers because they don't know this context. In fact it just suggests that Lojban is a normal natlangish conlang. Of course there are no problems perceived by humans in ordinary "vulgar" speech. The problem is that Lojban is too loose in allowing what can be inside abstraction-sumti ({mi kakne lo nu do citka lo plise} is still gendra although absolutely nalsmudra). A fix to this problem might sound like this. *The first unfilled place of the first brivla inside {cortu2} is automatically assumed to be filled with {ce'u} which refers to {cortu1}. so that we have {mi cortu lo stedu [be ce'u]} or {mi cortu ti} that has no places to be filled.* * * *For other nesting brivla similar to {cortu} {ce'u} can refer to other non-x1 places of nesting brivla. Those places are to be specially marked in updated definitions of those brivla for maximum clarity for computers.* Obviously this is 100% backward compatible with the current Lojban. > The current {mi cortu lo xunre}, {mi cortu ti}, > {mi cortu lo se janli} wouldn't be easily expressible, just to mention the > first few that come up to my mind. > > > I can't say that I like such solution, it's a bit awkward but shows the > > idea. > > > > Non-problem, non-solution. > > mu'o > mi'e .asiz. > -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@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. ------=_Part_73_4862496.1360495952768 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Saturday, February 9, 2013 9:08:46 PM UTC+4, .asiz. wrote:On 9 February 2013 13:50, la gleki &= lt;gleki.is...@gmail.com> wrote:
>
>
> On Saturday, February 9, 2013 6:21:29 PM UTC+4, .asiz. wrote:
>>
>> I still don't see the problem. And, while I agree with most of= tsani's
>> stance on use
>> of abstractions, I think he went too far here. The locus of pa= in IS a
>> concrete object,
>> and the fact that it is usually described with a part-whole re= lation
>> doesn't mean that
>> it has to be always like that. Consider
>>   {mi cortu lo xunre}
>>
>
> Well, he said he was semi-serious. Next, IMO this is not lojban bu= t a
> dialect of it. Lastly, this shows how this problem could be solved= .
>

Again, I don't see the problem. Restricting cortu2 to involve a part-of= -body
relation would be a problem.

Of course.= I didn't suggest that. The problem is that two arbitrary sumti from one ju= fra may not be equal.
E.g. there can be semi-abstractions like in= the case with {mi kakne lo ka citka lo plise} where {kakne2} mustn't conta= in anything but this semi-abstraction where one inner sumti is automaticall= y replicated from kakne1. This is something that just wasn't built into the= design of Lojban. That's why such questions as "I don't see a problem" ari= se (e.g. long long ago I used to think that all languages must have verbs a= nd nouns, which Lojban proved wrong to me). Saying that unfilled places are= {zo'e} and can be easily derived from context makes Lojban not so intuitiv= e for computers because they don't know this context. In fact it just sugge= sts that Lojban is a normal natlangish conlang. Of course there are no prob= lems perceived by humans in ordinary "vulgar" speech.
The problem= is that Lojban is too loose in allowing what can be inside abstraction-sum= ti ({mi kakne lo nu do citka lo plise} is still gendra although absolutely = nalsmudra).

A fix to this problem might sound like= this.

The first unfilled place of the first br= ivla inside {cortu2} is automatically assumed to be filled with {ce'u} whic= h refers to {cortu1}. so that we have {mi cortu lo stedu [be ce'u]} or {mi = cortu ti} that has no places to be filled.

<= div>For other nesting brivla similar to {cortu} {ce'u} can refer to othe= r non-x1 places of nesting brivla. Those places are to be specially marked = in updated definitions of those brivla for maximum clarity for computers.

Obviously this is 100% backward compatible with= the current Lojban.

 
The current {mi cortu lo xunre}, {mi cortu ti}= ,
{mi cortu lo se janli} wouldn't be easily expressible, just to mention = the
first few that come up to my mind.

> I can't say that I like such solution, it's a bit awkward but show= s the
> idea.
>

Non-problem, non-solution.

mu'o
mi'e .asiz.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
------=_Part_73_4862496.1360495952768--