From a.rosta@dtn.ntl.com Sat Jul 28 14:30:41 2001 Return-Path: X-Sender: a.rosta@dtn.ntl.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_2_0); 28 Jul 2001 21:30:41 -0000 Received: (qmail 90243 invoked from network); 28 Jul 2001 21:30:40 -0000 Received: from unknown (10.1.10.27) by m8.onelist.org with QMQP; 28 Jul 2001 21:30:40 -0000 Received: from unknown (HELO relay3-gui.server.ntli.net) (194.168.4.200) by mta2 with SMTP; 28 Jul 2001 21:30:40 -0000 Received: from m189-mp1-cvx1b.bir.ntl.com ([62.255.40.189] helo=andrew) by relay3-gui.server.ntli.net with smtp (Exim 3.03 #2) id 15QbQF-0003YF-00 for lojban@yahoogroups.com; Sat, 28 Jul 2001 22:14:56 +0100 To: Subject: RE: [lojban] Tidying notes on {goi} Date: Sat, 28 Jul 2001 22:29:53 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 From: "And Rosta" Jorge: > la pycyn cusku di'e > > >Cowan: > > >normal quantifier, so the second {su'o da} means "one or more of (the > >existing) da", not very useful.But ro da poi .... re da would mean "two of > >those which etc."> > > > >Well, those are remarkably UNnormal quantifiers in logic, but right for > >that > >part of lojban that has the standard sumti as quantifier-gadri-bridi.i.e., > >quantifier-sumti. The point is also correct. > > What has the world come to? I thought pc was going to be horrified > at this new binding of an already bound variable! > > Anyway, how do we read this then: > > ro da poi prenu zo'u da prami su'o da > > Is that {ro da poi prenu zo'u da prami da}, or is it > {ro da poi prenu ku'o ro de poi prenu zo'u da prami de}? I must have misunderstood. I glorked that the idea was that "ci da poi prenu prami re da" would mean "There are exactly three people such that each of the three loves some two of the three". > >Proposal (clarification?): {goi} is always defining and always takes the > >form > > {x goi y}, where y is assigned the value of x. > [...] > >Objection. (I really need help here, since the one objection seems to be > >that > >we sometimes want to do the defining in the reverse order and so need {goi} > >not {no'u}, which is only factual, not defining. This seems to trivial to > >bother with -- and can {goi} take {se} if it really makes a difference?) > > I would say that the objection is that it is not strictly > necessary to fix one order. In the cases where both sumti already > have a referent, goi makes no sense. In the cases where neither > has a referent, goi makes little sense, but none that requires the > connectands to be in a particular order anyway. And if one has > a referent and the other doesn't, it is clear which one gets assigned. > Of course, the order helps when the listener is in doubt as to what > the speaker means, so it works as a measure of redundancy. This was the objection, but I dispute that it is always clear which sumti has or lacks a referent. > In any case, I find goi too cumbersome for actual use, so I don't > have a strong opinion one way or the other. I agree it's too cumbersome, but AFAIAA there is no equally robust and unambiguous alternative. I wish there were more multiple alternative methods of doing anaphora, distinguished by method rather than by verbosity; I'd have been extremely interested to see which found most favour in usage. In fact, if I could have designed one kosher academic research project with loglan, it would have been this. --And.