This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I find the precedence of the simple map operator a little surprising in general use. For instance, this is valid syntax: foo ! bar But this is not valid syntax: foo ! /bar I think we should change the grammar to make this expression valid, as follows: ValueExpr ::= ValidateExpr | SimpleMapExpr | ExtensionExpr SimpleMapExpr ::= PathExpr ("!" PathExpr)* PathExpr ::= ("/" RelativePathExpr?) | ("//" RelativePathExpr) | RelativePathExpr RelativePathExpr ::= StepExpr (("/" | "//") StepExpr)*
Actually this change would also affect the associativity of "!" with respect to "/". The current grammar has "/" and "!" at the same precedence, and left associative. Here's an example where that makes a difference: let $doc := document { <a><b>1</b><a><b>2</b></a></a>,<a><b>3</b></a> } return $doc // a ! descendant::b / text() This is implicitly parameterized like this: (($doc // a) ! descendant::b) / text() -> ("1", "2", "3") However my proposed change parameterizes it like this: ($doc // a) ! (descendant::b / text()) -> ("1", "2", "2", "3") I believe that by using the "!" operator, the user has explicitly chosen not to have document ordering and duplicate removal applied to the result sequence. The latter precedence and associativity more closely matches this expectation. Other more minor differences with my proposed change include the one in the bug description above, as well as allowing the following currently illegal syntax: / ! document-uri(.)
I think I'm persuaded. It seems that (apart from a syntactic interaction with edge cases involving lone-slash), the only impact is on expressions that use "/" to the right of "!". And it's hard to construct realistic examples where (under the current rules) such a use of "!" is usefully different from "/", given that the lhs of "/" has to be nodes, and the "/" does any document-ordering that the "!" might otherwise have prevented. So the current precedence rules don't allow you to do anything very useful, wheras the proposed precedence rules allow expressions such as $page//@href ! doc(.)//title where the fact that "!" doesn't do document-ordering is potentially useful.
I'm persuaded also. This example from Comment 1 was particularly convincing: $doc // a ! descendant::b / text()
The Working Group agrees. We will make this change.