Received: from mail-gw0-f61.google.com ([74.125.83.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P4cYI-0002gn-1i; Sat, 09 Oct 2010 09:45:45 -0700 Received: by gwj21 with SMTP id 21sf537769gwj.16 for ; Sat, 09 Oct 2010 09:45:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received:received-spf:received:received:references:from :in-reply-to:mime-version:date:message-id:subject:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=KX2+ZpN+7on3hZSDzisvp6r+zGKV+/dAI/6TuFiCEU0=; b=Uqo5kdKPx96tLn+jCxRB+slPebfuYyIgksgHBSdA8jjS+ylfkNwDGIqxAo/hdUIkLo XMGqCt1l+yvYitzDeS0qmJL7Zb7F+amIKy8t/LiXFgIACW1zoNK4zBtO2kfW0Vz+eqGt cvYEZYyNaxVIYGTwmYZjjnp7Am+WP6AAGAUOw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:references:from:in-reply-to:mime-version :date:message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; b=mOodYCGcFep7M/oa/6mOZHyTQUQBpFXG5i2WZZMtEq0WuTtFl6GCRhPOhNNx9K5Og/ iho63Y6UmiHbZ446ChKjrk29+Hi/0nqXyIjKTK1cQ/Qx4l16LTcIA/sw/+jnU44ptGbV KuRCq72NAqsykjpCS6rnLn4od8NroumLNOgS8= Received: by 10.151.116.16 with SMTP id t16mr320883ybm.68.1286642729991; Sat, 09 Oct 2010 09:45:29 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.150.158.14 with SMTP id g14ls717938ybe.7.p; Sat, 09 Oct 2010 09:45:29 -0700 (PDT) Received: by 10.151.105.8 with SMTP id h8mr934456ybm.21.1286642729586; Sat, 09 Oct 2010 09:45:29 -0700 (PDT) Received: by 10.229.212.137 with SMTP id gs9mr580861qcb.15.1286621042387; Sat, 09 Oct 2010 03:44:02 -0700 (PDT) Received: by 10.229.212.137 with SMTP id gs9mr580860qcb.15.1286621042343; Sat, 09 Oct 2010 03:44:02 -0700 (PDT) Received: from mail-qw0-f50.google.com (mail-qw0-f50.google.com [209.85.216.50]) by gmr-mx.google.com with ESMTP id l26si1953933qck.1.2010.10.09.03.44.01; Sat, 09 Oct 2010 03:44:01 -0700 (PDT) Received-SPF: pass (google.com: domain of dbrockman@gmail.com designates 209.85.216.50 as permitted sender) client-ip=209.85.216.50; Received: by mail-qw0-f50.google.com with SMTP id 5so1392210qwg.37 for ; Sat, 09 Oct 2010 03:44:01 -0700 (PDT) Received: by 10.229.204.169 with SMTP id fm41mr2980855qcb.259.1286621041175; Sat, 09 Oct 2010 03:44:01 -0700 (PDT) References: <20100903032539.GY5990@digitalkingdom.org> From: Daniel Brockman In-Reply-To: Mime-Version: 1.0 (iPhone Mail 8A293) Date: Sat, 9 Oct 2010 12:45:09 +0200 Message-ID: <8136604407292225759@unknownmsgid> Subject: Re: [bpfk] BPFK work To: "bpfk-list@googlegroups.com" X-Original-Sender: dbrockman@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dbrockman@gmail.com designates 209.85.216.50 as permitted sender) smtp.mail=dbrockman@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Length: 1258 This is a very typical example of someone trying to "standardize" an aspect of the language that obviously is very context-dependent. This is impossible and the only effect is to generate endless flame wars. Jorge suggested a workable solution several messages ago: use a cmavo to explicitly distinguish between the two candidate interpretations when necessary. This is the only practical way to avoid ambiguity. It also adds flexibility to the language in a very lojbanic way: suddenly it supports both isolating yourself from previous speakers and continuing other utterances (something which, by the way, is very rare in practice). Most importantly, this leaves the unmarked forms context-dependent, which means nobody needs to fight over what these extremely common expressions "actually" mean: it's simply up to context. You only have to use the explicit marker in unusual cases, or when extreme unambiguity is needed. -- 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.