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 17:30:03 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MKFFT-00064f-QB@wiggum.w3.org>

Jonathan Robie <jonathan.robie@redhat.com> changed:

           What    |Removed                     |Added
                 CC|                            |jonathan.robie@redhat.com

--- Comment #3 from Jonathan Robie <jonathan.robie@redhat.com>  2009-06-26 17:30:03 ---
(In reply to comment #2)

> Also note that this doesn't affect XPath matching in XML documents in any way.
> As far as I can tell, applying XPath to HTML documents has always been outside
> the immediate interest and charter of the XSL WG.

Both XQuery and XSLT are frequently applied to HTML documents. The document is
first parsed to create an XDM instance (often using tools like Tagsoup to deal
with cruft), then processed appropriately. 

Screen scraping and data integration are one important class of applications
that do this.

XPath is used in both XQuery and XSLT. It's going to be extremely confusing if
XPath expressions are interpreted differently when executed inside a browser
environment, especially since the documents that define the XPath standard do
not support this interpretation.

I suggest that you define a profile of XPath 2.0 that corresponds to the
functionality of XPath 1.0 plus default namespaces, and also define the mapping
of your XML documents to XDM (you have to do this regardless, because XPath is
defined in terms of the XDM, not the DOM). 

You may also want to allow implementations to optionally support all of XPath

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 17:30:13 UTC

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