Received: from mail-wm0-f61.google.com ([74.125.82.61]:51578) by stodi.digitalkingdom.org with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1eFMuh-0007V6-Mk for lojban-list-archive@lojban.org; Thu, 16 Nov 2017 08:21:18 -0800 Received: by mail-wm0-f61.google.com with SMTP id k3sf256458wmg.6 for ; Thu, 16 Nov 2017 08:21:15 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1510849269; cv=pass; d=google.com; s=arc-20160816; b=EO1fmS00n45eavx43fk5+nMIxaOB0sSHPRhGALayKQitcoE25u6QFaVcU+1vDPyvpZ f8ge2qizE4SgP1mELLiAPXXXjLdiyRfaZ5InbzdAh3NYD0xYAoyEdKlgea5rGt7OD9z4 qVdsp0YXU2Q1sTbtPYS1NRFTZpoPmD3Sjoji9T165a1FKdaoJAjAV3MqUuZQZqL+IFqG P6A0Z8DXYQWVHb4GTFYuE+iTx5JwX/ijOcL0o25bvXQuiBxOOq5aWVY4azCt3JjTp4Rh 01N6iCZXNvr7mhMnfKvVhl2/q96wwjTzEvpu6XorfcCFtAhak2zduNi7AoIFK6V8Yegv xAUg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:message-id:from:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date:arc-authentication-results:arc-message-signature :sender:dkim-signature:arc-authentication-results; bh=5IgdYKUR7rRHRVf7FRphMb1kx65jfoL2V0aD/uIp+oE=; b=Z8LkatBj14vbUlFoeAfIuwIpKqLHKEmGr8M8I+GofG4yHgtPu9X8tt99P5ZxCOutRm ytsaf+bwvt3ry3h6blpn8VrtZOdcZ2g/aEKmdzqPxCzGyM5rnZl/XdInWyrjEooB9jp1 pWs9QNQTkJAaZ5YJ9XWj2fUPmETGdZPTYB8YKVIx7PgCMOsZv38BBtz3i6MeC49kaMNk Dcha6SS7NW2Xn6ayUZv2IcsPcpaDhOo/zDAg8eCO/S1EFdrM/qPEDiu2+7P1dC5zmfjd n8JxLHQHYwCiwkQPM6eXHjRwJZ3zu8XNVQo++LxUdOQCXJGr+UNeUUKcN07Mhon92B/Z CivQ== ARC-Authentication-Results: i=2; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of sukender@free.fr designates 212.27.42.3 as permitted sender) smtp.mailfrom=sukender@free.fr DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:from:message-id :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=5IgdYKUR7rRHRVf7FRphMb1kx65jfoL2V0aD/uIp+oE=; b=gRCsvYASSlUjZpMpuo+ARO06NJaSunaJowQ6da9Qgojnu9pV/0aEpf8m8w/S41B63F TvhH8VtOTs8NoayG40e+k6MNzdm/uCbPnePa6J+dGLNNjuOjAOMJI2qglRMoXzrn1mJG XWBHDsj0inh23VniAhma1fVEOlGn7mRsMjwEENhklpz2hZSbkm4c9bwYRXOPrIgBN+HV 2JfPma9KcrISbAjKt1Byeya8ZjKDWxXGO3+RFcC0vmqkoi5Wt/BwTeRqXcaHbLtjwE37 1s+6R+fL81/RQZqKjaAO0KdMfPaBLsAQXiAc1TxAuC2a1MGHuaGuz8ekjSP70iRg5omP xfCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:from:message-id :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=5IgdYKUR7rRHRVf7FRphMb1kx65jfoL2V0aD/uIp+oE=; b=tTbAwxMGPL4RMg0EkuF5Pv3ZsFJIDl74TNra00KVue7tPmceszjmO4+vEnPyM1px4H oWbllnC4Miu1cKeePWkLj4jHfJqr+Elwj1RgmMe8Oz0npfvTANLbs1d5EEcfJ+YOLLuP w4DnwtD/CA44yCJn9G3SgQ3rvStjd5L4xE1rsfpBws+DwXCnzZFkEZNH1X86LiMnxgoo HBfPU+ILzrEMi1f9anrtqMBlh7T2gllj6wrk2XPn6M9Ngek3Bh9DksTRg0gjixpZqVNm hHzegVm+Wu+c8NvfLjKj+0RkWbLbdDawyHJG1jfNhX2T73fE7yzpHnt4qwWHxEXCLXX7 PxlQ== Sender: lojban@googlegroups.com X-Gm-Message-State: AJaThX5lRLnFcLV13NghBBkuLZfFlYNAGZc3lPr70gHmNQ3d1ayM/xdy xxR4Qn8oIAMHtrYhxZs6Ov8= X-Google-Smtp-Source: AGs4zMbwlGG3pmKQGkfVJqTjM8ZYQAOoAJrX8NG5iVXSY/d0qc4AqT9guL7XF1TNoX2CoESVZCrNFQ== X-Received: by 10.28.147.75 with SMTP id v72mr24469wmd.2.1510849269085; Thu, 16 Nov 2017 08:21:09 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.80.167.100 with SMTP id h91ls1171612edc.8.gmail; Thu, 16 Nov 2017 08:21:08 -0800 (PST) X-Received: by 10.80.201.7 with SMTP id o7mr899596edh.3.1510849268475; Thu, 16 Nov 2017 08:21:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510849268; cv=none; d=google.com; s=arc-20160816; b=WFsgKKc1+KcM9BicDW7vY9SAT4o3MBhlqq2x0mQ5gRnjNVMYPsJoSMROYK6svFeW9Q iwcTDUIZUW4bzzdc1Xnval4LD233g9M4avElxnS+gyTMWSCTiGFnqKUEnDWU+is+Hw58 eMIeTl2wBVUW9+4AGEXxdFMwfto9Zl/bKK2fRiUpIMA1ikrEyuw+4g6vAUxrII+MH7ik cLCQSkiswI3trQ7F3m1J/6zP1rjA9pFCYiZL92MQaiApEV/k0PazsMgC51zAbGO1FKuR i6O9RTSixk01EPGrO7BlbMHiMCbQU4vlUAVC2p+J13mdXrFIMp/AdOFXfxv9gM+jx0Xz /85g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=message-id:from:to:subject:content-transfer-encoding:mime-version :references:in-reply-to:user-agent:date:arc-authentication-results; bh=rUkcifHF1I5G4cQCtDVSzdTdodd/YXA7sHVaDTy2Q8Y=; b=lM49S9we7vL8Imq6Oq0o+N4+Yml7xIfA8EH9Az6tB30Ap+7vUNd2prjQzJfYMWseK+ PJw92Xm9NCtRwZj0oLvU+7F4AkRKo0KpoOSRH469BQ1sE4kOiiKkqot2liEOl9hge2Sl 45Lg+Gk4REJ6GI30dO0GvIQr7NL/QiC92LNruTtP0DuZX4xUmXUpZeO3eWixJlcXg+Nx kwq24DbiZIBdIxZyjzpnXIRTi9zPHevVj9GW8BsFSfyjhDnLkjl+A1/OF/8gQuRspNgY hhrx2RQ5AtCarNHNbkuevAfIOnN74x8z9LwEcAHiLbymGnDBRHCupmsnMY9THTeEdtik ubNQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of sukender@free.fr designates 212.27.42.3 as permitted sender) smtp.mailfrom=sukender@free.fr Received: from smtp3-g21.free.fr (smtp3-g21.free.fr. [212.27.42.3]) by gmr-mx.google.com with ESMTPS id h23si185281ede.4.2017.11.16.08.21.08 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 16 Nov 2017 08:21:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of sukender@free.fr designates 212.27.42.3 as permitted sender) client-ip=212.27.42.3; Received: from [10.41.239.171] (unknown [37.172.177.57]) (Authenticated sender: sukender@free.fr) by smtp3-g21.free.fr (Postfix) with ESMTPSA id B71DB13F892; Thu, 16 Nov 2017 17:20:58 +0100 (CET) Date: Thu, 16 Nov 2017 17:20:53 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: <78156dc5-1fb3-4e9d-992c-a8f30facc4fd@googlegroups.com> <963393d6-a9f1-4232-be13-b4ee76eb69e1@googlegroups.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----NDN29NHDCPX81RQMY1HUXDFCQ5ZY1T" Content-Transfer-Encoding: 7bit Subject: Re: [lojban] Re: CLL and modern Lojban To: lojban@googlegroups.com,guskant ,lojban From: Sukender Message-ID: X-Original-Sender: sukender@free.fr X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of sukender@free.fr designates 212.27.42.3 as permitted sender) smtp.mailfrom=sukender@free.fr Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: lojban@googlegroups.com X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.4 (--) X-Spam_score: -2.4 X-Spam_score_int: -23 X-Spam_bar: -- ------NDN29NHDCPX81RQMY1HUXDFCQ5ZY1T Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'll answer more in detail soon, but in the meantime, can you tell us more = about "Group 3 consist[ing] of some incompatible groups"? Which subgroups, = actually? ki'e la .sykyndyr. Le 16 novembre 2017 17:06:11 CET, guskant a =C3=A9c= rit : > > >Le mercredi 15 novembre 2017 09:38:00 UTC, Benoit Neil a =C3=A9crit : >> >> And, you told that there are 3 groups. If I rephrase: >> >> 1. CLL 1.1 "purists", who want to "throw away" what has been >learned >> 2. The ones who want to "bug fix" CLL regarding to logic. >> 3. The ones who want to "upgrade" CLL. >> >> It is not clear to me if 2nd and 3rd ideas would break up *many* >things=20 >> (thus forcing to "re-learn" when having learned CLL 1.1), or only >details.=20 >> Somebody has clues on this? >> (And yes, each potential change would have to be evaluated on that=20 >> question.) >> >> Aside from that, I feel that the 2nd and 3rd group should agree to >perform=20 >> first common steps altogether. Isn't it the case? If not, why? >> >> la .sykyndyr. >> > > >=20 >I regard that And Rosta is one of the great contributors for refining >the=20 >theory behind Lojban, but he seems to take a distance from the current=20 >active Lojban speakers. He once kindly gave me his thoughts on my=20 >documetary film {lo vliraitru}, but I guess he doesn't know much about >the=20 >current 2nd or 3rd group. > >I also take a distance from active speakers, but I still observe the=20 >community from time to time. Here are what I understand according to >the=20 >observation. > >- Group 2 and Group 3 consist mostly of the same people. That is to >say,=20 >There are few people in Group 2 who are not in Group 3. Group 3 >consists of=20 >some incompatible groups. The members of Group 3 have agreement on "bug > >fix"-ing the CLL regarding to logic. > >- Group 1 should permit "adding grammatical mechanisms" without >changing=20 >the existing mechanism, because it is clearly permitted in Section 4.2 >of=20 >the CLL. However, it seems to me that some people in Group 1 don't >accept=20 >any new grammatical mechanisms. > >Now, Group 3, including Group 2, should "perform first common steps=20 >altogether", but it isn't the case: there is poor progress in "bug=20 >fix"-ing. I observed again the BPFK meeting, and recognized some points > >that might be useful for considering the solution of problems. > > >Summary. >1. Discussions for removing grammatical defects were more active than >those=20 >for removing semantic defects. See Observations 1 and 3 below. >2. Discussions for removing semantic defects are always stopped at some > >stage, no voting, and buried in many other topics of simple Q&As. See=20 >Observations 3 and 4 below. >3. The Lojban Coders' Group has no intention of cooperating with BPFK. >See=20 >Observation 2.1 below. > > >Suggestion. >Summary 1 and 2 suggest that we need an easy-to-use working system, >where=20 >the members clearly see what to be put for voting, what to be >discussed,=20 >what are important, what are unimportant. >Summary 3 suggests a problem more difficult to solve. Some members of >BPFK=20 >are members of the Lojban Coders' Group. They don't distinguish >missions of=20 >BPFK from voluntary services. I have no idea to change their mind. > > >Observations. >1. Some defects in grammar were discussed and voting occurred. > >Examples: >1.1. YACC to PEG >(discussion from 2015-11-17 to 2016-05-19) >In order to remove some defects in grammar, it is necessary to make the > >grammar written in PEG official, because YACC is less expressive than >PEG=20 >[Note 1].=20 >There was a stubborn resistant, but voting occurred. As a result, The=20 >proposal that the grammar written in PEG should be official got the=20 >majority. >https://groups.google.com/d/msg/bpfk-list/A8qyiW7Uod8/GN7F-pZXCgAJ >However, I didn't see any official declaration about the result. > >1.2. ([{lo KU} CU] [{ba brode} VAU]) >(discussion from 2015-11-16 to 2016-03-15) >Most members agreed that it should be official and voted for it. The >result=20 >was declared: >https://groups.google.com/d/msg/bpfk-list/A8qyiW7Uod8/jRLrsM9WDQAJ >https://mw.lojban.org/papri/BPFK:_lo_nu_broda_ba_brode > > >2. Not all modifications to the grammar were put for voting. > >Examples: >2.1. {broda be ba brode} >(discussion from 2016-02-23 to 2016-04-06) >It becomes ungrammatical under the agreement 1.2 above. >The proposal of making it grammatical again by modifying some parts of >the=20 >grammar was not accepted by some people including me, and the >discussion=20 >stopped without voting. >https://groups.google.com/d/topic/bpfk-list/kXZ5aBNPI_A/discussion > >However, the Lojban Coders' Group made it grammatical on Camxes on=20 >2016-03-27, and it is still valid: >https://github.com/lojban/ilmentufa/commit/e9f578607dcc1a1dddfa8f9132175f5= bc22c7b4d#diff-373e39fcf7056e72d5e0e4cdab4068f3 >Even after the voting for the above proposal 1.1 of making PEG grammar=20 >official, that Camxes is modified little by little without consulting >BPFK,=20 >though called "camxes: standard" on the parser page: >https://github.com/lojban/ilmentufa/commits/master/camxes.peg >http://lojban.github.io/ilmentufa/camxes.html > >That fact shows that any decisions by BPFK have no influence to the=20 >contents created by the Lojban Coders' Group, still the Lojban Coders'=20 >Group is deceiving users into believing that their "camxes: standard"=20 >reflected the official grammar. > >2.2. {ni'o .i} >(discussion from 2016-03-11 to 2016-03-30) >The idea of making it grammatical was discussed and mostly agreed but >no=20 >voting occurred. Maybe the topic was not very important for the members >of=20 >BPFK. >https://groups.google.com/d/topic/bpfk-list/nk049jbIBlQ/discussion > > >3. Defects in semantics are discussed but voting has never occurred. >Examples: >3.1. Removing defects in meaning of {na} >(discussion from 2016-06-23 to 2016-07-02) >Most people agreed, some did not, and the discussion was stopped for no > >reason. >https://groups.google.com/d/topic/bpfk-list/svR3FuAr0pA/discussion > >3.2. meaning of {bridi} >(discussions: from 2014-10-07 to 2014-10-09; from 2016-01-19 to >2016-05-30) >It was once agreed by 2014-10-09 that {bridi} is relationship of >meanings,=20 >not of symbols.=20 >https://groups.google.com/d/topic/bpfk-list/yChr3cGT1_Q/discussion >It was discussed again in 2016, mostly agreed again, but no voting >occurred. >https://groups.google.com/d/topic/bpfk-list/V1TNzpGE3XI/discussion > >3.3. meaning of causation sumtcita >(discussion from 2015-05-13 to 2015-06-17) >https://groups.google.com/d/topic/bpfk-list/FdM1mYXfn3s/discussion >It was discussed, the document was given, but no voting occurred. > > >4. There are many simple Q&A that don't require voting. >Examples: >https://groups.google.com/d/topic/bpfk-list/CLJ21LkJ9jw/discussion >https://groups.google.com/d/topic/bpfk-list/rHreOMRRpKs/discussion >https://groups.google.com/d/topic/bpfk-list/wz5_QcTTC8U/discussion >and many more. > > >[Note 1] >Such an example is explained at 35m15s of the documentary video: >https://vimeo.com/190637628#t=3D2115s > > >mu'o mi'e la guskant > >--=20 >You received this message because you are subscribed to a topic in the >Google Groups "lojban" group. >To unsubscribe from this topic, visit >https://groups.google.com/d/topic/lojban/e94H-wdh5gc/unsubscribe. >To unsubscribe from this group and all its topics, send an email to >lojban+unsubscribe@googlegroups.com. >To post to this group, send email to lojban@googlegroups.com. >Visit this group at https://groups.google.com/group/lojban. >For more options, visit https://groups.google.com/d/optout. --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at https://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. ------NDN29NHDCPX81RQMY1HUXDFCQ5ZY1T Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'll answer more in detail soon, but in the me= antime, can you tell us more about "Group 3 consist[ing] of some incom= patible groups"? Which subgroups, actually?
ki'e

