Received: from mail-vc0-f185.google.com ([209.85.220.185]:43469) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TuRuD-0008Cq-Ko; Sun, 13 Jan 2013 10:03:55 -0800 Received: by mail-vc0-f185.google.com with SMTP id m18sf2081288vcm.2 for ; Sun, 13 Jan 2013 10:03:30 -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=wKPe+Nu+ikjcgGfkYPurf8HBqxXFtLjG4tOJe4Y7VXQ=; b=Jy9lSzMK0UEdkA0f59EI6uQr/NRz4sgKn+yL7+P7lVNBthCzbdTt9hDy2gU7OiFJiX eyJ/xMO537jpnrNVCmYL5m1PiN+NIgQOBpFqeaLNuXZuGZe85Nljl8nDQNTWMIptsJQS nX2BU7Ow0hN1a8QOEx+u4KqNSlL5tp+itGhxN8CmkyfCjlNDWrSoAVtgGlSfYsdMDd/P ELnW9wGdxibem2rFmZfN15eX3YwHoPOn0ZM82cEVjUKY60SWPSw4FM5UTtqTN6sypD9b UZ9lVS1Eoa91yeKSwIVAVGdErxw2seulRQ8OtMwEZMidvevoCKb0HSazO2xr9PH6B0Ph jNfw== 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=wKPe+Nu+ikjcgGfkYPurf8HBqxXFtLjG4tOJe4Y7VXQ=; b=upFJET8Y8S5MQMWrwmI184iZ6bk6vyfLJXYtEiQUYVgxAGz0gZlqJ3vZhYInkRw9tA pA65whboFB5x6wTaaspnIE8WZkBYsPTTB/Hv/jXa0Bb9AI1zLGU9EVetfeRlThtKoI1s C+bukx9VNSk2V6AJ7oGfp8/Jb4z9wIiqsw+EwGa5DfLrQz1lBBT1ypcA4PcImhkPPh3z MXqjXCMwEJ8xDTACv7GtBbyMfU6wAaAKzBNXnIDhujrVL2mvxjc9YsbgQezqqROOjgS2 X1Ap0paraq2NEDgnKaPJ9mqZ3tHHnivwqndZzIHpAnASX1FsDKQb+aPBBzaaxMkLg4wr dkSQ== X-Received: by 10.49.75.9 with SMTP id y9mr15022099qev.9.1358100210148; Sun, 13 Jan 2013 10:03:30 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.16.37 with SMTP id c5ls2718927qed.80.gmail; Sun, 13 Jan 2013 10:03:29 -0800 (PST) X-Received: by 10.58.255.230 with SMTP id at6mr36389115ved.31.1358100209202; Sun, 13 Jan 2013 10:03:29 -0800 (PST) X-Received: by 10.58.255.230 with SMTP id at6mr36389113ved.31.1358100209166; Sun, 13 Jan 2013 10:03:29 -0800 (PST) Received: from mail-vb0-f46.google.com (mail-vb0-f46.google.com [209.85.212.46]) by gmr-mx.google.com with ESMTPS id h20si1730476vdg.3.2013.01.13.10.03.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Jan 2013 10:03:29 -0800 (PST) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 209.85.212.46 as permitted sender) client-ip=209.85.212.46; Received: by mail-vb0-f46.google.com with SMTP id b13so2911984vby.33 for ; Sun, 13 Jan 2013 10:03:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.22.107 with SMTP id c11mr87944472vdf.73.1358100209027; Sun, 13 Jan 2013 10:03:29 -0800 (PST) Received: by 10.220.13.197 with HTTP; Sun, 13 Jan 2013 10:03:28 -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> <1357929461.99777.YahooMailNeo@web184406.mail.bf1.yahoo.com> Date: Sun, 13 Jan 2013 13:03:28 -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.212.46 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=20cf307c9eaa87493c04d32f587c X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --20cf307c9eaa87493c04d32f587c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Assuming your "something" is indefinite (i.e. you'd be satisfied by whatever 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 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 Sun, 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, 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 > things; > > 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 > Lojban > > -- 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 > abstraction 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 > have > > {tu'a}, stripped of its connection to (unspecified) buried abstractions > and > > 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 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 > 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 > 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 > {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 > > > > 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 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 > 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, 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 > 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 hav= e > 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 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 > {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 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 > 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 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) =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 > 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 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. > > -- > 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. --20cf307c9eaa87493c04d32f587c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Assuming your "something" is indefinite (i.e. you'd be satisf= ied by whatever green thing), this is somewhat true, though I think xorlo m= akes 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 Sun, Jan 13, 2013 at 12:28 AM, Felipe Gon=E7alves Assis <f= elipeg.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 g= reen
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 o= f
2+2" can be rendered as {mi djuno lo sumji be li re bei li re}, which<= br> 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. =A0O= n 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). =A0Your 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). = =A0But
> not all opaque cases are contrary-to-fact, we have the cases with {du&= #39;u} and
> {nu} and the like already (and regularly screw them up anyhow -- see > raising). =A0The difficult cases are where we are not sure what abstra= ction is
> appropriate -- or even that one is, like thing {sisku} and {djica} and= so
> on. =A0These very often are buried contrary-to-facts and for them we d= o have
> {tu'a}, stripped of its connection to (unspecified) buried abstrac= tions 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}. =A0I = 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 &q= uot;If
> 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 f= act 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 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 m= ajor
> 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). =A0Quantifiers =A0take two wffs and = a variable,
> AxFxGx is AllFsareGs, that universality restricted to the (non-null) > extension of F. =A0or [x:Fx]Gx. =A0I suppose one could avoid the probl= em here by
> using =A0(x)(Green x =3D> Seek I, x), but that doesn't really h= elp.
>
> I would be happy to have a better analysis of "seek", in par= ticular, one
> that allowed for quantifiers to be placed properly without question, b= ut I
> don't see it anywhere. =A0Much of the problem is in how we deal wi= th
> intensional phrases. =A0Of the two usual approaches, having certain pl= aces
> 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. =A0Unfortunately, these cas= es 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= 9;a}. =A0So,
> for me, at least, {mi sisku tu'a da poi crino} means "I am lo= oking 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 gr= een",
> with the quantifier tucked in the right place. =A0The standard explana= tion of
> {tu'a} gets close to this but gets bogged down in technicalities.<= br> > 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. =A0If the extension of {crino} is already non-null, howev= er, this
> object is to be identified with some already present object, which one=
> depending on which one I actually find (more or less). =A0But that kin= d 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. =A0Or, taking the broader view, I am really seeking = every
> green thing individually. =A0Not 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?<= br> >>
>> 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))&q= uot;
> or "A(x) =3D> Green(x) =3D> seek(I, x)" or "foral= l 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 fulfilled
>> if I were to have (in whatever the appropriate sense is) x" a= nd so every
>> green thing fits and none is special ("if my goal were fulfil= led, 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 thin= k, is the
> 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 no= tation)
>
> 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.&quo= t;,
> "I'm searching for something green.", "Ich suche ei= ne 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 &= quot;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@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--20cf307c9eaa87493c04d32f587c--