Received: from mail-ye0-f183.google.com ([209.85.213.183]:35811) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TuSNe-0008Qs-W1; Sun, 13 Jan 2013 10:34:29 -0800 Received: by mail-ye0-f183.google.com with SMTP id r5sf2089238yen.0 for ; Sun, 13 Jan 2013 10:33:56 -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-id:x-yahoo-newman-property:x-ymail-osg:x-yahoo-smtp :subject:references:from:x-mailer:in-reply-to:message-id:date:to :mime-version: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:content-transfer-encoding; bh=LjfIwi3Fc55nlIBBK3lxV1MNtAcvaL6pmfUiZh9LMSI=; b=KCfUgWniFzwEpptdAG0c/PnnLwumybfkmEUI4HC2TInPxLM8l0bfT/F4Hqvn/b5J4l Ih9dcOCGFl1SsXdH8dt1hUMNHlcPVemw96R3I9ntgxAqB6l7k4j1KLEBFKQwMjS+vex9 Sf7EGcwV/itdaCGTdefQjcCMnyWdpL1b0cDbSRcZi1viaz4jMDXf5GjMUeSfll2TiJbu eenJDN9Y+IhuLa2N9RVS3Np7e7+pvHBrbOhC696HZydE6x0BCz/uS2ni2exnlPbR/YPj C8IreZRKIMzpNShpHxKBNn8KmNotIlteOGQmR+7wTOiYXD7iYPS0GLhOvXPIsp1VfTuu jC+g== X-Received: by 10.49.1.162 with SMTP id 2mr11520355qen.2.1358102035724; Sun, 13 Jan 2013 10:33:55 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.94.139 with SMTP id dc11ls2971022qeb.1.gmail; Sun, 13 Jan 2013 10:33:54 -0800 (PST) X-Received: by 10.59.0.73 with SMTP id aw9mr36043553ved.1.1358102034236; Sun, 13 Jan 2013 10:33:54 -0800 (PST) X-Received: by 10.59.0.73 with SMTP id aw9mr36043552ved.1.1358102034206; Sun, 13 Jan 2013 10:33:54 -0800 (PST) Received: from nm34-vm4.bullet.mail.bf1.yahoo.com (nm34-vm4.bullet.mail.bf1.yahoo.com. [72.30.239.76]) by gmr-mx.google.com with ESMTPS id u2si1747140vdi.2.2013.01.13.10.33.53 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 13 Jan 2013 10:33:54 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 72.30.239.76 as permitted sender) client-ip=72.30.239.76; Received: from [98.139.212.151] by nm34.bullet.mail.bf1.yahoo.com with NNFMP; 13 Jan 2013 18:33:53 -0000 Received: from [98.139.173.161] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 13 Jan 2013 18:33:53 -0000 Received: from [127.0.0.1] by smtp104-mob.biz.mail.bf1.yahoo.com with NNFMP; 13 Jan 2013 18:33:53 -0000 X-Yahoo-Newman-Id: 690406.63393.bm@smtp104-mob.biz.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: tMjQd4IVM1meTLuStt1JGXFqOu3VF_zOjUKkYvae_CgvfAW FtEWpmcOzO3icvUtfpV9xXNSndzeJ4.7mefQxAG59uuzgK6eE3YL0KaO8.p3 Ibk1McKjHoUHWWNYZo1XLJamK1jSsJLj.GC78KNlUeCWgi0WkNrW5UUughWf GxhyY3CqIf2ycOOQJ5JCFJLSqtRFp95IdSfIJ4xivxCLmXT5TraKdSKfyrpC ywFSPyCoLZmekQwvgDfztGTzcysfIuC4aak9lHFwCHIxsphipYSZmrrbkjpg WBGj6mpZPau4Fdh6jhTMpVwItBN.vaLF3h.5pC7g61vfVmsw0WsUSdWtVO2x Q_ihJCDxWTNjrZhWd4aYvUW69H37aXVRDU2BFd4S2_WgPfSKCLiYpGNAgCod ZIaBCoUwZPZ.CDeC3rdj_kRVi3.E9PW5dbZ6eSl1b7hSehKRP37Lw8Pqtszg XaOA_gEppaZjha7eIDIxfvipheXSExe1gg4PWAA5kMZHimstHMpjmhk91Z03 312DDZIc0FoX8wcpKsza_3WtS_gm3Mf1xCduKnqvYem3z1IfilxL2Dd6.lA- - X-Yahoo-SMTP: xvGyF4GswBCIFKGaxf5wSjlg3RF108g- Received: from [192.168.1.64] (kali9putra@99.92.108.194 with xymcookie) by smtp104-mob.biz.mail.bf1.yahoo.com with SMTP; 13 Jan 2013 10:33:53 -0800 PST Subject: Re: [lojban] searching 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> From: "John E. Clifford" X-Mailer: iPad Mail (9B206) In-Reply-To: Message-Id: <33AF83F9-B183-42BB-86BC-9344C4E2F93F@yahoo.com> Date: Sun, 13 Jan 2013 12:33:53 -0600 To: "lojban@googlegroups.com" Mime-Version: 1.0 (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 72.30.239.76 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass header.i=@yahoo.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=Apple-Mail-9B2156EE-044E-4284-8C80-93D1873913D1 Content-Transfer-Encoding: 7bit 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: Well, yes, {lo crino} might be the topmost node in the extension of {crino} and apply disjunctively as {sisku2}, but there still have to be green things for this to work, and there made not be -- hence the search, after all. [...] 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 --Apple-Mail-9B2156EE-044E-4284-8C80-93D1873913D1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Well, yes, {lo crino} might be the topmost node in the extension of {crino}= and apply disjunctively as {sisku2}, but there still have to be green thin= gs for this to work, and there made not be -- hence the search, after all. Sent from my iPad On Jan 13, 2013, at 12:03, Ian Johnson wrote: > Assuming your "something" is indefinite (i.e. you'd be satisfied by whate= ver green thing), this is somewhat true, though I think xorlo makes it more= slippery than your example. That is, {lo crino} could just be a blob of al= l the green things and could interact with sisku in such a way that you're = satisfied by finding any of them. >=20 > mi'e la latro'a mu'o >=20 > On Sun, Jan 13, 2013 at 12:28 AM, Felipe Gon=E7alves Assis wrote: > John has already made a very careful logical analysis of the topic, > so let me try something more concrete: >=20 > 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}. >=20 > mu'o > mi'e .asiz. >=20 >=20 > On 11 January 2013 15:37, John E Clifford wrote: > > Not sure how this helps, but there are two different issues here. On t= he > > one hand, we need to deal with opaque phrases in the ordinary run of th= ings; > > on the other hand we need to deal with contrary-to-fact situations as n= ot > > ordinary run of things (though far more common than appears in most Loj= ban > > -- mainly 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 back= into > > the definition of words involved, so still available to surprise us). = 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). 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. 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= and > > nebulous predicates, as a mark that the following term 1) cannot be mov= ed 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 world= s > > 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 invol= ve > > just working out the rules on scope and the like for {da'i}. I do not > > include the problems with truth conditions here, of course, since, so f= ar 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 = been > > 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 a= s "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 crin= o} > > 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 {sisk= u}). > > 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 han= dle > > 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 interrogati= ve, > > but thosedon't turn up here). Quantifiers take two wffs and a variabl= e, > > AxFxGx is AllFsareGs, that universality restricted to the (non-null) > > extension of F. or [x:Fx]Gx. I suppose one could avoid the problem he= re 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, on= e > > that allowed for quantifiers to be placed properly without question, bu= t 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 place= s > > specified as such in the lexicon or having all places transparent but s= ome > > phrases labelled as intensional, Lojban has chosen a position in the mi= ddle. > > 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} (whi= ch is > > not actually in Lojban, after all, but is popularly uses as though it w= ere), > > where the transparent place yields unwanted results. > > Ultimately, of course, what we want is a particular quantifier in the s= cope > > 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 hav= e a > > goal which would be satisfied just in case I were to have something gre= en", > > with the quantifier tucked in the right place. 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}= may > > change the UD by adding an object to guarantee that the extension of {c= rino} > > 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 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= of > > the external quantifier (which we never did really leave, if the slot w= as > > 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 eve= ry > > green thing individually. 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> see= k(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 fulfil= led > >> 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 wo= uld > >> have"). > > > > I'm not sure I like that "goal driven" analysis of seek. > > Especially, mixing up quantifiers and goal constraints is rather confus= ing. > > > > 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 th= ings > > 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 a= bout > > 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 U= D, > >> so the property sense is still better. > > > >> Of course, spelling out the counterfactual stuff in such a way as to m= ake > >> 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 Grou= ps > > "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 Grou= ps > > "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 Grou= ps > > "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@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?hl=3Den. >=20 >=20 > --=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@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?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. --Apple-Mail-9B2156EE-044E-4284-8C80-93D1873913D1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
Well, yes, {lo crino} mig= ht be the topmost node in the extension of {crino} and apply disjunctively = as {sisku2}, but there still have to be green things for this to work, and = there made not be -- hence the search, after all.

Sent from m= y iPad

On Jan 13, 2013, at 12:03, Ian Johnson <blindbravado@gmail.com> wrote:
Assuming your "something" = is indefinite (i.e. you'd be satisfied by whatever green thing), this is so= mewhat true, though I think xorlo makes it more slippery than your example.= That is, {lo crino} could just be a blob of all the green things and could= interact with sisku in such a way that you're satisfied by finding any of = them.

mi'e la latro'a mu'o

On Su= n, Jan 13, 2013 at 12:28 AM, Felipe Gon=E7alves Assis <= ;felipeg.assis= @gmail.com> wrote:
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, Joh= n E Clifford <kali9putra@yahoo.c= om> wrote:
> Not sure how this helps, but there are two different issues here. &nbs= p;On the
> one hand, we need to deal with opaque phrases in the ordinary run of t= hings;
> 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 Lo= jban
> -- mainly 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 bac= k into
> the definition of words involved, so still available to surprise us). =  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).  The difficult cases are where we are not sure what abs= traction is
> appropriate -- or even that one is, like thing {sisku} and {djica} and= so
> on.  These very often are buried contrary-to-facts and for them w= e do have
> {tu'a}, stripped of its connection to (unspecified) buried abstraction= s and
> nebulous predicates, as a mark that the following term 1) cannot be mo= ved 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 worl= ds
> which represent the working out of the predicate to which the term is<= br> > attached as argument.
> The matter of contrary-to-fact or hypothetical sentences seems to invo= lve
> just working out the rules on scope and the like for {da'i}.  I d= o 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 "I= f
> Socrates were a 17th century Irish washerwoman, would Plato still have= been
> gay?"
>
>
> ________________________________
> From: Ian Johnson <blindb= ravado@gmail.com>
> 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", the= n {mi
> sisku lo ckiku} does what was originally wanted while {mi sisku ro cri= no}
> does what {mi sisku lo ka crino} is defined to do. So this definition<= br> > 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<= br> > (rather common) case. {.e} frustratingly doesn't work.)
>
> This definition feels highly nonprimitive (though so does current {sis= ku}).
> In particular (in this regard unlike current {sisku}) it induces hidde= n
> 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 ha= ndle
> 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, 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).  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 he= lp.
>
> I would be happy to have a better analysis of "seek", in particular, o= ne
> that allowed for quantifiers to be placed properly without question, b= ut I
> don't see it anywhere.  Much of the problem is in how we deal wit= h
> 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 m= iddle.
> 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} (wh= ich 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 th= e
> present UD) is required, since it expands to the more satisfying "I ha= ve a
> goal which would be satisfied just in case I were to have something gr= een",
> with the quantifier tucked in the right place.  The standard expl= anation 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 po= i
> 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, ho= wever, 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 positio= n of
> the external quantifier (which we never did really leave, if the slot = was
> transparent), that I was really seeking this particular thing, not jus= t any
> old thing at all.  Or, taking the broader view, I am really seeki= ng every
> green thing individually.  Not what is wanted.
>
>
>
> ________________________________
> From: v4hn <me@v4hn.de>
> 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 sen= se,
>> not the property sense) is short for "has a goal which would be fu= lfilled
>> 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 confu= sing.
>
> What your "Ax Greenx I seek x" is _supposed_ to mean, I think, is the<= br> > following.
>
> There exists a goal G1 which I have in mind, such that for all green t= hings
> it is true that if I have such a green object, the goal G1 is fulfille= d.
>
> 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) =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 ma= p
> 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<= br> > 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 t= he 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 Gro= ups
> "lojban" group.
> To post to this group, send email to lojban@googlegroups.com.
> To unsubscribe from this group, send email to
> lojban+unsubs= cribe@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 Gro= ups
> "lojban" group.
> To post to this group, send email to lojban@googlegroups.com.
> To unsubscribe from this group, send email to
> lojban+unsubs= cribe@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 Gro= ups
> "lojban" group.
> To post to this group, send email to lojban@googlegroups.com.
> To unsubscribe from this group, send email to
> lojban+unsubs= cribe@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/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@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@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--Apple-Mail-9B2156EE-044E-4284-8C80-93D1873913D1--