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

[Bug 7059] Forking XPath

From: <bugzilla@wiggum.w3.org>
Date: Wed, 09 Sep 2009 12:18:36 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MlM8C-0004ZU-8x@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7059


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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |




--- Comment #26 from Jonathan Robie <jonathan.robie@redhat.com>  2009-09-09 12:18:35 ---
First off, I believe that our Working Groups have agreed to meet to discuss
this issue. I suggest that we not resolve the issue before that discussion.

The suggestion in comment #18 is that you use the XPath 1.0 semantics as
defined in that specification, and be clear about the default namespace:

> In XPath 1.0, if a NameTest has no prefix, 
> then the namespace URI is null. In the context 
> of document.evaluate(), HTML5 specifies a different 
> default element namespace: if a NameTest has no prefix 
> and the principle node type of the NameTest is element, 
> the namespace URI is http://www.w3.org/1999/xhtml; if a
> NameTest has no prefix and the principle node type of the 
> NameTest is not element, the namespace URI is null.


What I see in the current draft gives match conditions in addition to those
defined in XPath 1.0, plus match conditions defined in XPath 1.0 that do not
apply, and says that it is willfully violating the XPath specification.

> In addition to the cases where a name expression would match a
> node per XPath 1.0, a name expression must evaluate to matching a
> node when all the following conditions are also met:
> 
>     * The name expression has no namespace.
>     * The name expression has local name that is a match for local.
>     * The expression is being tested against an element node.
>     * The element has local name local.
>     * The element is in the HTML namespace.
>     * The element's document is an HTML document.
> 
> Irrespective of the requirements defined in XPath 1.0, a name
> expression must not evaluate to matching a node when the
> following conditions are all met:
> 
>     * The name expression has no namespace.
>     * The expression is being tested against an element node.
>     * The element is in no namespace.
>     * The element's document is an HTML document.
> 
> These requirements are a willful violation of the XPath 1.0
> specification, motivated by desire to have implementations be
> compatible with legacy content while still supporting the changes
> that this specification introduces to HTML regarding which
> namespace is used for HTML elements. [XPATH10]


-- 
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 Wednesday, 9 September 2009 12:18:46 UTC

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