XSLT Tutorial
XSLT Tutorial
XSLT Tutorial
XSLT Tutorial
XSL stands for EXtensible Stylesheet Language.
The World Wide Web Consortium (W3C) started to develop XSL because
there was a need for an XML-based style sheet language.
XSLT stands for XSL Transformations. In this tutorial you will learn how
to use XSLT to transform XML documents into other formats, like XHTML.
XSLT References
XSLT Elements
Description of all the XSLT elements from the W3C Recommendation, and information about
browser support.
XSLT Functions
XSLT includes over 100 built-in functions. There are functions for string values, numeric values,
date and time comparison, node and QName manipulation, sequence manipulation, Boolean values,
and more.
Table of Contents
XSL Languages
Defines the sub-languages of XSL: XSLT, XPath and XSL-FO.
XSLT Introduction
An introduction to XSLT. What it is, and what it can do.
XSLT Browsers
Overview of browser support for XSLT.
XSLT Transformation
How XSLT can be used to transform XML documents into XHTML documents.
XSLT Templates
The <xsl:template> element contains rules to apply when a specified node is matched.
1
XSLT <xsl:choose> Element
The <xsl:choose> element is used in conjunction with <xsl:when> and <xsl:otherwise> to express
multiple conditional tests.
XSL Editors
Why you should use an XML editor when you edit your XSL documents.
XSLT Summary
This chapter contains a summary on what you have learned in this tutorial and a recommendation
on what subject you should study next.
XSLT References
XSLT Functions
XSLT includes over 100 built-in functions. There are functions for string values, numeric values,
date and time comparison, node and QName manipulation, sequence manipulation, Boolean values,
and more.
XSL Languages
It started with XSL and ended up with XSLT, XPath, and XSL-FO.
The World Wide Web Consortium (W3C) started to develop XSL because there was a need for an
XML-based Stylesheet Language.
HTML uses predefined tags and the meaning of the tags are well understood.
2
The <table> element in HTML defines a table - and a browser knows how to display it.
Adding styles to HTML elements is simple. Telling a browser to display an element in a special font
or color, is easy with CSS.
XML does not use predefined tags (we can use any tag-names we like), and the meaning of these
tags are not well understood.
A <table> element could mean an HTML table, a piece of furniture, or something else - and a
browser does not know how to display it.
The rest of this tutorial is about XSLT - the language for transforming XML documents.
But you can also study our XPath Tutorial and our XSL-FO Tutorial.
Introduction to XSLT
XSLT is a language for transforming XML documents into XHTML documents or to other
XML documents.
Before you continue you should have a basic understanding of the following:
• HTML / XHTML
• XML / XML Namespaces
• XPath
If you want to study these subjects first, find the tutorials on our Home page.
3
What is XSLT?
XSLT is used to transform an XML document into another XML document, or another type of
document that is recognized by a browser, like HTML and XHTML. Normally XSLT does this by
transforming each XML element into an (X)HTML element.
With XSLT you can add/remove elements and attributes to or from the output file. You can also
rearrange and sort elements, perform tests and make decisions about which elements to hide and
display, and a lot more.
A common way to describe the transformation process is to say that XSLT transforms an XML
source-tree into an XML result-tree.
XSLT uses XPath to find information in an XML document. XPath is used to navigate through
elements and attributes in XML documents.
If you want to study XPath first, please read our XPath Tutorial.
In the transformation process, XSLT uses XPath to define parts of the source document that should
match one or more predefined templates. When a match is found, XSLT will transform the matching
part of the source document into the result document.
To read more about the XSLT activities at W3C, please read our W3C Tutorial.
XSLT Browsers
Nearly all major browsers have support for XML and XSLT.
4
Mozilla Firefox
As of version 1.0.2, Firefox has support for XML and XSLT (and CSS).
Mozilla
Mozilla includes Expat for XML parsing and has support to display XML + CSS. Mozilla also has some
support for Namespaces.
Netscape
As of version 8, Netscape uses the Mozilla engine, and therefore it has the same XML / XSLT
support as Mozilla.
Opera
As of version 9, Opera has support for XML and XSLT (and CSS). Version 8 supports only XML +
CSS.
Internet Explorer
As of version 6, Internet Explorer supports XML, Namespaces, CSS, XSLT, and XPath.
XSLT - Transformation
The root element that declares the document to be an XSL style sheet is <xsl:stylesheet> or
<xsl:transform>.
Note: <xsl:stylesheet> and <xsl:transform> are completely synonymous and either can be used!
The correct way to declare an XSL style sheet according to the W3C XSLT Recommendation is:
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
5
or:
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
To get access to the XSLT elements, attributes and features we must declare the XSLT namespace
at the top of the document.
Viewing XML Files in Firefox and Internet Explorer: Open the XML file (typically by clicking on
a link) - The XML document will be displayed with color-coded root and child elements. A plus (+) or
minus sign (-) to the left of the elements can be clicked to expand or collapse the element
structure. To view the raw XML source (without the + and - signs), select "View Page Source" or
"View Source" from the browser menu.
Viewing XML Files in Netscape 6: Open the XML file, then right-click in XML file and select "View
Page Source". The XML document will then be displayed with color-coded root and child elements.
Viewing XML Files in Opera 7: Open the XML file, then right-click in XML file and select "Frame" /
"View Source". The XML document will be displayed as plain text.
View "cdcatalog.xml"
Then you create an XSL Style Sheet ("cdcatalog.xsl") with a transformation template:
6
<body>
<h2>My CD Collection</h2>
<table border="1">
<tr bgcolor="#9acd32">
<th align="left">Title</th>
<th align="left">Artist</th>
</tr>
<xsl:for-each select="catalog/cd">
<tr>
<td><xsl:value-of select="title"/></td>
<td><xsl:value-of select="artist"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
View "cdcatalog.xsl"
Add the XSL style sheet reference to your XML document ("cdcatalog.xml"):
If you have an XSLT compliant browser it will nicely transform your XML into XHTML.
The details of the example above will be explained in the next chapters.
An XSL style sheet consists of one or more set of rules that are called templates.
7
Each template contains rules to apply when a specified node is matched.
The match attribute is used to associate a template with an XML element. The match attribute can
also be used to define a template for the entire XML document. The value of the match attribute is
an XPath expression (i.e. match="/" defines the whole document).
Ok, let's look at a simplified version of the XSL file from the previous chapter:
Since an XSL style sheet is an XML document itself, it always begins with the XML declaration: <?
xml version="1.0" encoding="ISO-8859-1"?>.
The next element, <xsl:stylesheet>, defines that this document is an XSLT style sheet document
(along with the version number and XSLT namespace attributes).
The <xsl:template> element defines a template. The match="/" attribute associates the
template with the root of the XML source document.
The content inside the <xsl:template> element defines some HTML to write to the output.
The last two lines define the end of the template and the end of the style sheet.
My CD Collection
Title Artist
. .
8
View the XML file, View the XSL file, and View the result
The result from this example was a little disappointing, because no data was copied from the XML
document to the output.
In the next chapter you will learn how to use the <xsl:value-of> element to select values from the
XML elements.
The <xsl:value-of> element can be used to extract the value of an XML element and add it to the
output stream of the transformation:
Note: The value of the select attribute is an XPath expression. An XPath expression works like
navigating a file system; where a forward slash (/) selects subdirectories.
My CD Collection
Title Artist
Empire Burlesque Bob Dylan
View the XML file, View the XSL file, and View the result
9
The result from this example was also a little disappointing, because only one line of data was
copied from the XML document to the output.
In the next chapter you will learn how to use the <xsl:for-each> element to loop through the XML
elements, and display all of the records.
The XSL <xsl:for-each> element can be used to select every XML element of a specified node-set:
Note: The value of the select attribute is an XPath expression. An XPath expression works like
navigating a file system; where a forward slash (/) selects subdirectories.
My CD Collection
Title Artist
Empire Burlesque Bob Dylan
Hide your heart Bonnie Tyler
Greatest Hits Dolly Parton
10
Still got the blues Gary More
Eros Eros Ramazzotti
One night only Bee Gees
Sylvias Mother Dr.Hook
Maggie May Rod Stewart
Romanza Andrea Bocelli
When a man loves a woman Percy Sledge
Black angel Savage Rose
1999 Grammy Nominees Many
For the good times Kenny Rogers
Big Willie style Will Smith
Tupelo Honey Van Morrison
Soulsville Jorn Hoel
The very best of Cat Stevens
Stop Sam Brown
Bridge of Spies T`Pau
Private Dancer Tina Turner
Midt om natten Kim Larsen
Pavarotti Gala Concert Luciano Pavarotti
The dock of the bay Otis Redding
Picture book Simply Red
Red The Communards
Unchain my heart Joe Cocker
View the XML file, View the XSL file, and View the result
We can also filter the output from the XML file by adding a criterion to the select attribute in the
<xsl:for-each> element.
• = (equal)
• != (not equal)
• < less than
• > greater than
11
<body>
<h2>My CD Collection</h2>
<table border="1">
<tr bgcolor="#9acd32">
<th>Title</th>
<th>Artist</th>
</tr>
<xsl:for-each select="catalog/cd[artist='Bob
Dylan']">
<tr>
<td><xsl:value-of select="title"/></td>
<td><xsl:value-of select="artist"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
My CD Collection
Title Artist
Empire Burlesque Bob Dylan
View the XML file, View the XSL file, View the result
To sort the output, simply add an <xsl:sort> element inside the <xsl:for-each> element in the XSL
file:
12
<xsl:sort select="artist"/>
<tr>
<td><xsl:value-of select="title"/></td>
<td><xsl:value-of select="artist"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
Note: The select attribute indicates what XML element to sort on.
My CD Collection
Title Artist
Romanza Andrea Bocelli
One night only Bee Gees
Empire Burlesque Bob Dylan
Hide your heart Bonnie Tyler
The very best of Cat Stevens
Greatest Hits Dolly Parton
Sylvias Mother Dr.Hook
Eros Eros Ramazzotti
Still got the blues Gary Moore
Unchain my heart Joe Cocker
Soulsville Jorn Hoel
For the good times Kenny Rogers
Midt om natten Kim Larsen
Pavarotti Gala Concert Luciano Pavarotti
1999 Grammy Nominees Many
The dock of the bay Otis Redding
When a man loves a woman Percy Sledge
Maggie May Rod Stewart
Stop Sam Brown
Black angel Savage Rose
Picture book Simply Red
Bridge of Spies T`Pau
Red The Communards
Private Dancer Tina Turner
Tupelo Honey Van Morrison
Big Willie style Will Smith
View the XML file, View the XSL file, and View the result
13
XSLT <xsl:if> Element
The <xsl:if> element is used to put a conditional test against the content of the XML file.
To put a conditional if test against the content of the XML file, add an <xsl:if> element to the XSL
document.
Syntax
<xsl:if test="expression">
...
...some output if the expression is true...
...
</xsl:if>
To add a conditional test, add the <xsl:if> element inside the <xsl:for-each> element in the XSL
file:
Note: The value of the required test attribute contains the expression to be evaluated.
The code above will only output the title and artist elements of the CDs that has a price that is
higher than 10.
14
The result of the transformation above will look like this:
My CD Collection
Title Artist
Empire Burlesque Bob Dylan
Still got the blues Gary Moore
One night only Bee Gees
Romanza Andrea Bocelli
Black Angel Savage Rose
1999 Grammy Nominees Many
View the XML file, View the XSL file, and View the result
Syntax
<xsl:choose>
<xsl:when test="expression">
... some output ...
</xsl:when>
<xsl:otherwise>
... some output ....
</xsl:otherwise>
</xsl:choose>
To insert a multiple conditional test against the XML file, add the <xsl:choose>, <xsl:when>, and
<xsl:otherwise> elements to the XSL file:
15
</tr>
<xsl:for-each select="catalog/cd">
<tr>
<td><xsl:value-of select="title"/></td>
<xsl:choose>
<xsl:when test="price > 10">
<td bgcolor="#ff00ff">
<xsl:value-of select="artist"/></td>
</xsl:when>
<xsl:otherwise>
<td><xsl:value-of select="artist"/></td>
</xsl:otherwise>
</xsl:choose>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
The code above will add a pink background-color to the "Artist" column WHEN the price of the CD is
higher than 10.
My CD Collection
Title Artist
Empire Burlesque Bob Dylan
Hide your heart Bonnie Tyler
Greatest Hits Dolly Parton
Still got the blues Gary Moore
Eros Eros Ramazzotti
One night only Bee Gees
Sylvias Mother Dr.Hook
Maggie May Rod Stewart
Romanza Andrea Bocelli
When a man loves a woman Percy Sledge
Black angel Savage Rose
1999 Grammy Nominees Many
For the good times Kenny Rogers
Big Willie style Will Smith
Tupelo Honey Van Morrison
Soulsville Jorn Hoel
The very best of Cat Stevens
Stop Sam Brown
Bridge of Spies T`Pau
Private Dancer Tina Turner
16
Midt om natten Kim Larsen
Pavarotti Gala Concert Luciano Pavarotti
The dock of the bay Otis Redding
Picture book Simply Red
Red The Communards
Unchain my heart Joe Cocker
View the XML file, View the XSL file, and View the result
Another Example
The code above will add a pink background color to the "Artist" column WHEN the price of the CD is
higher than 10, and a grey background-color WHEN the price of the CD is higher than 9 and lower
or equal to 10.
17
The result of the transformation will look like this:
My CD Collection
Title Artist
Empire Burlesque Bob Dylan
Hide your heart Bonnie Tyler
Greatest Hits Dolly Parton
Still got the blues Gary Moore
Eros Eros Ramazzotti
One night only Bee Gees
Sylvias Mother Dr.Hook
Maggie May Rod Stewart
Romanza Andrea Bocelli
When a man loves a woman Percy Sledge
Black angel Savage Rose
1999 Grammy Nominees Many
For the good times Kenny Rogers
Big Willie style Will Smith
Tupelo Honey Van Morrison
Soulsville Jorn Hoel
The very best of Cat Stevens
Stop Sam Brown
Bridge of Spies T`Pau
Private Dancer Tina Turner
Midt om natten Kim Larsen
Pavarotti Gala Concert Luciano Pavarotti
The dock of the bay Otis Redding
Picture book Simply Red
Red The Communards
Unchain my heart Joe Cocker
View the XML file, View the XSL file, and View the result
The <xsl:apply-templates> element applies a template to the current element or to the current
element's child nodes.
18
If we add a select attribute to the <xsl:apply-templates> element it will process only the child
element that matches the value of the attribute. We can use the select attribute to specify the order
in which the child nodes are processed.
My CD Collection
Title: Eros
Artist: Eros Ramazzotti
19
Title: Sylvias Mother
Artist: Dr.Hook
Title: Romanza
Artist: Andrea Bocelli
Title: Soulsville
Artist: Jorn Hoel
Title: Stop
Artist: Sam Brown
Title: Red
Artist: The Communards
20
Title: Unchain my heart
Artist: Joe Cocker
View the XML file, View the XSL file, and View the result.
XSLT ADVANCED
If your browser supports it, XSLT can be used to transform the document to XHTML in
your browser.
A JavaScript Solution
In the previous chapters we have explained how XSLT can be used to transform a document from
XML to XHTML. We did this by adding an XSL style sheet to the XML file and let the browser do the
transformation.
Even if this works fine, it is not always desirable to include a style sheet reference in an XML file
(e.g. it will not work in a non XSLT aware browser.)
• do browser-specific testing
• use different style sheets according to browser and user needs
That is the beauty of XSLT! One of the design goals for XSLT was to make it possible to transform
data from one format to another, supporting different browsers and different user needs.
XSLT transformation on the client side is bound to be a major part of the browsers work tasks in the
future, as we will see a growth in the specialized browser market (Braille, aural browsers, Web
printers, handheld devices, etc.)
Look at the XML document that you have seen in the previous chapters:
21
.
</catalog>
Notice that the XML file does not have a reference to the XSL file.
IMPORTANT: The above sentence indicates that an XML file could be transformed using many
different XSL style sheets.
Here is the source code needed to transform the XML file to XHTML on the client:
<html>
<body>
<script type="text/javascript">
// Load XML
var xml = new ActiveXObject("Microsoft.XMLDOM")
xml.async = false
xml.load("cdcatalog.xml")
// Load XSL
var xsl = new ActiveXObject("Microsoft.XMLDOM")
xsl.async = false
xsl.load("cdcatalog.xsl")
// Transform
document.write(xml.transformNode(xsl))
22
</script>
</body>
</html>
Tip: If you don't know how to write JavaScript, you can study our JavaScript tutorial.
The first block of code creates an instance of the Microsoft XML parser (XMLDOM), and loads the
XML file into memory. The second block of code creates another instance of the parser and loads
the XSL file into memory. The last line of code transforms the XML document using the XSL
document, and displays the result as XHTML in your browser. Nice!
Since not all browsers support XSLT, one solution is to transform the XML to XHTML on
the server.
To make XML data available to all kind of browsers, we must transform the XML document on the
SERVER and send it as XHTML back to the browser.
That's another beauty of XSLT. One of the design goals for XSLT was to make it possible to
transform data from one format to another on a server, returning readable data to all kinds of
browsers.
Look at the XML document that you have seen in the previous chapters:
23
View the XML file.
Notice that the XML file does not have a reference to the XSL file.
IMPORTANT: The above sentence indicates that an XML file could be transformed using many
different XSL style sheets.
Here is the ASP source code needed to transform the XML file to XHTML on the server:
<%
'Load XML
set xml = Server.CreateObject("Microsoft.XMLDOM")
xml.async = false
xml.load(Server.MapPath("cdcatalog.xml"))
'Load XSL
set xsl = Server.CreateObject("Microsoft.XMLDOM")
xsl.async = false
xsl.load(Server.MapPath("cdcatalog.xsl"))
'Transform file
Response.Write(xml.transformNode(xsl))
%>
Tip: If you don't know how to write ASP, you can study our ASP tutorial.
24
The first block of code creates an instance of the Microsoft XML parser (XMLDOM), and loads the
XML file into memory. The second block of code creates another instance of the parser and loads
the XSL file into memory. The last line of code transforms the XML document using the XSL
document, and sends the result as XHTML to your browser. Nice!
Now, we will show how to open, edit, and save an XML file that is stored on the server.
We will use XSL to transform the XML document into an HTML form. The values of the XML elements
will be written to HTML input fields in an HTML form. The HTML form is editable. After editing the
data, the data is going to be submitted back to the server and the XML file will be updated (this part
is done with ASP).
25
<xsl:for-each select="tool/field">
<tr>
<td>
<xsl:value-of select="@id"/>
</td>
<td>
<input type="text">
<xsl:attribute name="id">
<xsl:value-of select="@id" />
</xsl:attribute>
<xsl:attribute name="name">
<xsl:value-of select="@id" />
</xsl:attribute>
<xsl:attribute name="value">
<xsl:value-of select="value" />
</xsl:attribute>
</input>
</td>
</tr>
</xsl:for-each>
</table>
<br />
<input type="submit" id="btn_sub" name="btn_sub" value="Submit" />
<input type="reset" id="btn_res" name="btn_res" value="Reset" />
</form>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
The XSL file above loops through the elements in the XML file and creates one input field for each
XML "field" element. The value of the XML "field" element's "id" attribute is added to both the "id"
and "name" attributes of each HTML input field. The value of each XML "value" element is added to
the "value" attribute of each HTML input field. The result is an editable HTML form that contains the
values from the XML file.
Then, we have a second style sheet: "tool_updated.xsl". This is the XSL file that will be used to
display the updated XML data. This style sheet will not result in an editable HTML form, but a static
HTML table:
26
</html>
</xsl:template>
</xsl:stylesheet>
The HTML form in the "tool.xsl" file above has an action attribute with a value of "edittool.asp".
The "edittool.asp" page contains two functions: The loadFile() function loads and transforms the
XML file for display and the updateFile() function applies the changes to the XML file:
<%
function loadFile(xmlfile,xslfile)
Dim xmlDoc,xslDoc
'Load XML file
set xmlDoc = Server.CreateObject("Microsoft.XMLDOM")
xmlDoc.async = false
xmlDoc.load(xmlfile)
'Load XSL file
set xslDoc = Server.CreateObject("Microsoft.XMLDOM")
xslDoc.async = false
xslDoc.load(xslfile)
'Transform file
Response.Write(xmlDoc.transformNode(xslDoc))
end function
function updateFile(xmlfile)
Dim xmlDoc,rootEl,f
Dim i
'Load XML file
set xmlDoc = Server.CreateObject("Microsoft.XMLDOM")
xmlDoc.async = false
xmlDoc.load(xmlfile)
'Set the rootEl variable equal to the root element
Set rootEl = xmlDoc.documentElement
'Loop through the form collection
for i = 1 To Request.Form.Count
'Eliminate button elements in the form
if instr(1,Request.Form.Key(i),"btn_")=0 then
'The selectSingleNode method queries the XML file for a
'single node that matches a query. This query requests
'the value element that is the child of a field element
'that has an id attribute which matches the current key
'value in the Form Collection. When there is a match -
'set the text property equal to the value of the current
'field in the Form Collection.
set f = rootEl.selectSingleNode("field[@id='" & _
Request.Form.Key(i) & "']/value")
f.Text = Request.Form(i)
end if
next
'Save the modified XML file
xmlDoc.save xmlfile
'Release all object references
set xmlDoc=nothing
set rootEl=nothing
27
set f=nothing
'Load the modified XML file with a style sheet that
'allows the client to see the edited information
loadFile xmlfile,server.MapPath("tool_updated.xsl")
end function
'If the form has been submitted update the
'XML file and display result - if not,
'transform the XML file for editing
if Request.Form("btn_sub")="" then
loadFile server.MapPath("tool.xml"),server.MapPath("tool.xsl")
else
updateFile server.MapPath("tool.xml")
end if
%>
Tip: If you don't know how to write ASP, you can study our ASP tutorial.
Note: We are doing the transformation and applying the changes to the XML file on the server. This
is a cross-browser solution. The client will only get HTML back from the server - which will work in
any browser.
XML Editors
If you are serious about XML, you will benefit from using a professional XML Editor.
XML is Text-based
One great thing about XML is that XML files can be created and edited using a simple text-editor like
Notepad.
However, when you start working with XML, you will soon find that it is better to edit XML
documents using a professional XML editor.
Many web developers use Notepad to edit both HTML and XML documents because Notepad is
included with the most common OS and it is simple to use. Personally I often use Notepad for quick
editing of simple HTML, CSS, and XML files.
But, if you use Notepad for XML editing, you will soon run into problems.
Notepad does not know that you are writing XML, so it will not be able to assist you.
Today XML is an important technology, and development projects use XML-based technologies like:
28
• XML Schema to define XML structures and data types
• XSLT to transform XML data
• SOAP to exchange XML data between applications
• WSDL to describe web services
• RDF to describe web resources
• XPath and XQuery to access XML data
• SMIL to define graphics
To be able to write error-free XML documents, you will need an intelligent XML editor!
XML Editors
Professional XML editors will help you to write error-free XML documents, validate your XML against
a DTD or a schema, and force you to stick to a valid XML structure.
Altova® XMLSpy®
At W3Schools we have been using XMLSpy for many years. XMLSpy is our favorite XML editor.
These are some of the features we especially like:
• Easy to use
• Automatic tag completion
• Context-sensitive entry helpers
• Automatic well-formedness checking
• Syntax coloring and pretty printing
• Built in DTD and/or XML Schema-based validation
• Easy switching between text view and grid view
• Built in graphical XML Schema editor
• Powerful conversion utilities
• Database import and export
• Built in templates for many XML document types
• Built in XPath 1.0/2.0 analyzer
• XSLT 1.0/2.0 editor, profiler, and debugger
• XQuery editor, profiler, and debugger
• SOAP client and debugger
• Graphical WSDL editor
• Powerful project management capabilities
• Code generation in Java, C++, and C#
29
You Have Learned XSLT, Now What?
XSLT Summary
This tutorial has taught you how to use XSLT to transform XML documents into other formats, like
XHTML.
You have learned how to add/remove elements and attributes to or from the output file.
You have also learned how to rearrange and sort elements, perform tests and make decisions about
which elements to hide and display.
XSL includes 3 languages: XSLT, XPath and XSL-FO, so the next step is to learn about XPath and
XSL-FO.
XPath
XPath is a major element in the W3C's XSL standard. An understanding of XPath is fundamental for
advanced use of XML.
Without any XPath knowledge, you will not be able to create XSLT documents.
If you want to learn more about the XPath, please visit our XPath tutorial.
XSL-FO
XSL-FO describes the formatting of XML data for output to screen, paper or other media.
XSL-FO documents are XML files with information about the output layout and output content.
If you want to learn more about XSL-FO, please visit our XSL-FO tutorial.
The XSLT elements from the W3C Recommendation (XSLT Version 1.0).
XSLT Elements
The links in the "Element" column point to attributes and more useful information about each
specific element.
30
• N: indicates the earliest version of Netscape that supports the tag
• IE: indicates the earliest version of Internet Explorer that supports the tag
Note: Elements supported in IE 5 may have NON-standard behavior, because IE 5 was released
before XSLT became an official W3C Recommendation.
Element Description IE N
apply-imports Applies a template rule from an imported style sheet 6.0
apply-templates Applies a template rule to the current element or to 5.0 6.0
the current element's child nodes
attribute Adds an attribute 5.0 6.0
attribute-set Defines a named set of attributes 6.0 6.0
call-template Calls a named template 6.0 6.0
choose Used in conjunction with <when> and <otherwise> to 5.0 6.0
express multiple conditional tests
comment Creates a comment node in the result tree 5.0 6.0
copy Creates a copy of the current node (without child 5.0 6.0
nodes and attributes)
copy-of Creates a copy of the current node (with child nodes 6.0 6.0
and attributes)
decimal-format Defines the characters and symbols to be used when 6.0
converting numbers into strings, with the format-
number() function
element Creates an element node in the output document 5.0 6.0
fallback Specifies an alternate code to run if the processor 6.0
does not support an XSLT element
for-each Loops through each node in a specified node set 5.0 6.0
if Contains a template that will be applied only if a 5.0 6.0
specified condition is true
import Imports the contents of one style sheet into another. 6.0 6.0
Note: An imported style sheet has lower precedence
than the importing style sheet
include Includes the contents of one style sheet into another. 6.0 6.0
Note: An included style sheet has the same
precedence as the including style sheet
key Declares a named key that can be used in the style 6.0 6.0
sheet with the key() function
message Writes a message to the output (used to report errors) 6.0 6.0
namespace-alias Replaces a namespace in the style sheet to a different 6.0
namespace in the output
number Determines the integer position of the current node 6.0 6.0
and formats a number
otherwise Specifies a default action for the <choose> element 5.0 6.0
output Defines the format of the output document 6.0 6.0
param Declares a local or global parameter 6.0 6.0
preserve-space Defines the elements for which white space should be 6.0 6.0
preserved
processing-instruction Writes a processing instruction to the output 5.0 6.0
sort Sorts the output 6.0 6.0
strip-space Defines the elements for which white space should be 6.0 6.0
removed
stylesheet Defines the root element of a style sheet 5.0 6.0
template Rules to apply when a specified node is matched 5.0 6.0
31
text Writes literal text to the output 5.0 6.0
transform Defines the root element of a style sheet 6.0 6.0
value-of Extracts the value of a selected node 5.0 6.0
variable Declares a local or global variable 6.0 6.0
when Specifies an action for the <choose> element 5.0 6.0
with-param Defines the value of a parameter to be passed into a 6.0 6.0
template
XSLT Functions
XQuery 1.0, XPath 2.0, and XSLT 2.0 share the same functions library.
XSLT Functions
XSLT includes over 100 built-in functions. There are functions for string values, numeric values,
date and time comparison, node and QName manipulation, sequence manipulation, Boolean values,
and more.
Tip: Functions are often called with the fn: prefix, such as fn:string(). However, since fn: is the
default prefix of the namespace, the function names do not need to be prefixed when called.
The reference of all the built-in XSLT 2.0 functions is located in our XPath tutorial.
Name Description
current() Returns the current node
document() Used to access the nodes in an external XML document
element-available() Tests whether the element specified is supported by the XSLT processor
format-number() Converts a number into a string
function-available() Tests whether the function specified is supported by the XSLT processor
generate-id() Returns a string value that uniquely identifies a specified node
key() Returns a node-set using the index specified by an <xsl:key> element
system-property() Returns the value of the system properties
unparsed-entity-uri() Returns the URI of an unparsed entity
32