- alias
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
A stylesheet can use the xsl:namespace-alias element to declare that a literal namespace URI is being used as an alias for a target namespace URI.
- arity
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The arity of a stylesheet function is the number of xsl:param elements in the function definition.
- atomization
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The term atomization is defined in . It is a process that takes as input a sequence of nodes and atomic values, and returns a sequence of atomic values, in which the nodes are replaced by their typed values as defined in .
- attribute set
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The xsl:attribute-set element defines a named attribute set: that is, a collection of attribute definitions that can be used repeatedly on different constructed elements.
- attribute value template
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
In an attribute that is designated as an attribute value template, such as an attribute of a literal result element, an expression can be used by surrounding the expression with curly brackets ({})
- backwards compatibility feature
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
A processor that claims conformance with the backwards compatibility featuremust support the processing of stylesheet instructions and XPath expressions with backwards compatible behavior, as defined in .
- base output URI
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The base output URI is a URI to be used as the base URI when resolving a relative URI allocated to a final result tree. If the transformation generates more than one final result tree, then typically each one will be allocated a URI relative to this base URI.
- basic XSLT processor
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
A basic XSLT processor is an XSLT processor that implements all the mandatory requirements of this specification with the exception of certain explicitly-identified constructs related to schema processing.
- character map
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
A character map allows a specific character appearing in a text or attribute node in the final result tree to be substituted by a specified string of characters during serialization.
- circularity
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
A circularity is said to exist if a construct such as a global variable, an attribute set, or a key is defined in terms of itself. For example, if the expression or sequence constructor specifying the value of a global variableX references a global variable Y, then the value for Ymust be computed before the value of X. A circularity exists if it is impossible to do this for all global variable definitions.
- collation
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
Facilities in XSLT 2.0 and XPath 2.0 that require strings to be ordered rely on the concept of a named collation. A collation is a set of rules that determine whether two strings are equal, and if not, which of them is to be sorted before the other.
- context item
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The context item is the item currently being processed. An item (see ) is either an atomic value (such as an integer, date, or string), or a node. The context item is initially set to the initial context node supplied when the transformation is invoked (see ). It changes whenever instructions such as xsl:apply-templates and xsl:for-each are used to process a sequence of items; each item in such a sequence becomes the context item while that item is being processed.
- context node
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
If the context item is a node (as distinct from an atomic value such as an integer), then it is also referred to as the context node. The context node is not an independent variable, it changes whenever the context item changes. When the context item is an atomic value, there is no context node.
- context position
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The context position is the position of the context item within the sequence of items currently being processed. It changes whenever the context item changes. When an instruction such as xsl:apply-templates or xsl:for-each is used to process a sequence of items, the first item in the sequence is processed with a context position of 1, the second item with a context position of 2, and so on.
- context size
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The context size is the number of items in the sequence of items currently being processed. It changes whenever instructions such as xsl:apply-templates and xsl:for-each are used to process a sequence of items; during the processing of each one of those items, the context size is set to the count of the number of items in the sequence (or equivalently, the position of the last item in the sequence).
- core function
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The term core function means a function that is specified in and that is in the standard function namespace.
- current captured substrings
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
While the xsl:matching-substring instruction is active, a set of current captured substrings is available, corresponding to the parenthesized sub-expressions of the regular expression.
- current group
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The evaluation context for XPath expressions includes a component called the current group, which is a sequence. The current group is the collection of related items that are processed collectively in one iteration of the xsl:for-each-group element.
- current grouping key
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
The evaluation context for XPath expressions includes a component called the current grouping key, which is an atomic value. The current grouping key is the grouping key shared in common by all the items within the current group.
- current mode
-
From XSL Transformations (XSLT) 2.0 (2007-01-23)
At any point in the processing of a stylesheet, there is a current mode. When the transformation is initiated, the current mode is the default mode, unless a different initial mode has been supplied, as described in . Whenever an xsl:apply-templates instruction is evaluated, the current mode becomes the mode selected by this instruction.