Glossary of "XSL Transformations (XSLT) 2.0"

Term entries in the "XSL Transformations (XSLT) 2.0" glossary

W3C Glossaries

Showing results 81 - 100 of 142

population

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The sequence of items to be grouped, which is referred to as the population, is determined by evaluating the XPath expression contained in the select attribute.
population order

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The population is treated as a sequence; the order of items in this sequence is referred to as population order
principal stylesheet module

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A stylesheet may consist of several stylesheet modules, contained in different XML documents. For a given transformation, one of these functions as the principal stylesheet module. The complete stylesheet is assembled by finding the stylesheet modules referenced directly or indirectly from the principal stylesheet module using xsl:include and xsl:import elements: see and .
processing order

From XSL Transformations (XSLT) 2.0 (2007-01-23)

There is another ordering among groups referred to as processing order. If group R precedes group S in processing order, then in the result sequence returned by the xsl:for-each-group instruction the items generated by processing group R will precede the items generated by processing group S.
processor

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The software responsible for transforming source trees into result trees using an XSLT stylesheet is referred to as the processor. This is sometimes expanded to XSLT processor to avoid any confusion with other processors, for example an XML processor.
qName

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A QName is always written in the form (NCName ":")? NCName, that is, a local name optionally preceded by a namespace prefix. When two QNames are compared, however, they are considered equal if the corresponding expanded-QNames are the same, as described below.
recoverable errors

From XSL Transformations (XSLT) 2.0 (2007-01-23)

Some dynamic errors are classed as recoverable errors. When a recoverable error occurs, this specification allows the processor either to signal the error (by reporting the error condition and terminating execution) or to take a defined recovery action and continue processing.
required type

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The context within a stylesheet where an XPath expressionappears may specify the required type of the expression. The required type indicates the type of the value that the expression is expected to return.
reserved namespaces

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The XSLT namespace, together with certain other namespaces recognized by an XSLT processor, are classified as reserved namespaces and must be used only as specified in this and related specifications.
result tree

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The term result tree is used to refer to any tree constructed by instructions in the stylesheet. A result tree is either a final result tree or a temporary tree.
schema components

From XSL Transformations (XSLT) 2.0 (2007-01-23)

Type definitions and element and attribute declarations are referred to collectively as schema components.
schema instance namespace

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The schema instance namespacehttp://www.w3.org/2001/XMLSchema-instance is used as defined in
schema namespace

From XSL Transformations (XSLT) 2.0 (2007-01-23)

The schema namespacehttp://www.w3.org/2001/XMLSchema is used as defined in
schema-aware XSLT processor

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A schema-aware XSLT processor is an XSLT processor that implements all the mandatory requirements of this specification, including those features that a basic XSLT processor signals as an error. The mandatory requirements of this specification are taken to include the mandatory requirements of XPath 2.0, as described in . A requirement is mandatory unless the specification includes wording (such as the use of the words should or may) that clearly indicates that it is optional.
sequence constructor

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A sequence constructor is a sequence of zero or more sibling nodes in the stylesheet that can be evaluated to return a sequence of nodes and atomic values. The way that the resulting sequence is used depends on the containing instruction.
serialization

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A frequent requirement is to output a final result tree as an XML document (or in other formats such as HTML). This process is referred to as serialization.
serialization error

From XSL Transformations (XSLT) 2.0 (2007-01-23)

If a transformation has successfully produced a final result tree, it is still possible that errors may occur in serializing the result tree. For example, it may be impossible to serialize the result tree using the encoding selected by the user. Such an error is referred to as a serialization error.
serialization feature

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A processor that claims conformance with the serialization featuremust support the conversion of a final result tree to a sequence of octets following the rules defined in .
shadows

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A binding shadows another binding if the binding occurs at a point where the other binding is visible, and the bindings have the same name.
simplified stylesheet module

From XSL Transformations (XSLT) 2.0 (2007-01-23)

A simplified stylesheet module is a tree, or part of a tree, consisting of a literal result element together with its descendant nodes and associated attributes and namespaces. This element is not itself in the XSLT namespace, but it must have an xsl:version attribute, which implies that it must have a namespace node that declares a binding for the XSLT namespace. For further details see .

The Glossary System has been built by Pierre Candela during an internship in W3C; it's now maintained by Dominique Hazael-Massieux

Copyright © 2000-2003W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.