From pycyn@aol.com Tue Sep 10 12:35:43 2002 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_1_0_1); 10 Sep 2002 19:35:43 -0000 Received: (qmail 52798 invoked from network); 10 Sep 2002 19:35:42 -0000 Received: from unknown (66.218.66.218) by m3.grp.scd.yahoo.com with QMQP; 10 Sep 2002 19:35:42 -0000 Received: from unknown (HELO imo-r03.mx.aol.com) (152.163.225.99) by mta3.grp.scd.yahoo.com with SMTP; 10 Sep 2002 19:35:42 -0000 Received: from Pycyn@aol.com by imo-r03.mx.aol.com (mail_out_v34.10.) id r.16.251b4397 (25711) for ; Tue, 10 Sep 2002 15:35:37 -0400 (EDT) Message-ID: <16.251b4397.2aafa389@aol.com> Date: Tue, 10 Sep 2002 15:35:37 EDT Subject: Re: [lojban] Re: Archive location. To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_16.251b4397.2aafa389_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_16.251b4397.2aafa389_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 9/10/2002 1:36:54 PM Central Daylight Time, gordon.dyke@bluewin.ch writes: << > the www is a seltcana, while an individual page is a tcana. >> This is true, maybe with a modfier to cut down on the number of possibiities for what kind of network is involved. But this is generic, and we are (apparently) looking for a predicate that fits exactly the Web or the internet or only the two. << Both are velsku >> True again, but still not getting down to just the ones we are intrested in -- we still have radio and tv stations, telephones and newspapers for starters. << for the jondatnymu'e people, it is {co linsi}, not {co jorne}, it contains very little {datna be da bei de} and it is (the www, not the internet) {munje be fi ji'inoda} >> Well, I don't like the word much either, but that it is {linsi} rather than {jorne} is not obvious (nor is it that it is {jorne} neither). Since these all seem to be literalist lujvo (feh!), the "links" here are immaterial and so don't make up a chain -- and a chain is too incomplex to do justice to the the interconnectedness. As for {jorne}, there is no common locus -- things are connected but not united. Etc, etc, etc. As for the {datni} part, that depends on what you take as data and, taken generally, just about anything turns out to be data, even "raw data." And, of course, there are all sorts of rules that define the Web, starting with HTML (which is quite enough to start with). --part1_16.251b4397.2aafa389_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 9/10/2002 1:36:54 PM Central Daylight Time, gordon.dyke@bluewin.ch writes:

<<

the www is a seltcana, while an individual page is a tcana.

>>
This is true, maybe with a modfier to cut down on the number of possibiities for what kind of network is involved. But this is generic, and we are (apparently) looking for a predicate that fits exactly the Web or the internet or only the two.

<<
Both are velsku
>>
True again, but still not getting down to just the ones we are intrested in -- we still have radio and tv stations, telephones and newspapers for starters.

<<
for the jondatnymu'e people, it is {co linsi}, not {co jorne}, it contains
very little {datna be da bei de} and it is (the www, not the internet)
{munje be fi ji'inoda}
>>
Well, I don't like the word much either, but that it is {linsi} rather than {jorne} is not obvious (nor is it that it is {jorne} neither). Since these all seem to be literalist lujvo (feh!), the "links" here are immaterial and so don't make up a chain -- and a chain is too incomplex to do justice to the the interconnectedness. As for {jorne}, there is no common locus -- things are connected but not united. Etc, etc, etc. As for the {datni} part, that depends on what you take as data and, taken generally, just about anything turns out to be data, even "raw data." And, of course, there are all sorts of rules that define the Web, starting with HTML (which is quite enough to start with).

--part1_16.251b4397.2aafa389_boundary--