I was just being consistent when I designed it, and treated it like any
other global attribute. I didn't ever see anything that said I should do
otherwise, but I could have easily missed it. Another difference may come
from the fact that I did the very literal thing of making:
xmlns=""
be an attribute and note a prefix. And in
xmlns:foo=""
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.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: Chris Hill [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 2:13 PM
To: [EMAIL PROTECTED]
Subject: Namespace of xmlns attribute
Xerces 1.4 puts the xmlns attribute in a default namespace declaration
(such as <a xmlns="blah"/>) in the global namespace, like all other
attributes without a prefix. I see that a couple other specifications
place it in the "http://www.w3.org/2000/xmlns/" namespace, as well as the
document at http://www.w3.org/2000/xmlns/. Does anybody know the what the
history and current thinking is in this area and what is planned for Xerces
in the future?
http://www.w3.org/TR/DOM-Level-2-Core/core.html#Namespaces-Considerations
(see Note)
http://www.w3.org/TR/xml-infoset/#infoitem.namespace
(see 6. [namespace attributes])
http://www.w3.org/2000/xmlns/
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
