Received: from mail-vb0-f61.google.com ([209.85.212.61]:39721) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T3TZp-0006Ca-HR; Mon, 20 Aug 2012 08:07:50 -0700 Received: by vbzb23 with SMTP id b23sf6471290vbz.16 for ; Mon, 20 Aug 2012 08:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :x-ymail-osg:x-mailer:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=mcQKvtGzsdyv8nlI+GPKBkdoBYoVbhGd+cHT4uhHli8=; b=RKLDnzbjzlBdxoEHh/Pns5y9L+HvjtKlqLPGXggLLlXgY+9ShEu1+qqcIuxP0BIqd7 a6CWAAplOQbOffcGb/eA2T+4SupDsF4Z/+ZsHWuh0tRvP1YOJnoKBRcpSOf0sitoxeKd ZbYjP51EVUYcPB5Ni3xk74y+QGdG2ANIfYf1Q= Received: by 10.52.67.71 with SMTP id l7mr1614929vdt.12.1345475250712; Mon, 20 Aug 2012 08:07:30 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.100.72 with SMTP id ew8ls4306512vdb.9.gmail; Mon, 20 Aug 2012 08:07:30 -0700 (PDT) Received: by 10.58.91.100 with SMTP id cd4mr1660604veb.8.1345475250009; Mon, 20 Aug 2012 08:07:30 -0700 (PDT) Received: by 10.58.91.100 with SMTP id cd4mr1660603veb.8.1345475249983; Mon, 20 Aug 2012 08:07:29 -0700 (PDT) Received: from nm30.bullet.mail.ac4.yahoo.com (nm30.bullet.mail.ac4.yahoo.com. [98.139.52.227]) by gmr-mx.google.com with SMTP id c10si1640398vdu.1.2012.08.20.08.07.29; Mon, 20 Aug 2012 08:07:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.139.52.227 as permitted sender) client-ip=98.139.52.227; Received: from [98.139.52.188] by nm30.bullet.mail.ac4.yahoo.com with NNFMP; 20 Aug 2012 15:07:29 -0000 Received: from [68.142.200.227] by tm1.bullet.mail.ac4.yahoo.com with NNFMP; 20 Aug 2012 15:07:29 -0000 Received: from [66.94.237.98] by t8.bullet.mud.yahoo.com with NNFMP; 20 Aug 2012 15:07:29 -0000 Received: from [127.0.0.1] by omp1003.access.mail.mud.yahoo.com with NNFMP; 20 Aug 2012 15:07:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 428507.31018.bm@omp1003.access.mail.mud.yahoo.com Received: (qmail 92931 invoked by uid 60001); 20 Aug 2012 15:07:28 -0000 X-YMail-OSG: 0kbfTEEVM1mdD3psa1JdDpkg.WLHoT_58aJ9JXEU_ZOWKJ3 1Hej8p8AbqEDeEjBY65wuHEMhAcH3I_SfZl1xDfp11vRdOfXIAMb7NQ2xEXN tWMUU1B7.VKnNedHw8Gf7Oa6esw4fIhT0rWjB_fhLwsHdyY1aGTbKV3mUbYK cCoZAsRkc6bTOXp6_QmT1nLQqP5AfxNG7asCkK0rDzFgrbl2bAD4UECXqfe9 IvMEzCfEkipOUduQszpFd6TLpHVDbF8pjrLpL5BenCdJPB2oNmBZ1hjgcOqn mqHFGuthyHQJ64QqPYc.fW5dDoAwvGB8rfalRjJZyOu7K_8yHiID92vm62K4 BClXEC1tS6s1xLfpLICcw.NUYB.hWwGFYQB8ilNH8W9Luk2tA0QtnEkkEb7S ALP6Km.qKDU2CmD1VJDFgGSZj.MrASlFiqiK1DF8wi04kNXet9sTI1O1ZHmr ysYr7.dUMqafk0jomxKFYabRD73wkt6Bn.V7KWQgidK7RTXB46UNcKh_gvmV FJTc1vjfCP95D0eviNWmfIT13qCicZtdyncQv2rbZ9wJLDlhmQDHqdT.ZPU5 EpPeiT6DHwHSBTLCiaB23K6xNUiV6l7SNldpZnEdsXnU- Received: from [99.92.108.194] by web184401.mail.bf1.yahoo.com via HTTP; Mon, 20 Aug 2012 08:07:28 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: <4eae7ab1-572f-44cc-a260-a78b3bf93a9c@googlegroups.com> Message-ID: <1345475248.82420.YahooMailNeo@web184401.mail.bf1.yahoo.com> Date: Mon, 20 Aug 2012 08:07:28 -0700 (PDT) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] Cowan's summary: opacity and sumti-raising To: "lojban@googlegroups.com" In-Reply-To: <4eae7ab1-572f-44cc-a260-a78b3bf93a9c@googlegroups.com> MIME-Version: 1.0 X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.139.52.227 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.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="1009959307-1523492265-1345475248=:82420" X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --1009959307-1523492265-1345475248=:82420 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I haven't gone through the discussion in a while, so my memory (never at it= s best) may have oversimplified and compressed the last few rounds.=A0 Lojb= an=A0 decided that no argument place would be intensional (necessarily refe= r to things that span possible worlds), since all such places do have exten= sional (this world only) uses.=A0 The intensional effect was to be obtained= using intensional sumti, of which there are many available (nu, ka, du'u, = etc. predicates).=A0 Although which intensional sumti was appropriate for a= given place was a matter of discussion, it was agreed (well, as much as su= ch things ever are here) that the focus in actual speech was usually on an = object, a sumti within the larfer bridi within the argument to fill the slo= t.=A0 So, it was decided to abbreviate the whole surrounding bridi to just = {tu'a} -- it already would typically have had just a dummy predicate anyhow= .=A0 What the actual abstractor was in each case was not generally relevant (the suggestion that they were all ultimately {du'u} never got mu= ch traction), except when the term was taken out quantificationally.=A0 So,= the different "restrictions" were, in fact, all treated as as the same.=A0= I suppose, it is occasionally the case that one actually wants to use the = full form -- as when what one wants is not, say, merely a girl but explicit= ly to be dancing with a girl.=A0 But then it will be found that the recomme= nded abstractions are appropriate.=A0=20 I will be interested (since I am not going to dig back through all this, ru= nning 30-odd years in my notes) to see what the present situation is differ= ent from that moment of consensus. ________________________________ From: la gleki To: lojban@googlegroups.com=20 Sent: Monday, August 20, 2012 3:46 AM Subject: [lojban] Cowan's summary: opacity and sumti-raising =20 Again Google Groups didn't let me resurrect this old discussion. So please = follow the link to follow the whole discussion. And now it's my turn to ask the community once again after 18 years of disi= nterest. {djica}, {nitcu} and {sisku}, for example, have all been >dealt with differently: {djica} only accepts events, {nitcu} still accepts >objects, and the solution for {sisku} was the weirdest: the x2 place was >directly eliminated and replaced by only a property of some inaccesible >entity, so that {le se sisku} is not the thing looked for, but a property >of said thing. > > >Why not treat them all the same? > > >The transparent case: > > >{mi djica lo tanxe} =3D "There is a box wanted by me" >{mi nitcu lo tanxe} =3D "There is a box needed by me" >{mi sisku lo tanxe} =3D "There is a box sought by me" One more moment. Are there any other gismu that have the same "problem"?=A0 On Tuesday, November 22, 1994 4:03:33 AM UTC+4, Jorge Llambias wrote: la lojbab cusku di'e >> Of course there is nothing strange about a brivla relating two objects -= a >> seeker and the thing known-and-sought-after, and having a certain predic= ate >> relating them. =A0The problem that I see is that there is more than one = such >> predicate, and the choice is dependent on the specificity =A0(or is that >> definiteness %^) of x2 vs. its opacity, etc., and what the desire is of = the >> seeker for the final state after finding. >The problem is transparency vs opacity. Transparent references can be >specific or nonspecific, and that can be marked with the appropriate >quantifiers, but we don't have any way to mark explicitly opaque reference= s. >The other properties that you mention, like desires of the seeker for what >to do after (or rather if) the sought after thing is found, are not really >to the point. If you want a place for them I guess you do need a lujvo. >Also, in English, the meaning of "seek an object" has been generalized >to "seek knowledge", where by "finding it", we mean that we get to >know the truth value of some utterance. (I suppose that's what you call th= e >seeking of science.) I don't have a problem with letting this metaphorical >extension into Lojban, but in any case this is not part of the opaque prob= lem. >An interesting property of sisku as it is defined now, is that the lambda >variable of its property really never takes a value. Normally, the lambda >variable of a property corresponds to one or more of the places of the >selbri (for example for {zmadu}, it's the x1 and x2) but for sisku, there >is no place for the thing being sought, so there is no place that fits the >lambda variable. >> WE have other cases in Lojban where the Lojban word covers a misleading >> subset of the English meanings of the keywords ("old" and "know" being t= wo >> cases that come to mind). >BTW, because of my mail problems a month or so ago I never found out wheth= er >{citno} means "young", so that it only refers to living things, or whether >it is more general. Would an "old car" in lojban be a {tolcitno karce} or >a {tolcnino karce}? >> In all such casesa we have learned to live with the >> fact that the English word is tto broad and have come up with lujvo for = the >> alternative meanings. =A0Such lujvo can always exist, and if this whole >> issue of "lo" and "existence" blows away. the number of distinctions we = need >=A0to >> make may be reduced. =A0But I remain unconvinced of this - as pc said a = while >> back in this discussion - there are some predicates that embody a hidden >> abstraction involving one of the sumti, and we have to live with this >What do you mean by "some predicates"? English verbs, like "want", "need", >"look for", etc, or Lojban predicates like {djica}, {nitcu}, {sisku}, etc.= ? >I totally agree that the English verbs can accept opaque references as dir= ect >objects, without any marking. They also, in other contexts, can take trans= parent >direct objects. >Because of the logical aspect of Lojban, this can't work like that in Lojb= an, >and so the arguments are always transparent. >But, the fact is that the opaque meaning is often very useful for these >predicates, so what do we do? >I propose to find one solution for all such predicates, rather than patche= s >for each of them. {djica}, {nitcu} and {sisku}, for example, have all been >dealt with differently: {djica} only accepts events, {nitcu} still accepts >objects, and the solution for {sisku} was the weirdest: the x2 place was >directly eliminated and replaced by only a property of some inaccesible >entity, so that {le se sisku} is not the thing looked for, but a property >of said thing. >Why not treat them all the same? >The transparent case: >{mi djica lo tanxe} =3D "There is a box wanted by me" >{mi nitcu lo tanxe} =3D "There is a box needed by me" >{mi sisku lo tanxe} =3D "There is a box sought by me" >and the opaque case: >{mi djica xe'e lo tanxe} =3D "I want a box (I don't care which)" >{mi nitcu xe'e lo tanxe} =3D "I need a box (I don't care which)" >{mi sisku xe'e lo tanxe} =3D "I seek a box (I don't care which)" >(I don't mind using {lo'e} instead of {xe'e lo}, I think it makes sense >as well.) >As things stand now, for the transparent case I have to say: >{da poi tanxe zo'u mi djica tu'a da} >{mi nitcu lo tanxe} >{da poi tanxe zo'u mi sisku le ka du da} >Why so complicated? >> =A0 =A0 =A0 =A0mi'e la lojbab noi sisku loka lo danfu be le me zo sisku = me'u nabmi >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 cu mansa roda >That doesn't make much sense to me. You probably mean {noi sisku lo ka dan= fu >le me zo sisku me'u nabmi gi'e mansa roda}, otherwise you are saying that >you are looking for something with property an answer satisfies everyone, >but what is it that you look for? the answer, everyone? I think this is an >unnecessarily complicated way to deal with {sisku}. >Jorge --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To view this discussion on the web visit https://groups.google.com/d/msg/lo= jban/-/dm2yBBR5LXAJ. 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. --=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. --1009959307-1523492265-1345475248=:82420 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I haven't = gone through the discussion in a while, so my memory (never at its best) ma= y have oversimplified and compressed the last few rounds.  Lojban = ; decided that no argument place would be intensional (necessarily refer to= things that span possible worlds), since all such places do have extension= al (this world only) uses.  The intensional effect was to be obtained = using intensional sumti, of which there are many available (nu, ka, du'u, e= tc. predicates).  Although which intensional sumti was appropriate for= a given place was a matter of discussion, it was agreed (well, as much as = such things ever are here) that the focus in actual speech was usually on a= n object, a sumti within the larfer bridi within the argument to fill the s= lot.  So, it was decided to abbreviate the whole surrounding bridi to just {tu'a} -- it already would typically have had just a dummy p= redicate anyhow.  What the actual abstractor was in each case was not = generally relevant (the suggestion that they were all ultimately {du'u} nev= er got much traction), except when the term was taken out quantificationall= y.  So, the different "restrictions" were, in fact, all treated as as = the same.  I suppose, it is occasionally the case that one actually wa= nts to use the full form -- as when what one wants is not, say, merely a gi= rl but explicitly to be dancing with a girl.  But then it will be foun= d that the recommended abstractions are appropriate. 
I will be interested (since I am not going to dig back through = all this, running 30-odd years in my notes) to see what the present situati= on is different from that moment of consensus.


From:<= /span> la gleki <gleki.is.my.name@gmail.com>
To: lojban@googlegroups.com
Sent: Monday, August 20, 2012 3:4= 6 AM
Subject: [lojban]= Cowan's summary: opacity and sumti-raising

Again Google Groups didn't let me resurrect = this old discussion. So please foll= ow the link to follow the whole discussion.

And no= w it's my turn to ask the community once again after 18 years of disinteres= t.

{djica}, {nitcu} and {sisku}, for example, have all= been
dealt with differently: {djica} only accepts events, {nitcu= } still accepts
objects, and the solution for {sisku} was the wei= rdest: the x2 place was
directly eliminated and replaced by only = a property of some inaccesible
entity, so that {le se sisku} is n= ot the thing looked for, but a property
of said thing.
=
Why not treat them all the same?

The transparent case:

{mi djica lo tanxe} =3D "There is a box wanted by me"
{mi= nitcu lo tanxe} =3D "There is a box needed by me"
{mi sisku lo t= anxe} =3D "There is a box sought by me"

One more moment. Are there any other gismu that have the same "problem"?=  

On Tuesday, November 22, 1994 4:03:33 AM UTC+4, Jorge = Llambias wrote:
la lojbab cusku di'e
&g= t; Of course there is nothing strange about a brivla relating two objects -= a
> seeker and the thing known-and-sought-after, and having a certai= n predicate
> relating them.  The problem that I see is that the= re is more than one such
> predicate, and the choice is dependent on = the specificity  (or is that
> definiteness %^) of x2 vs. its opaci= ty, etc., and what the desire is of the
> seeker for the final state = after finding.
The problem is transparency vs opacity. Transparen= t references can be
specific or nonspecific, and that can be marked with= the appropriate
quantifiers, but we don't have any way to mark explicit= ly opaque references.
The other properties that you mention, like= desires of the seeker for what
to do after (or rather if) the sought af= ter thing is found, are not really
to the point. If you want a place for= them I guess you do need a lujvo.
Also, in English, the meaning = of "seek an object" has been generalized
to "seek knowledge", where by "= finding it", we mean that we get to
know the truth value of some utteran= ce. (I suppose that's what you call the
seeking of science.) I don't hav= e a problem with letting this metaphorical
extension into Lojban, but in any case this is not part of the opaque problem.
An inter= esting property of sisku as it is defined now, is that the lambda
variab= le of its property really never takes a value. Normally, the lambda
vari= able of a property corresponds to one or more of the places of the
selbr= i (for example for {zmadu}, it's the x1 and x2) but for sisku, there
is = no place for the thing being sought, so there is no place that fits the
= lambda variable.
> WE have other cases in Lojban where the Loj= ban word covers a misleading
> subset of the English meanings of the = keywords ("old" and "know" being two
> cases that come to mind).
BTW, because of my mail problems a month or so ago I never found out = whether
{citno} means "young", so that it only refers to living things, = or whether
it is more general. Would an "old car" in lojban be a {tolcit= no karce} or
a {tolcnino karce}?
> In all such casesa we have learned to live with the
> fact that the English word= is tto broad and have come up with lujvo for the
> alternative meani= ngs.  Such lujvo can always exist, and if this whole
> issue of = "lo" and "existence" blows away. the number of distinctions we need
&nbs= p;to
> make may be reduced.  But I remain unconvinced of this - = as pc said a while
> back in this discussion - there are some predica= tes that embody a hidden
> abstraction involving one of the sumti, an= d we have to live with this
What do you mean by "some predicates"= ? English verbs, like "want", "need",
"look for", etc, or Lojban predica= tes like {djica}, {nitcu}, {sisku}, etc.?
I totally agree that th= e English verbs can accept opaque references as direct
objects, without = any marking. They also, in other contexts, can take transparent
direct o= bjects.
Because of the logical aspect of Lojban, this can't work like that in Lojban,
and so the arguments are always transpa= rent.
But, the fact is that the opaque meaning is often very usef= ul for these
predicates, so what do we do?
I propose to find o= ne solution for all such predicates, rather than patches
for each of the= m. {djica}, {nitcu} and {sisku}, for example, have all been
dealt with d= ifferently: {djica} only accepts events, {nitcu} still accepts
objects, = and the solution for {sisku} was the weirdest: the x2 place was
directly= eliminated and replaced by only a property of some inaccesible
entity, = so that {le se sisku} is not the thing looked for, but a property
of sai= d thing.
Why not treat them all the same?
The transpare= nt case:
{mi djica lo tanxe} =3D "There is a box wanted by me"{mi nitcu lo tanxe} =3D "There is a box needed by me"
{mi sisku lo tanx= e} =3D "There is a box sought by me"
and the opaque case:
{mi djica xe'e lo tanxe} =3D "I want a box (I don't care w= hich)"
{mi nitcu xe'e lo tanxe} =3D "I need a box (I don't care which)"<= br>{mi sisku xe'e lo tanxe} =3D "I seek a box (I don't care which)"
(I don't mind using {lo'e} instead of {xe'e lo}, I think it makes sense<= br>as well.)
As things stand now, for the transparent case I have= to say:
{da poi tanxe zo'u mi djica tu'a da}
{mi nitcu lo tan= xe}
{da poi tanxe zo'u mi sisku le ka du da}
Why so complicate= d?
>        mi'e la lojbab noi sisku loka = lo danfu be le me zo sisku me'u nabmi
>         &= nbsp;                 cu mansa roda=
That doesn't make much sense to me. You probably mean {noi sisku= lo ka danfu
le me zo sisku me'u nabmi gi'e mansa roda}, otherwise you a= re saying that
you are looking for something with property an answer satisfies everyone,
but what is it that you look for? the answer, every= one? I think this is an
unnecessarily complicated way to deal with {sisk= u}.
Jorge
--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://= groups.google.com/d/msg/lojban/-/dm2yBBR5LXAJ.
=20 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.


--
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.
--1009959307-1523492265-1345475248=:82420--