Altova Mailing List Archives

Re: [xml-dev] Motivations for namespaces (sorry)

From: "Eric van der Vlist" <vdv@--------.--->
To: <xml-dev@-----.---.--->
Date: 7/11/2003 1:04:00 AM
Thomas B. Passin said:

> That is a different kind of thing, Eric, that's all.  I wasn't trying
> to identify document types.

I must have read this out of context, sorry but I thought that's where we
had ended up...
And I do think that we have a problem for defining document types even if
this not the point of the discussion ;-) ...
> But even in this example, say I wanted to
> be sure what dc:publisher really was supposed to be, so I can ut the
> right data in there.  "dc"  is pretty familiar - I would probably say
> to myself, "hey, I bet that is Dublin Core, let's see, the URL has
>, so I am going to pull out my Dublin Core info and check it
> out" (and the first thing I will do is to check the namespace, because
> I don't remember it exactly).

I agree that prefixes are easier to identify and memorized for human
readers, but that's also dangerous: that's what makes it difficult for us
to spot XSLT transformations using the old namespace for instance!
I see namespaces as a hack which is doing what it's been designed for (no
more, no less) and has unexpected side effects (such as the fact that we,
human readers, attach more importance to the prefix than to the URI and
also  such as QNames in values which abuse the xmlns declaration).
Freelance consulting and training.
Eric van der Vlist  
(W3C) XML Schema ISBN:0-596-00252-1


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.