Received: from mail-qa0-f56.google.com ([209.85.216.56]:52818) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TuPez-0007K9-Th; Sun, 13 Jan 2013 07:40:10 -0800 Received: by mail-qa0-f56.google.com with SMTP id cr7sf1081234qab.21 for ; Sun, 13 Jan 2013 07:39:39 -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 :x-yahoo-newman-property:x-yahoo-newman-id:x-ymail-osg :x-rocket-mimeinfo: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=m3/4QkQKL4Oez1DN555+lJs/O7Xw59PnerLAn0dSkAo=; b=iHUM6gtzmlzlI2t2VsFbe3gpGMDSAfaAspjwlP2OID4+LGSKtUcOU8bg/Ow0Mts+ER LneQKPwptpNcWVMmexwRyAA6cgSGQ+eKJGXXkxmdPRxH6h/aJA8+L3mKAfssTwF7Dmxh zV/UlSQWcUKC0TzGbMAe9mW3vfX5vnTk/tVDpQjji1tlKx2rn3rVxOqT8RRvVy+yoLXx xmD4hF8DybpkV4LXdq1+QUogErKnCKO8OcmAdeZgogal6k28bzW6OKB5wlGc9Er6ruRp BiRtH3Ap1/8YVhgCsawglcaR8x3uHi9FWr7zFPmqKm105yeIaxMqD3VmJAO1474dRWle ulgQ== X-Received: by 10.49.1.70 with SMTP id 6mr14850130qek.27.1358091579168; Sun, 13 Jan 2013 07:39:39 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.0.102 with SMTP id 6ls3161299qed.24.gmail; Sun, 13 Jan 2013 07:39:37 -0800 (PST) X-Received: by 10.236.158.168 with SMTP id q28mr45059235yhk.20.1358091577686; Sun, 13 Jan 2013 07:39:37 -0800 (PST) X-Received: by 10.236.158.168 with SMTP id q28mr45059233yhk.20.1358091577624; Sun, 13 Jan 2013 07:39:37 -0800 (PST) Received: from nm22.access.bullet.mail.mud.yahoo.com (nm22.access.bullet.mail.mud.yahoo.com. [66.94.237.223]) by gmr-mx.google.com with ESMTPS id l20si572667yhi.2.2013.01.13.07.39.37 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 13 Jan 2013 07:39:37 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.237.223 as permitted sender) client-ip=66.94.237.223; Received: from [66.94.237.192] by nm22.access.bullet.mail.mud.yahoo.com with NNFMP; 13 Jan 2013 15:39:37 -0000 Received: from [66.94.237.122] by tm3.access.bullet.mail.mud.yahoo.com with NNFMP; 13 Jan 2013 15:39:36 -0000 Received: from [127.0.0.1] by omp1027.access.mail.mud.yahoo.com with NNFMP; 13 Jan 2013 15:39:36 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 971604.28506.bm@omp1027.access.mail.mud.yahoo.com Received: (qmail 5380 invoked by uid 60001); 13 Jan 2013 15:39:36 -0000 X-YMail-OSG: 2UurHE0VM1kkRmc0AXgRgwIe8DjapQhPyIdjMn_P5.ySdAD hk1Ma61P.cVcsLvFSxav3xCbaBuIbBokAZJG93M7ZSKkkMrZluOu2XN0..l3 lMUkhhJ29DqLfdRD_9EgzNQcXUaZfhkDuGbUYG1OrtKPkibTeV5IiKg2XUYV sd6_3a1ePGA_3F4YgHK_Sh1JUxTGVV2lWzvwyryIk_9U6cTkZPfLJqrNcVfS 7byJBC15hduDutTgOWVmsPJALYXM_Gfzz2UuftEXEAFwEke5yvKYCy7vAbfD 2qHqcObehKg1hZQrfhftM6FsrGTCeP1lGvg_mYr0W0vt3O1ngNYcxIaCb3l7 W7R6jOIey2QBto8IAHtUPrbEcf0XO4SieDSCu.P.IGYLoDz3sJrwP17fYRrI WJDZgEo22PzkpZHDaHSp6dNTdEd3bVgxnqJCpc2H9LtBRTDJNWWgYvbDjs4J uGjzOB8wk8glgG3SZ3U28LF6YCpQ97P7gDhHLuBZyQ6esfa48pUS2dgBGa6l Nc9WCk60g0kqLux_7UPDMDCgb_rsEcmlQIGt46Gj3TDnF83v8vYyG3y1TUt6 v.XXcluCHjPJEn39d55ql4fZ6coeI1fYT8XO0PgWSSQLz5k7.STHbcqZf5wp HuNwA Received: from [99.92.108.194] by web184401.mail.bf1.yahoo.com via HTTP; Sun, 13 Jan 2013 07:39:36 PST X-Rocket-MIMEInfo: 001.001,SG1tbSEgWWVzLsKgIFNvcnRhLsKgIFRoZSByaWdodCByZWZlcmVudCBidXQgdGhlIHdyb25nIHNlbnNlLCBsaWdodCBwb2ludGluZyB0byBWZW51cyBzaGluaW5nIGp1c3QgYWZ0ZXIgc3Vuc2V0IGFuZCBzYXlpbmcgIkxvLCB0aGUgTW9ybmluZyBTdGFyISIKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwogRnJvbTogRmVsaXBlIEdvbsOnYWx2ZXMgQXNzaXMgPGZlbGlwZWcuYXNzaXNAZ21haWwuY29tPgpUbzogbG9qYmFuQGdvb2dsZWdyb3Vwcy5jb20gClNlbnQ6IFNhdHVyZGF5LCBKYW51YXIBMAEBAQE- X-Mailer: YahooMailWebService/0.8.130.494 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> <1357929461.99777.YahooMailNeo@web184406.mail.bf1.yahoo.com> Message-ID: <1358091576.2626.YahooMailNeo@web184401.mail.bf1.yahoo.com> Date: Sun, 13 Jan 2013 07:39:36 -0800 (PST) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] searching To: "lojban@googlegroups.com" In-Reply-To: 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 66.94.237.223 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass 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-837315209-1358091576=:2626" X-Spam-Score: 0.1 (/) X-Spam_score: 0.1 X-Spam_score_int: 1 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hmmm! Yes. Sorta. The right referent but the wrong sense, light pointing to Venus shining just after sunset and saying "Lo, the Morning Star!" From: Felipe Gonçalves Assis To: lojban@googlegroups.com Sent: Saturday, January 12, 2013 11:28 PM Subject: Re: [lojban] searching [...] Content analysis details: (0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kali9putra[at]yahoo.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid --1009959307-837315209-1358091576=:2626 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hmmm! Yes.=A0 Sorta.=A0 The right referent but the wrong sense, light point= ing to Venus shining just after sunset and saying "Lo, the Morning Star!" ________________________________ From: Felipe Gon=E7alves Assis To: lojban@googlegroups.com=20 Sent: Saturday, January 12, 2013 11:28 PM Subject: Re: [lojban] searching =20 John has already made a very careful logical analysis of the topic, so let me try something more concrete: Saying that "I look for something green", in the sense that any green thing will do, can be rendered as {mi sisku lo crino} for a convenient definition of {sisku} is analogous to saying that "I know the result of 2+2" can be rendered as {mi djuno lo sumji be li re bei li re}, which is actually expressing a relation between me and the number 4: {mi djuno li vo}. mu'o mi'e .asiz. On 11 January 2013 15:37, John E Clifford wrote: > Not sure how this helps, but there are two different issues here.=A0 On t= he > one hand, we need to deal with opaque phrases in the ordinary run of thin= gs; > on the other hand we need to deal with contrary-to-fact situations as not > ordinary run of things (though far more common than appears in most Lojba= n > -- mainly because we are not sure how to do it).=A0 Your suggestion is to > reduce the first problem to the second (and then make it disappear back i= nto > the definition of words involved, so still available to surprise us).=A0 = But > not all opaque cases are contrary-to-fact, we have the cases with {du'u} = and > {nu} and the like already (and regularly screw them up anyhow -- see > raising).=A0 The difficult cases are where we are not sure what abstracti= on is > appropriate -- or even that one is, like thing {sisku} and {djica} and so > on.=A0 These very often are buried contrary-to-facts and for them we do h= ave > {tu'a}, stripped of its connection to (unspecified) buried abstractions a= nd > nebulous predicates, as a mark that the following term 1) cannot be moved= or > quantified out of its place (identified with things outside) and 2) at so= me > point in an analysis will take its place in one or more alternate worlds > which represent the working out of the predicate to which the term is > attached as argument. > The matter of contrary-to-fact or hypothetical sentences seems to involve > just working out the rules on scope and the like for {da'i}.=A0 I do not > include the problems with truth conditions here, of course, since, so far= as > I can tell, no one has come up with a good answer to questions like "If > Socrates were a 17th century Irish washerwoman, would Plato still have be= en > gay?" > > > ________________________________ > From: Ian Johnson > To: lojban@googlegroups.com > Sent: Friday, January 11, 2013 11:37 AM > Subject: Re: [lojban] searching > > 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 yo= u > 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 handl= e > subjunctivity? > > mi'e la latro'a mu'o > > 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).=A0 Quantifiers=A0 take two wffs and a varia= ble, > AxFxGx is AllFsareGs, that universality restricted to the (non-null) > extension 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'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.=A0 Much of the problem is in how we deal with > intensional phrases.=A0 Of the two usual approaches, having certain place= s > specified as such in the lexicon or having all places transparent but som= e > phrases labelled as intensional, Lojban has chosen a position in the midd= le. > All places are transparent, but some have recommended or required > intensional phrase 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 left with thing like thing {sisku} (which= is > not actually in Lojban, after all, but is popularly uses as though it wer= e), > where the transparent place yields unwanted results. > Ultimately, of course, what we want is a particular quantifier in the sco= pe > of the subjunctive, which is my informal summary of the role of {tu'a}.= =A0 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.=A0 The standard explanatio= n 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} m= ay > change the UD by adding an object to guarantee that the extension of {cri= no} > is non-null.=A0 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).=A0 But that kind o= f > 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 o= f > the external quantifier (which we never did really leave, if the slot was > transparent), that I was really seeking this particular thing, not just a= ny > old thing at all.=A0 Or, taking the broader view, I am really seeking eve= ry > green thing individually.=A0 Not what is wanted. > > > > ________________________________ > From: v4hn > To: lojban@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) =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 "has a goal which would be fulfille= d >> 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 woul= d >> have"). > > I'm not sure I like that "goal driven" analysis of seek. > Especially, mixing up quantifiers and goal constraints is rather confusin= g. > > 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 thin= gs > 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 abo= ut > the existential goal quantification. > Else you could end up searching for _all_ green things: > > forall x. there exists g. have(I, x) =3D> 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 mak= e >> 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 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=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@googlegroups.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@googlegroups.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. --=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-837315209-1358091576=:2626 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hmmm! Yes. = Sorta.  The right referent but the wrong sense, light pointing to Ven= us shining just after sunset and saying "Lo, the Morning Star!"
=
=
From: Feli= pe Gon=E7alves Assis <felipeg.assis@gmail.com>
To: lojban@googlegroups.com
Sent: Saturday, January 12, 2013 11:2= 8 PM
Subject: Re: [loj= ban] searching

