Received: from mail-ia0-f183.google.com ([209.85.210.183]:32887) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Ttu35-0004hp-DI; Fri, 11 Jan 2013 21:54:40 -0800 Received: by mail-ia0-f183.google.com with SMTP id k27sf225665iad.10 for ; Fri, 11 Jan 2013 21:54:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=vZ8VUFcjxzJqlzzhP16Yaa0ZjcNYDkE2RsuZ39BBJB4=; b=zFiYsNctsM+ngsWxc19mGafB7oae5fvr12Sb3Y1OV4ouPcXvBOENP45ZxQ7pSFCp1b TFk51VKbaw1jdmCgwp0WjG315sNzQxyp2KHh+Mklv7ovd9//1nOBz/8bqC8DjKQBoFfq GUq+lLtZFP17mbF7AlnCfT1JhF97+F8fS91RrqlhLJ58pdWgQQQNXAoGDiH1yLNpIY4m 0Hjr9rtyaFi65ndxiplUwyHRGo++IMGuZKrv3Y7F296caO+cZW8J4wytCqmSDHD4yxbg sxyWS8x52lX5czDOKCPukdXiwSHugozmaj97e5E1G929rXtrY9lJWofSQ2S24Ejg+r4b /5rg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=vZ8VUFcjxzJqlzzhP16Yaa0ZjcNYDkE2RsuZ39BBJB4=; b=fKTH7sV4wNbxRHBq4AN9LYNNDRHocxSo88tdJd7ZF59opUufSE3ayDyd0XVJJJoUJr 8pzm8m/gbj+KrFQntcTyjVCbxW9/hXFeMuBMSO5cC/WZbzIaTfgtUjNapaSB4xJe/0AT QbRQs/1oZ7wRzt1KrBZ5GqRseducTyqXGr1b2RzMHHQlAm7yR3el06Ms7szEVR31bp91 +TWqJASnDsy9zj1F5Sze2s7rt5mUzuUQwF3HiIJDLZY4YraVcTNelGz3VepT6JGfB3Hb rdpwfDJunR3jX5WlL4X7s5gWTaFHsxKU+4bbg3hXowrtnEQ9MP0EYqKsqOMoB8N9ROgv TRRg== X-Received: by 10.49.63.164 with SMTP id h4mr14082433qes.39.1357970064827; Fri, 11 Jan 2013 21:54:24 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.74.42 with SMTP id q10ls2694623qev.65.gmail; Fri, 11 Jan 2013 21:54:24 -0800 (PST) X-Received: by 10.49.72.169 with SMTP id e9mr14547161qev.3.1357970064298; Fri, 11 Jan 2013 21:54:24 -0800 (PST) Date: Fri, 11 Jan 2013 21:54:23 -0800 (PST) From: la gleki To: lojban@googlegroups.com Message-Id: In-Reply-To: References: <50EC7334.8040607@gmx.de> <50ECB7C1.2020501@gmx.de> <20130109124414.GD14601@samsa.fritz.box> <20130111001919.GA17367@samsa.fritz.box> <1357872173.57379.YahooMailNeo@web184406.mail.bf1.yahoo.com> <20130111104236.GB17367@samsa.fritz.box> <1357921456.64440.YahooMailNeo@web184402.mail.bf1.yahoo.com> Subject: Re: [lojban] searching MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@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="----=_Part_1014_24399769.1357970063786" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_1014_24399769.1357970063786 Content-Type: text/plain; charset=ISO-8859-1 On Friday, January 11, 2013 9:37:48 PM UTC+4, Latro wrote: > > Here's an idea I just had. I don't actually like it, but the fact that it > works seems to say something about the issue. If {sisku} were defined as > "x1 is searching among x3 and x1 would be satisfied if they found x2", then > {mi sisku lo ckiku} does what was originally wanted while {mi sisku ro > crino} does what {mi sisku lo ka crino} is defined to do. So this > definition basically solves the problem (I think using {joi} you can > specify that you would only be satisfied if you found several different > sumti, in that (rather common) case. {.e} frustratingly doesn't work.) > > This definition feels highly nonprimitive (though so does current > {sisku}). In particular (in this regard unlike current {sisku}) it induces > hidden quantifier/subjunctivity scope, which is rather important to what is > actually meant. I'm pretty sure hiding such things is one of the major > things we'd like to get away from with this language. > > Perhaps we should just derail this into a discussion of how best to handle > subjunctivity? > > mi'e la latro'a mu'o > For me sisku2 parallels jimpe2 and djuno2. But djuno3 is often duplicated inside djuno2. So why doesnt sisku work like this x1 searches for x2 being x3 (nu). {mi sisku lo ckiku lo ka zvati makau.} "I'm searching for the keys, where they are located to be precise." > On Fri, Jan 11, 2013 at 11:24 AM, John E Clifford > > wrote: > >> Sorry, standard (in at least some groups I write in) logical notation: A for >> universal quantifier, S fo particular (L for salient, ? for interrogative, >> but thosedon't turn up here). Quantifiers take two wffs and a >> variable, AxFxGx is AllFsareGs, that universality restricted to the(non-null) extension >> of F. or [x:Fx]Gx. I suppose one could avoid the problem here by >> using (x)(Green x => Seek I, x), but that doesn't really help. >> >> I would be happy to have a better analysis of "seek", in particular, one >> that allowed for quantifiers to be placed properly without question, but I >> don't see it anywhere. Much of the problem is in how we deal with >> intensional phrases. Of the two usual approaches, having certain places >> specified as such in the lexicon or having all places transparent but some >> phrases labelled as intensional, Lojban has chosen a position in the >> middle. All places are transparent, but some have recommended or required >> intensional phrase structures for filling. Unfortunately, these cases >> don't cover all the intensional cases (and cover a number which are not >> intensional as well), so we are left with thing like thing {sisku} (which >> is not actually in Lojban, after all, but is popularly uses as though it >> were), where the transparent place yields unwanted results. >> Ultimately, of course, what we want is a particular quantifier in the >> scope of the subjunctive, which is my informal summary of the role of >> {tu'a}. So, for me, at least, {mi sisku tu'a da poi crino} means "I am >> looking for something green" with no hint that a particular one (or even >> one in the present UD) is required, since it expands to the more satisfying >> "I have a goal which would be satisfied just in case I were to have >> something green", with the quantifier tucked in the right place. The >> standard explanation of {tu'a} gets close to this but gets bogged down in >> technicalities. >> Your solution, as I understand it (if at all), is that {mi sisku da poi >> crino} is indeed transparent and the occurrence there of {da poi crino} may >> change the UD by adding an object to guarantee that the extension of >> {crino} is non-null. If the extension of {crino} is already non-null, >> however, this object is to be identified with some already present object, >> which one depending on which one I actually find (more or less). But that >> kind of anonymous object isn't allowed in the semantics game, nor does it >> help, since, as soon as its identity is revealed we fall back to the >> position of the external quantifier (which we never did really leave, if >> the slot was transparent), that I was really seeking this particular thing, >> not just any old thing at all. Or, taking the broader view, I am really >> seeking every green thing individually. Not what is wanted. >> >> >> >> ------------------------------ >> *From:* v4hn > >> *To:* loj...@googlegroups.com >> *Sent:* Friday, January 11, 2013 4:42 AM >> *Subject:* Re: [lojban] searching >> >> On Thu, Jan 10, 2013 at 06:42:53PM -0800, John E Clifford wrote: >> > Howsabout going back to the basics of "any" in English? >> > >> > It is a context leaper, a universal embedded in a verso context >> > with scope over the whole in which the context is subordinate. >> >> > So, what we want is Ax Greenx I seek x. >> >> I already asked you two days ago to explain your notation, please. >> Does this mean something like "forall x : Green(x).(seek(I, x))" >> or "A(x) => Green(x) => seek(I, x)" or "forall x. Green(x) => seek(I, x)" >> ... >> >> > Not, notice, {mi sisku ro crino}, because {sisku}(in the thing sense, >> > not the property sense) is short for "has a goal which would be >> fulfilled >> > if I were to have (in whatever the appropriate sense is) x" and so every >> > green thing fits and none is special ("if my goal were fulfilled, I >> would have"). >> >> I'm not sure I like that "goal driven" analysis of seek. >> Especially, mixing up quantifiers and goal constraints is rather >> confusing. >> >> What your "Ax Greenx I seek x" is _supposed_ to mean, I think, is the >> following. >> >> There exists a goal G1 which I have in mind, such that for all green >> things >> it is true that if I have such a green object, the goal G1 is fulfilled. >> >> I very much prefer the analysis I described in my last mail, >> because if you try to apply quantifiers here, you have to be explicit >> about >> the existential goal quantification. >> Else you could end up searching for _all_ green things: >> >> forall x. there exists g. have(I, x) => satisfied(g) >> >> (I just invented the "satisfied" for the lack of a better notation) >> >> Again, I prefer to say that {mi sisku da poi crino} adds an >> object to the universe of discourse which satisfies {crino} and can map >> to a number of physical objects, therefore creating the feeling of >> a restricted universal quantification. >> >> We do this in NatLangs as well: "I'm looking for a shirt.", >> "I'm searching for something green.", "Ich suche eine Kuh.", >> "Je cherche une vache.", ... >> >> Just to point this out again: This is an analysis which I proposed in >> my last mail and which I never directly read about anywhere. Therefore, >> I'm still waiting for criticism and comments. >> >> > This still supposes, of course, that there is something green in the UD, >> > so the property sense is still better. >> >> > Of course, spelling out the counterfactual stuff in such a way as to >> make >> > the quantifier scope points clearer would be nice, too, >> > but no one seems to like {tu'a} >> > and it is a little iffy around the edges anyhow. >> >> I don't really get, what you try to point out here. >> >> >> v4hn >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "lojban" group. >> To post to this group, send email to loj...@googlegroups.com >> . >> To unsubscribe from this group, send email to >> lojban+un...@googlegroups.com . >> For more options, visit this group at >> http://groups.google.com/group/lojban?hl=en. >> > > -- 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/-/r8er0cinPMYJ. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. ------=_Part_1014_24399769.1357970063786 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Friday, January 11, 2013 9:37:48 PM UTC+4, Latro wrote:Here's an idea I just had. I don't actu= ally like it, but the fact that it works seems to say something about the i= ssue. If {sisku} were defined as "x1 is searching among x3 and x1 would be = satisfied if they found x2", then {mi sisku lo ckiku} does what was origina= lly wanted while {mi sisku ro crino} does what {mi sisku lo ka crino} is de= fined to do. So this definition basically solves the problem (I think using= {joi} you can specify that you would only be satisfied if you found severa= l different sumti, in that (rather common) case. {.e} frustratingly doesn't= work.)

