Received: from mail-bk0-f61.google.com ([209.85.214.61]:38623) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1W7EDX-0008B4-3l for lojban-list-archive@lojban.org; Sat, 25 Jan 2014 17:09:03 -0800 Received: by mail-bk0-f61.google.com with SMTP id d7sf558555bkh.26 for ; Sat, 25 Jan 2014 17:08:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=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:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=qXAH5utVoV3ZKMrN9gFEksERaX5dqcT8zzF00UdNi6k=; b=WVlHYrQBhBPZYulYtuCmF634XJGreTCwuyG8OTr5xVN6XjQRkT4iWfzNfpP924TvOB VD4uKOfhBBPzKoSTepgZTUeOvlK1W7SQijSPjn3Fwi5nYQtA2oUn4koKnHwfhT9e0R2Q xQncYQS3J1rZQsXKa5H6c1rWPhhUpTauAhoKO15Unmf+/b49BKonNk+ffFB/Vc5SWtZb wFyN4KjltlppgU3yWY5n8BlIPvjYri2weCj7mPC/8tgZDRSTZ9zDqSPpX5PUL054jfPZ ESATB9VKg6zf/RAeh6iNy6SSQ/rOCwBgfHEqfhTlv35v2zaFHvYxnRNWJxD/aS2haj8n 2s+w== X-Received: by 10.180.104.136 with SMTP id ge8mr174312wib.1.1390698527689; Sat, 25 Jan 2014 17:08:47 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.80.133 with SMTP id r5ls8110wix.32.canary; Sat, 25 Jan 2014 17:08:47 -0800 (PST) X-Received: by 10.180.11.41 with SMTP id n9mr7501439wib.2.1390698527045; Sat, 25 Jan 2014 17:08:47 -0800 (PST) Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [2607:f8b0:4001:c03::22f]) by gmr-mx.google.com with ESMTPS id w8si2000453bkn.0.2014.01.25.17.08.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 17:08:47 -0800 (PST) Received-SPF: pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c03::22f as permitted sender) client-ip=2607:f8b0:4001:c03::22f; Received: by mail-ie0-f175.google.com with SMTP id ar20so4306305iec.6 for ; Sat, 25 Jan 2014 17:08:45 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.154.102 with SMTP id vn6mr11266467igb.1.1390698525781; Sat, 25 Jan 2014 17:08:45 -0800 (PST) Received: by 10.64.223.168 with HTTP; Sat, 25 Jan 2014 17:08:45 -0800 (PST) In-Reply-To: <52E4544C.4080702@gmx.de> References: <52E449FD.90002@gmx.de> <52E4544C.4080702@gmx.de> Date: Sat, 25 Jan 2014 23:08:45 -0200 Message-ID: Subject: Re: [lojban] [oz] {binxo} From: =?ISO-8859-1?Q?Felipe_Gon=E7alves_Assis?= To: lojban@googlegroups.com X-Original-Sender: felipeg.assis@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c03::22f as permitted sender) smtp.mail=felipeg.assis@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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=047d7bd7581e9e787904f0d53bbe X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --047d7bd7581e9e787904f0d53bbe Content-Type: text/plain; charset=ISO-8859-1 On 25 January 2014 22:18, selpa'i wrote: > Sure, {co'a} is often enough, and I use it a lot myself. It just lacks the > sense of transformation that I get from {binxo}. > > I would say that {ro nu binxo lo ka broda cu nu co'a broda .i ku'i na ku > ro nu co'a broda cu nu binxo lo ka broda}. That is, to me, {binxo} is about > an experiencer undergoing a change (where experiencer should be understood > loosely in the thematic role sense. Certainly a binxo1 need not be > sentient); it is making a claim specifically about the binxo1. {co'a} on > the other hand just says that some event starts to occur, with no focus on > any of its parts. That's why I don't consider them the same, but as I said, > {co'a} is always true when {binxo} is, though not vice-versa. The > difference is often subtle or completely invisible, but sometimes it isn't. > > Hmmm... How would you compare then property-binxo and {co'a} to {co'arkai}? I feel that your experiencer has just a special place in the discourse, but otherwise no distinctive ontological characteristic... I do agree that object-binxo has a distinctive sense of transformation, which to me is to say that an object either comes to existence or ceases to exist. That is not only about ontological commitment (to me, you may divide the world in objects in more than one way), but it has implications on how you can use the objects in other sentences, for example, and it always has a salient rhetorical effect. 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. For more options, visit https://groups.google.com/groups/opt_out. --047d7bd7581e9e787904f0d53bbe Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 25 January 2014 22:18, selpa'i <seladwa@gmx.de> wrote:
Sure, {co'a} is often= enough, and I use it a lot myself. It just lacks the sense of transformati= on that I get from {binxo}.

I would say that {ro nu binxo lo ka broda cu nu co'a broda .i ku'i = na ku ro nu co'a broda cu nu binxo lo ka broda}. That is, to me, {binxo= } is about an experiencer undergoing a change (where experiencer should be = understood loosely in the thematic role sense. Certainly a binxo1 need not = be sentient); it is making a claim specifically about the binxo1. {co'a= } on the other hand just says that some event starts to occur, with no focu= s on any of its parts. That's why I don't consider them the same, b= ut as I said, {co'a} is always true when {binxo} is, though not vice-ve= rsa. The difference is often subtle or completely invisible, but sometimes = it isn't.


Hmmm... How would you compare th= en property-binxo and {co'a} to {co'arkai}? I feel that your experi= encer has just a special place in the discourse, but otherwise no distincti= ve ontological characteristic...

I do agree that object-binxo has a distinctive se= nse of transformation, which to me is to say that an object either comes to= existence or ceases to exist. That is not only about ontological commitmen= t (to me, you may divide the world in objects in more than one way), but it= has implications on how you can use the objects in other sentences, for ex= ample, and it always has a salient rhetorical effect.

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.
For more options, visit https://groups.google.com/groups/opt_out.
--047d7bd7581e9e787904f0d53bbe--