XSLT 2.0 and XPath 2.0 Programmer's Reference, 4th Edition (416 page)
Read XSLT 2.0 and XPath 2.0 Programmer's Reference, 4th Edition Online
Authors: Michael Kay
is followed by something that could be a legitimate step in a path expression, then that's the interpretation that's chosen. Adding whitespace after the
/
doesn't make any difference. What you need to do if you want the other interpretation is to put the/in parentheses, thus:(/) union /*.
This ambiguity was actually present, and unremarked upon, in XPath 1.0, though, it arose less frequently because there weren't many operators in XPath 1.0 that could sensibly be applied to
/
as an operand. The|operator does not cause any ambiguities because it cannot be confused with an element name.
I've classified the root expression as an abbreviated axis step because for most purposes it can be regarded as equivalent to the expressionancestor-or-self::document-node(). However, there's a significant difference: if the context item doesn't have an ancestor that is a document node, you get a runtime error rather than an empty sequence as the result.
Technically, therefore, the expression/is defined in the language specification as being equivalent to:
