Home > Articles > Web Services > XML

This chapter is from the book

Creating a Well-Formed XML Document

Let's take a look at the creation of a well-formed XML document. In this example, we will create a simple document for keeping track of appointments.

First, we could create this document using only elements. Here are the elements we're going to use in the document:

  • appointments—This element will serve as the root element of the document, containing all the other elements in the document.

  • event—The event element will contain the information about each individual appointment.

  • date—A child of the event element, this is the date of the event.

  • start-time—A child of the event element, this is the starting time for the appointment.

  • end-time—A child element of the event element, this is the ending time for the appointment.

  • type—Also a child of event, the type of appointment, such as a meeting, doctor's appointment, and so on.

  • title—A child of event, a title for the appointment.

  • description—A child of event, the description of the appointment.

  • location—A child of event, the location of the appointment.

  • reminder—A child of event, this element is used to define a reminder (instant message or e-mail) for the event.

  • status—A child of reminder, the status of whether or not a reminder should be sent.

  • interval—A child of reminder, the interval of time before the event when a reminder should be sent.

  • method—A child of reminder, the method by which the reminder should be sent.

We can create the XML document using only these elements. All XML documents should begin with the XML declaration. The XML declaration takes the following form:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

The declaration has three attributes:

  • version—The version attribute specifies the version of XML that was used to author the document. The version attribute is required.

  • encoding—The encoding attribute is used to specify the character set that the document utilizes. The attribute is not required, but if it is not specified, the parser will assume the default value of "UTF-8," which is the standard 8-bit Unicode encoding.

  • standalone—The standalone attribute is optional, and is used to indicate whether the document is self-contained (standalone="yes") or whether it requires a DTD/Schema (standalone="no"). In our example, we won't be using a DTD or XML Schema—our document will be self-contained, so the attribute value will be "yes."

The XML declaration is not required in order for the XML document to be considered well formed; however, there are very few instances when you should not use the XML declaration. Unless you have a specific reason not to (such as working with a document fragment), you should always use it.

The appointments element is the root element of the document, and will contain the remaining elements. When we populate the document with the elements with the proper relationships, here is the result:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
 <title>Staff Meeting</title>
 <description>Weekly staff meeting.</description>
 <location>Conference Room</location>

This is a well-formed XML document, which does describe appointments adequately. However, you will notice that the document does not make any use of attributes, and there are a couple of places where it might be easier to use attributes to describe our data.

For example, we could easily describe some of the factual information regarding the event, such as the date and times, as attributes. If we start with the event element


we can easily rework this structure to make use of attributes. The result is an event element with three attributes:

 <event date="" start-time="" end-time="">

We can do something similar with the reminder element. We start with the element-only structure:


And change the child elements into attributes as well:

 <reminder status="" interval="" method=""/>

Although both structures work, the use of the attributes helps streamline the data and results in a cleaner-looking document:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
 <event date="" start-time="" end-time="">
 <reminder status="" interval="" method=""/>

In the content of the attributes is primarily a limited set of data; with the date, we will keep a standard format "MM-DD-YY" and the start time and end times will be in 24-hour time format. Later, when we discuss XML Schemas and datatypes, we could easily make these attributes date/time datatypes, which would mean that if the content of the attribute weren't properly formatted, the document would be invalid. Because here we are concerned only with well-formedness, that capability isn't as crucial.

However, data that is always of a limited type is often appropriate for attributes. For example, the "status" of the reminder is a boolean, either a yes or a no. Booleans are a perfect application for attributes because they explicitly modify the state of an element.

Again, there are no clear-cut rules for when to use attributes and when to use elements. You have to use a combination of consensus among the other developers you are working with and your own personal preferences. But as you can see from this example, there are often as many ways to structure an XML document as there are to write a sentence. Let your applications dictate how you structure your documents.

Now, if we take our document and populate it with some data, we get the results shown in Listing 3.1.

Listing 3.1 A Complete, Well-Formed XML Document with Data

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
 <event date="03-05-02" start-time="09:00" end-time="10:00">
 <title>Staff Meeting</title>
 <description>Weekly staff meeting</description>
 <location>Conference Room</location>
 <reminder status="no"/>

 <event date="03-06-02" start-time="14:00" end-time="15:00">
 <title>Developer Interview</title>
 <description>Interview new developer candidate.</description>
 <reminder status="yes" interval="15-min" method="ICQ"/>

 <event date="03-15-02" start-time="13:45" end-time="15:00">
 <title>Root Canal</title>
 <description>Root canal on lower left molar.</description>
 <location>Dr. Scrivello's Office</location>
 <reminder status="yes" interval="1-day" method="e-mail"/>

This is a simple document, but it does utilize all the concepts outlined here. The element and attribute names meet the naming requirements, the elements are properly nested, with proper start and end tags. The document contains a single root element, appointments, and there are no errors in the content that would cause parsing problems, such as a < symbol. Yet, this document could be used by a calendar application to store information about appointments. That is the power of XML: Documents do not have to be overly complicated in order to be useful.

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