Received: from mail-wg0-f61.google.com ([74.125.82.61]:63332) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XjGBb-0008JF-2b for lojban-list-archive@lojban.org; Tue, 28 Oct 2014 16:28:28 -0700 Received: by mail-wg0-f61.google.com with SMTP id a1sf140198wgh.6 for ; Tue, 28 Oct 2014 16:28:16 -0700 (PDT) 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=cFYTAttuMfkBLQ8rqEuksWnDpvsZN6a/Ql67VRdsNoQ=; b=q5VZVacAWdvd0k1v+4RqloF8tkj3bPnqUaiGgxg1nDR76YqUHNG7Qiqq/q04oUzcQy APdm5uaqdP7HOqCKFuDg/lHkznk/yOabvFNjaoL/e/fZiyE1r3e0WLx815oS76qRYN6F ZESlk1xJR0giLop+Lz1+97uphMQhOBdqT7CJ+5aCRcg/WLiEFRCtoCKBR3ZgGTvYbC3+ NtxX9NVQSdhj2wk+FTMwceZxqToIoqxoUlHKptjNyTiJ7vJGypGEtM2aScghjia7jfqi Buymsv9PwaqT000l/SMcskpJaccM2vmb0Q1smiX7GWMeVH1L+fM8HPQqKSoQAyV5Hv6h 1BXA== X-Received: by 10.152.1.67 with SMTP id 3mr35080lak.7.1414538896210; Tue, 28 Oct 2014 16:28:16 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.152.42.197 with SMTP id q5ls133596lal.39.gmail; Tue, 28 Oct 2014 16:28:14 -0700 (PDT) X-Received: by 10.112.225.135 with SMTP id rk7mr1110212lbc.6.1414538894777; Tue, 28 Oct 2014 16:28:14 -0700 (PDT) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com. [2a00:1450:400c:c05::229]) by gmr-mx.google.com with ESMTPS id ta1si773189wic.0.2014.10.28.16.28.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Oct 2014 16:28:14 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) client-ip=2a00:1450:400c:c05::229; Received: by mail-wi0-f169.google.com with SMTP id n3so242842wiv.4 for ; Tue, 28 Oct 2014 16:28:14 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.93.194 with SMTP id cw2mr7252634wjb.112.1414538894640; Tue, 28 Oct 2014 16:28:14 -0700 (PDT) Received: by 10.217.105.201 with HTTP; Tue, 28 Oct 2014 16:28:14 -0700 (PDT) In-Reply-To: <20141028022945.GA6097@gonzales> References: <20141018180946.GF20049@gonzales> <20141018233648.GA29040@gonzales> <20141021010639.GB11705@gonzales> <20141022002214.GD25753@gonzales> <20141022230855.GG2128@gonzales> <20141028022945.GA6097@gonzales> Date: Tue, 28 Oct 2014 20:28:14 -0300 Message-ID: Subject: Re: [lojban] Re: tersmu 0.2 From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) smtp.mail=jjllambias@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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=047d7bb04c18560cb60506840021 X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --047d7bb04c18560cb60506840021 Content-Type: text/plain; charset=UTF-8 On Mon, Oct 27, 2014 at 11:29 PM, Martin Bays wrote: > > I'm not sure that using {se} like this is robust, though. There's no > formal reason that > [BAI] gi bakni gi zajba > should be equivalent to > se [BAI] gi zajba gi bakni > , even if it often is, right? > Right, it would only work for BAIs that come from a selbri with events in (only) x1 and x2. I don't know what "pu'e gi broda gi brode" means, for example. Is it equivalent to "se pu'e gi brode gi broda", "te pu'e gi brode gi broda", "ve pu'e gi brode gi broda", something else? A lojban statement is interpreted as a proposition in the corresponding > logic, and by default the illocutionary force is to assert the truth of > the proposition. Often the assertion is spatiotemporally restricted, and > we can say that an event (of the proposition being true) is being > asserted to occur. Again, for this discussion I'll pretend (or note?) > that this is the only case to consider. > "Pretend" at most. In "ro namcu poi zmadu li re cu zmadu li pa .i se ni'i bo li ci noi zmadu li re cu zmadu li pa" there's probably no event involved. In lojban, and I suppose in human cognition, events are things. They can > be counted and measured in various ways, and can satisfy predicates. > Yes. A tag is interpreted as mapping an optional term to a modal operator > - something which takes formulae to formulae. The semantics of these > operators are highly miscellaneous; {ba}, {no roi}, {ja'e}, {bau} all > have quite distinct flavours. > Ideally we should be able to find common rules for families of tags, if not one rule for all of them. Now to return to tag connectives, and to correct some mistakes I made > earlier in this thread, let me first think through again the simple case > of {[tag] gi broda gi brodu}. > > Earlier I implied that this could be handled symmetrically, but that was > just wrong-headed; e.g. in {no roi gi broda gi brodu}, we're claiming an > event of broda occurs, but not so for brodu. > Must we be claiming an event of broda occurs though? Without any context, I'd tend to read it as very generic, something like "never when it brodas it brodus", or more likely in Enlish "it never brodus when it brodas", which doesn't really claim that an event of broda occurs. So it must be something like > "an event E of broda occurs; {[tag] E brodu}". > > I think it must actually be: > [tag] gi broda gi brodu > <=> su'o da tu'e da fasnu gi'e nu broda .i [tag] da brodu > , or maybe that but with {su'oi} in place of {su'o}. > (For this to make sense, {fasnu} must behave the with respect to > tense the way "occurs" does, e.g. an event which occurred in the past > fasnued then but doesn't fasnu now.) > Evidence for this being the right thing: we can rule out any "lo-style" > semantics, where some definite nu broda are involved, by considering how > the construction works in negated scope: > na ba gi broda gi brodu > should make sense, and be true, if no events of broda occur. "It is not the case that after it brodas, it brodus". I agree that no event of broda need occur, but that's not the same as saying that we cannot talk of generic/kind "lo nu broda". > So {lo ge > nu broda gi fasnu} can't be involved, nor is it about a specific > contextually specified nu broda, nor the kind, nor anything similar that > I can think of. > I don't see that. My first interpretation would be something like "na ku lo nu brodu cu balvi lo nu broda". Universal quantification would be silly. So by elimination of the other > natural choices, it has to be existential quantification. > That's the kind of reasoning that led to making "su'o" a default quantifier for "lo". I think postulating a hidden "su'o" is generally a bad idea. In particular, {broda .i brodu [tag] lo nu broda} may be a handy > shorthand reformulation, but it isn't actually equivalent. > I'm now not too sure that forethought and afterthought tag connectives are completely equivalent, because given "broda .i (ku'i) no roi bo brodu" I would want to read it as "it brodas, (but) never when it brodus". But that's because I see broda as a separate sentence in the afterthought case, but not in the forethought case. It's hard not to see broda as being asserted in the afterthought case. > Now: > > broda .i [jek tag] bo brode > > -> broda .i [jek] brode [(se} tag] lo nu xu kau broda > . For simplicity, let's assume the tag is a tense (so there's no {se}). > It seems the rules for tenses are quite different than the rules for most tags: (1) broda .i ba bo brode -> broda .i ba la'e di'u brode (2) broda .i no roi bo brode -> broda .i go'i no roi lo nu brode In other words, "tag bo" only affects the reading of the second connectand, or so it seems to me at this point, and tenses affect it in a different way than most other tags. > Again, if this is to work in embedded scopes, I think we need to recast > it in terms of quantification over events. > > Annoyingly, I can't see a way to do that that's uniform over the > possible jeks. But e.g. for {jo}, I guess it would have to be: > da zo'u ge da fasnu > gi ga ge da nu broda gi [tag] da brode > gi ge da nu na broda gi [tag] da na brode > > Is that faithful to your intention? Let's see, this would be my current thinking: carvi i jo glare It rains iff it's warm. carvi .i jo ba bo glare It rains iff later it's warm. (Either it rains and then later it's warm, or else it doesn't rain and then later it isn't warm.) carvi .i jo no roi bo glare It rains iff never when it's warm. (Either it rains but never when it's warm, or it doesn't rain but at least once when not warm.) > I don't really know how this kind of use of q-kau works, > but I'm guessing it jumps scope like actual questions do, so can't > really be used here for this kind of thing. > I use "xu kau" as the tautology operator. A word in NA would be better, "ja'a ja na", if it were grammatical. mu'o mi'e xorxes -- 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/d/optout. --047d7bb04c18560cb60506840021 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Mon, Oct 27, 2014 at 11:29 PM, Martin Bays <mbays@sdf.org> wr= ote:

