• To: xml-dev@l...
• Subject: Re: Namespace URI question
• From: Richard Tobin <richard@c...>
• Date: Fri, 13 Dec 2002 14:19:32 GMT
• Cc:
• In-reply-to: <879123D97A01D711B0F500508B4464E4027764@l...>
• Organization: HCRC, University of Edinburgh

In article <879123D97A01D711B0F500508B4464E4027764@l...> you write:

>xmlns:foo="file:///foodom.xsd"    

file:///foodom.xsd is (for retrieval purposes) is the same as
file://localhost/foodom.xsd, and is an absolute URI referring to a
file on the machine where the URI is being interpreted (RFC 1738).

It's not a relative URI any more than http://127.0.0.1/~richard is.

Its interpretation depends on the machine you use it on, but not on
the current base URI.

>As a namespace identifier it's just a string (please, no arguments). But
>relative URIs were deprecated in [1].

Since it's not a relative URI, it's not deprecated by that decision
(now an erratum, http://www.w3.org/XML/xml-names-19990114-errata#NE04).

On the other hand, it's not a very good namespace name because it
isn't tied to the author in the way a URI containing a normal domain
name is.  Someone else might use it with just as much justification as
you.  As the Namespace spec says:

  The namespace name, to serve its intended purpose, should have the
  characteristics of uniqueness and persistence.

-- Richard

• References:
  • RE: Namespace URI question
    • From: Jeff Lowery <jlowery@s...>

• Prev by Date: Re: [OT] VOTE Was: The privilege of XML parsing - Datatypes, binary XML and XML pipelines (LONG)
• Next by Date: Re: xml-dev@l...
• Previous by thread: Re: Namespace URI question
• Next by thread: RE: Namespace URI question
• Index(es):
  • Date
  • Thread