XML Namespaces
Chaos Theory tells us that the mere flapping of a butterfly's wings in
a South American rain forest can cause hurricanes on the other side of
the world. Believing this makes it hard not to be awestruck. After all,
a butterfly is a small and beautiful creature. How could something so
harmless looking be the root cause of significant and detrimental
events on a global scale?
The XML world has its own chaos theory-enabled butterfly known as
the "Namespaces in XML" W3C Recommendation from 1999. Weighing in at a
mere 15 pages, the namespaces Rec is certainly small, though opinions
differ on its beauty. Aesthetics aside, its ability to wreak havoc on a
global scale in the XML world is beyond doubt.
Ostensibly, the namespace Rec is just a simple way of allowing element
type names to be globally unique. Unfortunately, in so doing, it
introduces rules for defaulting namespaces that significantly
complicates any software it touches. XPath, SAX, DOM, XQuery, XSchema,
and XSLT -- all of these are caught up in the flapping of the namespace
Rec's wings, and it is not a pretty sight! I won't go into the details
here, but type any of the previous words into a search engine along
with "namespace" and "problem" and you will see what I mean.
Recently, the W3C introduced a draft of version 1.1 of the namespace
Rec. The changes suggested are minor but have caused the namespace
debate to erupt again on xml-dev (http://lists.xml.org/archives/xml-
dev/200204/threads.html). Joe English, who is one of the most
knowledgeable people about markup technology on the planet, was moved
to post a plea for sanity that is well worth reading
(http://lists.xml.org/archives/xml-dev/200204/msg00170.html).
When someone as knowledgeable as Joe English starts classifying
compliant namespace usage patterns into categories
called "neurotic", "borderline", and "psychotic", it behooves us to
take a step back and look at what is going on here! When the XML world
revisits its fundamentals (around 2008 I suspect as these things always
take a decade), namespaces will need to have their wings well and truly
clipped in order to redress some of the chaos and damage caused from a
decade of inconsiderate flapping.
My advice: Don't use namespaces at all if you can avoid it. If you
can't, then only put them on the root element. Oh, and don't lend money
to anyone who tries to tell you namespaces are simple.
» posted by ITworld staff
ITworld
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.













My advice: Don't use
My advice: Don't use namespaces at all if you can avoid it. If youcan't, then only put them on the root element. Oh, and don't lend moneyto anyone who tries to tell you namespaces are simple.Blackberry 8300 cover silver
Nokia 6300 metal cover
Motorola Razr V3 keypad
replica bags
I'am crazy about replica handbags . I think these replica bags are very attractive .