> its a prefix that maps to the xmlns URL. In the former, if you go by XML
> rules, and I don't see why you shouldn't, xmlns="" is an
> attribute just like
> any other attribute and its in the global namespace and I think
> it should be
> treated the same as any other such, to avoid having to have special case
> code in applications that use the parser. In the later, xmlns is clearly a
> prefix and should map to a URL.
>
> Personally, I can't see any good enough argument to deviate and treat the
> first scenario specially, and force everyone else to as well.
Namespace declarations are not attributes. They do not appear in the infoset
as attribute information items. They do not have to be declared in XML
Schema to make a document that uses them valid. While I wasn't aware that
they were associated with a namespace, they do require special handling.
Xerces should follow the DOM spec in this regard and associate all xmlns
attributes with the proper namespace. The tricky part which I didn't see in
the DOM spec was how would prefix and localname work. I would assume that
the default namespace decl would have a null or zero length local name.
David Cleary
Progress Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
