"has an Attr with
nodeName = "xmlns"
prefix = null (unspecified)
localName = "xmlns"
namespaceURI = "http://www.w3.org/2000/xmlns/"
nodeValue="xxx""
Is the part that I think is bad. You've got no prefix, but its in a
namespace, which is inconsistent and requires special casing. Why couldn't
they have just said that if you see an unprefixed attribute named xmlns,
that's all the signal that you need.
Anyway, I'm pretty sure that the parser is not doing this now. Its correctly
passing out the xmlns as the unprefixed name, but probably not putting it
into the magic namespace since I thought that was inconsistent to do. And I
mean that parser here, not the DOM. The DOM might be doing the right thing,
but the parser spits out output that is completely consistent to what you'd
expect in this case according to standard XML rules, i.e. an attribute named
xmlns with no prefix and no URL.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"I'm not sure how I feel about ambivalence"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
