Received: from mail-pw0-f61.google.com ([209.85.160.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1Q3zkZ-0007AK-2G; Sun, 27 Mar 2011 16:52:06 -0700 Received: by pwi1 with SMTP id 1sf508462pwi.16 for ; Sun, 27 Mar 2011 16:51:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf:date:from:to:subject :message-id:mail-followup-to:mime-version:user-agent :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-disposition; bh=BQSv41RlnZuhJbDe0wuZk4ZhEok2EUYzcqJFJ32ngh8=; b=5u/d38yH8BC73cywXKA3aMpM/MoUrW5R3YoUlmDVBTz7NNuwvfGalEuJaUAse9btwX CY1yfI3QfwxIcZx8GwpuMRTJSokqkkEnZYhC/zGYSLDTdz+TOQdu1Kpt8/gSpSU5s519 oU8C+o0oPwcSEQWHUDjH+6hRpV4jchgNedrW8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:date:from:to:subject:message-id :mail-followup-to:mime-version:user-agent: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-disposition; b=EHuSe7II+yVwc8wJpmw1JGrJgXs2684ziMmOGAiHUjarPSyKMmmt0e9Omb8IXPm7e5 DbzZPYlopqIiULwvPxMpY21FAsVFtMQwj4SJZ6k4GKN58zEkhOCn+6sC9mUmJDAFLOj3 18nO4jiZbr6qBrcTNQcc91RzGhReR+hmKuZqE= Received: by 10.142.158.14 with SMTP id g14mr274704wfe.37.1301269911457; Sun, 27 Mar 2011 16:51:51 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.142.97.18 with SMTP id u18ls4720085wfb.2.p; Sun, 27 Mar 2011 16:51:50 -0700 (PDT) Received: by 10.142.195.3 with SMTP id s3mr3184539wff.22.1301269910582; Sun, 27 Mar 2011 16:51:50 -0700 (PDT) Received: by 10.142.195.3 with SMTP id s3mr3184538wff.22.1301269910557; Sun, 27 Mar 2011 16:51:50 -0700 (PDT) Received: from chain.digitalkingdom.org (digitalkingdom.org [173.13.139.234]) by gmr-mx.google.com with ESMTPS id u26si3606005wfc.1.2011.03.27.16.51.49 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Mar 2011 16:51:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of nobody@digitalkingdom.org designates 173.13.139.234 as permitted sender) client-ip=173.13.139.234; Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1Q3zkK-0007A9-5R for bpfk-list@googlegroups.com; Sun, 27 Mar 2011 16:51:48 -0700 Received: from rlpowell by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1Q3zkJ-0007A2-Vt for bpfk@lojban.org; Sun, 27 Mar 2011 16:51:48 -0700 Date: Sun, 27 Mar 2011 16:51:47 -0700 From: Robin Lee Powell To: bpfk@lojban.org Subject: [bpfk] Uniqueness across quantification. Message-ID: <20110327235147.GM14415@digitalkingdom.org> Mail-Followup-To: bpfk@lojban.org MIME-Version: 1.0 User-Agent: Mutt/1.5.20 (2009-06-14) X-Original-Sender: rlpowell@digitalkingdom.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of nobody@digitalkingdom.org designates 173.13.139.234 as permitted sender) smtp.mail=nobody@digitalkingdom.org Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Length: 1503 In {ci remna cu xabju pa zdani}, we have 3 houses total, one for each person, due to distributivity. But as far as I can tell, the red book does not specificy if each of those houses is distinct; they could all be living in one house, or sharing 2, or one each, there's no way to tell. Worse, there's no way to explicitely mark one case or the other. 1. Am I missing something? 2. Is there a decent, short way to handle this rigorously? {ro le ci zdani cu se xabju pa le ci remna .i je re le ci remna cu xabju pa le ci zdani} is the best I've found, and it's pretty shitty. 3. If the answer to #2 is no, does this seem worthy of explicitely handling? If so, what solution do you propose? I note http://dag.github.com/cll/16/7/ for your consideration, as that seems the only relevant section. I imagine {po'o} could be used here, perhaps with the termset trick shown there. -Robin -- http://singinst.org/ : Our last, best hope for a fantastic future. Lojban (http://www.lojban.org/): The language in which "this parrot is dead" is "ti poi spitaki cu morsi", but "this sentence is false" is "na nei". My personal page: http://www.digitalkingdom.org/rlp/ -- You received this message because you are subscribed to the Google Groups "BPFK" group. To post to this group, send email to bpfk-list@googlegroups.com. To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.