I'm not sure that using {se} like this is robust, though. There's n= o
formal reason that
=C2=A0 =C2=A0 [BAI] gi bakni gi zajba
should be equivalent to
=C2=A0 =C2=A0 se [BAI] gi zajba gi bakni
, even if it often is, right?

Right, it= would only work for BAIs that come from a selbri with events in (only) x1 = and x2. I don't know what "pu'e gi broda gi brode" means,= for example. Is it equivalent to "se pu'e gi brode gi broda"= , "te pu'e gi brode gi broda", "ve pu'e gi brode gi = broda", something else?


A lojban statement is interpreted as a proposition in the corresponding
logic, and by default the illocutionary force is to assert the truth of
the proposition. Often the assertion is spatiotemporally restricted, and we can say that an event (of the proposition being true) is being
asserted to occur. Again, for this discussion I'll pretend (or note?) that this is the only case to consider.

"Pretend" at most. In "ro namcu poi zmadu li re cu zmadu li= pa .i se ni'i bo li ci noi zmadu li re cu zmadu li pa" there'= s probably no event involved.

In lojban, and I suppose in human cognition, events are things. They can be counted and measured in various ways, and can satisfy predicates.

Yes.=C2=A0

A tag is interpreted as mapping an optional term to a modal operator
- something which takes formulae to formulae. The semantics of these
operators are highly miscellaneous; {ba}, {no roi}, {ja'e}, {bau} all have quite distinct flavours.

Ideally w= e should be able to find common rules for families of tags, if not one rule= for all of them.=C2=A0

Now to return to tag connectives, and to correct some mistakes I made
earlier in this thread, let me first think through again the simple case of {[tag] gi broda gi brodu}.

Earlier I implied that this could be handled symmetrically, but that was just wrong-headed; e.g. in {no roi gi broda gi brodu}, we're claiming a= n
event of broda occurs, but not so for brodu.

Must we be claiming an event of broda occurs though? Without any cont= ext, I'd tend to read it as very generic, something like "never wh= en it brodas it brodus", or more likely in Enlish "it never brodu= s when it brodas", which doesn't really claim that an event of bro= da occurs.=C2=A0

So it must be something like
=C2=A0 =C2=A0 "an event E of broda occurs; {[tag] E brodu}".

I think it must actually be:
=C2=A0 =C2=A0 [tag] gi broda gi brodu
=C2=A0 =C2=A0 <=3D> su'o da tu'e da fasnu gi'e nu broda .= i [tag] da brodu
, or maybe that but with {su'oi} in place of {su'o}.=C2=A0

(For this to make sense, {fasnu} must behave the with respect to
tense the way "occurs" does, e.g. an event which occurred in the = past
fasnued then but doesn't fasnu now.)

Evidence for this being the right thing: we can rule out any "lo-style= "
semantics, where some definite nu broda are involved, by considering how the construction works in negated scope:
=C2=A0 =C2=A0 na ba gi broda gi brodu
should make sense, and be true, if no events of broda occur.

"It is not the case that after it brodas, it brodus&= quot;. I agree that no event of broda need occur, but that's not the sa= me as saying that we cannot talk of generic/kind "lo nu broda".= =C2=A0
=C2=A0
So {lo ge
nu broda gi fasnu} can't be involved, nor is it about a specific
contextually specified nu broda, nor the kind, nor anything similar that I can think of.

I don't see that. M= y first interpretation would be something like "na ku lo nu brodu cu b= alvi lo nu broda".=C2=A0

Universal quantification would be silly. So by elimination of the other
natural choices, it has to be existential quantification.
<= div>
That's the kind of reasoning that led to making &quo= t;su'o" a default quantifier for "lo". I think postulati= ng a hidden "su'o" is generally a bad idea.

In particular, {broda .i brodu [tag] lo nu broda} may be a handy
shorthand reformulation, but it isn't actually equivalent.

I'm now not too sure that forethought and after= thought tag connectives are completely equivalent, because given "brod= a .i (ku'i) no roi bo brodu" I would want to read it as "it b= rodas, (but) never when it brodus". But that's because I see broda= as a separate sentence in the afterthought case, but not in the forethough= t case. It's hard not to see broda as being asserted in the afterthough= t case.
=C2=A0
Now:
> broda .i [jek tag] bo brode
> -> broda .i [jek] brode [(se} tag] lo nu xu kau broda
. For simplicity, let's assume the tag is a tense (so there'= s no {se}).

