From pycyn@aol.com Fri Sep 13 09:07:36 2002
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_1_1_3); 13 Sep 2002 16:07:36 -0000
Received: (qmail 63303 invoked from network); 13 Sep 2002 16:07:36 -0000
Received: from unknown (66.218.66.217)
  by m6.grp.scd.yahoo.com with QMQP; 13 Sep 2002 16:07:36 -0000
Received: from unknown (HELO imo-r05.mx.aol.com) (152.163.225.101)
  by mta2.grp.scd.yahoo.com with SMTP; 13 Sep 2002 16:07:35 -0000
Received: from Pycyn@aol.com
  by imo-r05.mx.aol.com (mail_out_v34.10.) id r.e6.2e1bbd97 (4584)
  for <lojban@yahoogroups.com>; Fri, 13 Sep 2002 12:07:15 -0400 (EDT)
Message-ID: <e6.2e1bbd97.2ab36733@aol.com>
Date: Fri, 13 Sep 2002 12:07:15 EDT
Subject: RE: I like chocolate (types, tokens and {lo'e})
To: lojban@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_e6.2e1bbd97.2ab36733_boundary"
X-Mailer: AOL 7.0 for Windows US sub 10509
From: pycyn@aol.com
X-Yahoo-Group-Post: member; u=2455001
X-Yahoo-Profile: kaliputra

--part1_e6.2e1bbd97.2ab36733_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

One of the features of flying across six time zones is that you end up with a 
distorted sleep cycle. So, I have been waking up at weird times (and falling 
asleep at weird times, too, but that is not so objectionable -- or so useful) 
and when I do ideas turn up in my head that I can't get their in the normal 
course of things. Which just happened in re xorxes' {lo'e}:
xorxes insists that his {lo'e} is not that of Lojban, but he also wants it to 
have the semantic properties of that locution (and {le'e} and "the average 
..." if we still had one of those). These, while in the shape of sumti, are, 
in fact, shorthand for fairly complex constructions -- and different 
constructions in different contexts. What binds them together are the 
properties that are actually (standard {lo'e}) or thought to be ({le'e}) 
typical of members of a class. In various contexts, a {le/o'e} may bring up 
some of those properties or a thing that has them or ... (I haven't looked 
with all the possibilities here, so I can't give a complete list), or simply 
describe what one of those properties is. xorxes want his {lo'e} to do this 
as well -- with, I suppose, the properties universal or defining to a set. 
Unfortunately for me (and you all -- if there is still anyone reading this 
besides xorxes), he chose to describe this usage with a word that just 
doesn't fit: "type." So, I have been riffing on types and tokens -- which 
are not (in sort of standard usage) idiomatic, but normal referential words 
referring to abnormal things. And xorxes has, in that context, been trying to 
sort out some of the semantic expansions of his expression in various 
contexts. His "use" is, I think, mainly about things which have the 
properties embedded in his lo'e ... and, I suspect, his "talk about" will 
turn out to be expanding on what those properties are. That is, 
{mi nelci lo'e sfofa} means I like things that have certain properties had by 
sofas and
and {ta simsa lo'e sfofa} means that that has some properties of sofas (or 
some closely related properties, perhaps). I expect examples of talking 
about to be like {lo'e sfofa cu nilce} or {lo'e sfofa cu clani}, pulling out 
the properties involved.
If this is correct, then I don't really see much difference between xorxes 
{lo'e} and Lojban's -- except perhaps a stricter rule for what counts as a 
relevant property, which may or may not be significant.

--part1_e6.2e1bbd97.2ab36733_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT style="BACKGROUND-COLOR: #ffffff" SIZE=2>One of the features of flying across six time zones is that you end up with a distorted sleep cycle.&nbsp; So, I have been waking up at weird times (and falling asleep at weird times, too, but that is not so objectionable -- or so useful) and when I do ideas turn up in my head that I can't get their in the normal course of things.&nbsp; Which just happened in re xorxes' {lo'e}:<BR>
xorxes insists that his {lo'e} is not that of Lojban, but he also wants it to have the semantic properties of that locution (and {le'e} and "the average ..." if we still had one of those).&nbsp; These, while in the shape of sumti, are, in fact, shorthand for fairly complex constructions&nbsp; -- and different constructions in different contexts.&nbsp; What binds them together are the properties that are actually (standard {lo'e}) or thought to be ({le'e}) typical of members of a class.&nbsp; In various contexts, a {le/o'e} may bring up some of those properties or a thing that has them or ... (I haven't looked with all the possibilities here, so I can't give a complete list), or simply describe what one of those properties is.&nbsp; xorxes want his {lo'e} to do this as well -- with, I suppose, the properties universal or defining to a set.&nbsp; Unfortunately for me (and you all -- if there is still anyone reading this besides xorxes), he chose to describe this usage with a word that just doesn't fit: "type."&nbsp; So, I have been riffing on types and tokens -- which are not (in sort of standard usage) idiomatic, but normal referential words referring to abnormal things. And xorxes has, in that context, been trying to sort out some of the semantic expansions of his expression in various contexts.&nbsp; His "use" is, I think, mainly about things which have the properties embedded in his lo'e ... and, I suspect, his "talk about" will turn out to be expanding on what&nbsp; those properties are.&nbsp; That is, <BR>
{mi nelci lo'e sfofa} means I like things that have certain properties had by sofas and<BR>
and {ta simsa lo'e sfofa} means that that has some properties of sofas (or some closely related properties, perhaps).&nbsp; I expect examples of talking about to be like {lo'e sfofa cu nilce}&nbsp; or {lo'e sfofa cu clani}, pulling out the properties involved.<BR>
If this is correct, then I don't really see much difference between xorxes {lo'e} and Lojban's -- except perhaps a stricter rule for what counts as a relevant property, which may or may not be significant.</FONT></HTML>

--part1_e6.2e1bbd97.2ab36733_boundary--

