Altova Mailing List Archives

Re: [xml-dev] Interoperability [long]

From: David Brownell <david-b@-------.--->
To: "Champion, Mike" <Mike.Champion@--------------.--->, xml-dev@-----.---.---
Date: 11/15/2001 11:37:00 PM
> - The DOM WG naively believed a literal reading of the namespace spec and
> treats prefixes as mere syntax sugar and URIs as the "real thing".  This
> causes problems when interoperating with specs that treat prefixes as being
> significant.

Huh?  The DOM spec preserves both.  I don't follow.  Since it
preserves both, what's the problem?  Implementation bugs?

> - Elements created with a namespace URI may not have a prefix, and you may
> have to invent one when you need one, e.g., when serializing.

Yeah, but  I remember constantly getting "writing XML from DOM is
out of scope" whenever I raised similar issues.  That's why it's rather
important not to put such things prematurely out of scope ... :)

> - since DOM nodes don't intrinsically know their namespace (unlike XPath
> nodes, as I understand it), the namespace of a node when moved around in the
> tree may change in undesireable ways unless you take lots of care to make
> sure that it is in the same namespace scope in the source and target
> locations, or that you *intended* to make that HTML <p> element a <p>
> element in the "foo" namespace ....

Now I'm totally confused.  Since when is that true?  DOM nodes must
be created with namesepaces, which stick to them like glue.  Moving a
node around doesn't change the namespace URI, or add one.

There was a discussion when DOM first got namespace support, and
I seem to recall one vendor insisting on that "early binding" approach
rather than matching the "late binding" approach that'd match XML text
better ...

- Dave


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.