Home > Articles > Web Services > XML

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

This chapter is from the book

A Simple Airline Ticket Itinerary DTD

In this section, let's take a look at building a simple DTD, so that we have a solid understanding of the DTD's structure and the process of converting the DTD into an XML Schema. Because we have not dealt extensively with the mechanics of Schema yet, we will keep this example very straightforward and simple. But it's still a good idea to cover this kind of information now, so that you have these types of applications in mind going forward, as we learn about the finer details of XML Schema.

For this example, we are going to build a DTD that could be used to describe an airline ticket itinerary. This would include information about the flight and airline, including departure times, arrival times, seating information, flight duration, and so on. Of course, if we were actually building an application for the travel industry, this type of schema could be very complex, but for our application, we will limit the data to the basics, so it should be easy to follow.

Design Goals for a Ticket Itinerary XML Document

What kind of information needs to be contained in our ticket itinerary document? Well, let's start off by making our root element <itinerary>, and then creating a child element called <ticket> that contains the actual ticket information.

Within that ticket, we will need information about the airline, the flight number, departing information, arrival information, and some details about the flight.

So, let's create some elements for that information, say <airline>, <flight>, <departing>, and <arriving>, to deal with the details. It's also pretty common to have information about the seating arrangements, and some details like the mileage and duration of the flight.

Of course, there are more details that we need in the document. For example, we need the date and time of the departure and arrival. It would probably also be a good idea to include information about the gate and airport of the flights, since many areas have more than one airport.

We could also include some information about the seating arrangements for the flight, as that can also be known in advance. For this type of information, we'll use attributes. Is it better to use attributes for this information? Maybe, maybe not. There are no hard, fast rules for designing this kind of information. However, for detail-oriented information like this which describes an element (like an adjective describes a noun), attributes are certainly appropriate.

So, let's take a look at the elements we have for our document so far. The elements (and the attributes) are summarized in Table 3.2.

Table 3.2 An Overview of the Ticket Itinerary Elements

Element

Attributes

Description

itinerary

None

The document root element. Parent to the <ticket> child element.

ticket

None

The ticket serves as the parent element for all of the children containing information about the airline ticket.

airline

None

The name of the airline.

flight

None

The flight number for the ticket.

departing

date, time, airport, gate

An element for the departing information about the flight, with attributes for the details.

arriving

date, time, airport, gate

An element for the arriving information about the flight, with attributes for the details.

miles

None

The total mileage of the flight.

seating

class, seat

The seating assignment for the flight.

duration

None

The duration of the flight in hours and minutes.


Those elements will make up the bulk of our document. And the remaining information will be stored in attributes, as outlined in Table 3.3.

Table 3.3 An Overview of the Attributes for the Ticket Itinerary Elements

Attribute

Description

date

An attribute describing the day, month, and year.

time

The time of the flight.

airport

The three-letter airport code.

gate

The boarding gate of the flight.

class

The seating class.

seat

The seat number assignment.


Now that you have an outline, build an XML document which uses the elements and attributes outlined in Tables 3.2 and 3.3. It would look something like Listing 3.1

Listing 3.1 The XML Document for an Airline Ticket Itinerary

<?xml version="1.0" encoding="UTF-8" ?>
<itinerary>
 <ticket>
 <airline>American</airline>
 <flight>4090</flight>
 <departing date="10-Apr-01" time="6:45AM" airport="IND" gate="A20" />
 <arriving date="10-Apr-01" time="7:52AM" airport="ORD" gate="B64" />
 <miles>168</miles>
 <seating class="Coach" seat="D3"/>
 <duration>1hr 7mn</duration>
 </ticket>
</itinerary>

Describing the Ticket Itinerary XML Document in a DTD

Okay, now that we have an outline of the elements and attributes for our document, and we have an idea of what we want our final document to look like, let's take a look at the DTD.

The first thing we need to do is define the root <itinerary> element, which will contain the <ticket> element. We can do that with a simple element declaration:

<!ELEMENT itinerary (ticket*)>

The * following the ticket element simply indicates that the itinerary may contain more than one ticket. Next, we need to declare the ticket element, and specify the content model:

<!ELEMENT ticket (airline, flight, departing, arriving, miles, seating, duration)>

Here, the ticket element contains a number of elements which will hold the data about the ticket. Note that none of the *, +, or ? symbols were used, which indicates that each of these elements will be used exactly once per ticket element.

Now we can move on to declaring our other elements. These elements are very straightforward. Since they will all simply contain text, we can use a very simple element declaration:

<!ELEMENT airline (#PCDATA)>

For the elements such as departing which will not have any content, but instead use attributes, we could use the EMPTY keyword in place of #PCDATA. However, in order to keep this DTD (and the later conversion to a Schema) as simple as possible, we'll just leave them as #PCDATA. That gives us the following as the rest of our element declarations:

<!ELEMENT flight (#PCDATA)>
<!ELEMENT departing (#PCDATA)>
<!ELEMENT arriving (#PCDATA)>
<!ELEMENT seating (#PCDATA)>
<!ELEMENT miles (#PCDATA)>
<!ELEMENT duration (#PCDATA)>

We now have all of our elements defined. Next, we need to declare our attributes. This is done with the ATTLIST declaration:

<!ATTLIST departing
  date  CDATA #REQUIRED
  time  CDATA #REQUIRED
  airport CDATA #REQUIRED
  gate  CDATA #IMPLIED>

The ATTLIST declaration allows us to specify the element we are declaring attributes for, and then list the attributes, followed by the value type (CDATA) and then by a keyword which indicates whether an attribute is #REQUIRED or #IMPLIED. Of course, required attributes must be used, while implied attributes are optional. Our ATTLIST declaration for the arriving element is the same as our declaration for the departing element, since they have the same attributes:

<!ATTLIST arriving
  date  CDATA #REQUIRED
  time  CDATA #REQUIRED
  airport CDATA #REQUIRED
  gate  CDATA #IMPLIED>

Finally, we declare the attributes for our seating element:

<!ATTLIST seating
  class CDATA #REQUIRED
  seat CDATA #IMPLIED>

Now all of the pieces for our DTD are done, and if we pull them all together, we get the final code for the Airline Ticket Itinerary as shown in Listing 3.2.

Listing 3.2 The DTD Describing an Airline Ticket Itinerary

<!-- A Simple Airline Ticket Itinerary DTD -->

<!ELEMENT itinerary (ticket*)>

<!ELEMENT ticket (airline, flight, departing, arriving, miles, seating,
duration)>

<!ELEMENT airline (#PCDATA)>

<!ELEMENT flight (#PCDATA)>

<!ELEMENT departing (#PCDATA)>
<!ATTLIST departing

Listing 3.2 Continued

  date  CDATA #REQUIRED
  time  CDATA #REQUIRED
  airport CDATA #REQUIRED
  gate  CDATA #IMPLIED>

<!ELEMENT arriving (#PCDATA)>
<!ATTLIST arriving
  date  CDATA #REQUIRED
  time  CDATA #REQUIRED
  airport CDATA #REQUIRED
  gate  CDATA #IMPLIED>

<!ELEMENT miles (#PCDATA)>

<!ELEMENT seating (#PCDATA)>
<!ATTLIST seating
  class  CDATA #REQUIRED
  seat  CDATA #IMPLIED>

<!ELEMENT duration (#PCDATA)>
  • + 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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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