Re: Re:Namespace resolution in L3 Core and XPath (was Full infoset support for DOM 3 Core) from Curt Arnold on 2001-09-07 (www-dom@w3.org from July to September 2001)

From: Curt Arnold <carnold@houston.rr.com>
Date: Fri, 7 Sep 2001 13:37:17 -0500
To: <www-dom@w3.org>
Message-ID: <000f01c137cc$1f60acd0$a800a8c0@CurtMicron>

Actually, in that context you wouldn't even need to go to Unicode
characters, you could use the return value "#default" when the URI matches
the default namespace and leave "" for no match.

The design of element.getAttribute() seems to have anticipated the problem
by explicitly returning "" instead of null when the attribute name is not
found.

For already recommended methods, there needs to be a resolution that
accomodates the deployed implementations where Java implementations return
null and ECMAScript implementations return "".  However, for L3 methods,
avoiding the use of null DOMString parameters and attributes in the
definition would preempt having to deal with it in the bindings.

Received on Friday, 7 September 2001 14:37:57 UTC