Home > Articles > Web Services > XML

XML and Namespaces

Learn more about Namespaces in the XML family of specifications as this sample chapter addresses the fundamental aspects of the relationship between the two.
This chapter is from the book

Briefly stated, the primary purpose of XML namespaces is to define a mechanism for uniquely naming elements and attributes so that different vocabularies can be mixed in an XML document without name conflicts. For example, if you want to refer to both the price element defined in the SuperDuperCatalog.dtd and also the price element from the DiscountHouseCatalog.dtd, you need a way to unambiguously identify which type of price you are referring to at any point in an XML instance that references both DTDs. This name collision is a potential problem when you consider that the content models and/or attribute lists for these elements may differ. Consider for example these fragments:

<!-- from SuperDuperCatalog.dtd -->
<!ELEMENT price (#PCDATA) >
<!ATTLIST price currency CDATA "US" >

<!-- from DiscountHouseCatalog.dtd -->
<!ELEMENT price (#PCDATA) >
<!ATTLIST price type (wholesale | retail) #REQUIRED >

Although these two have the same content model, their attributes differ, so what is valid for one is invalid for the other, not to mention the fact that the two price elements may be based on completely different factors. (In fact, if we were using XML Schema, the two elements could even be different datatypes.) So we clearly need a way to differentiate which price element we mean at all times.

The Namespaces in XML Recommendation (http://www.w3.org/TR/REC-xml-names/) wasn't published until January 1999, nearly a full year after the XML 1.0 Recommendation. Therefore, although the concept of namespaces is now considered part of the core XML technology, you won't see them mentioned in the original XML 1.0 Recommendation or in any of the W3C specifications that appeared in 1998. You will, however, find a few references to namespaces in the XML 1.0 Recommendation, Second Edition, from October 2000 (http://www.w3.org/TR/1998/REC-xml-19980210 and http://www.w3.org/TR/REC-xml, respectively). Virtually every major W3C specification from 1999 onwards contains some mention of the role played by namespaces, or at least states the namespaces that apply to that spec. Namespaces aren't fully supported by some tools (especially those that handle DTDs but not XML Schema), but they are very important to XSLT, XML Schema, XLink, and most of the more recent XML family of specifications.


Even if you don't plan to create documents that use mixed vocabularies, you need to understand what XML namespaces are and how they are used because you will encounter them in XSLT, XML Schema, and XLink, as well as in programming APIs such as DOM Level 2 and SAX2.

Although the Namespaces in XML specification itself is only fourteen pages, it has managed to generate far more pages of controversy since its publication. For example, Ronald Bourret's excellent XML Namespace FAQ (http://www.rpbourret.com/xml/NamespacesFAQ.htm.) is forty-six pages, more than three times the length of the W3C recommendation on which it is based. How can this be possible? In his XML.com article, "Namespace Myths Exploded" (http://www.xml.com/pub/a/2000/03/08/namespaces/), Bourret points out that the actual Namespace in XML Recommendation omits many details about issues that programmers have raised, although the specification does achieve its stated purpose of defining a two-part naming scheme for elements and attributes. In his FAQ, Bourret also contends that namespaces do not themselves provide a technology for merging documents that reference different DTDs, although they are useful in developing this capability. Furthermore, the URIs1 used as XML namespace names need not point to anything at all since they are merely intended to be unique identifiers, a distinction that often confuses newcomers. Another point of confusion and controversy is the problem namespaces pose for validation based on DTDs, which are to some degree incompatible with the Namespace in XML Recommendation.

Why is there so much controversy? And what are namespaces anyway? Why do we need them, and how do we use them? This chapter addresses these questions. Readers interested in many more subtle issues concerning namespaces should refer to Bourret's two previously cited resources.

Why Namespaces Are Needed: Resolving Name Conflicts

The element name title appears in many vocabularies: XHTML, SVG, XLink (as both an element and an attribute), XSLFO, Schematron, RSS, and Dublin Core (as Title). The familiar table element from XHTML also appears in XSLFO (and as mtable in MathML2). Both SVG and MathML define a set element. Both SVG and XSLT have a text element. (You can check for element names, attribute names, function names, keywords, and much more using the Smart Reference Search of XML specifications on ZVON.org at http://zvon.org/php/Search/codes.php.)

What happens when we need to refer to identically named elements from different XML languages from within the same XML document? This need can arise when we are combining W3C languages or, as in the example at the beginning of this chapter, referencing multiple custom languages that include common element names like price and item. It is also necessary if you wish to convert between two versions of the same language, such as when translating an XSLT stylesheet originally written for the early MSXML parser from Microsoft to a stylesheet compatible with the XSLT 1.0 Recommendation, or eventually when converting from a XSLT 1.0 stylesheet to a 2.0 stylesheet. We need a way to unambiguously differentiate "the element named title from the XLink namespace" from "the element title from the SVG namespace" from "the element title from the XSLFO namespace" from "the element title from the XHTML namespace."

One way to achieve unique naming is to leverage the uniqueness provided by URIs. Since the Domain Name System guarantees unique names, identifiers based on unique addresses are also unique. That is, if we combine an element name with a URI in some manner, an element with that same name but combined with a different URI will not be considered identical by parsers. For example, we could consider four references to a unique title element, each from a separate namespace, as indicated by a URI for each language (thinking of each language as defining a separate namespace):


If the languages are created and maintained by different organizations, this scheme still works fine:


While this URI-based naming approach solves the problem of possible name collision, it certainly makes for ungainly element names. As it turns out, the syntax shown here is conceptual, rather than literal, since slash and curly braces are not legal characters in XML Names.3 So, how do we really declare and use these unique names?

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