W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2009

[Bug 7059] Forking XPath

From: <bugzilla@wiggum.w3.org>
Date: Fri, 26 Jun 2009 15:18:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MKDC5-00035Z-GY@wiggum.w3.org>

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
                 CC|                            |hsivonen@iki.fi

--- Comment #1 from Henri Sivonen <hsivonen@iki.fi>  2009-06-26 15:18:25 ---
> I strongly suggest that you work with XQuery and XSL Working Groups, which
produce the XPath specification, to come up with a better solution.

Note that that's what I tried first.

> In this discussion, the reason given for forking XPath is that some people do
not want to implement XPath 2.0, which solves your problems.

Browsers have XPath 1.0 implementations and don't have XPath 2 implementations.
It isn't feasible to make the namespacing of elements in HTML DOMs gated on
browsers implementing XPath 2.0.

> XPath 2.0 was published 23 January 2007 (before your Working Group was even
chartered), solves your problem, and is widely implemented.

What's relevant is what the status quo of XPath support in browsers is.

> And this incompatible version is not even a subset of XPath 2.0.

I'd personally be OK with pursuing making prefixless expressions not to match
no-namespace nodes in HTML documents Gecko if the WebKit developers are OK with
making the same change to WebKit. Right now, the HTML5 spec, Gecko and WebKit
agree, so we have interop and a spec that matches implementation, which is a
pretty good situation to be in.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 26 June 2009 15:18:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:00:55 UTC