This definition feels highly nonprimitive (though so does cu= rrent {sisku}). In particular (in this regard unlike current {sisku}) it in= duces hidden quantifier/subjunctivity scope, which is rather important to w= hat is actually meant. I'm pretty sure hiding such things is one of the maj= or things we'd like to get away from with this language. 

Perhaps we should just derail this into a discussion of= how best to handle subjunctivity? 

mi'e= la latro'a mu'o

For me sis= ku2 parallels jimpe2 and djuno2.
But djuno3 is often duplicated i= nside djuno2. So why doesnt sisku work like this 

=
x1 searches for x2 being x3 (nu).

{mi sisku l= o ckiku lo ka zvati makau.}
"I'm searching for the keys, where th= ey are located to be precise."


On Fri, Jan 1= 1, 2013 at 11:24 AM, John E Clifford <kali9...@y= ahoo.com> wrote:
Sorry, standard (in at l= east some groups I write in) logical notation: A for universal quantifier, S fo particular = (L for salient, ? for interrogative, but th= osedon't turn up here).  Quantifiers  take two wffs = and a variable, AxFxGx is AllFsareGs, that univer= sality restricted to the (non-null) extension of F.&nbs= p; or [x:Fx]Gx.  I suppose one could avoid the problem here by using  (x)(Green x =3D> Seek I, x), but that doesn= 't really help.
I would be happy t= o have a better analysis of "seek", in particular, one that allowed for qua= ntifiers to be placed properly without question, but I don't see it anywher= e.  Much of the problem is in how we deal with intensional phrases.&nb= sp; Of the two usual approaches, having certain places specified as such in= the lexicon or having all places transparent but some phrases labelled as = intensional, Lojban has chosen a position in the middle.  All places a= re transparent, but some have recommended or required intensional phrase st= ructures for filling.  Unfortunately, these cases don't cover all the intensional = cases (and cover a number which are not intensional as well), so we are lef= t with thing like thing {sisku} (which is not actually in Lojban, after all= , but is popularly uses as though it were), where the transparent place yie= lds unwanted results.
Ultimately, of course, w= hat we want is a particular quantifier in the scope of the subjunctive, whi= ch is my informal summary of the role of {tu'a}.  So, for me, at least= , {mi sisku tu'a da poi crino} means "I am looking for something green" wit= h no hint that a particular one (or even one in the present UD) is required= , since it expands to the more satisfying "I have a goal which would be sat= isfied just in case I were to have something green", with the quantifier tu= cked in the right place.  The standard explanation of {tu'a} gets close to this b= ut gets bogged down in technicalities.
Your solution, as I understand it (if at all), is that {mi sisku da poi cri= no} is indeed transparent and the occurrence there of {da poi crino} may ch= ange the UD by adding an object to guarantee that the extension of {crino} = is non-null.  If the extension of {crino} is already non-null, however= , this object is to be identified with some already present object, which o= ne depending on which one I actually find (more or less).  But that ki= nd of anonymous object isn't allowed in the semantics game, nor does it hel= p, since, as soon as its identity is revealed we fall back to the position = of the external quantifier (which we never did really leave, if the slot wa= s transparent), that I was really seeking this particular thing, not just any old thing at all.=   Or, taking the broader view, I am really seeking every green thing i= ndividually.  Not what is wanted. 
=  


Sent: Friday, January= 11, 2013 4:42 AM
Subject: Re: [lojban] searching

On Thu, Jan 10, 2013 at 06:42:53PM -0800, John E Clifford wrote:
> Ho= wsabout going back to the basics of "any" in English?
>
> It is= a context leaper, a universal embedded in a verso context
> with scope over the whole in which the context is subordinate.

= > So, what we want is Ax Greenx I seek x.

I already asked you two= days ago to explain your notation, please.
Does this mean something lik= e "forall x : Green(x).(seek(I, x))"
or "A(x) =3D> Green(x) =3D> seek(I, x)" or "forall x. Green(x) =3D>= ; seek(I, x)"
...

> Not, notice, {mi sisku ro crino}, because = {sisku}(in the thing sense,
> not the property sense) is short for "h= as a goal which would be fulfilled
> if I were to have (in whatever the appropriate sense is) x" and so eve= ry
> green thing fits and none is special ("if my goal were fulfilled= , I would have").

I'm not sure I like that "goal driven" analysis of seek.
Especially, mixing up quantifiers and goal constraints is rather = confusing.

What your "Ax Greenx I seek x" is _supposed_ to mean, I t= hink, is the following.

There exists a goal G1 which I have in mind,= such that for all green things
it is true that if I have such a green object, the goal G1 is fulfilled.
I very much prefer the analysis I described in my last mail,
becaus= e if you try to apply quantifiers here, you have to be explicit about
the existential goal quantification.
Else you could end up searching for= _all_ green things:

forall x. there exists g. have(I, x) =3D> sa= tisfied(g)

(I just invented the "satisfied" for the lack of a better= notation)

Again, I prefer to say that {mi sisku da poi crino} adds an
object t= o the universe of discourse which satisfies {crino} and can map
to a num= ber of physical objects, therefore creating the feeling of
a restricted = universal quantification.

We do this in NatLangs as well: "I'm looking for a = shirt.",
"I'm searching for something green.", "Ich suche eine Kuh.","Je cherche une vache.", ...

Just to point this out again: This is an analysis which I proposed inmy last mail and which I never directly read about anywhere. Therefore,I'm still waiting for criticism and comments.

> This still supp= oses, of course, that there is something green in the UD,
> so the property sense is still better.

> Of course, spelling= out the counterfactual stuff in such a way as to make
> the quantifi= er scope points clearer would be nice, too,
> but no one seems to lik= e {tu'a}
> and it is a little iffy around the edges anyhow.

I don't reall= y get, what you try to point out here.


v4hn


--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@googl= egroups.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 view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/r8= er0cinPMYJ.
=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.
------=_Part_1014_24399769.1357970063786--