XPath 2.0 is a version of the XPath language defined by the World Wide Web Consortium, W3C. It became a recommendation on 23 January 2007. As a W3C Recommendation it was superseded by XPath 3.0 on 10 April 2014.
XPath is used primarily for selecting parts of an XML document. For this purpose the XML document is modelled as a tree of nodes. XPath allows nodes to be selected by means of a hierarchic navigation path through the document tree.
The language is significantly larger than its predecessor, XPath 1.0, and some of the basic concepts such as the data model and type system have changed. The two language versions are therefore described in separate articles.
XPath 2.0 is used as a sublanguage of XSLT 2.0, and it is also a subset of XQuery 1.0. All three languages share the same data model (the XDM), type system, and function library, and were developed together and published on the same day.
Every value in XPath 2.0 is a sequence of items. The items may be nodes or atomic values. An individual node or atomic value is considered to be a sequence of length one. Sequences may not be nested.
Nodes are of seven kinds, corresponding to different constructs in the syntax of XML: elements, attributes, text nodes, comments, processing instructions, namespace nodes, and document nodes. (The document node replaces the root node of XPath 1.0, because the XPath 2.0 model allows trees to be rooted at other kinds of node, notably elements.)
Nodes may be typed or untyped. A node acquires a type as a result of validation against an XML Schema. If an element or attribute is successfully validated against a particular complex type or simple type defined in a schema, the name of that type is attached as an annotation to the node, and determines the outcome of operations applied to that node: for example, when sorting, nodes that are annotated as integers will be sorted as integers.
Atomic values may belong to any of the 19 primitive types defined in the XML Schema specification (for example, string, boolean, double, float, decimal, dateTime, QName, and so on). They may also belong to a type derived from one of these primitive types: either a built-in derived type such as integer or Name, or a user-defined derived type defined in a user-written schema.
Operations such as arithmetic and boolean comparison require atomic values as their operands. If an operand returns a node (for example,
@price * 1.2), then the node is automatically atomized to extract the atomic value. If the input document has been validated against a schema, then the node will typically have a type annotation, and this determines the type of the resulting atomic value (in this example, the
price attribute might have the type
decimal). If no schema is in use, the node will be untyped, and the type of the resulting atomic value will be
untypedAtomic. Typed atomic values are checked to ensure that they have an appropriate type for the context where they are used: for example, it is not possible to multiply a date by a number. Untyped atomic values, by contrast, follow a weak typing discipline: they are automatically converted to a type appropriate to the operation where they are used: for example with an arithmetic operation an untyped atomic value is converted to the type
The location paths of XPath 1.0 are referred to in XPath 2.0 as path expressions. Informally, a path expression is a sequence of steps separated by the "
/" operator, for example
a/b/c (which is short for
child::a/child::b/child::c). More formally, however, "
/" is simply a binary operator that applies the expression on its right-hand side to each item in turn selected by the expression on the left hand side. So in this example, the expression
a selects all the element children of the context node that are named
<a>; the expression
child::b is then applied to each of these nodes, selecting all the
<b> children of the
<a> elements; and the expression
child::c is then applied to each node in this sequence, which selects all the
<c> children of these
/" operator is generalized in XPath 2.0 to allow any kind of expression to be used as an operand: in XPath 1.0, the right-hand side was always an axis step. For example, a function call can be used on the right-hand side. The typing rules for the operator require that the result of the first operand is a sequence of nodes. The right hand operand can return either nodes or atomic values (but not a mixture). If the result consists of nodes, then duplicates are eliminated and the nodes are returned in document order, an ordering defined in terms of the relative positions of the nodes in the original XML tree.
In many cases the operands of "
/" will be axis steps: these are largely unchanged from XPath 1.0, and are described in the article on XPath 1.0.
Other operators available in XPath 2.0 include the following:
|+, -, *, div, mod, idiv||Arithmetic on numbers, dates, and durations|
|=, !=, <, >, <=, >=||General comparison: compare arbitrary sequences. The result is true if any pair of items, one from each sequence, satisfies the comparison|
|eq, ne, lt, gt, le, ge||Value comparison: compare single items|
|is||Compare node identity: true if both operands are the same node|
|<<, >>||Compare node position, based on document order|
|union, intersect, except||Compare sequences of nodes, treating them as sets, returning the set union, intersection, or difference|
|and, or||boolean conjunction and disjunction. Negation is achieved using the
|to||defines an integer range, for example
|instance of||determines whether a value is an instance of a given type|
|cast as||converts a value to a given type|
|castable as||tests whether a value is convertible to a given type|
Conditional expressions may be written using the syntax
if (A) then B else C.
XPath 2.0 also offers a
for expression, which is a small subset of the FLWOR expression from XQuery. The expression
for $x in X return Y evaluates the expression
Y for each value in the result of expression
X in turn, referring to that value using the variable reference
The function library in XPath 2.0 is greatly extended from the function library in XPath 1.0. (Bold items are available in XPath 1.0)
The functions available include the following:
|General string handling||lower-case, upper-case, substring, substring-before, substring-after, translate, starts-with, ends-with, contains, string-length, concat, normalize-space, normalize-unicode|
|Regular expressions||matches, replace, tokenize|
|Arithmetic||count, sum, avg, min, max, round, floor, ceiling, abs|
|Dates and times||adjust-dateTime-to-timezone, current-dateTime, day-from-dateTime, month-from-dateTime, days-from-duration, months-from-duration, etc.|
|Properties of nodes||name, node-name, local-name, namespace-uri, base-uri, nilled|
|Document handling||doc, doc-available, document-uri, collection, id, idref|
|URIs||encode-for-uri, escape-html-uri, iri-to-uri, resolve-uri|
|QNames||QName, namespace-uri-from-QName, prefix-from-QName, resolve-QName|
|Sequences||insert-before, remove, subsequence, index-of, distinct-values, reverse, unordered, empty, exists|
|Type checking||one-or-more, exactly-one, zero-or-one|
Because of the changes in the data model and type system, not all expressions have exactly the same effect in XPath 2.0 as in 1.0. The main difference is that XPath 1.0 was more relaxed about type conversion, for example comparing two strings (
"4" > "4.0") was quite possible but would do a numeric comparison; in XPath 2.0 this is defined to compare the two values as strings using a context-defined collating sequence.
To ease transition, XPath 2.0 defines a mode of execution in which the semantics are modified to be as close as possible to XPath 1.0 behavior. When using XSLT 2.0, this mode is activated by setting
version="1.0" as an attribute on the
xsl:stylesheet element. This still doesn't offer 100% compatibility, but any remaining differences are only likely to be encountered in unusual cases.
|This section requires expansion. (December 2009)|
Support for XPath 2.0 is still limited.
- For browser support, see Comparison of layout engines (XML).
- "XML and Semantic Web W3C Standards Timeline" (PDF). 2012-02-04.