The xsl:apply-imports instruction processes the current node using only templates that were imported into the stylesheet with xsl:import . A template rule that overrides a template rule in an imported stylesheet can invoke the overridden template rule with xsl:apply-imports .
<xsl:apply-templates select=" node-set-expression " mode=" QualifiedName "> <! -- (xsl:sort xsl:with-param)* -- > </xsl:apply-templates>
The xsl:apply-templates instruction tells the processor to search for and apply the highest-priority template rule in the stylesheet that matches each node identified by the select attribute.
This is an XPath expression that returns a node-set. Each node in this set will be processed further. If the select attribute is omitted, then all child nodes of the context node should be processed.
If the mode attribute is present, then only templates that have a matching mode attribute will be applied. If the mode attribute is absent, then only templates without a mode attribute will be applied.
The xsl:apply-templates element may have xsl:sort child elements to specify the order in which the selected nodes will be processed. Without any xsl:sort children, the default is to process nodes in document order.
The xsl:apply-templates element may have xsl:with-param child elements to pass parameter values to the matched templates.
<xsl:attribute name = " QualifiedName " namespace = " URI "> <! -- template for the attribute value -- > </xsl:attribute>
The xsl:attribute instruction adds an attribute to an element in the result tree. This element can be a child of an xsl:attribute-set element, an xsl:element instruction, or a literal result element. In each case, all xsl:attribute elements must precede all literal result elements and other instructions that insert content into the output element.
The name of the attribute this instruction creates.
The namespace URI of the attribute. If a nonempty namespace URI is specified, then the processor will pick an appropriate prefix for the attributeprobably, but not necessarily , the one used in the name attribute.
The contents of this element are a template whose instantiation only produces text nodes. The value of the attribute added to the result tree is determined by instantiating the template.
<xsl:attribute-set name = " QualifiedName " use-attribute-sets = " QualifiedName1 QualifiedName2... "> <! -- xsl:attribute* -- > </xsl:attribute-set>
The xsl:attribute-set top-level element defines a collection of attributes that can be applied to elements elsewhere in the stylesheet. For instance, you could define an attribute set that includes the necessary attributes to create a simple XLink, and then you could attach the set to each simple XLink element.
The name attribute gives a name for the set, by which xsl:element and other xsl:attribute-set elements can load this attribute set.
The use-attribute-sets attribute adds attributes from a different attribute set into this attribute set. More than one attribute set can be loaded by separating multiple names with whitespace. The attributes defined in all loaded sets and all attributes defined by child xsl:attribute elements are merged so that no attribute appears in the set more than once. It is an error if an attribute set uses itself directly or indirectly.
This element contains zero or more xsl:attribute elements. Each such element adds one attribute to the set.
<xsl:call-template name = " QualifiedName "> <! -- xsl:with-param* -- > </xsl:call-template>
The xsl:call-template instruction invokes a template by name. The current node and context node list are the same for the called template as for the calling template. Templates may be called recursively; an xsl:template element may contain an xsl:call-template element that calls that very xsl:template element. This technique is useful for doing things you'd accomplish with loops in a traditional procedural programming language.
The name of the xsl:template element to call.
This element contains zero or more xsl:with-param elements that pass parameters to the named template.
<xsl:choose> <! -- (xsl:when+, xsl:otherwise?) -- > </xsl:choose>
The xsl:choose element selects one (or none) of a sequence of alternatives.
This element contains one or more xsl:when elements, each of which has a test condition. The contents of the first xsl:when child whose test condition is true are output.
The xsl:choose element may have an optional xsl:otherwise element whose contents are output only if none of the test conditions in any of the xsl:when elements is true.
If the xsl:choose does not have an xsl:otherwise child element, and none of the test conditions in any of the xsl:when child elements is true, then this element does not produce output.
<xsl:comment> <! -- template -- > </xsl:comment>
The xsl:comment instruction inserts a comment into the result tree.
The content of xsl:comment is a template that will be instantiated to form the text of the comment inserted into the result tree. The result of instantiating this template should only be text nodes that do not contain the double hyphen ( -- ) or end with a hyphen.
<xsl:copy use-attribute-sets = " QualifiedName1 QualifiedName2... "> <! -- template -- > </xsl:copy>
The xsl:copy element copies the current node from the source document into the output document. It copies the node itself and any namespace nodes the node possesses. However, it does not copy the node's children or attributes.
A whitespace-separated list of xsl:attribute-set names. These attribute sets are merged, and all attributes in the merged set are added to the copied element.
If the current node is an element node, attributes can be added via xsl:attribute children. If the current node is the root node or an element node (a node that can have children), then xsl:copy may contain a template that specifies the content of the element inserted into the result tree. All xsl:attribute elements must precede the output template.
<xsl:copy-of select = " expression " />
The xsl:copy-of instruction inserts whatever is identified by the select attribute into the output document. This instruction copies the specific nodes identified by the expression, as well as all those nodes' children, attributes, namespaces, and descendants. This is how it differs from xsl:copy . If the expression selects something other than a node-set, such as a number, then the expression is converted to its string-value, and the string is output.
An XPath expression identifying the object to copy into the result tree.
<xsl:decimal-format name = " QualifiedName " decimal-separator = " char " grouping-separator = " char " infinity = " string " minus-sign = " char " NaN = " string " percent = " char " per-mille = " char " zero-digit = " char " digit = " char " pattern-separator = " char " />
The xsl:decimal-format top-level element defines a pattern by which the format-number( ) function can convert floating-point numbers into text strings. The defaults work well for English, but details may change for other languages and locales, such as French or Chinese.
The string by which the format-number( ) function identifies the xsl:decimal-format element to use. If this attribute is omitted, then this element establishes the default decimal format used by the format-number() function.
The character that separates the integer part from the fractional point in a floating-point number. This character is a period (decimal point) in English and a comma in French. It may be something else in other languages. If not specified, the default is a period.
The character that separates groups of digits; for example, the comma that separates every three digits in English or the space in French. If this is not specified, the comma is the default.
The string that represents IEEE 754 infinity; Infinity by default.
The character prefixed to negative numbers; a hyphen by default.
The string that represents IEEE 754 Not a Number; NaN by default.
The character that represents a percent; % by default.
The character that represents a per mille; by default.
The character that represents zero; by default. Digits 1 through 9 will be represented by the nine subsequent Unicode values after this one. For instance, setting zero-digit to A would set 1 to B , 2 to C , 3 to D , and so on. This is also the character used to represent 0 in format patterns.
The character that represents a digit in a format pattern; # by default.
The character that separates positive and negative subpatterns in a format pattern; ; by default.
<xsl:element name = " QualifiedName " namespace = " URI " use-attribute-sets = " QualifiedName1 QualifiedName2... "> <! -- template -- > </xsl:element>
The xsl:element instruction inserts an element into the result tree. The element's name is given by the name attribute. The element's namespace URI, if any, is given by the optional namespace attribute. Attributes can be added via xsl:attribute children or by referencing an xsl:attribute-set declared elsewhere in the stylesheet from the use-attribute-sets attribute. Finally, the element's contents are determined by instantiating the template contained in the xsl:element element's content.
The name of the element this instruction creates.
The namespace URI of the element this instruction creates. If this attribute is omitted, then the namespace is determined by matching the name's prefix (or lack thereof) to the namespace declarations in scope at this point in the stylesheet.
A whitespace-separated list of names of xsl:attribute-set elements declared as top-level elements elsewhere in the stylesheet. These attribute sets are merged, and all attributes in the merged set are added to the element.
The contents of this element are a template. Once instantiated, this template forms the content of the element inserted into the result tree.
<xsl:fallback> <! -- template -- > </xsl:fallback>
The xsl:fallback instruction normally appears as a child of an extension element. If the processor does not recognize the extension element, then it instantiates the contents of all the element's xsl:fallback children in order. If the processor does recognize the element in which the xsl:fallback element appears, then the contents of the xsl:fallback element will not be output.
The contents of this element are a template that is instantiated and output if and only if the XSLT processor does not recognize the xsl:fallback element's parent element.
<xsl:for-each select = " node-set-expression "> <! -- (xsl:sort*, template) -- > </xsl:for-each>
The xsl:for-each instruction iterates over the nodes identified by its select attribute and applies templates to each one.
An XPath node-set expression identifying which nodes to iterate over.
Normally, the selected nodes are processed in the order in which they appear in the document. However, nodes can be sorted using xsl:sort child elements. The first such element is the primary sort key, the second is the secondary sort key, and so on.
The xsl:for-each element must also contain a template that is instantiated once for each member of the node-set returned by the node-set expression in the select attribute.
<xsl:if test = " boolean-expression "> <! -- template -- > </xsl:if>
The xsl:if instruction contains a template that is instantiated if and only if the XPath expression contained in its test attribute is true . There is no xsl:else or xsl:else-if element. For these purposes, use xsl:choose instead.
An XPath expression returning a Boolean. If this expression is true , the contents of the xsl:if element are instantiated. If it's false , they're not.
A template is instantiated if the test attribute evaluates to true .
<xsl:import href = " URI " />
The xsl:import top-level element imports the XSLT stylesheet found at the URI given by the href attribute. Source documents are processed using the combination of templates in the imported and importing stylesheets. In the event of a conflict between templates in the two stylesheets, the ones in the importing stylesheet take precedence. In the event of a conflict between imported stylesheets, the last one imported takes precedence.
All xsl:import elements must be immediate children of the root xsl:stylesheet element. Furthermore, they must appear before all other top-level elements.
An imported stylesheet may itself import another stylesheet. A stylesheet may not import a stylesheet that was already imported, directly or indirectly. That is, it's an error if A imports B, which imports A, thus creating a circular reference.
The relative or absolute URI of the stylesheet to import. Relative URIs are resolved relative to the base URI of the importing stylesheet.
<xsl:include href = " URI " />
The xsl:include top-level element copies the contents of the xsl:stylesheet or xsl:transform element found at the URI given by the href attribute. Unlike xsl:import , whether a template or other element comes from the including or the included stylesheet has absolutely no effect on the precedence of the various rules.
An included stylesheet may include another stylesheet. A stylesheet may not include a stylesheet that was already included, directly or indirectly; it is an error if A includes B, which includes A.
The relative or absolute URI of the stylesheet to include. Relative URIs are resolved relative to the including stylesheet's base URI.
<xsl:key name = " QualifiedName " match = " pattern " use = " expression " />
The xsl:key top-level element defines one or more keys that can be referenced from elsewhere in the stylesheet using the key( ) function. Each key has a name, a string-value, and a node.
The key's name.
An XSLT match pattern, like that used by xsl:template , specifying which nodes have this key. If this pattern matches more than one node in the source document, then a single xsl:key element may define many keys, all with the same name and possibly the same value, but with different nodes.
An XPath expression that is converted to a string to give the value of keys defined by this element. The expression is evaluated with respect to each key's node. If match identifies multiple nodes, then use may produce different values for each key.
<xsl:message terminate = "yes" "no"> <! -- template -- > </xsl:message>
The xsl:message instruction sends a message to the XSLT processor. Which messages the processor understands and what it does with messages it understands is processor-dependent. Printing debugging information on stderr or stdout is one common use of xsl:message .
If the attribute is present and has the value yes , then the XSLT processor should halt after the message is delivered and acted on.
An xsl:message element's content is a template instantiated to create an XML fragment . The result is then delivered to the XSLT processor as the message.
<xsl:namespace-alias stylesheet-prefix = " prefix " result-prefix = " prefix " />
The top-level xsl:namespace-alias element declares that one namespace URI in the stylesheet should be replaced by a different namespace URI in the result tree. Aliasing is particularly useful when transforming XSLT into XSLT using XSLT; consequently, it is not obvious which names belong to the input, which belong to the output, and which belong to the stylesheet.
The prefix bound to the namespace used inside the stylesheet itself. May be set to #default to indicate that the nonprefixed default namespace should be used.
The prefix bound to the namespace used in the result tree. May be set to #default to indicate that the nonprefixed default namespace should be used.
<xsl:number value = " number-expression " count = " pattern " from = " pattern " level = "single" "multiple" "any" format = " letter or digit " lang = " langcode " letter-value = "alphabetic" "traditional" grouping-separator = " char " grouping-size = " number " />
The xsl:number instruction inserts a formatted integer into the result tree.
This XPath expression returns the number to be formatted. If necessary, the result of the expression is rounded to the nearest integer. The value attribute is often omitted, in which case the number is calculated from the position of the current node in the source document. The position is calculated as specified by the level , count , and from attributes.
This attribute contains a pattern that specifies which nodes should be counted at those levels. The default is to count all nodes with the same node type (element, text, attribute, etc.) and name as the current node.
This attribute contains a pattern identifying the node from which counting starts; that is, it identifies a node that serves as a cutoff point. Any nodes that precede this node are not counted, even if they match the count pattern.
This attribute specifies which levels of the source tree should be considered in determining the position of the current node. It can be set to single to count the preceding siblings of the current node's ancestor that match the count pattern. It can be set to any to count all nodes in the document that match the count pattern and precede the current node. It can be set to multiple to produce hierarchical sequences of numbers such as 2.7.3, where each number in the sequence is calculated from the preceding sibling's ancestor node that matches the count pattern. The default is single .
This attribute determines how the list is numbered. Format tokens and sequences they produce include the following:
1, 2, 3, 4, 5, 6, . . .
01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, . . .
A, B, C, D, . . . , Z, AA, AB, AC, . . .
a, b, c, d, . . . , z, aa, ab, ac, . . .
i, ii, iii, iv, v, vi, vii, viii, ix, x, xi, . . .
I, II, III, IV, V, VI, VII, VIII, IX, X, XI, XII, . . .
This is the RFC 1766 language code describing the language in which the number should be formatted (e.g., en or fr-CA ).
The default is traditional . However, you can set this attribute to alphabetic to indicate that a format of I should start the sequence I, J, K, L, M, N, . . . rather than I, II, III, IV, V, VI, . . .
This is the character that separates groups of digits. For instance, in English, the comma customarily separates every three digits, as in 2,987,667,342. In French, a space is used instead, so this number would be formatted as 2 987 667 342.
This is the number of digits in each group. In most languages, including English, digits are divided into groups of three. However, a few languages use groups of four.
<xsl:otherwise> <! -- template -- > </xsl:otherwise>
The xsl:otherwise element only appears as the last child element of an xsl:choose element. It serves as the default result if no xsl:when element in the same xsl:choose element is instantiated.
The contents are a template that is instantiated if and only if none of the xsl:choose element's xsl:when sibling elements is true .
<xsl:output method = " xml " "html" "text" " PrefixedName " version = " NMTOKEN " encoding = " encoding_name " omit-xml-declaration = "yes" "no" standalone = "yes" "no" doctype-public = " PUBLIC_ID " doctype-system = " SYSTEM_ID " cdata-section-elements = " element_name_1 element_name_2 ..." indent = "yes" " no " media-type = " string " />
The top-level xsl:output element helps determine the exact formatting of the XML document produced when the result tree is stored in a file, written onto a stream, or otherwise serialized into a sequence of bytes. It has no effect on the production of the result tree itself.
The default method is xml , which simply means that the serialized output document will be a well- formed external parsed entity or XML document. If method is set to html , or if the method attribute is not present and the root element of the output tree is html , in any combination of case, then the processor attempts to generate HTML that is more compatible with existing browsers. For example, empty-element tags like <br/> are converted to <br> . The text method outputs only the contents of the text nodes in the output tree. It strips all markup. XSLT processors may also recognize and support other values that are indicated by prefixed names, such as saxon:xhtml and jd:canonical-xml .
A name token that identifies the output method's version. In practice, this has no effect on the output.
The encoding the serializer should use, such as ISO-8859-1 or UTF-16.
If this attribute has the value yes , then no XML declaration is included. If it has the value no or is not present, then an XML declaration is included.
The value of the standalone attribute in the XML declaration. Like that attribute, it must have the value yes or no .
The public identifier used in the document type declaration.
The system identifier used in the document type declaration.
A whitespace-separated list of qualified element names in the result tree whose contents should be emitted using CDATA sections.
If this attribute has the value yes , then the processor is allowed (but not required) to insert extra whitespace to attempt to "pretty-print" the output tree. The default is no .
The output's MIME media type, such as text/html or application/xml .
<xsl:param name = " QualifiedName " select = " expression "> <! -- template -- > </xsl:param>
Inside an xsl:template element, an xsl:param element receives a named argument passed to the template by xsl:with-param . It also provides a default value that's used when the caller does not provide a value for the parameter. A top-level xsl:param element defines a global variable that can be set from the outside environment when invoking the stylesheet. If an xsl:apply-templates or xsl:call-template passes in a parameter value using xsl:with-param when the template is invoked, that value overrides any default value the xsl:param element may have. The parameter can be dereferenced using the form $ name in expressions.
The parameter's name.
An XPath expression that is evaluated to produce the parameter's value. If xsl:param has a select attribute, then it must be an empty element. If a nonempty xsl:param element does not have a select attribute, then the value is the result of instantiating the template in the content. If an empty xsl:param element does not have a select attribute, then the value is the empty string.
An xsl:param element's content is a template that is instantiated to produce a result-tree fragment. This result-tree fragment then becomes the parameter's value. A nonempty xsl:param element must not have a select attribute.
<xsl:preserve-space elements=" QualifiedName_1 QualifiedName_2... " />
The top-level xsl:preserve-space element specifies which elements in the source document will not have whitespace stripped from them before they are transformed. Whitespace stripping removes text nodes that contain only whitespace (the space character, the tab character, the carriage return, and the line feed). By default, whitespace is preserved in an element unless its name is listed in the elements attribute of an xsl:strip-space element. This element allows you to override the list given in xsl:strip-space ; if an element is listed in both xsl:strip-space and xsl:preserve-space , then its whitespace is preserved.
A whitespace-separated list of elements in which space should be preserved. Besides element names, the elements attribute can contain an asterisk to indicate that whitespace should be preserved in all elements. It can also contain a namespace prefix followed by a colon and an asterisk to indicate that whitespace should be preserved in all elements in the given namespace.
<xsl:processing-instruction name = " target "> <! -- template -- > </xsl:processing-instruction>
The xsl:processing-instruction element inserts a processing instruction into the result tree.
The processing instruction's target.
The xsl:processing-instruction element's contents are a template that is instantiated to produce the processing-instruction data. This template may include XSLT instructions, provided that the result of instantiating this template is text that does not contain the two-character string ?> .
<xsl:sort select = " string-expression " data-type = "text" "number" " PrefixedName " lang = " langcode " order = "ascending" "descending" case-order = "upper-first" "lower-first" />
The xsl:sort instruction appears as a child of either xsl:apply-templates or xsl:for-each . It changes the order in which templates are applied to the context node list from document order to another order, such as alphabetic. You can perform multiple key sorts (e.g., sort first by last name, then by first name, then by middle name) using multiple xsl:sort elements in descending order of the keys' importance.
The key to sort by. If select is omitted, then the sort key is set to the value of the current node.
By default, sorting is purely alphabetic. However, alphabetic sorting leads to strange results with numbers. For instance, 10, 100, and 1,000 all sort before 2, 3, and 4. You can specify numeric sorting by setting data-type to number .
Sorting is language dependent. Setting the lang attribute to an RFC 1766 language code changes the language. The default language is system dependent.
The order by which strings are sorted, either descending or ascending . The default is ascending order.
upper-first or lower-first to specify whether uppercase letters sort before lowercase letters or vice versa. The default depends on the language.
<xsl:strip-space elements=" QualifiedName_1 QualifiedName_2... " />
The top-level xsl:strip-space element specifies which elements in the source document have whitespace stripped from them before they are transformed. Whitespace stripping removes all text nodes that contain only whitespace (the space character, the tab character, the carriage return, and the line feed). By default, whitespace is not stripped from an element unless its name is listed in the elements attribute of an xsl:strip-space element.
This element does not trim leading or trailing whitespace, or otherwise normalize whitespace in elements that contain even a single nonwhitespace character.
A whitespace-separated list of elements in which space should be stripped. Besides element names, the elements attribute can contain an asterisk to indicate that whitespace should be stripped in all elements or contain a namespace prefix followed by a colon and asterisk to indicate that whitespace should be stripped in all elements in the given namespace.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" id = " ID " extension-element-prefixes = " prefix1 prefix2... " exclude-result-prefixes = " prefix1 prefix2... " version = "1.0"> <! -- (xsl:import*, top-level-elements) -- > </xsl:stylesheet>
The xsl:stylesheet element is the root element for XSLT documents.
A standard namespace declaration that maps the prefix xsl to the namespace URI http://www.w3.org/1999/XSL/Transform . The prefix can be changed if necessary.
Any XML name that's unique within this document's ID type attributes.
A whitespace-separated list of namespace prefixes used by this document's extension elements.
A whitespace-separated list of namespace prefixes whose declarations should not be copied into the output document.
Currently, always the value 1.0 . However, XSLT 2.0 may be released in the lifetime of this edition with a concurrent updating of this number.
Any xsl:import elements, followed by any other top-level elements in any order.
<xsl:template match = " pattern " priority = " number " name = " QualifiedName " mode = " QualifiedName "> <! -- (xsl:param*, template) -- > </xsl:template>
The xsl:template top-level element is the key to all of XSLT. Confusingly, the xsl:template element itself is not a template. Rather, it contains a template. The entire xsl:template element is called a template rule . The match attribute contains a pattern against which nodes are compared as they're processed. If the pattern matches a node, then the template (i.e., the contents of the template rule) is instantiated and inserted into the output tree.
A pattern against which nodes can be compared. This pattern is a location path using only the child , attribute , and descendant-or-self axes or a combination of several such location paths.
A number. If more than one template rule with the same import precedence matches a given node, the one with the highest priority is chosen . If this attribute is not present, then the template rule's priority is calculated in the following way:
Template rules with match patterns composed of just an element or attribute name (e.g., person or @profession ) have priority 0.
Template rules with match patterns composed of just a processing-instruction( ' target ' ) node test have priority 0.
Template rules with match patterns in the form prefix :* have priority -0.25.
Template rules with match patterns that just have a wildcard node test ( * , @* , comment() , node( ) , text( ) , and processing-instruction( ) ) have priority -0.5. (This means that built-in template rules have priority -0.5. However, they are also imported before all other template rules, and thus never override any explicit template rule, regardless of priority.)
Template rules with any other patterns ( person[name='Feynman'] , people/person/@profession , person/text( ) , etc.) have priority 0.5.
It is an error if two or more template rules match a node and have the same priority. However, in this case, most XSLT processors choose the last template rule occurring in the stylesheet, rather than signaling the error.
A name by which this template rule can be invoked from an xsl:call-template element, rather than by node matching.
If the xsl:template element has a mode, then this template rule is matched only when the calling instruction's mode attribute matches this mode attribute's value.
The template that should be instantiated when this element is matched or called by name.
<xsl:text disable-output-escaping = "yes" " no "> <! -- #PCDATA -- > </xsl:text>
The xsl:text instruction is used inside templates to indicate that its contents should be output as text. Its contents are pure text, not elements. If the contents are composed exclusively of whitespace, then that whitespace is copied literally into the output document, rather than being stripped as it would be, by default, in most other elements.
Setting the disable-output-escaping attribute to yes indicates that characters such as < and & which are normally replaced by entity or character references such as < or < should instead be output as the literal characters themselves . Note that the xsl:text element's content in the stylesheet must still be well-formed, and any < or & characters must be written as < , & , or the equivalent character references. However, when the output document is serialized, these references are replaced by the actual represented characters rather than references that represent them.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" id = " ID " extension-element-prefixes = " prefix1 prefix2... " exclude-result-prefixes = " prefix1 prefix2... " version = "1.0"> <! -- (xsl:import*, top-level-elements) -- > </xsl:transform>
The xsl:transform element is a seldom-used synonym for the xsl:stylesheet root element. It has the same attributes and contents as xsl:stylesheet and is used in exactly the same way as xsl:stylesheet . See the description of the xsl:stylesheet element for the discussion of its attributes and content.
<xsl:value-of select = " expression " disable-output-escaping = "yes" " no " />
The xsl:value-of element computes the string-value of an XPath expression and inserts it into the result tree. The string-values of the seven different kinds of nodes are as follows:
The text content of the element after all entity references are resolved and all tags, comments, and processing instructions are stripped
The text of the node
The normalized value of the attribute
The value of the root element
The processing instruction data ( <? , ?> , and the target are not included)
The text of the comment ( <!-- and --> are not included)
The namespace URI
You can compute values of things that aren't nodes. The value of a node-set is the value of the first node in the set. The value of a string expression is the string. The value of a number expression is the string form of the number. The value of a Boolean expression is the string true if the Boolean is true or the string false if the Boolean is false.
This is the XPath expression whose value is inserted into the result tree.
If this attribute has the value yes , then when the output document is serialized, characters such as < and & in the value are not replaced with entity or character references. This may result in a malformed document.
<xsl:variable name = " QualifiedName " select = " expression "> <! -- template -- > </xsl:variable>
The xsl:variable element binds a name to a value of any type (string, number, node-set, etc.). This variable can then be dereferenced elsewhere using the form $ name in an expression.
The variable's name.
An XPath expression that sets the value of the variable. If xsl:variable has a select attribute, then it must be an empty element.
A template that is instantiated to produce the variable's value as a result-tree fragment. If an xsl:variable is not an empty element, it must not have a select attribute. If xsl:variable is empty and does not have a select attribute, then its value is the empty string.
<xsl:when test = " boolean-expression "> <! -- template -- > </xsl:when>
The xsl:when element only appears as a child of an xsl:choose element.
An XPath expression that evaluates to either true or false. The xsl:when contents are inserted into the result tree if and only if this is the first xsl:when element in the xsl:choose element whose test attribute evaluates to true.
The template to be instantiated and inserted into the result tree if the test attribute is true.
<xsl:with-param name = " QualifiedName " select = " expression "> <! -- template -- > </xsl:with-param>
The xsl:with-param element passes a named parameter to a template that expects it. This can either be a child of xsl:apply-templates or xsl:call-template . An xsl:template element receives the parameter via an xsl:param element with the same name. If a template expects to receive a particular parameter and doesn't get it, then it can take the default from the xsl:param element instead.
The name of the parameter.
An XPath expression evaluated to form the value of the parameter. If xsl:with-param has a select attribute, then it must be an empty element. If xsl:with-param does not have a select attribute, then the value is taken from the element's contents.
A template that is instantiated and passed as the parameter's value. If xsl:with-param is not an empty element, it must not have a select attribute. If xsl:with-param is empty and does not have a select attribute, then its value is the empty string.