- From: <bugzilla@jessica.w3.org>
- Date: Sun, 19 Feb 2012 21:46:52 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12455 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Michael Kay <mike@saxonica.com> 2012-02-19 21:46:48 UTC --- This was discussed during the Feb 2012 F2F. It was felt we should try to restore the semantic connection between patterns and XPath expressions in order to avoid surprises in this area (or at any rate, to make it possible to defend the surprises). I would suggest doing this as follows. (a) the construct ~typename is replaced by (.[. instance of typename]). This substitution is incorporated into the definition of "equivalent expression" (b) the ability to use union/intersect/except with non-node patterns is dropped (c) the current rule An item N matches a PathPattern if N is a node and the result of evaluating the expression root(.)//(EE) with a singleton focus based on N is a sequence that includes the node N, where EE is the equivalent expression to the PathPattern, is replaced by An item N matches a PathPattern if either of the following applies: (1) N is a node and the result of evaluating the expression root(.)//(EE) with a singleton focus based on N is a sequence that includes the node N, where EE is the equivalent expression to the PathPattern, (2) N is not a node and the result of evaluating the expression exists(EE) with a singleton focus based on N is true. -- Configure bugmail: https://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 Sunday, 19 February 2012 21:46:54 UTC