From - Tue Feb 20 14:56:52 1996 Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id EAA15314 for ; Wed, 14 Feb 1996 04:50:47 -0500 Message-Id: <199602140950.EAA15314@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id CD4E0623 ; Wed, 14 Feb 1996 4:17:22 -0500 Date: Wed, 14 Feb 1996 04:15:13 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: Re: TECH: fuzzy logic X-To: ucleaar@UCL.AC.UK X-cc: lojban@cuvmb.cc.columbia.edu To: John Cowan X-Mozilla-Status: 0011 Content-Length: 2060 >I too wish to declare that, like everyone else, I am not making >grammar change proposals either. I think an immediate baseline should >be declared, so your tension levels drop a bit. Instead, I am >engaged in discussions about how the grammar should change if it >ever were to change. Does this mean I do not have to read and respond to your postings? because I am not interested in anything beyond the baseline until after the baseline. %^) >Lojbab to djer: >> BUT na'e is not solely used for scales on brivla, so we have to be >> careful about adding to the set of scalar variables. > >Could you explain more? Look at references to NAhE in the machine grammar. Allow your construct in any of them. Do they make sense in all. Likewise NA (which among other things MAY mean that your fuzzy XVV construct can end up in a logical connective in place of, say "na.a"). NAhe is in rules # 136,152,374 (Mex) 482,483,945, and 972. NA is in rules 20,54,81,131,445,911,926,950,,991, Playingt with these guys is NOT fun. >> Otherwise we will get something or another that will use And's >> proposal and have to be interepreted isiomatically just as you fear >> as the case for NAhE xi quantifier. > >& explain this too...? Well, see the above reference to na.a, and imagine replacing na by your construct. Come up with a conventional interpetation. Promise me that no other conventional interpreetation will EVER conflict with it. Repeat for all occurances of NA and NAhE to cover all of your proposal. This is similar to the question of putting lambda in KOhA. Does it have meaning in ALL places where KOhA can appear. If not, you need conventions, and those conventions need to be immutable as possible (e.g. the convention on ke'a, which is anothe KOhA that has no meaning in many contexts) or we will have arguments that do not get settled after the baseline when it is our opinion that LLG should not settle arguments by fiat unless we can refer to something in the defined prescription. lojbab