IETF Draft Sets up Public Namespaces
figlet writes "A new IETF draft is out (URI Scheme for Information Assets with Identifiers in Public
Namespaces). It is a very cool idea and basically introduces namespaces through a new URI scheme. These would be used to refer to resources within their own context. NISO will be the registry for public namespaces. Example (from Herbert Van de Sompel): 'For example, assuming that the namespace of Dewey Decimal Classifications (ddc:) and the namespace of Library of Congress Control Numbers (lccn:) would be registered by their respective authorities, then: the Dewey Decimal Classification 22/eng//004.678 (for the term "Internet") could be expressed as the "info" URI:<info:ddc/22/eng//004.678> and the Library of Congress Control Number 2002022641 could be expressed as the
"info" URI <info:lccn/2002022641>.' NISO is going to act as the 'info' registry. Very neat. This basically sets up a parallel web of info spaces, where http/DNS space is just one of many, and anyone can register their namespace 'domain'. Way cool!!"
Just wait until someone like Verisign gets a hold of this. Utter chaos!
To get a namespace registered? ICANN? Verisign? This part was interesting: The "info" URI scheme explicitly decouples identification from resolution. Applications SHOULD NOT assume that an "info" URI can be dereferenced to a representation of the resource identified by the URI, though some business processes MAY make "info" URIs resolvable either directly or conditionally. The purposes of the "info" URI scheme are the identification of information assets and the standardization of rules for declaring and comparing identity of information assets without regard to any resolution of the URI or even whether the information asset identified by the URI is accessible on the Internet. This makes it look like this was intended more for internal use than for routing to specific information on the net. Anyone have a clear idea how and why this would be used on the internet?
This has some interesting possibilities, especially in the context of representing real-world elements in virtual space, and assist in more accurate search engine results. For example:
info:map/40.47N/73.58W for NYC's Central Park
could be encoded into any Web page about Central Park; and
info:palm/model/P80900US for the Palm Tungsten C
could be included in every online retailer's site where the T|C is sold.
This would seriously enhance the now piece-meal effort to pick the best search term to find specific items that may have common names. {Jonathan}
-------------------
Prof. Jonathan I. Ezor
Associate Professor of Law and Technology
Director, Institute for Business, Law and Technology (IBLT)
Touro Law Center
300 Nassau Road, Huntington, NY 11743
Tel: 631-421-2244 x412 Fax: 516-977-3001
e. jezor@tourolaw.edu
BizLawTech Blog: http://iblt.tourolaw.edu/blog
...and you can address (almost) everything! Look forward to a URI coming your way any time now..
--
What karma?
When I first read this article, it was the first thing that came to mind. (Maybe because I'm reading it now! :-)
-el_D