Received: from mail-pb0-f59.google.com ([209.85.160.59]:49855) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Tu3xp-0000yO-2c; Sat, 12 Jan 2013 08:29:52 -0800 Received: by mail-pb0-f59.google.com with SMTP id uo1sf1551379pbc.24 for ; Sat, 12 Jan 2013 08:29:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received: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:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; bh=9xbUSVWrMsE/v7WP0KXLlfMY0iMPAETbCMK1Thb50Jw=; b=bV8QY3rgqUUx2t6UHgcAXu/rIUzXqlWtY4FY7aHVtO5S4xQslOcGEGpSq3D+0IOF/T x4FpLeGWBpndcEk0JkzPLpX5DoAo75hE3v5hXJQ0fqh1aKrO6Su5M6CFr67pN40toab3 IwscJ6TMvvjavHC4ODpECR2gXtO8ZcZYWvqf7Gwj5pQrPjFknt18usLkiz8M7uMCJKv4 u4LmxQLAjxXIUMgQ0nXP+jEpdYo2bu35cahUACblBt8Z+uz1dlSbcb4C3BpInK0L2Q7z vSwrrvXxE1go/u2YqEfL/2BbGJKp59FOHQ5vAEf6Qboasr8zJxVDWjDxngRknKXt4Rhr m/GQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:x-received: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:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; bh=9xbUSVWrMsE/v7WP0KXLlfMY0iMPAETbCMK1Thb50Jw=; b=BrQHmnzCYjMMXew5E0MCbh18P71LD54Hrj1KgIhpnfObxp/egsD6fODxxM86ueVCo5 xqyQfFd3fwwkWXpZnV2D0vqwP39okb+j4YKp2wnZgnSN7UgJyfSUKA8iE9twYstgVW/q epU0anIb78Djf+EpQs68alG4C69MbmO0i2fTu/VqiFic31xQkTHFPBK5ECIopjw5xlL6 LnYTU1bnPHgy7dJ4+z/B+pzH1eJ8UvK7xiQA8GZI9dBj52Fu1+qld/VDzh6u19C57Lo0 JaE7IDjg/y0knQOLaWxLXIDN4xFRmDX2aHDHgZBp/RyQw1Q48MT4lqgD2Ang4Sw4zv3g EmZQ== X-Received: by 10.49.72.169 with SMTP id e9mr14740929qev.3.1358008178582; Sat, 12 Jan 2013 08:29:38 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.60.163 with SMTP id i3ls2599685qer.29.gmail; Sat, 12 Jan 2013 08:29:36 -0800 (PST) X-Received: by 10.58.191.68 with SMTP id gw4mr34785364vec.20.1358008176899; Sat, 12 Jan 2013 08:29:36 -0800 (PST) X-Received: by 10.58.191.68 with SMTP id gw4mr34785363vec.20.1358008176874; Sat, 12 Jan 2013 08:29:36 -0800 (PST) Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by gmr-mx.google.com with ESMTPS id h20si1154533vdg.3.2013.01.12.08.29.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Jan 2013 08:29:36 -0800 (PST) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 209.85.220.171 as permitted sender) client-ip=209.85.220.171; Received: by mail-vc0-f171.google.com with SMTP id n11so2363442vch.2 for ; Sat, 12 Jan 2013 08:29:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.22.107 with SMTP id c11mr85758415vdf.73.1358008176690; Sat, 12 Jan 2013 08:29:36 -0800 (PST) Received: by 10.220.13.197 with HTTP; Sat, 12 Jan 2013 08:29:36 -0800 (PST) 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> Date: Sat, 12 Jan 2013 11:29:36 -0500 Message-ID: Subject: Re: [lojban] searching From: Ian Johnson To: lojban@googlegroups.com X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 209.85.220.171 as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass header.i=@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=20cf307c9eaaf944a704d319eaaf X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --20cf307c9eaaf944a704d319eaaf Content-Type: text/plain; charset=ISO-8859-1 That doesn't really fix anything; with makau like that you are really just saying {mi sisku lo se zvati be lo ckiku}. That approach also doesn't get you access to indefinite searching, which is as has been noted occasionally necessary. mi'e la latro'a mu'o On Sat, Jan 12, 2013 at 12:54 AM, la gleki wrote: > > > 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. > -- 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@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --20cf307c9eaaf944a704d319eaaf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That doesn't really fix anything; with makau like that you are really j= ust saying {mi sisku lo se zvati be lo ckiku}. That approach also doesn'= ;t get you access to indefinite searching, which is as has been noted occas= ionally necessary.

mi'e la latro'a mu'o

On Sat, Jan 12, 2013 at 12:54 AM, la gleki <gleki.is.my.na= me@gmail.com> wrote:


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 t= hat it works seems to say something about the issue. If {sisku} were define= d 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 th= is definition basically solves the problem (I think using {joi} you can spe= cify 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 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= major things we'd like to get away from with this language.=A0

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

mi'= e la latro'a mu'o

For me sisku2 parallels jimpe2 and djuno2.
But djuno3 is oft= en duplicated inside djuno2. So why doesnt sisku work like this=A0

x1 searches for x2 being x3 (nu).

{mi sisku lo ckiku lo ka zvati makau.}
"I'm searching fo= r the keys, where they are located to be precise."


On Fri, Jan 11, = 2013 at 11:24 AM, John E Clifford <kali9...@yahoo.c= om> wrote:
Sorry,= standard (in at least some groups I write in) logical notation: A for universal quantifier, S fo particular (L for salient, ? for interrogat= ive, but thosedon't turn up here).=A0 Quantif= iers=A0 take two wffs and a variable, AxFxGx is AllFsareGs, that universality restricted to the (non-null) exte= nsion of F.=A0 or [x:Fx]Gx.=A0 I suppose one could avoid the problem here by using=A0 (x)(Green x =3D> Seek I, x), but that doesn= 9;t really help.
I would be happy t= o have a better analysis of "seek", in particular, one that allow= ed for quantifiers to be placed properly without question, but I don't = see it anywhere.=A0 Much of the problem is in how we deal with intensional = phrases.=A0 Of the two usual approaches, having certain places specified as= such in the lexicon or having all places transparent but some phrases labe= lled as intensional, Lojban has chosen a position in the middle.=A0 All pla= ces are transparent, but some have recommended or required intensional phra= se structures for filling.=A0 Unfortunately, these cases don't cover all the intensional= cases (and cover a number which are not intensional as well), so we are le= ft with thing like thing {sisku} (which is not actually in Lojban, after al= l, but is popularly uses as though it were), where the transparent place yi= elds 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}.=A0 So, for me, at leas= t, {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 goa= l which would be satisfied just in case I were to have something green"= ;, with the quantifier tucked in the right place.=A0 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 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.=A0 If the extension of {crino} is already non-null, however, t= his object is to be identified with some already present object, which one = depending on which one I actually find (more or less).=A0 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.= =A0 Or, taking the broader view, I am really seeking every green thing indi= vidually.=A0 Not what is wanted.=A0
=A0 =


<= font face=3D"Arial">
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 se= nse) is short for "has a goal which would be fulfilled
> if I were to have (in whatever the appropriate sense is) x" and s= o 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 hav= e 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 o= f 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 looki= ng 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 = 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 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 r= eally get, what you try to point out here.


v4hn


--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

For more options, visit this group at http://groups.google.com/grou= p/lojban?hl=3Den.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To view this discussion on the web visit https://groups.google.com= /d/msg/lojban/-/r8er0cinPMYJ.
=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/lojba= n?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.
--20cf307c9eaaf944a704d319eaaf--