Re: Keywords, direct navigation, ...

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> Mon, 10 December 2001 14:48 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GO400I04UG7N2@eListX.com> (original mail from brunner@nic-naa.net); Mon, 10 Dec 2001 09:48:08 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GO400I01UG7N0@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Mon, 10 Dec 2001 09:48:07 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GO400I01UG6MZ@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Mon, 10 Dec 2001 09:48:06 -0500 (EST)
Received: from nic-naa.net (216-220-241-232.midmaine.com [216.220.241.232]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GO400I2EUG60T@eListX.com> for ietf-irnss@lists.elistx.com; Mon, 10 Dec 2001 09:48:06 -0500 (EST)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.9.3) with ESMTP id fBAEkAl40938 for <ietf-irnss@lists.elistx.com>; Mon, 10 Dec 2001 09:46:10 -0500 (EST envelope-from brunner@nic-naa.net)
Date: Mon, 10 Dec 2001 09:46:10 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Subject: Re: Keywords, direct navigation, ...
To: ietf-irnss@lists.elistx.com
Message-id: <200112101446.fBAEkAl40938@nic-naa.net>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>

Good morning everyone,

Something that troubles me in the model John proposes is scope.  Another,
and unfortunately related thing that troubles me is, as Bill noted in his
"reading ...?" note, is that this is not greenfields, and that symbolic
conflict with layers-as-markitecture is already in full swing.

The introduction of ontologies (policies associted to a scope-capable
mechanisn, if one is in the on-line ad racket), or categories (ditto),
or (venturing into the IDN mechanism minefield) character encoding schemes,
or (in venturing into the IDN policy minefield) partitions of namespaces,
is widely rejected "in the DNS", but (by a smaller, but significant set in
this BOF) accepted "above the DNS".

The same arguement holds that alternatives to the DNS that offer "direct
navigation" must, of necessity, have the property of ontological meaning.
The problem is, hosttables pre-existed the DNS, and were an alternative
to the DNS, as are (not were) resource-to-resource isomorphisms for several
alternatives to the DNS. ARP is an example.

I'm not convinced that an alternative mechanism (and here I _personally_
include dns-directory hybrid and directory models) of necessity has to have
a different scope than the dns (a set of names, a set of addrs, a mapping),
and has to import ontologies, artificial intelligence, facets, and lots of
other neat bits.

I don't want to repeat the IDN WG fiasco, all talk and no implementation.
For my $.02, this BOF must converge in the standard 2-tries to a WG that is
implementation-centered, not layerist. We keep ISO for that role.

Eric