Received: from uga.cc.uga.edu by nfs2.digex.net with SMTP id AA09015
  (5.67b8/IDA-1.5 for <lojbab@ACCESS.DIGEX.NET>); Sun, 27 Nov 1994 07:32:00 -0500
Message-Id: <199411271232.AA09015@nfs2.digex.net>
Received: from UGA.CC.UGA.EDU by uga.cc.uga.edu (IBM VM SMTP V2R2)
   with BSMTP id 1455; Sun, 27 Nov 94 07:33:00 EST
Received: from UGA.CC.UGA.EDU (NJE origin LISTSERV@UGA) by UGA.CC.UGA.EDU (LMail V1.2a/1.8a) with BSMTP id 6961; Sun, 27 Nov 1994 07:33:00 -0500
Date:         Sun, 27 Nov 1994 12:30:50 +0000
Reply-To: ucleaar <ucleaar@ucl.ac.uk>
Sender: Lojban list <LOJBAN@CUVMB.BITNET>
From: ucleaar <ucleaar@ucl.ac.uk>
Subject:      more on lehe & ka
X-To:         lojban@cuvmb.cc.columbia.edu
To: Bob LeChevalier <lojbab@access.digex.net>
Status: RO
X-From-Space-Date: Sun Nov 27 07:32:01 1994
X-From-Space-Address: LOJBAN%CUVMB.BITNET@uga.cc.uga.edu

There is a controversial but widely accepted distinction between
"defining" and "nondefining" features of a category. Taking the
familiar example of "bachelor",
   "She's a regular bachelor"
means she possesses the nondefining but not necessarily the defining
properties of bachelorhood, e.g. has no significant other, endeavours
to be sexually promiscuous, never does any housework, etc etc.
   "Technically he's a bachelor, but ..."
means he has the defining properties of bachelorhood (male & unmarried)
but not necessarily the nondefining ones.

I have been wondering whether the intention behind "ka" is that it
picks out defining properties, and behind "lehe" is that it picks
out nondefining properties. "lohe", perhaps, is supposed to pick
out both.

---
And