XSLT教程：最新规范与代码资源

课程资源

需积分: 5 64 浏览量更新于2024-06-13 收藏 1.96MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

XSLT（Extensible Stylesheet Language Transformations）学习资料代码上传包含了关于XSLT语言的详细介绍，这是W3C（万维网联盟）于1999年11月16日发布的推荐标准，用于转换XML文档。XSLT 1.0版本规定了该语言的语法和语义，旨在使开发者能够将XML数据转换成多种形式，如HTML、文本或其他结构化的输出。这个标准的历史可以追溯到早期草稿阶段，包括1999年8月的Working Draft（草案），以及后续的修订版，如1999年10月、1999年7月、1999年4月和1998年的草案。这些版本反映了技术的发展和标准化过程中的反馈和改进。 XSLT的作者是James Clark，他的邮箱地址为jjc@jclark.com。该规范的版权属于W3C，受MIT、INRIA和Keio等机构的许可协议保护，这意味着在使用XSLT时必须遵守相应的使用规则，包括W3C的版权、商标和文档使用许可协议。 XSLT的核心概念包括模板、模式选择、变量、参数、函数和命名空间等。它通过XPath表达式来定位XML文档中的元素，然后根据模板定义如何转换这些元素。其工作原理是，用户编写XSLT样式表，这个样式表会按照预定义的规则对输入的XML文档进行解析、处理和转换，最终生成所需的输出格式。对于想要深入学习XSLT的读者，推荐访问W3C的官方网站（https://www.w3.org/TR/xslt/）获取最新和详尽的规格说明，同时GitHub上的Issue跟踪系统（https://github.com/w3c/qtspecs/issues）可以查看和报告错误或提供反馈。此外，如果你寻求更丰富的版本，还可以参考历史修订版本，了解技术演进的过程。掌握XSLT对于Web开发人员来说至关重要，特别是在数据处理和内容管理方面，因为它提供了强大的工具来标准化和优化XML数据的呈现。随着XML的广泛应用，XSLT依然是现代软件开发中不可或缺的一部分，尤其是在企业级应用、网站内容管理和数据集成等领域。

资源详情

资源推荐

NOTE:If xsl:apply-imports is used (see [5.6 Overriding Template Rules]), the behavior may

be different from the behavior if the stylesheet had been imported only at the place with

the highest import precedence.

2.7 Embedding Stylesheets

Normally an XSLT stylesheet is a complete XML document with the xsl:stylesheet element as the

document element. However, an XSLT stylesheet may also be embedded in another resource. Two

forms of embedding are possible:

the XSLT stylesheet may be textually embedded in a non-XML resource, or

the xsl:stylesheet element may occur in an XML document other than as the document element.

To facilitate the second form of embedding, the xsl:stylesheet element is allowed to have an ID

attribute that specifies a unique identifier.

NOTE:In order for such an attribute to be used with the XPath id function, it must actually

be declared in the DTD as being an ID.

The following example shows how the xml-stylesheet processing instruction [XML Stylesheet] can be

used to allow a document to contain its own stylesheet. The URI reference uses a relative URI with a

fragment identifier to locate the xsl:stylesheet element:

<?xml-stylesheet type="text/xml" href="#style1"?>

<!DOCTYPE doc SYSTEM "doc.dtd">

<doc>

<head>

<xsl:stylesheet id="style1"

version="1.0"

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

xmlns:fo="http://www.w3.org/1999/XSL/Format">

<xsl:import href="doc.xsl"/>

<xsl:template match="id('foo')">

<fo:block font-weight="bold"><xsl:apply-templates/></fo:block>

</xsl:template>

<xsl:template match="xsl:stylesheet">

</xsl:template>

</xsl:stylesheet>

</head>

<body>

...

</para>

</body>

</doc>

NOTE:A stylesheet that is embedded in the document to which it is to be applied or that

may be included or imported into an stylesheet that is so embedded typically needs to

contain a template rule that specifies that xsl:stylesheet elements are to be ignored.

3 Data Model

The data model used by XSLT is the same as that used by XPath with the additions described in this

section. XSLT operates on source, result and stylesheet documents using the same data model. Any

two XML documents that have the same tree will be treated the same by XSLT.

Processing instructions and comments in the stylesheet are ignored: the stylesheet is treated as if

neither processing instruction nodes nor comment nodes were included in the tree that represents

the stylesheet.

3.1 Root Node Children

The normal restrictions on the children of the root node are relaxed for the result tree. The result tree

may have any sequence of nodes as children that would be possible for an element node. In

