XSLT

Internet Technologies

• Processing XML using XSLT

• Using XPath

• Escaping to Java

Processing XML using XSLT

Instructions for dowloading Xalan can be found in Lab 2.

The following programs were tested with the command lineC:>xalan somefile.xml somefile.xsl resultfile.html

The Xalan classes (and xslt processing) may also be accessed viaa servlet or Java application (see Lab 2).

<?xml version="1.0" ?><?xml-stylesheet type="text/xsl" href="demo1.xsl"?><book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

<xsl:template match = "book"> <HTML><BODY><xsl:apply-templates/></BODY></HTML> </xsl:template> <xsl:template match = "title"> <H1><xsl:apply-templates/></H1> </xsl:template> <xsl:template match = "author"> <H3><xsl:apply-templates/></H3> </xsl:template> <xsl:template match = "publisher"> <P><I><xsl:apply-templates/></I></P> </xsl:template></xsl:stylesheet> Processing

<HTML><BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> <P><I>Little, Brown and Company</I></P> </BODY></HTML>

Output

<?xml version="1.0" ?><?xml-stylesheet type="text/xsl" href="demo1.xsl"?><library><block><book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book></block></library>

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

version="1.0">

<xsl:template match = "book">

</xsl:template>

<xsl:template match = "title">

</xsl:template>

<xsl:template match = "author">

</xsl:template>

<xsl:template match = "publisher">

</xsl:template>

</xsl:stylesheet>

The default rules matchesthe root, library and block elements.

<HTML><BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> <P><I>Little, Brown and Company</I></P> </BODY></HTML>

The output is the same.

<?xml version="1.0" ?><?xml-stylesheet type="text/xsl" href="demo1.xsl"?>

<book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> <book>Cliff Notes on The Catcher in the Rye</book> </book>

Two books in the input

<xsl:template match = "book"> <HTML><BODY><xsl:apply-templates/></BODY></HTML> </xsl:template>

<xsl:template match = "title"> <H1><xsl:apply-templates/></H1> </xsl:template>

<xsl:template match = "author"> <H3><xsl:apply-templates/></H3> </xsl:template>

<xsl:template match = "publisher"> <P><I><xsl:apply-templates/></I></P> </xsl:template>

</xsl:stylesheet>

What’s the output?

<HTML><BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> <P><I>Little, Brown and Company</I></P> <HTML><BODY>Cliff Notes on The Catcher in the Rye</BODY></HTML> </BODY></HTML>

Illegal HTML

<book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book>

<xsl:template match = "author"> <H3><xsl:apply-templates/></H3> </xsl:template></xsl:stylesheet>

We are not matchingon publisher.

<HTML><BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> Little, Brown and Company </BODY></HTML>

We get the default rule matching thepublisher and then printing its child.

<book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book>

<xsl:template match = "publisher">  </xsl:template>

</xsl:stylesheet>

We can skip the publisherby matching and stoppingthe recursion.

<HTML><BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> </BODY></HTML>

<?xml version="1.0" ?><?xml-stylesheet type="text/xsl" href="demo1.xsl"?><shelf> <book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book> <book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book> <book> <title>The Catcher in the Rye</title> <author>J. D. Salinger</author> <publisher>Little, Brown and Company</publisher> </book></shelf>

A shelfhas many books.

<xsl:template match = "publisher"> <i><xsl:apply-templates/></i> </xsl:template>

</xsl:stylesheet>

Will this do the job?

<HTML> <BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> <i>Little, Brown and Company</i> </BODY></HTML><HTML> <BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> <i>Little, Brown and Company</i> </BODY></HTML><HTML> <BODY> <H1>The Catcher in the Rye</H1> <H3>J. D. Salinger</H3> <i>Little, Brown and Company</i> </BODY></HTML>

This is not whatwe want.

Same input.

<xsl:template match = "shelf"> <HTML><BODY>Found a shelf</BODY></HTML> </xsl:template>

</xsl:stylesheet>

Checks for a shelf and quits.

<HTML><BODY>Found a shelf</BODY></HTML>

Output

Same input.

<xsl:template match = "shelf"> <HTML> <BODY> <b>These are a few of my favorite books</b> <table width = "640“ border = “5”> <xsl:apply-templates/> </table> </BODY> </HTML> </xsl:template> <xsl:template match = "book"> <tr> <td> <xsl:number/> </td> <xsl:apply-templates/> </tr> </xsl:template> <xsl:template match = "title | author | publisher"> <td><xsl:apply-templates/></td> </xsl:template></xsl:stylesheet>

