Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id DAA08647 for ; Mon, 26 Feb 1996 03:32:11 -0500 Message-Id: <199602260832.DAA08647@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id 4C9C0B67 ; Mon, 26 Feb 1996 2:55:07 -0500 Date: Sun, 25 Feb 1996 22:22:08 +0200 Reply-To: Veijo Vilva Sender: Lojban list From: Veijo Vilva Subject: Re: intemperate response to Lojbab on situational types X-To: lojban@cuvmb.cc.columbia.edu To: John Cowan X-Mozilla-Status: 0011 Content-Length: 1425 X-From-Space-Date: Mon Feb 26 10:39:47 1996 X-From-Space-Address: - > Date: Sun, 25 Feb 1996 17:44:51 +0000 > From: ucleaar > Subject: intemperate response to Lojbab on situation types [..] > > I have no idea what "ko'a mu'e" or "*ko'a pu'u" might mean > > They are both grammatical (as far as I know), and both have obvious > meanings. {koa mue} means "It is a point event abstraction" and {koa puu} > means "It is a process abstraction". If you look up NU in you cmavo > list you will find these two cmavo. {*ko'a mu'e} isn' grammatical. "mu'e", like any NU, must be followed by a sentence. {NU sentence /KEI/} is a selbri, while a lone NU isn't. {ko'a mu'e} parses as (ko'a VAU) -- "mu'e" is just trailing noise in this case. [..] > I realize that you have no problem viewing their act as lo za,i cinba. > That is precisely the problem. If {ti za,i} is true than {ti nuncinba} > is not (assuming {nuncinba} means "is a kiss"). {ti cinba za,i} or > {ti za,i zei cinba} might be fair descriptions. *{ti za'i} parses as (ti VAU) *{ti cinba za'i} parses as (ti VAU) {ti za'i ze'i cinba} is OK. It parses as (ti { VAU}) | sentence | | selbri | As za'i-events represent a subclass of the general nu-events, {ti za'i cinba} would seem to imply {ti nu cinba} -- {za'i} gives just a more precise characterization. co'o mi'e veion