It seems the rules for tens= es are quite different than the rules for most tags:=C2=A0

(1) broda .i ba bo brode -> broda .i ba la'e di'u brode=
(2) broda .i no roi bo brode -> broda .i go'i no roi lo n= u brode

In other words, "tag bo" only af= fects the reading of the second connectand, or so it seems to me at this po= int, and tenses affect it in a different way than most other tags.=C2=A0
=C2=A0
Again, if this is to work in embedded scopes, I think we need to recast
it in terms of quantification over events.

Annoyingly, I can't see a way to do that that's uniform over the possible jeks. But e.g. for {jo}, I guess it would have to be:
=C2=A0 =C2=A0 da zo'u ge da fasnu
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 gi ga ge da nu broda gi [tag] da = brode
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0gi ge da nu na broda= gi [tag] da na brode

Is that faithful to your intention?

Let'= ;s see, this would be my current thinking:

carvi i= jo glare
It rains iff it's warm.=C2=A0

<= div>carvi .i jo ba bo glare
It rains iff later it's warm.
(Either it rains and then later it's warm, or else it doesn'= t rain and then later it isn't warm.)
=C2=A0
carvi = .i jo no roi bo glare
It rains iff never when it's warm.
(Either it rains but never when it's warm, or it doesn't rain= but at least once when not warm.)=C2=A0
=C2=A0
I don't really know how this kind of use of q-kau works,
but I'm guessing it jumps scope like actual questions do, so can't<= br> really be used here for this kind of thing.

=
I use "xu kau" as the tautology operator. A word in NA would= be better, "ja'a ja na", if it were grammatical.
= =C2=A0
mu'o mi'e xorxes

<= /div>

--
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+unsub= scribe@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 http= s://groups.google.com/d/optout.
--047d7bb04c18560cb60506840021--