W3C home > Mailing lists > Public > public-webapi@w3.org > September 2006

Re: ISSUE-85: Where to define XPathNSResolver?

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 20 Sep 2006 11:05:11 -0000
To: "Web APIs WG" <public-webapi@w3.org>
Message-ID: <op.tf5b7rzv64w2qv@id-c0020.emi.ac.ma>

On Tue, 19 Sep 2006 12:59:30 -0000, Web APIs Issue Tracker  
<dean+cgi@w3.org> wrote:
> To make XPathNSResolver reusable in Selectors API it has to support a  
> notion of a default namespace.
>
> Since DOM Level 3 XPath isn't really moving yet one idea would be to  
> define it in Selectors API and have DOM Level 3 XPath refer to it or  
> later copy it back.

The idea (and a CVS copy of Selectors API is working towards that) is to  
specify NSResolver (not XPathNSResolver) in Selectors API and have XPath  
resolve that. If we really need the XPath prefix for XPath we'll do  
something like a typedef or an empty interface...

Anyone with strong opinions on this?


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Wednesday, 20 September 2006 11:05:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:55 GMT