Coordinates	51°40′43″N33°54′41″N
name	XSLT
extension	.xsl, .xslt
mime	application/xslt+xml
owner	World Wide Web Consortium
screenshot
genre	Stylesheet language
extendedfrom	XML
standard	1.0 (Recommendation),2.0 (Recommendation) }}

title	XSL Transformations
status	Published
year started	1997
editors	James Clark (1.0), Michael Kay (2.0)
base standards	XML
related standards	XSL, XSL-FO, XPath
abbreviation	XSLT
domain	XML transformation
website	2.0 }}

XSLT (Extensible Stylesheet Language Transformations) is a declarative, XML-based language used for the transformation of XML documents. The original document is not changed; rather, a new document is created based on the content of an existing one. The new document may be serialized (output) by the processor in standard XML syntax or in another format, such as HTML or plain text. XSLT is most often used to convert data between different XML schemas or to convert XML data into web pages or PDF documents.

Application

Applications often use XSLT to convert XML data into HTML or XHTML documents for display as a web page. The transformation may happen dynamically either on a client or on a server, or it may be done as part of the publishing process. It is also used to create output for printing or direct video display, typically by transforming the original XML into XSL Formatting Objects to create formatted output which can then be converted to a variety of formats, including PDF, PostScript and PNG. XSLT can also translate XML messages between different XML schemas, or make changes to documents within the scope of a single schema, for example by removing the parts of a message that are not needed.

Origins

XSLT is developed by the World Wide Web Consortium (W3C). The most recent version is XSLT 2.0, which reached W3C recommendation status on 23 January 2007. As of 2010, however, XSLT 1.0 is still widely used, as there are no products that support XSLT 2.0 running in the browser, nor on some important server environments such as LAMP.

Originally, XSLT was part of the W3C's Extensible Stylesheet Language (XSL) development effort of 1998–1999, a project that also produced XSL Formatting Objects and the XML Path Language, XPath. The editor of the first version was James Clark. XSLT 1.0 was published as a Recommendation by the W3C on 16 November 1999. After an abortive attempt to create a version 1.1 in 2001, the XSL working group joined forces with the XQuery working group to create XPath 2.0, with a richer data model and type system based on XML Schema. XSLT 2.0, developed under the editorship of Michael Kay, was built on this foundation in 2002–2006.

As a language, XSLT is influenced by functional languages, and by text-based pattern matching languages in the tradition of SNOBOL and awk. Its most direct predecessor was ISO DSSSL, a language that performed the same function for full SGML that XSLT performs for XML (Some members of the standards committee that developed XSLT, including James Clark, had previously worked on DSSSL.) Unlike DSSSL, however, XSLT code uses the syntax of its target language, XML, which means that it can also be viewed as a Turing-complete template processor.

Most of this article is applicable to both XSLT versions; any differences are noted in the text.

Concept

Overview

The XSLT processing model involves:

one or more XML ''source'' documents;

one or more XSLT ''stylesheet'' modules;

the XSLT template processing engine (the ''processor''); and

one or more ''result'' documents.

The XSLT processor ordinarily takes two input documents—an XML source document, and an XSLT stylesheet—and produces an output document. The XSLT stylesheet contains a collection of ''template rules'': ''instructions'' and other directives that guide the processor in the production of the output document.

Template rule processing

The XSLT language is declarative: rather than listing an imperative sequence of actions to perform in a stateful environment, template rules only define how to handle a node matching a particular XPath-like ''pattern'', if the processor should happen to encounter one, and the contents of the templates effectively comprise functional expressions that directly represent their ''evaluated'' form: the ''result tree'', which is the basis of the processor's output.

The processor follows a fixed algorithm: assuming a stylesheet has already been read and prepared, the processor builds a ''source tree'' from the input XML document. It then starts by processing the source tree's root node, finding in the stylesheet the best-matching template for that node, and evaluating the template's contents. Instructions in each template generally direct the processor to either create nodes in the result tree, or process more nodes in the source tree in the same way as the root node. Output is derived from the result tree.

Processor implementations

XSLT processor implementations fall into two main categories: client-side and server-side.

