Home > Articles > Web Services > XML

  • Print
  • + Share This
This chapter is from the book

XML Transformations

The final XML-based technology mentioned here handles how you transform XML from one vocabulary into another. That is, you can change one XML document format into another very easily using the eXtensible Stylesheet Language with Transforms (XSLT). Actually, we've already looked at a major component of XSLT—XPath. What we'll do here, briefly, is combine XPath with the XML style sheet vocabulary to change XML from one form into another.

Why would we want to do this in a Web Service book? After all, .NET does all the soapy stuff, right? Well, that's true, in a way. But you might have noticed that three versions of SOAP are available (1.0, 1.1, and 1.2). The SOAP specification states that you should return a version mismatch error if you receive a SOAP packet indicating that the packet is formed using a version of SOAP that you don't handle. But you might want to work with Web Services or clients that expect another version. If you accept a SOAP packet that .NET cannot handle (an old SOAP version, for example), you can easily intercept the packet using a .NET SoapExtension and then can transform it into something .NET can handle. We're simply showing you how to take SOAP in one form and convert it to another, in case you ever need to do so.


This is by far not the most common use of XSL and XSLT. In the vast majority of the cases we've seen, people are using XSLT to turn XML documents into an HTML representation for display purposes. You'll probably never have to actually transform XML from one version of SOAP to another, especially given Microsoft's aggressive acceptance of the SOAP standard. But this transformation, no matter how unlikely, is still a valid use of the XSLT technology. This use simply relates XML and XSLT to SOAP and Web Services. However, you might find that if you use Web Services often and long enough, you'll want to access a Web Service that will require you to modify your SOAP packets for one reason or another, and XSLT is an excellent alternative for doing so.


As I write this, the latest SOAP working draft specification has just been released. Therefore, my prediction that you might use XSL to transform SOAP 1.1 packets into SOAP 1.2 packets isn't necessarily so far-fetched. Luckily, the differences in the protocol versions aren't significant enough, for the most part, to truly merit XSL transformation. However, two clichés come to mind—"You never know" and "Never say never"... .

Before diving in, another caveat should be mentioned: XPath and XSL/XSLT are huge topics that merit books of their own, and many are available. What we intend to present here is just enough to get you working with the technology. For an in-depth view, definitely pick up a good reference.

XSLT Drilldown

XSLT combines XPath expressions with templates. A template combines a nodeset returned from a specific XPath location step and produces output based upon the contents of the template. More often than not, the template uses the results obtained from the nodeset as input.

Let's say that you were given this XML document:

<?xml version="1.0"?>
   <Part vehicle="Corvette" manufacturer="GM">
      <Desc>Special Hi-Perf Camshaft</Desc>
      <Comment>LT-1, Solid Lifters</Comment>
   (More part elements...)

This document is clearly parts-centric. What if you want an XML document that is vehicle-centric? Would you need to create that from scratch? Well, assuming that all (or some) of the data that you require is already contained in the parts XML document, you wouldn't—you could use XSLT to transform it from the parts-centric view to the vehicle-centric view rather easily.

Let's do just that. The vehicle XML document needs to look like this:

<?xml version="1.0"?>
      <Additional parts elements here)

The XSL style sheet to accomplish this is shown in Listing 3.1.

Listing 3.1  Example XSL Style Sheet

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

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

<xsl:template match="Parts">
      <Make><xsl:value-of select="Part/@manufacturer"/></Make>
      <Model><xsl:value-of select="Part/@vehicle"/></Model>
         <xsl:for-each select="Part">
                  <xsl:value-of select="Number"/>
                  <xsl:value-of select="Desc"/>
                  <xsl:text>: </xsl:text>
                  <xsl:value-of select="Comment"/>
                  <xsl:value-of select="MinYear"/>
                  <xsl:text> to </xsl:text>
                  <xsl:value-of select="MaxYear"/>


If you run the XML file and style sheet through Internet Explorer, you might not get the output that you expect. Internet Explorer will execute the transformation, but it will not display the result as XML. If you're interested in viewing the actual transformed output, it's best to run the XML document and style sheet through a program designed to execute the style sheet and save the resulting output to a file for later recall. You'll get an application that does just this when you get to .NET in the upcoming section ".NET and XSL."

XSL is an XML vocabulary, which is to say that your XSL style sheets will be XML documents in their own right. Many elements are associated with XSL; Table 3.4 gives you the more commonly used XSL instructions.

Table 3.4  Commonly Used XSL Vocabulary Elements




Tells the XSL processor to apply all appropriate templates to the nodeset


Invokes a template by name


Uses multiple conditional testing (use with when and otherwise)


Applies a template repeatedly to all nodes in the nodeset


Is a conditional construct (has no else clause—use <choose/> instead)


Inserts a formatted integer into the output document


Is a default conditional expression used in conjunction with <choose/>


Specifies serialization of the result tree


Sorts output nodes (used to rearrange output document)


Is the XSL style sheet document (root) element


Is the template tag (identifies and encapsulates template)


Inserts literal text into the output document


Copies the node of the input document to the output document


Is an optional conditional expression used in conjunction with <choose/>


Is an optional conditional expression used in conjunction with <choose/>

Here you see the XSL document element, <xsl:stylesheet/>, as well as the XSL workhorse, <xsl:template/>. The style sheet element encapsulates the style sheet itself, while the template element identifies what could be referred to as XSL subroutines. In fact, they're not subroutines, but you could view them that way and not be terribly incorrect. Although we didn't show the XSL elements related to variables, XSL does have the capability of passing variables and parameters between templates. Because they're so powerful, let's look at XSL templates in a bit more detail.

XSL Templates

Listing 3.1 provided two templates, one for the document element and one for the <Parts/> element. We could have created more templates, one for each <Part/> node and children, but instead we elected to dig more deeply into the original XML document using <xsl:for-each/>. This simply made the template a bit easier to read.

The template itself is the cookie cutter that XSL will use to create the newly formatted document. For each template that you include within your style sheet, you'll receive formatted output. The key is to set up the templates so that they operate on the nodeset returned from the match attribute. If you know that many XML nodes will match the template, but you want to constrain the use of some of those nodes, you can also apply the mode attribute to the template:

<xsl:template match="/">
   <xsl:apply-templates select="Parts" mode="Engine" />
   <xsl:apply-templates select="Parts" mode="Body" />

<xsl:template match="Parts" mode="Engine">
   (Something to do with engine parts...)

<xsl:template match="Parts" mode="Body">
   (Something to do with body parts...)

Essentially, mode enables you to process original document nodes many times, with each processing iteration producing a different result.

Notice that we also used the XSL instruction <xsl:apply-templates/>. This tells XSL to go through its template collection and, for any of the input XML nodes that match the templates, produce the output. The key is to create XPath expressions that draw from the XML document the precise nodeset that you want to work with.

The template is the key to transforming the original XML document. After you establish the XPath expression that will pull the set of nodes of interest, you insert the new XML document structure within the template. For each XML node XSL finds that matches the template, it spits out a copy of the resulting template into the new XML document.

At this point, you've reviewed enough XML to move into .NET. Although it's entirely possible to write .NET-based Web Services all day long and never need to access their XML nature, it's also very likely that you'll find a minor change to some part of your SOAP packet to be useful. In that case, you'll find yourself using some or all of the technologies described here. If you're comfortable with what has been discussed so far, let's now talk about XML within .NET.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020