Received: from mail-lb0-f190.google.com ([209.85.217.190]:33999) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YfFsj-0004Nq-1Q; Mon, 06 Apr 2015 15:52:39 -0700 Received: by lbiv13 with SMTP id v13sf12997122lbi.1; Mon, 06 Apr 2015 15:52:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type: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; bh=9sZFoiqBsRMV7aSXM7A4rZGG1DvFks42EsNU1YZAhRI=; b=op+Zsqffh+mIytNRbMRSEg02SNf6nHPSo6pw2LRJT/+cIrY0vsBFJBUc5NEH+ngM1b w9OYtP6fT8EV42U0XZjpaK1/Invzu8mfLkFgPPYtcKKpWxgIElENLW+wzgxQaFxKjyuF Pu7y5jkxPW6H80+zYNELyJYposOfFZguugIdQkAhc6Q6gtEPXmxlSHYKNfg9dlO2xlDG EJ3j1u80Yg2Nj4ju2pPpu26gklSXs0wOBmhAXoCyUhHRBQhyfmp4M0bxuQYbmJa88f2T NlvL6BU3nLU8o9ZuBA2LJ90iI+19OtlAIVaKXha7XhNms9twwQM2kzgaWVms5/P1THN+ xJXw== X-Received: by 10.152.27.35 with SMTP id q3mr91438lag.9.1428360749544; Mon, 06 Apr 2015 15:52:29 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.36.67 with SMTP id o3ls521431laj.67.gmail; Mon, 06 Apr 2015 15:52:29 -0700 (PDT) X-Received: by 10.152.5.168 with SMTP id t8mr3575961lat.3.1428360749052; Mon, 06 Apr 2015 15:52:29 -0700 (PDT) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com. [2a00:1450:400c:c05::22b]) by gmr-mx.google.com with ESMTPS id sf8si323142wic.2.2015.04.06.15.52.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Apr 2015 15:52:29 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22b as permitted sender) client-ip=2a00:1450:400c:c05::22b; Received: by mail-wi0-x22b.google.com with SMTP id a2so1300282wia.0 for ; Mon, 06 Apr 2015 15:52:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.63.16 with SMTP id c16mr34718450wjs.117.1428360748964; Mon, 06 Apr 2015 15:52:28 -0700 (PDT) Received: by 10.27.56.18 with HTTP; Mon, 6 Apr 2015 15:52:28 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Apr 2015 19:52:28 -0300 Message-ID: Subject: Re: [bpfk] Proposal: sumti must always be tagged with "tag" even if it's elidible. From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=047d7b86da3a0da10d05131627ea X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22b as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - --047d7b86da3a0da10d05131627ea Content-Type: text/plain; charset=UTF-8 On Mon, Apr 6, 2015 at 7:45 AM, Gleki Arxokuna wrote: > > > So this is what I propose: > > abs_term_1 = expr:(abs_tag_term / termset) {return _node("abs_term_1", > expr);} > > abs_tag_term = expr:((!gek tag free* !selbri !gek_sentence (sumti / > joik_ek sumti_3 / KU_elidible free*) / !gek (tag / FA_elidible) free* > !selbri !gek_sentence (sumti) / !gek (sumti free*) CO_clause tag free* / > NA_clause free* KU_clause free* / !selbri !gek_sentence !ek !joik_jek > !gihek NA_clause free* KU_elidible free* / SOI_clause free* subsentence > Let me see if I can understand that: abs_tag_term = !gek tag !selbri !gek_sentence (sumti / joik_ek sumti_3 / KU_elidible) / !gek (tag / FA_elidible) !selbri !gek_sentence sumti / !gek sumti CO_clause tag / NA_clause KU_clause / !selbri !gek_sentence !ek !joik_jek !gihek NA_clause KU_elidible / SOI_clause subsentence What does "abs_" stand for? Is it really necessary to have two parallel sets of term rules? Can you give some motivation for the "tag joik_ek sumti_3" term? No "FA joik_ek sumti_3" to go with it? Also you allow "CO tag" but no "CO FA"? I think you need the CO rule to go before the FA_elidible rule, or it will never be reached. "NA_clause KU_clause" seems unnecessary, since it doesn't capture anything that wouldn't be captured by "!selbri !gek_sentence !ek !joik_jek !gihek NA_clause KU_elidible" does it? Same goes for the first "sumti", it doesn't catch anything that wouldn't be caught by the second one. What does the SOI term mean? Is there a new proposed meaning for "soi"? Is it something like "lo poi'i"? BTW, are there any plans to get rid of SA, or are people still in love with it? It makes the grammar so much harder to read. I don't really have any useful comments at this point because I'm still not up to speed with all the changes in this grammar. mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an email to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --047d7b86da3a0da10d05131627ea Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Mon, Apr 6, 2015 at 7:45 AM, Gleki Arxokuna <gleki.is.my.name@= gmail.com> wrote:

<= /div>
So this is what I propose:

abs_term_1 = =3D expr:(abs_tag_term / termset) {return _node("abs_term_1", exp= r);}

abs_tag_term =3D expr:((!gek tag free* !s= elbri !gek_sentence (sumti / joik_ek sumti_3 / KU_elidible free*) / !gek (t= ag / FA_elidible) free* !selbri !gek_sentence (sumti) =C2=A0/ !gek (sumti f= ree*) CO_clause tag free* / NA_clause free* KU_clause free* / !selbri !gek_= sentence !ek !joik_jek !gihek NA_clause free* KU_elidible free* / SOI_claus= e free* subsentence=C2=A0

L= et me see if I can understand that:=C2=A0

=C2=A0ab= s_tag_term =3D=C2=A0
=C2=A0 =C2=A0!gek tag !selbri !gek_sentence = (sumti / joik_ek sumti_3 / KU_elidible)
=C2=A0/ !gek (tag / FA_el= idible) !selbri !gek_sentence sumti
=C2=A0/ !gek sumti CO_clause = tag
=C2=A0/ NA_clause KU_clause
=C2=A0/ !selbri !gek_se= ntence !ek !joik_jek !gihek NA_clause KU_elidible
=C2=A0/ SOI_cla= use subsentence=C2=A0

What does "abs_&qu= ot; stand for? Is it really necessary to have two parallel sets of term rul= es?

Can you give some motivation for the &qu= ot;tag joik_ek sumti_3" term? No "FA joik_ek sumti_3" to go = with it? Also you allow "CO tag" but no "CO FA"? I thin= k you need the CO rule to go before the FA_elidible rule, or it will never = be reached.

=C2=A0"NA_clause KU_clause" = seems unnecessary, since it doesn't capture anything that wouldn't = be captured by "!selbri !gek_sentence !ek !joik_jek !gihek NA_clause K= U_elidible" does it? Same goes for the first "sumti", it doe= sn't catch anything that wouldn't be caught by the second one.

What does the SOI term mean? Is there a new proposed m= eaning for "soi"? Is it something like "lo poi'i"?= =C2=A0

BTW, are there any plans to get rid of SA, = or are people still in love with it? It makes the grammar so much harder to= read.

I don't really have any useful comments= at this point because I'm still not up to speed with all the changes i= n this grammar.

mu'o mi'e xorxes

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
--047d7b86da3a0da10d05131627ea--