Client-side XSLT adoption has been slow due to widespread deployment of older (or alternative) browsers without XSLT support. For similar reasons, adoption of XSLT 2.0 in such environments remains limited. (See Comparison of layout engines (XML)#XSL technologies).

Nevertheless, early adopters included Microsoft Internet Explorer 6 (since 2001) and Netscape 7 (since 2002). Earlier still, Internet Explorer 5 supported XSLT’s draft specification since 1999 or earlier, although it was incompatible with the final W3C specification. Netscape 6 included partial support since 2000.

Server-side XSLT processors (a somewhat misleading term, as they don’t require a server to function; the name is intended to contrast with “client-side”) exist as both standalone products and components of other software. This includes web browsers, application servers, frameworks (such as Java and .NET), or even operating systems. For example, Windows XP’s MSXML3 library includes an XSLT 1.0 processor. The GNOME desktop environment 2 includes libxslt, an open source implementation with complete support for the XSLT 1.0 specification. The libxslt library is also used by other software, such as WebKit. Other examples include Apache’s Xalan and Saxon XSLT (which supports XSLT 2.0 as well).

Performance

XSLT processor performance has steadily improved as the technology has matured, although the very first processor, James Clark's xt, was unbeaten for several years.

Most early XSLT processors were interpreters. More recently, code generation is increasingly common, using portable intermediate languages (such as Java bytecode or .NET Common Intermediate Language) as the target. However, even the interpretive products generally offer separate analysis and execution phases, allowing an optimized expression tree to be created in memory and reused to perform multiple transformations. This gives substantial performance benefits in online publishing applications, where the same transformation is applied many times per second to different source documents. This separation is reflected in the design of XSLT processing APIs (such as JAXP).

Early XSLT processors had very few optimizations. Stylesheet documents were read into Document Object Models and the processor would act on them directly. XPath engines were also not optimized. Increasingly, however, XSLT processors use optimization techniques found in functional programming languages and database query languages, such as static rewriting of an expression tree (e.g., to move calculations out of loops), and lazy pipelined evaluation to reduce the memory footprint of intermediate results (and allow "early exit" when the processor can evaluate an expression such as following-sibling::*[1] without a complete evaluation of all subexpressions). Many processors also use tree representations that are significantly more efficient (in both space and time) than general-purpose DOM implementations.

XSLT and Streaming

XSLT 1.0 and XSLT 2.0 were all designed to allow XML Streaming of the output of the processing. It means that you had to read the whole input in memory before doing any processing of the XML. This behavior is particularly useful to certify "stability" on the document.

Future XSLT 3.0 implementation will also allow to stream on the input. It will allow implementation to have low latency between the input and the output. It is especially important when transformation are chained together in XML Pipelines, for example in XProc.

XSLT and XPath

XSLT relies upon the W3C's XPath language for identifying subsets of the source document tree, as well as for performing calculations. XPath also provides a range of functions, which XSLT itself further augments. This reliance upon XPath adds a great deal of power and flexibility to XSLT.

XSLT 1.0 uses XPath 1.0. Similarly, XSLT 2.0 relies on XPath 2.0; both specifications were published on the same date.

XSLT and XQuery compared

XSLT capabilities overlap with XQuery, which was initially conceived as a query language for large collections of XML documents.

The XSLT 2.0 and XQuery 1.0 standards were developed by separate working groups within W3C, working together to ensure a common approach where appropriate. They share the same data model, type system, and function library, and both include XPath 2.0 as a sublanguage.

The two languages, however, are rooted in different traditions and serve the needs of different communities. XSLT was primarily conceived as a stylesheet language whose primary goal was to render XML for the human reader on screen, on the web (as web template language), or on paper. XQuery was primarily conceived as a database query language in the tradition of SQL.

Because the two languages originate in different communities, XSLT is stronger in its handling of narrative documents with more flexible structure, while XQuery is stronger in its data handling, for example when performing relational joins.

XSLT media types

As of 2009, there is no MIME/Internet media type registered for XSLT.

The XSLT 1.0 Recommendation (1999) says "The MIME media types text/xml and application/xml should be used for XSLT stylesheets. It is possible that a media type will be registered specifically for XSLT stylesheets; if and when it is, that media type may also be used." It goes on to use text/xml in an example of how to embed a stylesheet with the xml-stylesheet processing instruction.

RFC 3023 points out potential technical problems with text/* types in general, and proposes application/xslt+xml as an ideal media type for XSLT. The XSLT 2.0 Recommendation (January 2007) includes a formal application to register this media type. However, at the time of writing (January 2009) the process of registration has not yet been completed, and RFC 3023 warns that "... this media type should not be used until such registration has been completed."

Pre-1.0 working drafts of XSLT used text/xsl in their embedding examples, and this type was implemented and continues to be promoted by Microsoft in Internet Explorer and MSXML. It is also widely recognized in the xml-stylesheet processing instruction by other browsers. In practice, therefore, users wanting to control transformation in the browser using this processing instruction are obliged to use this unregistered media type.

XSLT examples

Sample of incoming XML document John Smith Morka Ismincius

Example 1 (transforming XML to XML)

This XSLT stylesheet provides templates to transform the XML document:

Its evaluation results in a new XML document, having another structure:

John Morka

Example 2 (transforming XML to XHTML)

Processing the following example XSLT file

Persons

,

with the XML input file shown above results in the following XHTML (whitespace has been adjusted here for clarity):

Persons

• Ismincius, Morka
• Smith, John

This XHTML generates the output below when rendered in a web browser.

In order for a web browser to be able automatically to apply an XSL transformation to an XML document on display, an XML stylesheet processing instruction can be inserted into XML. So, for example, if the stylesheet in Example 2 above were available as "example2.xsl", the following instruction could be added to the original incoming XML:

(In this example, text/xsl is technically incorrect according to the W3C specifications, but it is the only media type that is widely supported across current (2009) browsers.)

See also

XProc - a W3C Standard pipeline language which can be used to combine XSLT transformations together with other operations like XQuery, XInclude or HTTP requests

XSLT elements - a list of some commonly used XSLT structures

XML transformation language - any computer language designed specifically to transform an ''input'' XML document into an ''output'' XML document that satisfies some specific goal

Extensible Stylesheet Language - a family of languages of which XSLT is a member

XQuery and XSLT compared

XSL formatting objects or ''XSL-FO'' - An XML-based language for documents, usually generated by transforming source documents with XSLT, consisting of objects used to create formatted output

Identity transform - a starting point for filter chains that add or remove data elements from XML trees in a transformation pipeline

Apache Cocoon - a Java-based framework for processing data with XSLT and other transformers.

Context Framework - a Java-based web framework using XSLT as sole templating language.

Omnimark - another structured text processing language (and a proprietary software)

Xs3p - is an XSLT stylesheet that generates XHTML documentation from XML Schema Definition language (XSD) schema.

References

Further reading

''XSLT'' by Doug Tidwell, published by O’Reilly (ISBN 0-596-00053-7)

''XSLT Cookbook'' by Sal Mangano, published by O’Reilly (ISBN 0-596-00974-7)

''XSLT 2.0 Programmer's Reference'' by Michael Kay (ISBN 0-764-56909-0)

''XSLT 2.0 and XPath 2.0 Programmer's Reference'' by Michael Kay (ISBN 978-0-470-19274-0)

''XSLT 2.0 Web Development'' by Dmitry Kirsanov (ISBN 0-13-140635-3)

''XSL Companion, 2nd Edition'' by Neil Bradley, published by Addison-Wesley (ISBN 0-201-77083-0)

''XSLT and XPath on the Edge (Unlimited Edition)'' by Jeni Tennison, published by Hungry Minds Inc, U.S. (ISBN 0-7645-4776-3)

''XSLT & XPath, A Guide to XML Transformations'' by John Robert Gardner and Zarella Rendon, published by Prentice-Hall (ISBN 0-13-040446-2)

''XSL-FO'' by Dave Pawson, published by O'Reilly (ISBN 978-0-596-00355-5)

External links

; Documentation

XSLT 1.0 W3C Recommendation

XSLT 2.0 W3C Recommendation

XSLT Frequently Asked Questions

Zvon XSLT 1.0 Reference

XSL Concepts and Practical Use by Norman Walsh

What kind of language is XSLT?

XSLT and Scripting Languages

schema-aware.com - examples of schema-aware XSLT

XSLT - MDC Docs by Mozilla Developer Network

; Tutorials

Tutorial from developerWorks by IBM (1 hour)

Zvon XSLT Tutorial

Quick tutorial

W3Schools XSLT Tutorial

; Mailing lists

The XSLT mailing list hosted by Mulberrytech

; XSLT code libraries

EXSLT is a widespread community initiative to provide extensions to XSLT.

FXSL is a library implementing support for Higher-order functions in XSLT. FXSL is written in XSLT itself.

The XSLT Standard Library xsltsl, provides the XSLT developer with a set of XSLT templates for commonly used functions. These are implemented purely in XSLT, that is they do not use any extensions. xsltsl is a SourceForge project.

Kernow A GUI for Saxon that provides a point and click interface for running transforms.

xslt.js – Transform XML with XSLT JavaScript library that transforms XML with XSLT in the browser.

; Further examples

XSLT Examples using JavaScript based on wiki examples and w3schools XSLT on the Client

How to use XSLT with PHP : Shows how to create a PHP class to convert a PHP array and an XSLT style-sheet into html.

XSLT Resource Links from Symphony CMS (based on XSLT)

Category:Declarative programming languages Category:Functional languages Category:Markup languages Category:Transformation languages Category:World Wide Web Consortium standards Category:XML-based programming languages Category:XML-based standards

ca:Extensible Stylesheet Language Transformations cs:XSLT da:XSLT de:XSL Transformation es:Extensible Stylesheet Language Transformations eu:XSLT fa:تبدیلات اکس‌اس‌ال fr:Extensible Stylesheet Language Transformations ko:XSLT id:Extensible Stylesheet Language Transformations is:XSLT it:XSL Transformations lt:XSLT hu:Extensible Stylesheet Language Transformations ms:XSLT nl:Extensible Stylesheet Language Transformations ja:XSL Transformations no:XSLT pl:XSL Transformations pt:XSLT ru:XSLT simple:XSLT fi:XSLT sv:XSLT tr:XSLT uk:XSL Transformations vi:XSLT bat-smg:XSLT zh:XSLT

Laura Rogers (born March 10, 1979 in Wales) is a British actress.

Biography

As a youngster Rogers was a member of the West Glamorgan Youth Theatre Company and Upland Arts, the Swansea Gilbert and Sullivan society. She studied at the Royal Academy of Dramatic Art (RADA) in London, where she was in the same year as Claudia Harrison, graduating in 2000.

Acting Roles

Rogers's highest-profile roles to date have been single mother and former drug addict Sheena Williams in Series 7 of the ITV drama ''''Bad Girls'''' (2005) and Chastity Green in the BAFTA-nominated BBC mini-series ''The Sins'' alongside Pete Postlethwaite (2000).

On stage, in December 2003 to January 2004 she was in ''Revelations'' at the Hampstead Theatre in London. In April and May 2004 she performed as Mary Yellan in ''Jamaica Inn'' at the Salisbury Playhouse. She then went into a production of ''Celestina'', which started at the Birmingham Rep Theatre and moved onto the King's Theatre, Edinburgh as part of the Edinburgh International Festival that year before returning to the Rep. In February 2006 she appeared at the Bristol Old Vic as Rosine in ''The Barber Of Seville''. In December of that year she played Milady de Winter in ''The Three Musketeers'' at the same venue.

In 2007 she played Wing Governor Helen Stewart in ''Bad Girls: The Musical'' in London's West End, a role played (as a non-musical part) in series 1-3 of the television series ''Bad Girls'' by Scottish actress Simone Lahbib. Rogers previously appeared in this role in the musical's run at the West Yorkshire Playhouse in 2006.

On television, Rogers has also made guest appearances in the BBC series ''Rockface'', ''Holby City'' and ''Doctors''.

In 2008 she played Helena in ''A Midsummer Night's Dream'' and Timandra in ''Timon of Athens'' at Shakespeare's Globe Theatre in London.

She performed the role of Celia in ''As You Like It'' at the Globe in 2009 and played Lady Macbeth in the same theatre from 23 April-27 June 2010.

Laura is currently performing in the West End production of ''The 39 Steps'' at the Criterion Theatre as Annabella Schmidt, Margaret and Pamela, succeeding well known Wicked actress Dianne Pilkington.

External links

Laura Rogers - Archive version of RADA Profile

Laura Rogers's 2008 showreel on YouTube

Bad Girls: The Musical official website

Category:Welsh television actors Category:Welsh stage actors Category:Alumni of the Royal Academy of Dramatic Art Category:1979 births Category:Living people