Slashdot Mirror
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!!"
From the article:
"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."
In other words, the info URI's will not be useful for anything other than providing context and identification. There is no resolution mechanism in place, nor do they intend to have any standard resolution mechanism, which makes the practical use of these URI's almost nonexistant (as current designed.)
Why do I h8 apple?
Anyone else notice info-uri.niso.org doesn't exist?
How exactly will browsers implement this new protocol?
I'm confused about the concept of a "public namespace". If these new URIs are intended to point to information, where will that information be stored and how will it be retrieved?
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
I haven't looked in on the politics of this one but there are two kinds of individual submissions
1 - Any idiot can mail something properly formatted to internet-drafts@ietf.org and get it published as an internet draft... don't believe me look here Individual Submissions - you will find this draft somewhere on this page
2 - A working group is looking for a new working group item - so they ask the author to post an individual submission so they can consider his work before making a decision - These actually become RFCs
Want a clue on WG items in the ietf - they come in the form draft-ietf-WGName-topic-rev.txt - The key is to not be fooled by people that post draft-ietf-lastname-topic-rev.txt
I have mod points and I am not afraid to use them
Arbitrary key names are now URIs?
Uh no.
There will be ONE new top-level scheme, "info". It will have (presumably a small-ish number of) second-level "namespaces". Each namespace will be a well-defined system run by some organization. So you could imagine an ISBN namespace, so a URI might look like "info:isbn:0465026567".
The "info" scheme, and therefore the list of namespaces, will be controlled by an existing standards body called NISO. It's their job to impose the discipline on these URIs. End-users won't get to create their own - only NISO-approved bodies with a well-run namespace can add to this system. Sounds like a good idea to me. I can rely on the fact that any legitimate "info" URI will be well-organized and sensible, I hope.