[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Overloaded URIs must GO!

• From: Paul Prescod <paul@p...>
• To: XML List <xml-dev@i...>
• Date: Mon, 28 Jun 1999 12:15:56 -0500

David Megginson wrote:
> 
> 1. URNs don't really exist, or at least, last I checked, there was no
>    authoritative specification of the different URN schemes (without
>    which URNs are worthless).  URNs have been under development for
>    most of the 1990s with few tangible results, and I'm growing
>    slightly skeptical.

When we had the namespaces discussion, I said that using URIs was a bad
idea because URNs don't exist yet so everyone could only use URLs. I
pointed out then that using URLs is bad and probably
standards-nonconformant. 

I was told, however, that URNs DO exist. Anything that conforms to the URN
syntax is a URN. I wasn't especially thrilled with this syntax-centric
definition but there was no other definition of a URN and in the rather
loosely formalized world of the Web what more could I expect? So I wasn't
happy with the loose definition of URNs but I accepted that they exist.

I see today, however, that we have a new document that clears up my
concerns.

It says:

"Not all syntactically correct URN namespaces (per the URN
syntax definition)  are valid URN namespaces.  A URN namespace
must have a recognized definition in order to be valid."

http://www.ietf.org/internet-drafts/draft-ietf-urn-nid-req-08.txt

It also gives a mechanism for defining new URNs. Furthermore, last month a
URN namespace was actually proposed as an Internet Draft:

http://www.ietf.org/internet-drafts/draft-ietf-urn-ietf-09.txt

So now I think it can truly be said that URNs *exist* and can be used. Of
course in the general case resolution could be a big problem but in the
specific case of XML namespaces it is not.

It is now both legal and appropriate for us to propose the hname:
namespace which is defined to mirror the HTTP namespace (in terms of
ownership and uniqueness) but be a URN instead of a URL and thus
explicitly unretrievable. In the meantime, it seems that we can use an
experimental namespace: "x-hname" and take our chances that nobody
somewhere else on the Web will use the same name incompatibly.

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
 http://itrc.uwaterloo.ca/~papresco

Alabama's constitution is 100 years old, 300 pages long and has more than
600 amendments. Highlights include "Amendment 393: Amendment of Amendment
No.  351", "Validation of Laws Regulating Court Costs in Randolph County",
"Miscegenation laws", "Bingo Games in Russell County", "Suppression
of dueling".  - http://www.legislature.state.al.us/ALISHome.html

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • RE: Overloaded URIs must GO!
    • From: "Didier PH Martin" <martind@n...>
  • Re: Overloaded URIs must GO!
    • From: David Megginson <david@m...>

• References:
  • RE: Overloaded URIs (was Re: XLink: behavior must go!)
    • From: Andrew Layman <andrewl@m...>
  • Overloaded URIs must GO!
    • From: Paul Prescod <paul@p...>
  • re: Overloaded URIs must GO!
    • From: David Megginson <david@m...>

• Prev by Date: URN Madness (was re: Overloaded URIs must GO!)
• Next by Date: Re: Web Resource Identity
• Previous by thread: RE: URN Madness (was re: Overloaded URIs must GO!)
• Next by thread: Re: Overloaded URIs must GO!
• Index(es):
  • Date
  • Thread