Received: from mail-yx0-f189.google.com ([209.85.213.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PCyTG-0000Fo-12; Mon, 01 Nov 2010 10:47:07 -0700 Received: by yxe42 with SMTP id 42sf9880110yxe.16 for ; Mon, 01 Nov 2010 10:46:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:mime-version:received:received :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=x6SrUbSpRrjdA79gTx3aZ4NQ7KnKz7f0VkRKJQZKQNs=; b=Aiu5mmemF4xwkh7M/3L60x3yreYu6IcsE0wk8dpVrE1CAn79vCB+tyzabC7Nt38L9W QJsHhvwVXtkqveVkstp7jqnoa4Fup3rNkJMErRWjhf282i84gUS7/5qR3rUn2DsS3ryy 9s+BXqJKxi33ekpNUtI7h25AFzi8pJj2oKKq0= DomainKey-Signature: a=rsa-sha1; c=nofws; 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:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; b=PRDZS38eXH9lSXRgN852A/KwNACK1fyiQ4pHmqxvQbl9P/1cigALUj/ziEZ1+2FJ5P IEVDTtZBAN6t9Au62YItqZL0glKrCHhf22j0dzVi5PEneVLFzxmem5YX/iW4K/HLzs+V /9p5TyaFu/DaQKi8R/+czmtECtl89yJDue9gI= Received: by 10.90.5.26 with SMTP id 26mr10687age.48.1288633604935; Mon, 01 Nov 2010 10:46:44 -0700 (PDT) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.231.180.73 with SMTP id bt9ls2898964ibb.0.p; Mon, 01 Nov 2010 10:46:43 -0700 (PDT) Received: by 10.42.226.132 with SMTP id iw4mr327228icb.58.1288633603643; Mon, 01 Nov 2010 10:46:43 -0700 (PDT) Received: by 10.42.226.132 with SMTP id iw4mr327227icb.58.1288633603612; Mon, 01 Nov 2010 10:46:43 -0700 (PDT) Received: from mail-iw0-f169.google.com (mail-iw0-f169.google.com [209.85.214.169]) by gmr-mx.google.com with ESMTP id bm7si5889364ibb.2.2010.11.01.10.46.42; Mon, 01 Nov 2010 10:46:42 -0700 (PDT) Received-SPF: pass (google.com: domain of lukeabergen@gmail.com designates 209.85.214.169 as permitted sender) client-ip=209.85.214.169; Received: by mail-iw0-f169.google.com with SMTP id 38so6560901iwn.14 for ; Mon, 01 Nov 2010 10:46:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.33.203 with SMTP id i11mr13238148ibd.8.1288633601849; Mon, 01 Nov 2010 10:46:41 -0700 (PDT) Received: by 10.231.149.14 with HTTP; Mon, 1 Nov 2010 10:46:41 -0700 (PDT) In-Reply-To: References: <20101027160630.GD43996@alice.local> <2b585d63-1def-4797-8c75-453e66cac098@a37g2000yqi.googlegroups.com> <201010280843.15900.jezuch@interia.pl> <2327e11e-c10a-42d4-9e8f-bc3841fd75d9@j33g2000vbb.googlegroups.com> <20101028171348.GB45294@alice.local> <73ebebef-27b3-4093-8a32-1a66115a02c0@e14g2000yqe.googlegroups.com> Date: Mon, 1 Nov 2010 13:46:41 -0400 Message-ID: Subject: Re: [lojban-beginners] Re: mi kakne lo bajra From: Luke Bergen To: lojban-beginners@googlegroups.com X-Original-Sender: lukeabergen@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lukeabergen@gmail.com designates 209.85.214.169 as permitted sender) smtp.mail=lukeabergen@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: lojban-beginners@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=002215048feb158d780494016451 Content-Length: 12508 --002215048feb158d780494016451 Content-Type: text/plain; charset=ISO-8859-1 I think the complaint that "the gismu definition doesn't somehow mark the places as needing an event/property" is kind of like saying "the gismu definition for {skari} doesn't explicitly tell me that the x3 must be a volitional entity". It's in the semantics of the definitions that x3 of skari is a volitional entity, that the x2 of djica is an event, and that the x2 of djuno is a fact. It's not that {djuno}'s x2 has some hidden {du'u} that gets magically inserted into it, it's just that that's the kind of thing that's expected based on the definition. It's like saying "why doesn't it explicitly warn me that {gerku}'s x1 must be a dog for my sentences to make sense". It's kind of silly to say such a thing. x1 of gerku is expected to be a dog, x2 of djica is expected to be an event that is desired, and x2 of djuno is expected to be a fact (which is conveniently expressed with a {lo du'u}. You could just as easily say "mi djuno lo fatci be fa ...", but we have a shortcut of {du'u}). On Mon, Nov 1, 2010 at 1:38 PM, Adam Lopresto wrote: > On Fri, Oct 29, 2010 at 11:57 PM, Oren wrote: > > @Ian and Lindar: Let me rephrase this you don't seem to hear what I'm > saying. > > > > "1. It's written out in the definition very plainly. > > djuno - x1 knows fact(s) x2 (du'u) about subject x3 by epistemology > > x4." > > > > I don't just mean there's an issue with how the sumti are labelled in > > the gismu list. Those are trivial to modify. I mean there's no way of > > knowing what gismu have those ka's and nu's built into them, and which > > need them explicitly added in certain sumti positions. > > No way other than how they're labeled in the gismu list, or by reading > and understanding them. But again, I think the fundamental problem is > that it isn't that some have a {ka} or {nu} *built in*, it's that > they're of different types. > > > For example, take a look at nandu and bajra. > > > > { mi kakne lo bajra } is nonsensical > > { mi kakne lo nu bajra } is sensical > > Right. bajra1 is something that runs, {nu bajra kei}1 is an event. > kakne2 is an event, not something that runs. > > > { mi kakne lo nandu } is sensical > > { mi kakne lo nu nandu } (I assume) is nonsensical or overspecified. > > Yes. The definition of {nandu} probably should be rephrased to make it > more clear that nandu1 is an event (the thing you said you didn't have > trouble with). If we did define it as > > x1 (event) is difficult/hard/challenging for x2 (agent) under > conditions x3 (event/state) > > then would it make more sense to you? > > But again, the distinction between events and objects isn't a matter > of inserting keywords. Does it bother you that *{mi pinxe lo jubme} > would also be considered semantic nonsense, because tables aren't the > sort of thing that one can drink? > > > That is, while its true that "There are no conventional > > parts-of-speech distinctions like adjectives or nouns in Lojban," > > there are still undeniable semantic roles that we expect -- and reject > > -- from gismu when allocated to sumti placement. > > > > I think it's great that we all know from the definition that { se > > kakne } is an event/state (so it should have a nu), but I don't like > > that there are unwritten rules for which gismu have event/state built > > into them. For example, I wouldn't have anticipated the bajra/nandu > > discrepancy shown above. I wish for something like: > > > > bajra - is a process (pu'u), is a state (za'i) > > No! bajra1 is the runner. You can talk about a process of something > running {pu'u barja kei}, or a state of something running {za'i bajra > kei}, or an event of something running, but none of them are something > that runs. > > > nandu - is an event (nu) > > nandu1 is something that is difficult to do (and anything that can be > done is an event, in lojban terms). So nandu1 is limited to events. > Similarly, nandu2 is some agent that (could or would) attempt to do > the event in nandu1. Again, putting an explicit "(event)" into the > definition of {nandu} would be good. > > > See what I mean? > > I'm afraid I honestly don't, and I've tried. {lo bajra} is something > that fills the x1 of "x1 runs on surface x2 with limbs x3 and gait > x4". {lo kakne} is something that fills the x1 of "x1 can perform > action x2 under conditions x3". {lo se kakne} is something that can > fill the x2 thereof. {lo kakne ku bajra} makes sense (something that > can be capable can also run), but *{lo se kakne ku bajra} doesn't (an > event someone is capable of doing isn't the sort of thing that can > run; it has no legs at all!). > > -- > You received this message because you are subscribed to the Google Groups > "Lojban Beginners" group. > To post to this group, send email to lojban-beginners@googlegroups.com. > To unsubscribe from this group, send email to > lojban-beginners+unsubscribe@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/lojban-beginners?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Lojban Beginners" group. To post to this group, send email to lojban-beginners@googlegroups.com. To unsubscribe from this group, send email to lojban-beginners+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban-beginners?hl=en. --002215048feb158d780494016451 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I think the complaint that "the gismu definition doesn't somehow m= ark the places as needing an event/property" is kind of like saying &q= uot;the gismu definition for {skari} doesn't explicitly tell me that th= e x3 must be a volitional entity". =A0It's in the semantics of the= definitions that x3 of skari is a volitional entity, that the x2 of djica = is an event, and that the x2 of djuno is a fact.

It's not that {djuno}'s x2 has some hidden {du'u= } that gets magically inserted into it, it's just that that's the k= ind of thing that's expected based on the definition. =A0It's like = saying "why doesn't it explicitly warn me that {gerku}'s x1 mu= st be a dog for my sentences to make sense". =A0It's kind of silly= to say such a thing. =A0x1 of gerku is expected to be a dog, x2 of djica i= s expected to be an event that is desired, and x2 of djuno is expected to b= e a fact (which is conveniently expressed with a {lo du'u}. =A0You coul= d just as easily say "mi djuno lo fatci be fa ...", but we have a= shortcut of {du'u}).

On Mon, Nov 1, 2010 at 1:38 PM, Adam Loprest= o <adamlopre= sto@gmail.com> wrote:
On Fri, Oct 29, 2010 at 11:57 PM, Oren <get.oren@gmail.com> wrote:
> @Ian and Lindar: Let me rephrase this you don't seem to hear what = I'm saying.
>
> "1. It's written out in the definition very plainly.
> djuno - x1 knows fact(s) x2 (du'u) about subject x3 by epistemolog= y
> x4."
>
> I don't just mean there's an issue with how the sumti are labe= lled in
> the gismu list. Those are trivial to modify. I mean there's no way= of
> knowing what gismu have those ka's and nu's built into them, a= nd which
> need them explicitly added in certain sumti positions.

No way other than how they're labeled in the gismu list, or by re= ading
and understanding them. But again, I think the fundamental problem is
that it isn't that some have a {ka} or {nu} *built in*, it's that they're of different types.

> For example, take a look at nandu and bajra.
>
> { mi kakne lo bajra } is nonsensical
> { mi kakne lo nu bajra } is sensical

Right. bajra1 is something that runs, {nu bajra kei}1 is an event. kakne2 is an event, not something that runs.

> { mi kakne lo nandu } is sensical
> { mi kakne lo nu nandu } (I assume) is nonsensical or overspecified.
Yes. The definition of {nandu} probably should be rephrased to make i= t
more clear that nandu1 is an event (the thing you said you didn't have<= br> trouble with). If we did define it as

x1 (event) is difficult/hard/challenging for x2 (agent) under
conditions x3 (event/state)

then would it make more sense to you?

But again, the distinction between events and objects isn't a matter of inserting keywords. Does it bother you that *{mi pinxe lo jubme}
would also be considered semantic nonsense, because tables aren't the sort of thing that one can drink?

> That is, while its true that "There are no conventional
> parts-of-speech distinctions like adjectives or nouns in Lojban,"=
> there are still undeniable semantic roles that we expect -- and reject=
> -- from gismu when allocated to sumti placement.
>
> I think it's great that we all know from the definition that { se<= br> > kakne } is an event/state (so it should have a nu), but I don't li= ke
> that there are unwritten rules for which gismu have event/state built<= br> > into them. For example, I wouldn't have anticipated the bajra/nand= u
> discrepancy shown above. I wish for something like:
>
> bajra - is a process (pu'u), is a state (za'i)

No! bajra1 is the runner. You can talk about a process of something running {pu'u barja kei}, or a state of something running {za'i baj= ra
kei}, or an event of something running, but none of them are something
that runs.

> nandu - is an event (nu)

nandu1 is something that is difficult to do (and anything that can be=
done is an event, in lojban terms). So nandu1 is limited to events.
Similarly, nandu2 is some agent that (could or would) attempt to do
the event in nandu1. Again, putting an explicit "(event)" into th= e
definition of {nandu} would be good.

> See what I mean?

I'm afraid I honestly don't, and I've tried. {lo bajra} is some= thing
that fills the x1 of "x1 runs on surface x2 with limbs x3 and gait
x4". {lo kakne} is something that fills the x1 of "x1 can perform=
action x2 under conditions x3". {lo se kakne} is something that can fill the x2 thereof. {lo kakne ku bajra} makes sense (something that
can be capable can also run), but *{lo se kakne ku bajra} doesn't (an event someone is capable of doing isn't the sort of thing that can
run; it has no legs at all!).

--
You received this message because = you are subscribed to the Google Groups "Lojban Beginners" group.=
To post to this group, send email to lojban-beginners@googlegroups.com.
To unsubscribe from this group, send email to lojban-beginners+unsubscribe@googlegr= oups.com.
For more options, visit this group at http://groups.google.com/g= roup/lojban-beginners?hl=3Den.


--
You received this message because you are subscribed to the Google Groups "= Lojban Beginners" group.
To post to this group, send email to lojban-beginners@googlegroups.com.
To unsubscribe from this group, send email to lojban-beginners+unsubscribe@= googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban= -beginners?hl=3Den.
--002215048feb158d780494016451--