- From: Ray Whitmer <rayw@netscape.com>
- Date: Thu, 06 Sep 2001 14:43:47 +0000
- To: "Arnold Curt" <Curt.Arnold@hyprotech.com>
- CC: "'www-dom@w3.org'" <www-dom@w3.org>
Arnold, Curt wrote: >XPathNamespaceResolver might be more appropriate in the Core however with the expectation that it would be supported by most objects that implement Node. If added to the core, then it should map both >ways, that is getNSPrefixForURI() and getURIForNSPrefix(). > This functionality is already expressed in Level 3 core in the Node interface. By keeping the XPath version of the interface abstract, we permit applications to construct maps for cases where the namespace context is not based upon a Node in the hierarchy (although we do not have a create method for that type of object). There are other differences, such as one you stumbled on: XPath never requires the default namespace (and requiring XPathNamespaceResolver to supply it might make the implementer erroneously apply it to prefixless names within the expression). Ray Whitmer rayw@netscape.com
Received on Thursday, 6 September 2001 17:38:20 UTC