la .sykyndyr.


Le 16 novembre 2017 17:06:11 CET, guskan= t <gusni.kantu@gmail.com> a =C3=A9crit :


Le mercredi 15 novembre 2017 09:38:00 UTC, Ben= oit Neil a écrit :
=
And, you told that there are 3 groups. If I rephrase:=
  1. CLL 1.1 "purists", who want to "throw awa= y" what has been learned
  2. The ones who want to "bug = fix" CLL regarding to logic.
  3. The ones who want to "= upgrade" CLL.
It is not clear to me if 2nd and 3rd= ideas would break up many things (thus forcing to "re-l= earn" when having learned CLL 1.1), or only details. Somebody has clue= s on this?
(And yes, each potential change would have to be evalu= ated on that question.)

Aside from that, I feel = that the 2nd and 3rd group should agree to perform first common steps altog= ether. Isn't it the case? If not, why?

la .sykyn= dyr.


 <= /div>
I regard that And Rosta is one of the great contributors for refi= ning the theory behind Lojban, but he seems to take a distance from the cur= rent active Lojban speakers. He once kindly gave me his thoughts on my docu= metary film {lo vliraitru}, but I guess he doesn't know much about the curr= ent 2nd or 3rd group.

I also take a distance fro= m active speakers, but I still observe the community from time to time. Her= e are what I understand according to the observation.

