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

[Bug 7059] New: Forking XPath

From: <bugzilla@wiggum.w3.org>
Date: Fri, 26 Jun 2009 14:45:44 +0000
To: public-html@w3.org
Message-ID: <bug-7059-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7059

           Summary: Forking XPath
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML 5: The Markup Language
        AssignedTo: mike@w3.org
        ReportedBy: jonathan.robie@redhat.com
         QAContact: public-html-bugzilla@w3.org
                CC: public-html@w3.org


http://www.whatwg.org/specs/web-apps/current-work/#interactions-with-xpath-and-xslt
intentionally forks XPath 1.0. 

I strongly suggest that you work with XQuery and XSL Working Groups, which
produce the XPath specification, to come up with a better solution. We started
discussion on a Bugzilla bug against our spec:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6777

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. But instead, your
draft forks the XPath standard by creating a new version of XPath 1.0 where the
name tests have special-purpose semantics.

XPath 2.0 was published 23 January 2007 (before your Working Group was even
chartered), solves your problem, and is widely implemented. Now, in June, 2009,
you propose to create an incompatible version of XPath 1.0 and say that web
browsers must implement this instead.

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


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 26 June 2009 14:45:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:04 UTC