Received: from mail-wy0-f189.google.com ([74.125.82.189]:33750) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RFE2R-0004J9-Hp; Sat, 15 Oct 2011 16:53:18 -0700 Received: by wyh11 with SMTP id 11sf7428957wyh.16 for ; Sat, 15 Oct 2011 16:52:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere: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=U2RZfcKbf9vfvPJowy+PHZV4o+S2yfzptWH2KbSBglU=; b=rz7cS37bmTugA/ePzP8r2Rij2O+Zbmgfrey6Iydg61QOOpYWH2IH+yHlERyrCOmUje /NdEXnYhVcMwgD5AnKsPguIvc5/ARtRODL4mfpb9O8zCBjbWEBZ3X8kyBNEWvYMUUUpp inM+J71cJDKUrvSBRl82PP2C0YxOixn3b/q+E= Received: by 10.216.167.138 with SMTP id i10mr616350wel.21.1318722776188; Sat, 15 Oct 2011 16:52:56 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.14.41.145 with SMTP id h17ls325791eeb.1.canary; Sat, 15 Oct 2011 16:52:54 -0700 (PDT) Received: by 10.14.7.212 with SMTP id 60mr404332eep.14.1318722774439; Sat, 15 Oct 2011 16:52:54 -0700 (PDT) Received: by 10.14.7.212 with SMTP id 60mr404331eep.14.1318722774428; Sat, 15 Oct 2011 16:52:54 -0700 (PDT) Received: from mail-ey0-f170.google.com (mail-ey0-f170.google.com [209.85.215.170]) by gmr-mx.google.com with ESMTPS id 4si3728015eew.1.2011.10.15.16.52.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Oct 2011 16:52:54 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.215.170 as permitted sender) client-ip=209.85.215.170; Received: by eyg7 with SMTP id 7so2361480eyg.15 for ; Sat, 15 Oct 2011 16:52:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.17.11 with SMTP id q11mr13904121faa.13.1318722774204; Sat, 15 Oct 2011 16:52:54 -0700 (PDT) Received: by 10.152.39.35 with HTTP; Sat, 15 Oct 2011 16:52:54 -0700 (PDT) In-Reply-To: <20111015232240.GG3779@gonzales> References: <4E981179.1030805@gmail.com> <20111015155009.GA5916@gonzales> <20111015185726.GC3779@gonzales> <20111015203444.GD3779@gonzales> <20111015221511.GF3779@gonzales> <20111015232240.GG3779@gonzales> Date: Sat, 15 Oct 2011 20:52:54 -0300 Message-ID: Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 209.85.215.170 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass (test mode) 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: text/plain; charset=ISO-8859-1 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / On Sat, Oct 15, 2011 at 8:22 PM, Martin Bays wrote: > > It could *suggest* that the {lo xasli} > should be interpreted more specifically, I suppose, but I don't see why > it should do so any more than the {noi} clause. "noi" makes perfect sense when applied to a singleton. "poi", while still interpretable, doesn't make that much sense because the only thing a singelton could be restricted to is itself, so no real restriction. It's the same situation that occurs with quantifiers: you can quantify over a singleton, but since doing so is rather pointless, the mere presence of a quantifier suggests the domain should not be a singleton. >> (In fact I'm never quite sure about what to do with "poi" when it is >> not being used to restrict the domain of a quantifier.) > > Quite. If it does do anything, there's also the issue of which gets > priority in {ro lo broda poi brode}. Does it make an actual difference? "ro lo broda poi brode" = "ro da poi me lo broda zi'e poi brode". >> "lo speni be da" is "zo'e noi speni da". I don't see how you could get >> rid of the unbound variable there. There's no referential "lo speni" >> in the non-referential "lo speni be da". > > OK, but if {lo speni be da} == {zo'e noi speni da}, then we have > a situation analogous to that above - with {zo'e} in place of {lo > xasli}. {zo'e} can be taken to referential, for example with referent > the kind 'humans', which does indeed satisfy {ke'a speni da} for each > da. > >> > Given this, I'm now slightly surprised that you're willing to allow {lo} >> > to ever give a Skolem function rather than a constant! >> >> If the selbri that "lo" transforms into a sumti contains an unbound >> variable, then I don't see how "lo" can create out of it anything >> other than a function. > > So am I taking "{lo} -> {zo'e noi}" too literally? Hmm... Maybe you are right, and it never need be a function, or at least not always. It needs more thought. mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en.