Received: from mail-qc0-f185.google.com ([209.85.216.185]:36193) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XTwj6-00042t-Jr for lojban-list-archive@lojban.org; Tue, 16 Sep 2014 10:39:41 -0700 Received: by mail-qc0-f185.google.com with SMTP id l6sf30936qcy.22 for ; Tue, 16 Sep 2014 10:39:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-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=Nxp/ZLsvgibfoYrQjF1gzZpuMGUqzMkVhMNqMicqUc0=; b=fa2VhSh3yzmz/b6HiJ1YjzJLXeJ/n/+AbUvXsDtHCmGIxINcFyeNdUYMqIWvLDTieO kpCsp/p05GNUCkfDtvU5eHFGQXb1jfjJk+24uUXqUnp8YMAQyrKjyRmDztkiKnCtw+A6 y+X9rnijre6bjGQcMV5PF2eUdH7bpQfJfYS6elSC6WqCHZgPtJ7GQVibTkHgwHc6qE9i Vt/jG/YOkpvY0IXlbp3Uavj/gFqYnZvzRgLdKa7Yl2R96/zszkHbc2opmkRpAizx/Crn vvMSV6l5fWiVLqBREgrP0+3BHR4/u8xorozvBpX2bwz9VtupnEblp7WpGv/ETtqgj/Vj 7Mng== X-Received: by 10.50.114.8 with SMTP id jc8mr370598igb.17.1410889174390; Tue, 16 Sep 2014 10:39:34 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.60.97 with SMTP id g1ls172625igr.0.gmail; Tue, 16 Sep 2014 10:39:34 -0700 (PDT) X-Received: by 10.66.187.193 with SMTP id fu1mr2115175pac.45.1410889174131; Tue, 16 Sep 2014 10:39:34 -0700 (PDT) Received: from eastrmfepo101.cox.net (eastrmfepo101.cox.net. [68.230.241.213]) by gmr-mx.google.com with ESMTP id k7si258242qcm.2.2014.09.16.10.39.33 for ; Tue, 16 Sep 2014 10:39:33 -0700 (PDT) Received-SPF: none (google.com: lojbab@lojban.org does not designate permitted sender hosts) client-ip=68.230.241.213; Received: from eastrmimpo306 ([68.230.241.238]) by eastrmfepo101.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20140916173927.HNAE5255.eastrmfepo101.cox.net@eastrmimpo306> for ; Tue, 16 Sep 2014 13:39:27 -0400 Received: from [192.168.0.102] ([72.209.248.61]) by eastrmimpo306 with cox id rt4T1o01P1LDWBL01t4TKY; Tue, 16 Sep 2014 13:04:28 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.54186D9C.008B,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=Huyo7TvS c=1 sm=1 a=z9jnGXjs1dxvEuWvIXKNSw==:17 a=BGi6d-X4uLYA:10 a=RpE3YcRdmCsA:10 a=xmHE3fpoGJwA:10 a=IkcTkHD0fZMA:10 a=8YJikuA2AAAA:8 a=o2srl7GOw8qCzZGVFf0A:9 a=QEXdDO2ut3YA:10 a=z9jnGXjs1dxvEuWvIXKNSw==:117 X-CM-Score: 0.00 Message-ID: <54186D9D.1030600@lojban.org> Date: Tue, 16 Sep 2014 13:04:29 -0400 From: "Bob LeChevalier, President and Founder - LLG" Organization: The Logical Language Group, Inc. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Logos Initiative References: <541714B1.9080300@gmail.com> In-Reply-To: X-Original-Sender: lojbab@lojban.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: lojbab@lojban.org does not designate permitted sender hosts) smtp.mail=lojbab@lojban.org Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Type: text/plain; charset=UTF-8; format=flowed X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - On 9/15/2014 2:22 PM, TR NS wrote: > I don't see how a fork can be avoided. I think it's become very clear > that Lojban, pretty much as it is presently documented, is how the > language is going to stay. The persons in charge give some service to > change by "usage" and potential consideration of proposals after full > documentation of the current language is complete. But how many decades > are we to wait for that to happen? I think we are closer than you imagine. Robin is working on the next edition of CLL this week, and I am reasonably sure it will be out when we need it next year. The consideration of proposals could take a long time, or relatively little. If the proposers document their proposed changes in the form of change pages to CLL, it makes it fairly easy to consider those changes and incorporate them relatively quickly (as well as to understand how minor or major a given proposal is). > And can it actually ever be complete? > And doesn't the whole notion of "completion" work against the notion of > change? If the language is essentially complete and well-documented, I hope and expect that the pressure for change will fall off. Right now we have 15-odd years of accumulated but undocumented change proposals. After they are decided, then one would hope that new proposals would come at a slower rate. If they don't, then any project that you come up with is just as doomed as Lojban to the same fate. > Besides, starting a new project also allows us to take a step back and > reconsider things that would simply not be possible otherwise. You'd be surprised as to the sort of things that were "reconsidered" in prior iterations. Look at guaspi and Voksigid for prior efforts to reconsider Lojban. lojbab -- 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 email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout.