Home > Articles > Web Services > XML

Applied SOAP: XML and Web Service Implementation

Understand why loosely coupled, interoperable XML is critical to Web Services. Read how to use XML technologies that are key to working with SOAP, such as XPath, XLink, and XSL.
This chapter is from the book


XML is critical to Web Services. It's a fundamental technology; without it, you wouldn't have Web Services—at least, not as they're implemented today.

This is true for two main reasons. First, XML is loosely coupled. That is, XML enables you to loosely bind the client and server, making it easier to change one or both, as well as add versioned information after the initial release. Second, XML is easily interpreted, making it highly interoperable. XML is simply text, so if you can interpret text on your computer system, you can interpret XML. You'll find XML in use in nearly every contemporary computer system available today, and perhaps even in some venerable systems that you used yesteryear. There is a great deal more to it than that, but, in a nutshell, XML is just text in a file or network packet.


My observation that XML is merely text is inarguably true. However, XML is becoming increasingly Unicode-aware. Most of the XML documents that you'll see in use today are encoded using either UTF-8 (single-byte Unicode) or UTF-16 (traditional 2-byte Unicode). Therefore, your system needs Unicode capability to truly handle these contemporary XML documents. .NET provides you with this capability, even if you're running on a 16-bit version of Windows, such as Windows 98.

The goal of this chapter is to introduce you to the fundamentals of XML and to dig deeper into XML to show how it plays a role in Web Service implementation. If you're new to XML, Appendix D, ".NET Web Service Resources," points to alternative sources of information that you can examine on your own. If you do know something about XML, you might want to scan this chapter for information that's new to you and skip the parts that you know well. With luck, you'll find something interesting and new, and you'll expand your understanding of XML, with both Web Services and .NET's handling of XML in general.

The true goal of this chapter is to make sure that you understand how XML fits into Web Service processing and to show you how to work with XML using the .NET class hierarchy. You might find that you'll need to modify the XML that your Web Service uses for some reason. If so, you'll use what you've learned from this chapter. We'll start with a discussion of XML as a wire representation, which should explain why XML is so important to Web Services.

XML as a Wire Representation

Whenever you transmit information over a network, that information is ultimately transformed from a binary representation in your computer's memory into another representation that was designed for network use. Perhaps the network representation is a highly efficient binary one, or perhaps its purpose is more general. In any case, you'll probably find that the information's binary format in memory is very different than its network form. The form that it takes for network transmission is called its wire representation. This is the form that the data takes when it's transmitted over the network, no matter what the network medium is.

Wire representations, and protocols in general, are often designed to meet specific design criteria, a few of which are listed here:

  • Compactness
  • Protocol efficiency
  • Coupling
  • Scalability
  • Interoperability

Compactness refers to how terse the network packet becomes while still conveying the same information. Small is usually best. Protocol efficiency is related to compactness—you rate efficiency by examining the overhead required to send the payload. The more overhead you require, the less efficient the protocol is.

A protocol's coupling, loose or tight, tells you how flexible consumers of the protocol will be if you change things. Loosely coupled protocols are quite flexible and easily adapt to change, while tightly coupled protocols will most likely require significant modifications to both the server and existing clients. Tightly coupled protocols, for example, are those that require (or force) such things as the same in-memory representation or the same processor type to avoid endian issues (byte ordering in multibyte values). Loosely coupled protocols avoid this altogether by abstracting the information to a degree that makes the byte order irrelevant. Converting an integer represented in big or little endian looks the same when represented as a string. The byte order conversion is made by the software handling the protocol, not by the protocol itself.

Scalability addresses the protocol's capability to work with a large number of potential recipients. Some protocols are limited to a handful of consumers, while others handle millions of users easily.

Finally, interoperability speaks to the protocol's acceptance on a variety of computing platforms. Will you have to issue network packets to one specific operating system or platform, or is the protocol a bit more general-purpose, enabling you to send information to a wider variety of systems?

Protocols, including XML, generally lie within a continuum of these characteristics. Highly efficient protocols tend to not scale well. Interoperable protocols tend to scale well but are often not as efficient as proprietary protocols. No single protocol does it all, and network engineers often make design decisions based upon these and many other criteria. Which protocol you choose depends upon where the protocol falls in the continuum.

XML is both loosely coupled and highly interoperable. In fact, XML is so interoperable that it is nearly ubiquitous. You can send XML to anyone on the planet—not only will that person receive the information, but he'll also be able to interpret and make use of it in nearly every case.

With XML, you pay for loose coupling and interoperability with protocol efficiency and compactness. XML is actually rather inefficient, although you can tailor this by judiciously choosing your element names (fewer characters in element names often yields more efficient XML, even though terseness of the XML was not a design goal of the inventors). Nor is XML particularly compact. XML is text, and, as with any text document, you might be either conservative with your expressiveness or creative yet a bit more verbose. In either case, you are still left with a loosely coupled and interoperable mechanism for encoding information to be transmitted over the wire.

XML and Loose Coupling

If XML isn't terribly efficient, why use it? Because XML is simply text formatted in a specific way. You could make the same argument about HTTP, SMTP, POP3, NNTP, and a host of other such Internet protocols, but they've also proven to be successful. XML works, and it works well—when you transmit information using XML, you're sending text rather than a proprietary protocol that has arbitrary design limitations. DCOM, for example, uses a fairly efficient wire representation but requires the object's server to keep track of the client. To do this, the DCOM client issues "I'm still here" messages to the server every two minutes. After three periods without one of these ping messages, the server chops off the object's head and reclaims the resources (memory and such). But imagine making changes to the DCOM wire representation and then trying to field that worldwide... .

Because XML is nothing more than text, with no claims made to object status or association, changes to your XML are rather easily accepted. You still send and receive text; it's just that the element names might have changed or the document layout might have been slightly altered.

XML and Interoperability

The fact that XML is so loosely coupled has undoubtedly been a contributing factor to its wide acceptance throughout the Internet. Nearly every major computing platform available today has some capability to accept and interpret XML. XML is text—and, if your computer can handle text, your computer can handle XML. Palm PCs, cellular telephones, desktop and laptop PCs, and the largest of mainframes all have XML processing capability.

If this is the case, you should expect to be able to send anyone an XML document and know that the recipient can make use of the information. Because this is so, SOAP architects chose XML as the encoding mechanism for the SOAP protocol. XML is a rich and expressive technology that readily lends itself to method parameter serialization. Best of all, everyone understands what has been serialized, regardless of computing platform, and can make use of it.

As you probably already know, it's one thing to create the XML document. It's quite another to interpret the contents using an automated system. You'll require some mechanism to reach into the XML to extract the portions of interest. That mechanism is called XPath. Here we'll move away from "Why is XML good?" toward "How do I use XML?"

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