particular, it may have text node children, and any number of element node children. When written

out using the XML output method (see [16 Output]), it is possible that a result tree will not be a well-

formed XML document; however, it will always be a well-formed external general parsed entity.

2024/4/30 09:23

XSL Transformations (XSLT)

https://www.w3.org/TR/xslt-10/#section-Creating-the-Result-Tree

11/66

When the source tree is created by parsing a well-formed XML document, the root node of the

source tree will automatically satisfy the normal restrictions of having no text node children and

exactly one element child. When the source tree is created in some other way, for example by using

the DOM, the usual restrictions are relaxed for the source tree as for the result tree.

3.2 Base URI

Every node also has an associated URI called its base URI, which is used for resolving attribute values

that represent relative URIs into absolute URIs. If an element or processing instruction occurs in an

external entity, the base URI of that element or processing instruction is the URI of the external entity;

otherwise, the base URI is the base URI of the document. The base URI of the document node is the

URI of the document entity. The base URI for a text node, a comment node, an attribute node or a

namespace node is the base URI of the parent of the node.

3.3 Unparsed Entities

The root node has a mapping that gives the URI for each unparsed entity declared in the document's

DTD. The URI is generated from the system identifier and public identifier specified in the entity

declaration. The XSLT processor may use the public identifier to generate a URI for the entity instead

of the URI specified in the system identifier. If the XSLT processor does not use the public identifier to

generate the URI, it must use the system identifier; if the system identifier is a relative URI, it must be

resolved into an absolute URI using the URI of the resource containing the entity declaration as the

base URI [RFC2396].

3.4 Whitespace Stripping

After the tree for a source document or stylesheet document has been constructed, but before it is

otherwise processed by XSLT, some text nodes are stripped. A text node is never stripped unless it

contains only whitespace characters. Stripping the text node removes the text node from the tree.

The stripping process takes as input a set of element names for which whitespace must be preserved.

The stripping process is applied to both stylesheets and source documents, but the set of

whitespace-preserving element names is determined differently for stylesheets and for source

documents.

A text node is preserved if any of the following apply:

The element name of the parent of the text node is in the set of whitespace-preserving element

names.

The text node contains at least one non-whitespace character. As in XML, a whitespace character

is #x20, #x9, #xD or #xA.

An ancestor element of the text node has an xml:space attribute with a value of preserve, and no

closer ancestor element has xml:space with a value of default.

Otherwise, the text node is stripped.

The xml:space attributes are not stripped from the tree.

NOTE:This implies that if an xml:space attribute is specified on a literal result element, it will

be included in the result.

For stylesheets, the set of whitespace-preserving element names consists of just xsl:text.

<xsl:strip-space

e l e m e n t s = tokens/>

<xsl:preserve-space

e l e m e n t s = tokens/>

For source documents, the set of whitespace-preserving element names is specified by xsl:strip-space

and xsl:preserve-space top-level elements. These elements each have an elements attribute whose value

2024/4/30 09:23

XSL Transformations (XSLT)

https://www.w3.org/TR/xslt-10/#section-Creating-the-Result-Tree

12/66

is a whitespace-separated list of NameTests. Initially, the set of whitespace-preserving element names
contains all element names. If an element name matches a NameTest in an xsl:strip-space element,
then it is removed from the set of whitespace-preserving element names. If an element name
matches a NameTest in an xsl:preserve-space element, then it is added to the set of whitespace-
preserving element names. An element matches a NameTest if and only if the NameTest would be
true for the element as an XPath node test. Conflicts between matches to xsl:strip-space and
xsl:preserve-space elements are resolved the same way as conflicts between template rules (see [5.5
Conflict Resolution for Template Rules]). Thus, the applicable match for a particular element name
is determined as follows:
First, any match with lower import precedence than another match is ignored.
Next, any match with a NameTest that has a lower default priority than the default priority of the
NameTest of another match is ignored.
It is an error if this leaves more than one match. An XSLT processor may signal the error; if it does not
signal the error, it must recover by choosing, from amongst the matches that are left, the one that
occurs last in the stylesheet.
4 Expressions
XSLT uses the expression language defined by XPath [XPath]. Expressions are used in XSLT for a
variety of purposes including:
selecting nodes for processing;
specifying conditions for different ways of processing a node;
generating text to be inserted in the result tree.
An expression must match the XPath production Expr.
Expressions occur as the value of certain attributes on XSLT-defined elements and within curly braces
in attribute value templates.
In XSLT, an outermost expression (i.e. an expression that is not part of another expression) gets its
context as follows:
the context node comes from the current node
the context position comes from the position of the current node in the current node list; the
first position is 1
the context size comes from the size of the current node list
the variable bindings are the bindings in scope on the element which has the attribute in which
the expression occurs (see [11 Variables and Parameters])
the set of namespace declarations are those in scope on the element which has the attribute in
which the expression occurs; this includes the implicit declaration of the prefix xml required by
the the XML Namespaces Recommendation [XML Names]; the default namespace (as declared
by xmlns) is not part of this set
the function library consists of the core function library together with the additional functions
defined in [12 Additional Functions] and extension functions as described in [14 Extensions]; it
is an error for an expression to include a call to any other function
5 Template Rules
5.1 Processing Model
A list of source nodes is processed to create a result tree fragment. The result tree is constructed by
processing a list containing just the root node. A list of source nodes is processed by appending the
result tree structure created by processing each of the members of the list in order. A node is
2024/4/30 09:23
XSL Transformations (XSLT)
https://www.w3.org/TR/xslt-10/#section-Creating-the-Result-Tree
13/66

