Operators and Special Characters

XSL Patterns are constructed using the operators and special characters shown in the following table.

/	Child operator; selects immediate children of the left-side collection. When this path operator appears at the start of the pattern, it indicates that children should be selected from the root node.
//	Recursive descent; searches for the specified element at any depth. When this path operator appears at the start of the pattern, it indicates recursive descent from the root node.
.	Indicates the current context.
*	Wildcard; selects all elements regardless of the element name.
@	Attribute; prefix for an attribute name.
@*	Attribute Wildcard; selects all attributes regardless of name.
:	Namespace separator; separates the namespace prefix from the element or attribute name.
! *	Applies the specified method to the reference node.
( ) *	Groups operations to explicitly establish precedence.
[ ]	Applies a filter pattern.
[ ] *	Subscript operator. Used for indexing within a collection.

* Extended XSL Pattern method described in the XQL Proposal .

(Note that this table does not list Boolean, Comparison, and Set Expressions or Set Operations. These are treated in subsequent topics.)

Precedence order (from highest precedence to lowest) is defined as indicated in the following table.

1.	( )	Grouping
2.	[ ]	Filters
3.	/ //	Path operations

Note that the filter pattern operator (the brackets) have a higher precedence than the path operators (the slash characters). For example, the expression "//comment()[3]" is interpreted as "//(comment()[3])", and selects all comments with an index equal to 3 relative to the comment's parent anywhere in the document. This differs from the expression "(//comment())[3]", which selects the third comment from the set of all comments relative to the parent. The first expression can return more than one comment, while the latter can return only one comment.

These operators and special characters are described in detail throughout this reference. Other topics discuss Set Operations.

Path Operators

The collection of elements of a certain type can be determined using the path operators (/ or //). These operators take as their arguments a "left side" collection on which to perform the selection, and a "right side" collection indicating which elements to select. The child operator (/) selects from immediate children of the left-side collection, while the descendant operator (//) selects from arbitrary descendants of the left-side collection. In effect, the // can be considered a substitute for one or more levels of hierarchy.

Note that the path operators change the context as the query is performed. By stringing path operators together, users can traverse the document tree.

Examples

Find all first-name elements within an author element. Note that the author children of the current context are found, and then first-name children are found relative to the context of the author elements.
author/first-name
Find all title elements, one or more levels deep in the bookstore (arbitrary descendants):
bookstore//title
Note that this is different from the following pattern, which finds all title elements that are grandchildren of bookstore elements:
bookstore/*/title
Find emph elements anywhere inside book excerpts, anywhere inside the bookstore:
bookstore//book/excerpt//emph
Find all titles, one or more levels deep in the current context. Note that this situation is essentially the only one where the period notation is required.
.//title

Wildcard Character

An element can be referenced without using its name by substituting the wildcard (*) collection. The * collection returns all elements that are children of the current context, regardless of the tag name.

Examples

Find all element children of author elements:
author/*
Find all last names that are grandchildren of books:
book/*/last-name
Find the grandchildren elements of the current context:
*/*
Find the book element from the "my" namespace:
my:book
Find all elements from the "my" namespace:
my:*
Note that the pattern "*:book" is not supported.

Attributes

XSL Patterns denotes attribute names with the @ symbol. Attributes and child elements are treated impartially, and capabilities are equivalent between the two types wherever possible.

Note: Attributes cannot contain child elements, so syntax errors occur when path operators are applied to attributes. In addition, you cannot apply an index to attributes because, by definition, no order is defined for attributes.

Examples

Find the style attribute of the current element context:
@style
Find the exchange attribute on price elements within the current context:
price/@exchange
The following example is not valid:
price/@exchange/total
Find the style attribute for all book elements:
book/@style

Finding Multiple Attributes

All attributes of an element can be returned using @*. This is potentially useful for applications that treat attributes as fields in a record.

Note that the pattern "@*:title" is not supported.

Examples

Find all attributes of the current element context:
@*
Find all attributes from the "my" namespace. This does not include unqualified attributes on elements from the "my" namespace:
@my:*