This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:w3c:xslt [2020/05/07 15:35] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:tech:w3c:xslt [2021/08/17 15:18] (current) murphy [Abstract] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== W3C: XSL Transformations (XSLT) Version 3.0 (acronym) ========= | + | ===== W3C: XSL Transformations (XSLT) Version 3.0 ===== |
| - | [[dido:public:xapend.stds:tech:w3c| return to the W3C Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:tech:w3c:start| return to the W3C Standards ]] |
| <table> | <table> | ||
| Line 13: | Line 13: | ||
| </table> | </table> | ||
| - | : **Note**: The following is an excerpt from the official NIST catalog. It is provided here as a connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note**: The following is an excerpt from the [[https://www.w3.org/TR/official| W3C site]]. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
| - | ====== Introduction ====== | + | ==== Abstract ==== |
| - | ===== What is XSLT? ===== | + | : //This specification defines the [[dido:public:ra:xapend:xapend.a_glossary:s:syntax|syntax]] and [[dido:public:ra:xapend:xapend.a_glossary:s:semantics|semantics]] of XSLT 3.0, a language designed primarily for transforming XML documents into other XML documents.// |
| + | |||
| + | ==== Introduction (What is XSLT?) ==== | ||
| : //This specification defines the syntax and semantics of the XSLT 3.0 language.// | : //This specification defines the syntax and semantics of the XSLT 3.0 language.// | ||
| Line 25: | Line 27: | ||
| : //The term stylesheet reflects the fact that one of the important roles of XSLT is to add styling information to an XML source document, by transforming it into a document consisting of XSL formatting objects (see XSL-FO), or into another presentation-oriented format such as HTML, XHTML, or SVG. However, XSLT is used for a wide range of transformation tasks, not exclusively for formatting and presentation applications.// | : //The term stylesheet reflects the fact that one of the important roles of XSLT is to add styling information to an XML source document, by transforming it into a document consisting of XSL formatting objects (see XSL-FO), or into another presentation-oriented format such as HTML, XHTML, or SVG. However, XSLT is used for a wide range of transformation tasks, not exclusively for formatting and presentation applications.// | ||
| - | : //A transformation expressed in XSLT describes rules for transforming input data into output data. The inputs and outputs will all be instances of the XDM data model, described in XDM 3.0. In the simplest and most common case, the input is an XML document referred to as the source tree, and the output is an XML document referred to as the result tree. It is also possible to process multiple source documents, to generate multiple result documents, and to handle formats other than XML. The transformation is achieved by a set of template rules. A template rule associates a pattern, which typically matches nodes in the source document, with a sequence constructor. In many cases, evaluating the sequence constructor will cause new nodes to be constructed, which can be used to produce part of a result tree. The structure of the result trees can be completely different from the structure of the source trees. In constructing a result tree, nodes from the source trees can be filtered and reordered, and arbitrary structure can be added. This mechanism allows a stylesheet to be applicable to a wide class of documents that have similar source tree structures.// | + | : //A transformation expressed in XSLT describes rules for transforming input data into output data. The inputs and outputs will all be instances of the XDM [[dido:public:ra:xapend:xapend.a_glossary:d:dm|data model]], described in XDM 3.0. In the simplest and most common case, the input is an XML document referred to as the source tree, and the output is an XML document referred to as the result tree. It is also possible to process multiple source documents, to generate multiple result documents, and to handle formats other than XML. The transformation is achieved by a set of template rules. A template rule associates a pattern, which typically matches nodes in the source document, with a sequence constructor. In many cases, evaluating the sequence constructor will cause new nodes to be constructed, which can be used to produce part of a result tree. The structure of the result trees can be completely different from the structure of the source trees. In constructing a result tree, nodes from the source trees can be filtered and reordered, and arbitrary structure can be added. This mechanism allows a stylesheet to be applicable to a wide class of documents that have similar source tree structures.// |
| : //Stylesheets have a modular structure; they may contain several packages developed independently of each other, and each package may consist of several stylesheet modules.// | : //Stylesheets have a modular structure; they may contain several packages developed independently of each other, and each package may consist of several stylesheet modules.// | ||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||