John has already made a very careful logical analysis of the topic,
so l= et me try something more concrete:

Saying that "I look for something= green", in the sense that any green
thing will do, can be rendered as {= mi sisku lo crino} for a convenient
definition of {sisku} is analogous t= o saying that "I know the result of
2+2" can be rendered as {mi djuno lo= sumji be li re bei li re}, which
is actually expressing a relation betw= een me and the number 4:
{mi djuno li vo}.

mu'o
mi'e .asiz.

On 11 January 2013 15:37, John E Clifford <kali9putra@yaho= o.com> wrote:
> Not sure how this helps, but there are two dif= ferent issues here.  On the
> one hand, we need to deal with opa= que phrases in the ordinary run of things;
> on the other hand we nee= d to deal with contrary-to-fact situations as not
> ordinary run of things (though far more common than appears in most Lojban
> -- m= ainly because we are not sure how to do it).  Your suggestion is to> reduce the first problem to the second (and then make it disappear ba= ck into
> the definition of words involved, so still available to sur= prise us).  But
> not all opaque cases are contrary-to-fact, we = have the cases with {du'u} and
> {nu} and the like already (and regul= arly screw them up anyhow -- see
> raising).  The difficult case= s are where we are not sure what abstraction is
> appropriate -- or e= ven that one is, like thing {sisku} and {djica} and so
> on.  Th= ese very often are buried contrary-to-facts and for them we do have
>= {tu'a}, stripped of its connection to (unspecified) buried abstractions an= d
> nebulous predicates, as a mark that the following term 1) cannot = be moved or
> quantified out of its place (identified with things outside) and 2) at some
> point in an analysis will take its = place in one or more alternate worlds
> which represent the working o= ut of the predicate to which the term is
> attached as argument.
&= gt; The matter of contrary-to-fact or hypothetical sentences seems to invol= ve
> just working out the rules on scope and the like for {da'i}.&nbs= p; I do not
> include the problems with truth conditions here, of cou= rse, since, so far as
> I can tell, no one has come up with a good an= swer to questions like "If
> Socrates were a 17th century Irish washe= rwoman, would Plato still have been
> gay?"
>
>
> _= _______________________________
> From: Ian Johnson <blin= dbravado@gmail.com>
> To: lojban@googlegroups.com
>= ; Sent: Friday, January 11, 2013 11:37 AM
> Subject: Re: [lojban] sea= rching
>
> 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 on= ly be satisfied if you found several different sumti, in that
> (rath= er common) case. {.e} frustratingly doesn't work.)
>
> This def= inition 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 t= o 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 ho= w best to handle
> subjunctivity?
>
> mi'e la latro'a mu'= o
>
> On Fri, Jan 11, 2013 at 11:24 AM, John E Clifford <kali9putra@yahoo.com>
> wrote:
>
> Sorry, standa= rd (in at least some groups I write in) logical notation: A for
> uni= versal quantifier, S fo particular (L for salient, ? for interrogative,
= > but thosedon't turn up here).  Quantifiers  take two wffs an= d 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 =3D> Seek I, x), but that doesn't really help.
>
> I would= be happy to have a better analysis of "seek", in particular, one
> t= hat 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 w= ith
> intensional phrases.  Of the two usual approaches, having = certain places
> specified as such in the lexicon or having all place= s transparent but some
> phrases labelled as intensional, Lojban has = chosen a position in the middle.
> All places are transparent, but so= me have recommended or required
> intensional phrase structures for f= illing.  Unfortunately, these cases don't
> cover all the intens= ional 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.
> Ultimat= ely, 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}.&n= bsp; 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 (o= r 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 cas= e I were to have something green",
> with the quantifier tucked in th= e 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 inde= ed transparent and the occurrence there of {da poi crino} may
> change the UD by adding an object to guarantee that the extens= ion of {crino}
> is non-null.  If the extension of {crino} is al= ready 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 exter= nal quantifier (which we never did really leave, if the slot was
> tr= ansparent), that I was really seeking this particular thing, not just any> old thing at all.  Or, taking the broader view, I am really see= king every
> green thing individually.  Not what is wanted.
&= gt;
>
>
> ________________________________
> From: = v4hn <me@v4hn.de>
> To: lojba= n@googlegroups.com
> Sent: Friday, January 11, 2013 4:42 AM
&g= t; Subject: Re: [lojban] searching
>
> On Thu, Jan 10, 2013 at = 06:42:53PM -0800, John E Clifford wrote:
>> Howsabout going back t= o the basics of "any" in English?
>>
>> It is a context l= eaper, 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 day= s ago to explain your notation, please.
> Does this mean something li= ke "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 t= hing sense,
>> not the property sense) is short for "has a goal which = would be fulfilled
>> if I were to have (in whatever the appropria= te sense is) x" and so every
>> green thing fits and none is speci= al ("if my goal were fulfilled, I would
>> have").
>
>= I'm not sure I like that "goal driven" analysis of seek.
> Especiall= y, mixing up quantifiers and goal constraints is rather confusing.
><= br>> What your "Ax Greenx I seek x" is _supposed_ to mean, I think, is t= he
> following.
>
> There exists a goal G1 which I have i= n mind, such that for all green things
> it is true that if I have su= ch a green object, the goal G1 is fulfilled.
>
> I very much pr= efer the analysis I described in my last mail,
> because if you try t= o apply quantifiers here, you have to be explicit about
> the existen= tial goal quantification.
> Else you could end up searching for _all_ green things:
>
> forall x. there exists g. have(I, = x) =3D> satisfied(g)
>
> (I just invented the "satisfied" fo= r the lack of a better notation)
>
> Again, I prefer to say tha= t {mi sisku da poi crino} adds an
> object to the universe of discour= se which satisfies {crino} and can map
> to a number of physical obje= cts, therefore creating the feeling of
> a restricted universal quant= ification.
>
> We do this in NatLangs as well: "I'm looking for= a shirt.",
> "I'm searching for something green.", "Ich suche eine K= uh.",
> "Je cherche une vache.", ...
>
> Just to point th= is out again: This is an analysis which I proposed in
> my last mail = and which I never directly read about anywhere. Therefore,
> I'm stil= l waiting for criticism and comments.
>
>> This still suppos= es, of course, that there is something green in the UD,
>> so the property sense is still better.
>
>> Of course, spellin= g out the counterfactual stuff in such a way as to make
>> the qua= ntifier scope points clearer would be nice, too,
>> but no one see= ms to like {tu'a}
>> and it is a little iffy around the edges anyh= ow.
>
> I don't really get, what you try to point out here.
= >
>
> v4hn
>
>
> --
> You received t= his message because you are subscribed to the Google Groups
> "lojban= " group.
> To post to this group, send email to lojban@goo= glegroups.com.
> To unsubscribe from this group, send email to> lojban+unsubscribe@googlegroups.com.
>= For more options, visit this group at
> h= ttp://groups.google.com/group/lojban?hl=3Den.
>
>
> -= -
> You received this message because you are subscribed to the Googl= e Groups
> "lojban" group.
> To post to this group, send email = to lojban@googlegroups.com.
> To unsubscribe from this= group, send email to
> lojban+unsubscribe@googl= egroups.com.
> For more options, visit this group at
> htt= p://groups.google.com/group/lojban?hl=3Den.
>
>
> --<= br>> 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 grou= p, 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 thi= s 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 gro= up at h= ttp://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-837315209-1358091576=:2626--