Produce a table of books.

<HTML><BODY><b>These are a few of my favorite books</b><table width="640“ border = “5”> <tr><td>1</td> <td>The Catcher in the Rye</td> <td>J. D. Salinger</td> <td>Little, Brown and Company</td> </tr> <tr><td>2</td> <td>The XSLT Programmer's Reference</td> <td>Michael Kay</td> <td>Wrox Press</td> </tr> <tr>

<td>3</td> <td>Computer Organization and Design</td> <td>Patterson and Henessey</td> <td>Morgan Kaufmann</td> </tr></table></BODY></HTML>

• Non-xml language used to identify particular parts of an xml document

• Used by XSLT for matching and selecting particular elements to be copied into the result tree.

• Used by Xpointer to identify a particular point in or part of an xml document that an Xlink links to.

Slides adapted from “XML in a Nutshell” by Harold

First, we’ll look at three commonly used XSLT instructions:

xsl:value-of xsl:template xsl:apply-templates

<xsl:value-of select = “XPathExpression” />

The xsl:value-of element computes the string value of an Xpathexpression and inserts it into the result tree. XPath allows us to select nodes in the tree and different node types produce differentvalues.

<xsl:value-of select = “XPathExpression” />

element => the text content of the element after all tags are stripped text => the text of the node attribute => the value of the attribute root => the value of the root processing-instruction => the processing instruction data (<?, ?>, and the target are not included comment => the text of the comment (no comment symbols) namespace => the namespace URI node set => the value of the first node in the set

<xsl:template match = “pattern” />

The xsl:template top-level element is the key to all of xslt.The match attribute contains a pattern (location path) againstwhich nodes are compared as they’re processed. If the patternmatches a node, then the contents are instantiated

<xsl:apply-templates select = “XPath node set expression” />

Find and apply the highest priority template that matches the node set expression.

If the select attribute is not present then all children of the context node are processed.

The Tree Structure of an XML Document

<?xml version="1.0" ?><?xml-stylesheet type="text/xsl" href = "pi.xsl" ?><people> <person born="1912" died = "1954" id="p342"> <name> <first_name>Alan</first_name> <last_name>Turing</last_name> </name>  <profession>computer scientist</profession> <profession>mathematician</profession> <profession>cryptographer</profession> </person>

See Harold Pg. 147

<person born="1918" died = "1988" id="p4567"> <name> <first_name>Richard</first_name> <middle_initial>M</middle_initial> <last_name>Feynman</last_name> </name> <profession>physicist</profession> <hobby>Playing the bongoes</hobby> </person></people>

Unicode ‘M’

personborn = “1914”died = “1952”id=“p342”

person

first_name

<!– Did the word “computer scientist”exist in Turing’s day?”-- >

<?xml-stylesheet type="text/xsl" href = “some.xsl" ?>

profession

The rootElement NodesText NodesAttribute NodesComment NodesProcessing InstructionsNamespace Nodes

Nodes seen by XPath Constructs not seen by XPath

CDATA sectionsEntity referencesDocument Type Declarations

The following appears in each example below so ithas been removed from the slides.

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"version="1.0"

>::</xsl:stylesheet>

Location Paths

• The root

<xsl:template match="/"><a>matched the root</a>

</xsl:template>

<?xml version="1.0" encoding="utf-8"?><a>matched the root</a>

Location Paths

• Child element location paths (relative to context node)

<xsl:template match="/"> <xsl:value-of select = "people/person/profession" /></xsl:template>

computer scientist

Location Paths

• Attribute location paths (relative to context node)

<xsl:template match="/"> <xsl:value-of select = "people/person/@born" /></xsl:template>

<?xml version="1.0" encoding="utf-8"?>1912

Location Paths

• Attribute location paths (relative to context node)<xsl:template match="/"> <xsl:apply-templates select = "people/person" /></xsl:template>

<xsl:template match = "person"> <date> <xsl:value-of select = "@born" /> </date></xsl:template>

Location Paths

• Comment Location Step (comments don’t have names)

<xsl:template match="/"> <xsl:value-of select = "people/person/comment()" /></xsl:template>

<?xml version="1.0" encoding="utf-8"?> Did the word "computer scientist" exist in Turing's day?

Location Paths

• Comment Location Step

<xsl:template match = "comment()" > <i>comment deleted</i></xsl:template>

Document content withcomments replaced as shown.Default – no comments output

Location Paths

• Text Location Step (Text nodes don’t have names)

<xsl:template match="/"> <xsl:value-of select = "people/person/profession/text()" /></xsl:template>

computer scientist

Location Paths

• Processing Instruction Location Step

<xsl:template match="/"> <xsl:value-of select = "processing-instruction()" /></xsl:template>

<?xml version="1.0" encoding="utf-8"?>type="text/xsl" href = "pi.xsl"

Location Paths

• Wild cards

There are three wild cards: *, node(), @*

The * matches any element node. It will not match attributes, text nodes, comments or processing instructions nodes.

Location Paths

• Matching with *<xsl:template match = "*" > <xsl:apply-templates select ="*" /></xsl:template>

Matches all elements and requestscalls on sub-elements only. Nothingis displayed. The text nodes are never reached.

Location Paths

• Matching with node()

The node() wild card matches all nodes: element nodes,text nodes, attribute nodes, processing instruction nodes,namespace nodes and comment nodes.

Not implemented in XT

Location Paths

• Matching with @*

The @* wild card matches all attribute nodes.

XT does not like it in an <xsl:template match ..>but likes it in an <xsl:apply-templates select=…>

Location Paths

• Matching with @*

<xsl:template match = "person" > <b> <xsl:apply-templates select = "@*" /> </b></xsl:template>

<?xml version="1.0" encoding="utf-8"?>

Location Paths

• Multiple matches with |

<xsl:template match = "profession|hobby" > <activity> <xsl:value-of select = "text()"/> </activity></xsl:template>

<xsl:template match = "*" > <xsl:apply-templates /></xsl:template>

<xsl:template match = "text()" ></xsl:template>

Matches all the elements.Skips the text nodes unlessthey describe a professionor hobby.

Location Paths

• Selecting from all descendants with //

// selects from all descendants of the context node as well as the context nodeitself. At the beginning of an Xpathexpression, it selects from all descendantsof the root node.

Location Paths

<xsl:template match = "//name/last_name/text()" > <xsl:value-of select = "." /></xsl:template>

<xsl:template match = "text()" ></xsl:template>

<?xml version="1.0" encoding="utf-8"?>TuringFeynman

Location Paths

<xsl:template match = "/" >

<xsl:value-of select = "//first_name/text()" />

</xsl:template>

<?xml version="1.0" encoding="utf-8"?>Alan

Location Paths

<xsl:apply-templates select = "//first_name/text()" />

</xsl:template>

<xsl:template select = "text()" >

<xsl:value-of select = "." />

</xsl:template> <?xml version="1.0" encoding="utf-8"?>AlanRichard

Location Paths

<xsl:apply-templates select = "//middle_initial/../first_name" />

</xsl:template>

</xsl:stylesheet>

<?xml version="1.0" encoding="utf-8"?>Richard

PredicatesIn general, an Xpath expression may refer to morethan one node. Predicates allow us to reduce the number of nodes we are interested in.

Each step in a location path may have a predicatethat selects from the node list that is current at thatstep in the expression.

The boolean expression in the predicate is tested against each node in the context node list. If the expressionis false then that node is deleted from the list.

Predicates<xsl:template match = "/" >

<xsl:apply-templates select = "//profession[.='physicist']/../name" />

</xsl:template>

</xsl:template><?xml version="1.0" encoding="utf-8"?>

Richard M Feynman

<xsl:apply-templates select = "//person[@id='p4567']" />

</xsl:template>

Richard M Feynman

physicist Playing the bongoes

<xsl:apply-templates select = "//person[@born <= 1915]" />

</xsl:template>

Alan Turing

computer scientist mathematician cryptographer

<xsl:apply-templates select = "//person[@born <= 1919 and @born >= 1917]" />

</xsl:template>

Richard M Feynman

physicist Playing the bongoes

<xsl:apply-templates select = "/people/person[@born < 1950]/ name[first_name='Alan']" />

</xsl:template>

Alan Turing

General XPath Expressions

Xpath expressions that are not node sets can’t be usedin the match attribute of an xsl:template element.

They can be used for the values for the select attributeof xsl:value-of elements and in location path predicates.

General XPath Expressions<xsl:template match = "/" > <xsl:apply-templates select = "/people/person" /></xsl:template>

<xsl:template match = "person"> <xsl:value-of select="@born div 10" /></xsl:template>

<xsl:template match = "text()"></xsl:template>

<?xml version="1.0" encoding="utf-8"?>191.2191.8

General XPath ExpressionsXpath Functions

<xsl:template match = "/" > <xsl:apply-templates select = "/people/person" /></xsl:template>

<xsl:template match = "person"> Person <xsl:value-of select="position()" /></xsl:template>

<xsl:template match = "text()"></xsl:template> <?xml version="1.0" encoding="utf-8"?>

Person 1

Person 2

General XPath ExpressionsXpath Functions

<xsl:template match = "/" > <xsl:apply-templates select = "//name[starts-with(last_name,'T')]"/></xsl:template>

<xsl:template match = "name"> Mr. T. <xsl:value-of select="." /></xsl:template>

Mr. T. Alan Turing

Node set convertedto string

Escaping to Java

Extension functions provide a mechanism for extendingthe capabilities of XSLT by escaping into another languageSuch as Java or JavaScript.

If there is no namespace prefix on the function then it mustbe a core function built into XSLT.

Otherwise, it’s an extension function.

General XPath ExpressionsExtended Xpath Functions

<xsl:call-template name = "show-date"/>

</xsl:template>

<xsl:template name = "show-date" xmlns:Date = "http://www.jclark.com/xt/java/java.util.Date"> <xsl:variable name = "today" select = "Date:new()" /> <xsl:value-of select = "Date:toString($today)" />

</xsl:template>

</xsl:stylesheet>Using James Clarke’sXT

Escaping to Java

<?xml version="1.0" encoding="utf-8"?>Mon Mar 19 10:46:17 EST 2001

Escaping to Java // A simple bean saved under Www/beans/MyDate.java// The classpath c:\Jigsaw\Jigsaw\Jigsaw\Www\beansimport java.util.*;

public class MyDate {

Date d;

public MyDate() {

d = new Date(); }

public Date getDate() { return d; }

public String toString() { return "The date is " + d.toString(); } public static void main(String a[]) {

MyDate x = new MyDate(); System.out.println(x); }}

Escaping to Java<xsl:template match = "/" > <xsl:call-template name = "show-date"/></xsl:template>

<xsl:template name = "show-date" xmlns:Date = "http://www.jclark.com/xt/java/MyDate"> <xsl:variable name = "today" select = "Date:new()" /> <xsl:value-of select = "Date:toString($today)" />

</xsl:template><?xml version="1.0" encoding="utf-8"?>The date is Mon Mar 19 11:17:24 EST 2001

XSLT

Documents

XSLT Programming

Crash Course in XSLT - stuff.mit.edu: students' portal · 1 Crash Course in XSLT: Overview of XML and XSLT Jan. 15, 2007 Crash Course in XSLT Overview of XML and XSLT Jan. 15, 2007

XSLT - SkillAdvance · 2006. 3. 1. · Non-XSLT elements and text are moved to the result tree. XSLT elements are recognized by the namespace prefix. XSLT child elements are processed,

XSLT? Where we are going, we don’t need XSLT

Xslt tutorial

Trasparencias XSLT/XPath

[MS-XSLT]: Microsoft XSLTransformations (XSLT) …...4 / 17 [MS-XSLT] - v20180828 Microsoft XSLTransformations (XSLT) Standards Support Document Copyright © 2018 Microsoft Corporation

Learning XSLT

XSLT Training

[MS-XSLT]: Microsoft XSLTransformations (XSLT) Standards ...interoperability.blob.core.windows.net/web/MS-XSLT/[MS-XSLT].pdf · 3.0 and 6.0 for XSL Transformations (XSLT), Version

Digital Media Technology Week 6. XML Source XSLT Stylesheet XML Result XSLT

XSL Transformations (XSLT)

Advanced XSLT. Branching in XSLT XSLT is functional programming –The program evaluates a function –The function transforms one structure into another

Internet Technologies XML/XSLT What is XML? What is XSLT? From XML to HTML using XSLT The XSLT processing model An Example from FpML Homework

XSLT I Robin Burke ECT 360. Outline XSLT processing XSLT syntax XPath XSLT basics Lab

Visualization of GML data using XSLT. · formation (XSLT) stylesheet together with an XSLT processor. The XSLT stylesheet is an XML based document that describes how data in GML do-cument

Xslt Process

openesb XSLT

Object Oriented Programming III1 XSLT Processing XML using XSLT Using XPath

What Tutorial: don’t be afraid of XSLT · XSLT basics XSLT standsfor‘eXtensibleStylesheetLanguage: Transformations. XSLT is a language for transforming the structure of an XML