- Group 2 and Group 3 consist mostly of the same people. That is to s= ay, There are few people in Group 2 who are not in Group 3. Group 3 consist= s of some incompatible groups. The members of Group 3 have agreement on &qu= ot;bug fix"-ing the CLL regarding to logic.

- Group 1 should permit "adding grammatical mechanisms" without = changing the existing mechanism, because it is clearly permitted in Section= 4.2 of the CLL. However, it seems to me that some people in Group 1 don't = accept any new grammatical mechanisms.

Now, Grou= p 3, including Group 2, should "perform first common steps altogether&= quot;, but it isn't the case: there is poor progress in "bug fix"= -ing. I observed again the BPFK meeting, and recognized some points that mi= ght be useful for considering the solution of problems.


Summary.
1. Discussions for removing gra= mmatical defects were more active than those for removing semantic defects.= See Observations 1 and 3 below.
2. Discussions for removing sema= ntic defects are always stopped at some stage, no voting, and buried in man= y other topics of simple Q&As. See Observations 3 and 4 below.
3. The Lojban Coders' Group has no intention of cooperating with BPFK. Se= e Observation 2.1 below.


Sugges= tion.
Summary 1 and 2 suggest that we need an easy-to-use working= system, where the members clearly see what to be put for voting, what to b= e discussed, what are important, what are unimportant.
Summary 3 = suggests a problem more difficult to solve. Some members of BPFK are member= s of the Lojban Coders' Group. They don't distinguish missions of BPFK from= voluntary services. I have no idea to change their mind.

