Received: from mail-wy0-f189.google.com ([74.125.82.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P50iz-0006Eh-Rg; Sun, 10 Oct 2010 11:34:25 -0700 Received: by wyb40 with SMTP id 40sf648735wyb.16 for ; Sun, 10 Oct 2010 11:34:15 -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-spf:received:mime-version:received:received :in-reply-to:references:date:message-id:subject:from: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 :content-transfer-encoding; bh=7ZWbEJXZmKNToaNZ+YYdGsg07wQuGl3DaWdw5I0G2bU=; b=bigjJP8hm5OLYCEesFVp/bTQCyPHYMJskaNxxSV2nx4Q76viBWDrKXYJsxUrnIVxlc AZu7ILTGEDpqOW08bKa4IwZ+yAXOiCj1sp5ukva7p6h7qwhifqIqVg7Dlg+3jV/cA6N6 gwxStVRI90s0E05eqnsEesnN1bdQptcmbzsVQ= DomainKey-Signature: a=rsa-sha1; c=nofws; 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:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type:content-transfer-encoding; b=rYGCaHffUCmM6OYRxK5yh+LbUj4Wph5scvJ2QDgeAyDt8IXNSAJUkz/Fbdkb7vmLCz sjXWbuquDWADEL1X3tnSJlGYUo7U+i7sPD01cA/YoKFJMfuMVjXnuGn8BexG+N+9X9oS D4tfmwzGS7dX2cv5PHJ7XqO7NUvW1b+lONTuY= Received: by 10.216.237.206 with SMTP id y56mr336524weq.12.1286735649138; Sun, 10 Oct 2010 11:34:09 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.227.168.134 with SMTP id u6ls896916wby.1.p; Sun, 10 Oct 2010 11:34:08 -0700 (PDT) Received: by 10.227.128.76 with SMTP id j12mr211731wbs.19.1286735647938; Sun, 10 Oct 2010 11:34:07 -0700 (PDT) Received: by 10.227.128.76 with SMTP id j12mr211730wbs.19.1286735647908; Sun, 10 Oct 2010 11:34:07 -0700 (PDT) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by gmr-mx.google.com with ESMTP id k1si1914559wbc.0.2010.10.10.11.34.06; Sun, 10 Oct 2010 11:34:06 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 74.125.82.181 as permitted sender) client-ip=74.125.82.181; Received: by wyf22 with SMTP id 22so2203002wyf.40 for ; Sun, 10 Oct 2010 11:34:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.135.75 with SMTP id m11mr4841816wbt.96.1286735646601; Sun, 10 Oct 2010 11:34:06 -0700 (PDT) Received: by 10.227.145.130 with HTTP; Sun, 10 Oct 2010 11:34:06 -0700 (PDT) In-Reply-To: <4CB1FC05.4030108@lojban.org> References: <4CB0B239.50107@lojban.org> <4CB1FC05.4030108@lojban.org> Date: Sun, 10 Oct 2010 15:34:06 -0300 Message-ID: Subject: Re: [bpfk] BPFK work From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: bpfk-list@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 74.125.82.181 as permitted sender) smtp.mail=jjllambias@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-Transfer-Encoding: quoted-printable Content-Length: 2900 On Sun, Oct 10, 2010 at 2:46 PM, Robert LeChevalier wro= te: > > Nora and I have been reading along in this thread now, and I think we > understand what the issue is, and see one ramification that has not been > mentioned. =A0She mentioned in IRC where there may be several conversatio= ns > going on at once. =A0I wish to reply to someone effectively continuing th= e > "text" that is comprised by the various exchanges in the conversation. The normal way would be to start your own text and address it to the person whose text you are replying to. Why is it necessary, or even desirable, to include your text as a part of their text? A conversation consists of an exchange of texts, it does not consist of a single text. Forcing the whole conversation into a single text makes little sense. In fact when we quote a text with lu...li'u we normally quote the text produced by one speaker. A text normally has a speaker and an audience. Those are the referents of "mi" and "do" as used in the text. The speaker may occasionally be a plurality, but it still counts as one producer of text, and all the words of the text count as coming from them. That's what the place structure of "cusku" tells us, doesn't it? The speaker, the text, the audience. It's not the participants of a conversation and some text they all weave together, > =A0Clearly such an explicit continuation needs to be a vocative (selma'o = COI). > =A0Only when there is one single other > "speaker" that could be continued would it not need to be a vocative. The normal thing would be to use "doi", and in fact that is how it is often done in IRC. > If none of them are quite what is wanted, I will admit that I am more > amenable to adding cmavo to the COI selma'o than probably any other, > especially if they are protocol-related as this is, because we knew from = the > beginning that we had not covered all conversation protocol issues. The proposed "di'ai" cannot be added to any selma'o, because it is a meta-syntactic indication to the pre-parser to merge two texts into one before parsing, it is not something that can be part of the formal grammar. It has to be processed before you feed the input to the parser, indeed as part of deciding what to feed to the parser. > The other observation is that whatever we are trying for is metalinguisti= c > in nature, and thus can probably be expressed using SEI. Not really. SEI is meta-semantic, but what some people are asking for is meta-syntactic, which is not somethiing SEI can handle. mu'o mi'e xorxes --=20 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@googleg= roups.com. For more options, visit this group at http://groups.google.com/group/bpfk-l= ist?hl=3Den.