Home > Articles > Web Services > XML

Valid XML Instances

In the sample chapter, Devan Shepherd explores the concept of valid XML. Learn what validity means in XML, why it is important when exchanging data with others, how XML deals with data structures and document structures, and some common misconceptions about valid XML.
This sample chapter was excerpted from Sams Teach Yourself XML in 21 Days, by Devan Shepherd.
This chapter is from the book

Why Should You Care About Valid XML?

You have learned that the use of XML requires strict adherence to syntax and that the parsers and processors used for XML will deal harshly with any violation of the rules. In fact, your document is considered "broken" by an XML parser if it has even the smallest of syntax errors. With such an exacting degree of constraint over XML, why do you need a more complex system of rules?

Validity in XML has to do with the structure of the document. You learned on Day 1 that XML provides a method of placing structured data into a text file. However, structure implies much more than syntax. An XML document, for instance, might be syntactically perfect, but include elements in the wrong order or exclude elements that might be required by a processor to complete an e-commerce transaction or to solve a particular business problem.

By way of example, imagine marking up this book in XML. You would probably have elements such as title, author, publisher, ISBN, date, toc (table of contents), and so on just for the front matter of the book. Within the body of the book, you might include markup for chapter, section, paragraph, emphasis, note, tip, table, and perhaps many more. You can see that the markup could become quite complex and elaborate. For purposes of this discussion, consider only the front matter elements just listed.

Listing 3.1 depicts an XML document that marks up sample front matter for this book.

Listing 3.1  Front Matter Marked Up in XML—MyXMLBook.xml

 1: <?xml version="1.0"?>
 2: <!-- listing 3.1 - myXMLBook.xml -->
 4: <book>
 5:    <title>Sams Teach Yourself XML in 21 Days, Second Edition</title>
 6:    <author>Devan Shepherd</author>
 7:    <publisher>SAMS Publishing</publisher>
 8:    <isbn>0-672-32093-2</isbn>
 9:    <date>June 2001</date>
10:    <toc>
11:      <day number="1">An Overview of the Internet and Markup Languages</day>
12:      <day number="2">XML Syntax Explored in Detail</day>
13:      <day number="3">Valid XML Instances</day>
14:    </toc>
15: </book>

Analysis The book root element (lines 2-13) contains title, author, publisher, isbn, data and toc child elements. All are well-formed with start and end tags shown in matching case. Child elements are properly nested in parent elements with no start and end tags overlapping. The toc element has three-day child elements with text content. The number attributes on the day elements serve to modify day elements in the same way that an adjective modifies a noun in a spoken language.

Not only is the XML document shown in Listing 3.1 well-formed and logical machine-readable code, but it truly is human intelligible. The structure of this document could be represented with a simple tree diagram, like the one shown in Figure 3.1. However, you have no rules in place yet to enforce that structure.

Figure 3.1 Tree structure for the Sams Teach Yourself XML in 21 Days, Second Edition front matter XML example.

Now examine the document in Listing 3.2. This is also a well-formed XML document. You can prove that by running it through an XML parser. Note that Microsoft Internet Explorer does not report errors and shows a formatted listing of the instance, as shown in Listing 3.2. Remember that this is because Internet Explorer has a built-in parser. Even though the document is well-formed, it no longer bears much resemblance to the structure diagrammed in Figure 3.1 and wouldn't serve to mark up the front matter of this book.

Listing 3.2  Well-Formed But Poorly Structured XML Document—mixed_front_matter.xml

 1: <?xml version="1.0"?>
 2: <!-- listing 3.2 - mixed_front_matter.xml -->
 4: <book>
 5:   <toc>
 6:     <day number="1">An Overview of the Internet and Markup Languages</day>
 7:     <title>Everything You Ever Wanted to Know About XML</title>
 8:     <title>XML an Why Cats Chase Laser Pointers</title>
 9:     <date>July 2001</date>
10:     <date>June 2001</date>
11:     <date>August 1908</date>
12:     <author>Devan Shepherd</author>
13:     <publisher>Sams Publishing</publisher>
14:     <title>Sams Teach Yourself XML in 21 Days, Second Edition</title>
15:     <day number="1">An XML Overview of the Internet and Markup Languages</day>
16:     <title>Sams Teach Yourself XML in 21 Days, Second Edition</title>
17:     <date>June 2001</date>
18:     <day number="2">XML Syntax Explored in Detail</day>
19:     <isbn>0-672-32093-2</isbn>
20:     <day number="3">Valid XML Instances</day>
21:   </toc>
22: </book>

The well-formed instance in Listing 3.2 contains multiple dates and titles and an illogical order of elements, and it no longer makes intuitive sense. For instance, the toc element contains dates and other elements that are not typically part of a table of contents. This is not at all what was intended when you set out to markup the front matter for the book.

You need a mechanism to ensure constraint beyond well-formedness. If you are describing this book using XML markup, it makes sense to use a mechanism to enforce some simple constraints. In many cases, the constraints enforce document content rules, business rules or stricture that determines the order of elements, the presence of elements and attributes, and an indication of the number of occurrences expected. For the book's front-matter instance, you might want to establish structural guidelines, such as

  • There is one and only one book element—the root element—that contains all others.

  • The book element contains one each of title, author, publisher, isbn, date, and toc elements in that order.

  • toc should contain as many day elements as needed.

  • Each of the day elements has a required number attribute indicating which day is being encoded.

These simple content rules can be incorporated into a schema that acts to define the structure of the XML instance. Think of a schema as being like a contract that you enter into with XML to ensure that the desired structure is maintained. As a programmer, you will create a schema to apply to your document that maps well on the business problem you are addressing, or perhaps you might be able to select one from a public repository of schemata. Most schemata, like other parts of the XML family, are extensible by nature. Therefore, if a preexisting schema is only 80% right for your business, you might choose to extend it to make it fit your specific needs. Then, when you share data with others, you can include your extended schema to ensure that they adhere to the structure of your XML data stream.


It is not always necessary to create a unique schema. There are large repositories of public schemata maintained on the Web for use by particular industries.

There are several forms of schemata that are used in XML programming. During Day 4 you will learn to create, use, and interpret Document Type Definition (DTD) schemata. The DTD approach originated with SGML and has carried over to XML, but suffers from some shortcomings with regard to data type constraints and a syntax that is not the same as XML. On Days 5 and 6, respectively, you will learn about the very powerful XML Data Reduced (XDR) Schema dialect of XML and the XML Schema Definition (XSD) Language recommended by the W3C. All three of these technologies offer a means by which you can enforce the business rules that define the structure of your document. Each approach has advantages and disadvantages, but in time, the disparate methods should be coalesced into a single standard by the W3C and widely supported by industry and software tool developers.


Data Type Validation enforces the classification of data values. Data Type Validation provides a means for a computer to make distinctions between such types as integers, percentages, floating point numbers, dates and strings, to name only a few.

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