Re: uri, urn and info

> http
> easiest and most functional, but the minter has to spend a lot of 
> money and time getting people to adopt the resulting URIs. 
> unfortunate car/document argument that always crops up.
> 
> tag
> even easier to mint, no function other than uniqueness. The minter 
> has an even bigger hurdle to get the URI  space adopted, due to 
> people's unfamiliarity with tag
> 
> urn
> rigorous requirements but the real hurdle with urn is to get IETF 
> consensus. IETF lapses most URN proposals and doesn't promote or use 
> the ones it does.
> 
> info
> minter has to obtain NISO sign-off. hardly any requirements. no 
> function except an unspecified namespace registry.

A combination of http techology and info human-resources might be
best.  How about using niso.org like I suggested [1], and writing an
informational RFC about it?  That puts everyone else writing RFCs on
notice about the existence of good URIs for these things, and doesn't
require real marketing dollars.   Or just announce it here, and word
will probably start to get around....

Of course, I'm not quite sure what NISO's role would be.
niso.org/isbn vs isbn.org...?  I dunno.  I guess they could be
maintaining a nice directory of this stuff.  And they could run a
redirector to help delegate authority and simultaneously help avoid
the car/document issue.

   -- sandro

[1] http://lists.w3.org/Archives/Public/uri/2003Oct/0042.html

Received on Tuesday, 7 October 2003 18:14:59 UTC