processed by finding all the template rules with patterns that match the node, and choosing the best

amongst them; the chosen rule's template is then instantiated with the node as the current node and

with the list of source nodes as the current node list. A template typically contains instructions that

select an additional list of source nodes for processing. The process of matching, instantiation and

selection is continued recursively until no new source nodes are selected for processing.

Implementations are free to process the source document in any way that produces the same result

as if it were processed using this processing model.

5.2 Patterns

Template rules identify the nodes to which they apply by using a pattern. As well as being used in

template rules, patterns are used for numbering (see [7.7 Numbering]) and for declaring keys (see

[12.2 Keys]). A pattern specifies a set of conditions on a node. A node that satisfies the conditions

matches the pattern; a node that does not satisfy the conditions does not match the pattern. The

syntax for patterns is a subset of the syntax for expressions. In particular, location paths that meet

certain restrictions can be used as patterns. An expression that is also a pattern always evaluates to

an object of type node-set. A node matches a pattern if the node is a member of the result of

evaluating the pattern as an expression with respect to some possible context; the possible contexts

are those whose context node is the node being matched or one of its ancestors.

Here are some examples of patterns:

para matches any para element

* matches any element

chapter|appendix matches any chapter element and any appendix element

olist/item matches any item element with an olist parent

appendix//para matches any para element with an appendix ancestor element

/ matches the root node

text() matches any text node

processing-instruction() matches any processing instruction

node() matches any node other than an attribute node and the root node

id("W11") matches the element with unique ID W11

para[1] matches any para element that is the first para child element of its parent

*[position()=1 and self::para] matches any para element that is the first child element of its parent

para[last()=1] matches any para element that is the only para child element of its parent

items/item[position()>1] matches any item element that has a items parent and that is not the first

item child of its parent

item[position() mod 2 = 1] would be true for any item element that is an odd-numbered item child

of its parent.

div[@class="appendix"]//p matches any p element with a div ancestor element that has a class

attribute with value appendix

@class matches any class attribute (

not

any element that has a class attribute)

@* matches any attribute

A pattern must match the grammar for Pattern. A Pattern is a set of location path patterns separated

by |. A location path pattern is a location path whose steps all use only the child or attribute axes.

Although patterns must not use the descendant-or-self axis, patterns may use the // operator as well as

2024/4/30 09:23

XSL Transformations (XSLT)

https://www.w3.org/TR/xslt-10/#section-Creating-the-Result-Tree

14/66

剩余65页未读，继续阅读

李周华

粉丝: 0
资源: 13

XSLT教程：最新规范与代码资源

资料--图片上传代码

资料更新上传程序与代码

写一段使用js格式化xslt语言的代码

C语言实现xslt转换

go语言怎么使用xslt.NewProcessor()

java xslt解析docx

"use_time":{ "bsonType": "date", "title": "起始时间" },怎么改

怎么定义一个XSLT语言

xml xsl xslt 文档

java xslt模板化xml

xslt-processor

写一段使用js格式化xslt语言，类似vscode的格式化

xslt apply-templates

xml和xslt是什么意思

xslt split

java web开发详解–xml+xslt+servlet+jsp深入剖析与实例应用

xslt template 循环

java xslt编译器警告

孙鑫. java web开发详解: xml+xslt+servlet+jsp深入剖析与实例应用[m].北京:电子

XSLT中<xsl:apply-templates>的使用方式

最新资源