Altova Mailing List Archives

Re: [xml-dev] Lesson Learned: Use namespaces for both markup anddata

From: Michael Ludwig <milu71@---.-->
To: xml-dev@-----.---.---
Date: 8/11/2009 10:55:00 PM
Glidden, Douglass A schrieb am 11.08.2009 um 17:44:19 (-0400):
> I have to say that, all in all, I don't understand why working with
> namespaces is supposedly so painful, so I've stayed out of this
> discussion; however, as an "application developer" who works with
> quite a bit of XML data, I have to disagree with you here.

Working with namespaces presents three or more burdens of varying

(1) It may be painful for novice users, until they figure it out.

(2) It frequently imposes a certain tedium on the reader and sometimes
traps even experienced users in silly errors because the established
convention of choosing unnecessarily complicated URIs or URLs to
identify namespaces is so horrible:

(3) It is a problem in the data model and in implementations because
of the context dependency that the mere possibilty of namespace
declarations in mid-markup introduces:

Well, the novice will have to do some grokking as per burden (1).

As an XML user past the novice stage, I find the current system quite
okay, and prefixes even good as they tell me what namespace an element
belongs to. We should just start using friendlier namespace identifiers.
Then, burden (2) would be alleviated.

But it seems there is more to prefixes than meets the eye, they cause a
lot of complexity in the data model and limit your ability to transplant
nodes from one location to another. (3) Things could be made to work in
a simpler fashion. A hypothetical better system might benefit both users
and implementors.

Michael Ludwig


XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address:
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive:
List Guidelines:


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.