[Bug 7059] Forking XPath

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 #33 from Jonathan Robie <jonathan.robie@redhat.com>  2009-09-11 13:22:04 ---
(In reply to comment #32)
> "NameTest" appears to be nothing but a token in the XPath grammar, so I don't
> understand what it means to talk about it matching elements or anything like
> that. 
> Also, it's hard to determine, out of context, if your proposed text is stating
> a fact that can be derived from other requirements, or if it is intended to be
> introducing new requirements.
> 
> How about this text:
> 
> A node test consisting of a QName with no prefix (i.e. that matches the
> UnprefixedName production) must be treated as if it instead had the namespace
> URI equal to HTML namespace when the node is an element whose document is an
> HTML document. [XPATH10] [XMLNS]

This is a *lot* closer. I would change "must be treated as if it instead had"
to "has", and also make it clear that it is the path expression, and not the
document, that determines whether the node test is testing an element name.

Here's my best shot at this:

"A node test consisting of a QName with no prefix (i.e. that matches the
UnprefixedName production) 
has the namespace URI http://www.w3.org/1999/xhtml (the HTML namespace)
when the node test occurs in a position where an element or type name is
expected
and the path expression is applied to a document that is an HTML document.
[XPATH10] [XMLNS]"

I would also change the note, since this is no longer such a willful violation:

Note: This is equivalent to adding the default element namespace feature of
XPath 2.0 to XPath 1.0, and using the HTML namespace as the default element
namespace for HTML documents. It is motivated by the desire to have
implementations be compatible with legacy HTML content while still supporting
the changes that this specification introduces to HTML regarding the namespace
used for HTML elements, and by the desire to use XPath 1.0 rather than XPath
2.0.


-- 
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, 11 September 2009 13:22:16 UTC