From lojbab@lojban.org Wed Apr 12 12:51:26 2000 Return-Path: Received: (qmail 18441 invoked from network); 12 Apr 2000 19:51:25 -0000 Received: from unknown (10.1.10.26) by m4.onelist.org with QMQP; 12 Apr 2000 19:51:25 -0000 Received: from unknown (HELO stmpy.cais.net) (205.252.14.63) by mta1 with SMTP; 12 Apr 2000 19:51:25 -0000 Received: from bob (ppp23.net-A.cais.net [205.252.61.23]) by stmpy.cais.net (8.8.8/8.8.8) with ESMTP id PAA18631 for ; Wed, 12 Apr 2000 15:50:11 -0400 (EDT) Message-Id: <4.2.2.20000412155015.00a96b70@127.0.0.1> X-Sender: vir1036/pop.cais.com@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 12 Apr 2000 15:55:08 -0400 To: lojban@onelist.com Subject: Re: [lojban] RECORD:name abstractions In-Reply-To: <31.39d59f0.2625fb65@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-eGroups-From: "Bob LeChevalier (lojbab)" From: "Bob LeChevalier (lojbab)" X-Yahoo-Message-Num: 2365 At 12:16 PM 04/12/2000 -0400, pycyn@aol.com wrote: >The property of being -- or being significantly related to n is mela n-- and >so reference to that involve leka mela n or so. Can you rephrase this (and include it in a new form of the RECORD)? I can't parse the English, hitting a wall either at "reference" or "involve", and the hyphen positions then cause me to double take back as "is". I believe that "mela n" should not include "being significantly related to n" given a prior ruling on what "me" means. This was our one major change to agree with a TLI correction from their logician. 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 (newly updated!)