From lojbab@lojban.org Sat Dec 07 13:13:41 2002
Return-Path: <lojbab@lojban.org>
X-Sender: lojbab@lojban.org
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_2_3_0); 7 Dec 2002 21:13:41 -0000
Received: (qmail 78698 invoked from network); 7 Dec 2002 21:13:41 -0000
Received: from unknown (66.218.66.218)
  by m7.grp.scd.yahoo.com with QMQP; 7 Dec 2002 21:13:41 -0000
Received: from unknown (HELO lakemtao01.cox.net) (68.1.17.244)
  by mta3.grp.scd.yahoo.com with SMTP; 7 Dec 2002 21:13:41 -0000
Received: from lojban.lojban.org ([68.100.206.153]) by lakemtao01.cox.net
  (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP
  id <20021207211339.VVGW2199.lakemtao01.cox.net@lojban.lojban.org>
  for <lojban@yahoogroups.com>; Sat, 7 Dec 2002 16:13:39 -0500
Message-Id: <5.2.0.9.0.20021207155837.03926140@pop.east.cox.net>
X-Sender: rlechevalier@pop.east.cox.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sat, 07 Dec 2002 16:06:57 -0500
To: lojban@yahoogroups.com
Subject: Re: [lojban] More stuff
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
From: Robert LeChevalier <lojbab@lojban.org>
X-Yahoo-Group-Post: member; u=1120595
X-Yahoo-Profile: lojbab

Earlier today I posted in response to Nick a hierarchy of lesser to greater 
changes to the baseline. Nora said that it came out unreadable to her 
because of the line wrapping, so I'm reposting that portion with more care 
taken.

...
For baseline changes, I think there is a hierarchy of stability, and for 
any part of the language definition, we want to think multiple times before 
elevating the to a higher level of change consideration, because opening 
the door to one change invites other changes at the same level and sooner 
or later you won't recognize the language.

Lowest to highest

1 typo correction

2 clarification that does not contradict a viable denotation of the 
existing definition

3 clarification that basically admits I/we chose poor wording so that the 
denotation of the existing definition is misleading (rewording a gismu 
definition)

4 splitting of a word into two words to resolve polysemy

5 addition of a new word not justified by polysemy on a currently 
unassigned cmavo (or adding a single line YACC grammar rule that changes no 
others, e.g. CAhA+NAI, adding a place to place structure)

6 deleting an assigned cmavo because it is useless (deleting a place from 
place structure, or a gismu)

7 addition of a new word reusing such a deassigned cmavo (seems much higher 
than using an unassigned cmavo - I would support using xVV before 
reassigning tei even if tei is deleted (changing a place structure other 
than simple addition or deletion)



Note that while deleting a cmavo, deleting a place from a place structure, 
or gismu are all listed as level 6, the hierarchy for each area has a 
different level of assumed stability, so deleting an apparently useless 
cmavo should be a little easier than deleting a useless gismu or place 
structure.

lojbab

-- 
lojbab lojbab@lojban.org
Bob LeChevalier, President, The Logical Language Group, Inc.
2904 Beau Lane, Fairfax VA 22031-1303 USA 703-385-0273
Artificial language Loglan/Lojban: http://www.lojban.org