<= /div>

Observations.
1. Some defects in gramm= ar were discussed and voting occurred.

Examples:=
1.1. YACC to PEG
(discussion from 2015-11-17 to 2016-0= 5-19)
In order to remove some defects in grammar, it is necessary= to make the grammar written in PEG official, because YACC is less expressi= ve than PEG [Note 1]. 
There was a stubborn resistant, but v= oting occurred. As a result, The proposal that the grammar written in PEG s= hould be official got the majority.
https://groups.google.com/d/m= sg/bpfk-list/A8qyiW7Uod8/GN7F-pZXCgAJ
However, I didn't see any o= fficial declaration about the result.

1.2. ([{lo= <nu (¹broda VAU¹) KEI> KU} CU] [{ba brode} VAU])
(discussion from 2015-11-16 to 2016-03-15)
Most members agreed t= hat it should be official and voted for it. The result was declared:
<= div>https://groups.google.com/d/msg/bpfk-list/A8qyiW7Uod8/jRLrsM9WDQAJ
https://mw.lojban.org/papri/BPFK:_lo_nu_broda_ba_brode


2. Not all modifications to the grammar were = put for voting.

Examples:
2.1. {broda = be ba brode}
(discussion from 2016-02-23 to 2016-04-06)
It becomes ungrammatical under the agreement 1.2 above.
The prop= osal of making it grammatical again by modifying some parts of the grammar = was not accepted by some people including me, and the discussion stopped wi= thout voting.
https://groups.google.com/d/topic/bpfk-list/kXZ5aBN= PI_A/discussion

However, the Lojban Coders' Grou= p made it grammatical on Camxes on 2016-03-27, and it is still valid:
=
https://github.com/lojban/ilmentufa/commit/e9f578607dcc1a1dddfa8f91321= 75f5bc22c7b4d#diff-373e39fcf7056e72d5e0e4cdab4068f3
Even after th= e voting for the above proposal 1.1 of making PEG grammar official, that Ca= mxes is modified little by little without consulting BPFK, though called &q= uot;camxes: standard" on the parser page:
https://github.com= /lojban/ilmentufa/commits/master/camxes.peg
http://lojban.github.= io/ilmentufa/camxes.html

That fact shows that an= y decisions by BPFK have no influence to the contents created by the Lojban= Coders' Group, still the Lojban Coders' Group is deceiving users into beli= eving that their "camxes: standard" reflected the official gramma= r.

2.2. {ni'o .i}
(discussion from 201= 6-03-11 to 2016-03-30)
The idea of making it grammatical was disc= ussed and mostly agreed but no voting occurred. Maybe the topic was not ver= y important for the members of BPFK.
https://groups.google.com/d/= topic/bpfk-list/nk049jbIBlQ/discussion


3. Defects in semantics are discussed but voting has never occurred= .
Examples:
3.1. Removing defects in meaning of {na}
(discussion from 2016-06-23 to 2016-07-02)
Most people ag= reed, some did not, and the discussion was stopped for no reason.
https://groups.google.com/d/topic/bpfk-list/svR3FuAr0pA/discussion

3.2. meaning of {bridi}
(discussions: from 20= 14-10-07 to 2014-10-09; from 2016-01-19 to 2016-05-30)
It was onc= e agreed by 2014-10-09 that {bridi} is relationship of meanings, not of sym= bols. 
https://groups.google.com/d/topic/bpfk-list/yChr3cGT1= _Q/discussion
It was discussed again in 2016, mostly agreed again= , but no voting occurred.
https://groups.google.com/d/topic/bpfk-= list/V1TNzpGE3XI/discussion

3.3. meaning of caus= ation sumtcita
(discussion from 2015-05-13 to 2015-06-17)
https://groups.google.com/d/topic/bpfk-list/FdM1mYXfn3s/discussion
=
It was discussed, the document was given, but no voting occurred.


4. There are many simple Q&A th= at don't require voting.
Examples:
https://groups.googl= e.com/d/topic/bpfk-list/CLJ21LkJ9jw/discussion
https://groups.goo= gle.com/d/topic/bpfk-list/rHreOMRRpKs/discussion
https://groups.g= oogle.com/d/topic/bpfk-list/wz5_QcTTC8U/discussion
and many more.=


[Note 1]
Such an exa= mple is explained at 35m15s of the documentary video:
https://vim= eo.com/190637628#t=3D2115s


mu'o= mi'e la guskant

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