Received: from mail-ee0-f61.google.com ([74.125.83.61]:33657) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RbB8m-0007Wh-Oq; Thu, 15 Dec 2011 05:14:33 -0800 Received: by eekc4 with SMTP id c4sf1822535eek.16 for ; Thu, 15 Dec 2011 05:14:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from: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=ajdCulkpNzWtcdJ+AcmX2Y0u/s9MCYYSCnqmhhp8DLg=; b=zVvGgtrRQ8wLM9EKNgy8S5t9KGZaqGIpUx7t03f+d7mLNyHbxbDz/7F7V1ZeSYMhsg NXySBOZ0XtC5RZqgMgv91Rt9xaWVWwlHSB+pRbyWCMZNsDFFEHjAqQXdUjucZqgM/1Z0 GcH5dTcyZDhQS131Ma16JB1o2xTXzONJgmrWw= Received: by 10.204.130.219 with SMTP id u27mr511691bks.20.1323954857276; Thu, 15 Dec 2011 05:14:17 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.14.124.66 with SMTP id w42ls283195eeh.6.canary; Thu, 15 Dec 2011 05:14:16 -0800 (PST) Received: by 10.14.4.161 with SMTP id 33mr645690eej.5.1323954856244; Thu, 15 Dec 2011 05:14:16 -0800 (PST) Received: by 10.14.4.161 with SMTP id 33mr645689eej.5.1323954856219; Thu, 15 Dec 2011 05:14:16 -0800 (PST) Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by gmr-mx.google.com with ESMTPS id q50si4304252eef.3.2011.12.15.05.14.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Dec 2011 05:14:16 -0800 (PST) Received-SPF: pass (google.com: domain of mturniansky@gmail.com designates 74.125.83.43 as permitted sender) client-ip=74.125.83.43; Received: by eekd4 with SMTP id d4so839884eek.2 for ; Thu, 15 Dec 2011 05:14:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.10.80 with SMTP id o16mr912193bko.13.1323954856045; Thu, 15 Dec 2011 05:14:16 -0800 (PST) Received: by 10.205.44.199 with HTTP; Thu, 15 Dec 2011 05:14:16 -0800 (PST) In-Reply-To: References: Date: Thu, 15 Dec 2011 08:14:16 -0500 Message-ID: Subject: Re: [lojban] state of {binxo} From: Michael Turniansky To: lojban@googlegroups.com X-Original-Sender: mturniansky@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mturniansky@gmail.com designates 74.125.83.43 as permitted sender) smtp.mail=mturniansky@gmail.com; dkim=pass (test mode) 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=0015175cd80ae4ad3f04b421427b X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --0015175cd80ae4ad3f04b421427b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Personally, I think that what is being discussed here is, yeah, metaphysics, despite Felipe's assertion to the contrary, and therefore, as John said, beyond the scope of what lojban chooses to define. And therefore, I am loath to get into the discussion. But, I was curious as to why this discussion didn't involve (and to my mind, should have in many places), binxo's sister valsi, farvi. After all, we are still dealing with something changing, explicitly FROM something (farvi3=3Dbinxo1) TO somethin= g (farvi2=3Dbinxo2), and yet, has some kind of eternal existence outside of those two endpoints (farvi1), and passes through as many stages as we wsih (farvi4), while still keeping its farvi1 identity. ta lo tsiju lo tricu ci'i da cu farvi. Does the existence of farvi inform your questions about binxo any, Felipe? --gejyspa On Tue, Dec 13, 2011 at 4:41 AM, tijlan wrote: > On 12 December 2011 14:05, Ian Johnson wrote: > > On Fri, Dec 9, 2011 at 7:27 AM, tijlan wrote: > >> > >> 2011/12/8 Felipe Gon=E7alves Assis : > >> > Not trying to amend {binxo}, just to clarify its implications. > >> > >> The Lojban grammar treats properties differently from non-abstract > >> objects. We cannot conventionally say {lo bisli} and imply that it's > >> {lo ka bisli}. If we decided that binxo2 be "an acquired property" to > >> be attributed to binxo1, that would be a new definition with a > >> mandatory NU, and currently valid expressions like {lo djacu cu binxo > >> lo bisli} would no longer be grammatical. > > > > > > Er, no; the grammar has no idea about what types of things different > sumti > > are. You can put properties and concrete sumti in the same places in an= y > > selbri grammatically. What you're talking about is a sort of low level > > semantics that is beneath most other semantics, namely what sorts of > things > > can do what, that is to say {ka'e} statements. > > A language's semantics can be considered part of the language's > grammar. Right use of Lojban requires right knowledge of its semantics > among other things. > > What types of things different sumti are, are sparsely defined. muvdu1 > is "object", jinzi1 "property", and so on; bisli1 currently lacks such > specification, not because it can be either an object or a property > but because people haven't bothered to write the definition in an > optimally consistent fashion. The grammar, in the broad sense, does > have as much ideas about what place can have what kind of sumti as > they are defined or commonly understood: it may not validate {lo muvdu > cu jinzi mi} if it isn't some metaphorical expression. Likewise, {lo > djacu cu binxo lo bisli} can be grammatical or ungrammatical depending > on the consensus the community may have over binxo2 and bisli1 as well > as other places. > > > 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. > For more options, visit this group at > http://groups.google.com/group/lojban?hl=3Den. > > --=20 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@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den. --0015175cd80ae4ad3f04b421427b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
=A0 Personally, I think that what is being discussed here = is, yeah, metaphysics, despite Felipe's assertion to the contrary, and = therefore, as John said, beyond the scope of what lojban chooses to define.= And therefore, I am loath to get into the discussion. But, I was curious a= s to why this discussion didn't involve (and to my mind, should have in= many places), binxo's sister valsi, farvi. =A0After all,=A0we are stil= l dealing with something changing, explicitly FROM something (farvi3=3Dbinx= o1) TO something (farvi2=3Dbinxo2), and yet, has some kind of eternal exist= ence outside of those two endpoints (farvi1), and passes through as many st= ages as we wsih (farvi4), while still keeping its farvi1 identity. =A0ta lo= tsiju lo tricu ci'i da cu farvi. =A0 Does the existence of farvi infor= m your questions about binxo any, Felipe?

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 --gejyspa

= On Tue, Dec 13, 2011 at 4:41 AM, tijlan <jbotijlan@gmail.com> wrote:
On 12 December 2011 14:05,= Ian Johnson <blindbravado@gma= il.com> wrote:
> On Fri, Dec 9, 2011 at 7:27 AM, tijlan <jbotijlan@gmail.com> wrote:
>>
>> 2011/12/8 Felipe Gon=E7alves Assis <felipeg.assis@gmail.com>:
>> > Not trying to amend {binxo}, just to clarify its implications= .
>>
>> The Lojban grammar treats properties differently from non-abstract=
>> objects. We cannot conventionally say {lo bisli} and imply that it= 's
>> {lo ka bisli}. If we decided that binxo2 be "an acquired prop= erty" to
>> be attributed to binxo1, that would be a new definition with a
>> mandatory NU, and currently valid expressions like {lo djacu cu bi= nxo
>> lo bisli} would no longer be grammatical.
>
>
> Er, no; the grammar has no idea about what types of things different s= umti
> are. You can put properties and concrete sumti in the same places in a= ny
> selbri grammatically. What you're talking about is a sort of low l= evel
> semantics that is beneath most other semantics, namely what sorts of t= hings
> can do what, that is to say {ka'e} statements.

A language's semantics can be considered part of the language'= ;s
grammar. Right use of Lojban requires right knowledge of its semantics
among other things.

What types of things different sumti are, are sparsely defined. muvdu1
is "object", jinzi1 "property", and so on; bisli1 curre= ntly lacks such
specification, not because it can be either an object or a property
but because people haven't bothered to write the definition in an
optimally consistent fashion. The grammar, in the broad sense, does
have as much ideas about what place can have what kind of sumti as
they are defined or commonly understood: it may not validate {lo muvdu
cu jinzi mi} if it isn't some metaphorical expression. Likewise, {lo djacu cu binxo lo bisli} can be grammatical or ungrammatical depending
on the consensus the community may have over binxo2 and bisli1 as well
as other places.


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@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojba= n?hl=3Den.


--
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@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--0015175cd80ae4ad3f04b421427b--