Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET> Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0rBjRq-00007EC; Sun, 27 Nov 94 15:15 EET Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 0385; Sun, 27 Nov 94 15:15:35 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 0381; Sun, 27 Nov 1994 14:42:02 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 4028; Sun, 27 Nov 1994 13:28:58 +0100 Date: Sun, 27 Nov 1994 12:30:50 +0000 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: more on lehe & ka X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 767 Lines: 18 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