From lojban-out@lojban.org Thu Mar 13 15:45:16 2003
Return-Path: <lojban-out@lojban.org>
X-Sender: lojban-out@lojban.org
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_2_6_1); 13 Mar 2003 23:45:16 -0000
Received: (qmail 25144 invoked from network); 13 Mar 2003 23:45:16 -0000
Received: from unknown (66.218.66.217)
  by m1.grp.scd.yahoo.com with QMQP; 13 Mar 2003 23:45:16 -0000
Received: from unknown (HELO digitalkingdom.org) (204.152.186.175)
  by mta2.grp.scd.yahoo.com with SMTP; 13 Mar 2003 23:45:15 -0000
Received: from lojban-out by digitalkingdom.org with local (Exim 4.12)
  id 18tcNv-0005QH-00
  for lojban@yahoogroups.com; Thu, 13 Mar 2003 15:45:15 -0800
Received: from digitalkingdom.org ([204.152.186.175] helo=chain)
  by digitalkingdom.org with esmtp (Exim 4.12)
  id 18tcNn-0005Pr-00; Thu, 13 Mar 2003 15:45:07 -0800
Received: with ECARTIS (v1.0.0; list lojban-list); Thu, 13 Mar 2003 15:45:06 -0800 (PST)
Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root)
  by digitalkingdom.org with esmtp (Exim 4.12)
  id 18tcNf-0005Pf-00
  for lojban-list@lojban.org; Thu, 13 Mar 2003 15:45:00 -0800
Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1])
  by cs6668125-184.austin.rr.com (8.12.3/8.12.3) with ESMTP id h2DNqXCG057499
  for <lojban-list@lojban.org>; Thu, 13 Mar 2003 17:52:33 -0600 (CST)
  (envelope-from fracture@cs6668125-184.austin.rr.com)
Received: (from fracture@localhost)
  by cs6668125-184.austin.rr.com (8.12.3/8.12.3/Submit) id h2DNqWbr057498
  for lojban-list@lojban.org; Thu, 13 Mar 2003 17:52:32 -0600 (CST)
Date: Thu, 13 Mar 2003 17:52:32 -0600
To: lojban-list@lojban.org
Subject: [lojban] Re: spofu skami
Message-ID: <20030313235232.GA57351@allusion.net>
References: <20030313183823.GH25165@digitalkingdom.org> <5.2.0.9.0.20030313174255.034e0c60@pop.east.cox.net> <20030313232720.GO25165@digitalkingdom.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP"
Content-Disposition: inline
In-Reply-To: <20030313232720.GO25165@digitalkingdom.org>
User-Agent: Mutt/1.5.1i
X-archive-position: 4513
X-ecartis-version: Ecartis v1.0.0
Sender: lojban-list-bounce@lojban.org
Errors-to: lojban-list-bounce@lojban.org
X-original-sender: fracture@allusion.net
Precedence: bulk
X-list: lojban-list
X-eGroups-From: Jordan DeLong <fracture@allusion.net>
From: Jordan DeLong <lojban-out@lojban.org>
Reply-To: fracture@allusion.net
X-Yahoo-Group-Post: member; u=116389790
X-Yahoo-Profile: lojban_out

--jRHKVT23PllUwdXP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 13, 2003 at 03:27:20PM -0800, Robin Lee Powell wrote:
> On Thu, Mar 13, 2003 at 05:52:12PM -0500, Robert LeChevalier wrote:
> > Bearing in mind that the word "nerve" long predates our current
> > understanding of the processing in a neural system, nirna would NOT be
> > limited to such a scientific definition. Lojban gismu are generally
> > defined as broadly as possible (for Jordan - the "metaphor" cues are
> > an attempt to force breadth of meaning - not polysemy).
> >=20
> > I think that a nerve/nirna is merely a relaying component of an
> > information system which transmits signals from one or more sources to
> > one or more destinations (possibly with conditions based on the
> > signals received). It is not even clear that the directionality
> > implied by "source" and "destination" is necessary.
> >=20
> > Under this broader definition, a transformer, a tunnel diode, and a
> > mechanical relay are also nirna.
>=20
> I'm fine with all that, but if that's the case, the definition needs to
> be fixed, because it's got the phrase "body-part" in it, for crying out
> loud.

.ie

> And again, cans with string, talking, telephone wires, etc, etc, all
> fit.

Yeah. What's with this overlap between nirna and cukta?

--=20
Jordan DeLong - fracture@allusion.net
lu zo'o loi censa bakni cu terzba le zaltapla poi xagrai li'u
sei la mark. tuen. cusku

--jRHKVT23PllUwdXP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE+cRnADrrilS51AZ8RAtGvAJwMjq6RcmWD1kmX1qiNEbJGmajR8gCfRz3X
ZIx7PqhQDBEAbSCpV1sojYA=
=H2mL
-----END PGP SIGNATURE-----

--jRHKVT23PllUwdXP--

