Home > Articles > Programming > Java

Like this article? We recommend

Like this article? We recommend

A Sample Conversion

Let's take a look at converting a DTD into an XML Schema. We'll start with an XML instance document that describes a basic airline ticket itinerary:

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

Here's the DTD that describes this document:

<!-- 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
   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)>

First, because XML Schemas are XML documents, we need to start off with the XML declaration, and then the schema element with the XML Schema namespace:

<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <!-- Schema content -->
</xs:schema>

Because the <itinerary> element is going to contain other elements, we need to create the tags that will allow us to include other elements inside the element:

<xs:element name="itinerary">
 <xs:complexType>
 <xs:sequence>
  <!-- Ticket element information -->
 </xs:sequence>
 </xs:complexType>
</xs:element>

<complexType> and <sequence> establish that the itinerary element is a complex type, and that it will contain a sequence of other elements, which we will then specify by nesting their declarations in the <sequence> tags. This nested method of creating element declarations is called the Russian Doll method, as mentioned in an earlier article in this series. This method is often the simplest way of converting a DTD, because it describes the content model simultaneously with the element declarations, much like a DTD.

With the itinerary element declared, now we can move on to declaring our ticket element, which is going to follow the same structure:

<xs:element name="ticket" maxOccurs="unbounded">
 <xs:complexType>
 <xs:sequence>
  <!-- Ticket content -->
 </xs:sequence>
 </xs:complexType>
</xs:element>

The only difference, aside from the name, is that the ticket declaration also makes use of the maxOccurs="unbounded" attribute. This is an attribute that allows us to specify that there may be any number of ticket elements inside an itinerary, which is similar to using the * symbol in a DTD.

The next element is the <airline> element, which only has text as the content, and is therefore a simple type:

<xs:element name="airline" type="xs:string"/>

Here, we only make use of the type attribute to specify that the element is a string. In fact, we can define our flight, miles, and duration elements in the same way, since they also don't have any complex content or any attributes:

<xs:element name="flight" type="xs:string"/>
<xs:element name="miles" type="xs:string"/>
<xs:element name="duration" type="xs:string"/>

With those elements out of the way, we only have three elements remaining to define: departing, arriving, and seating. The syntax for declaring our departing and arriving elements are nearly identical, save the value of the name. They will both look like this:

<xs:element name="arriving">
 <xs:complexType>
 <xs:attribute name="date" type="xs:string" use="required"/>
 <xs:attribute name="time" type="xs:string" use="required"/>
 <xs:attribute name="airport" type="xs:string" use="required"/>
 <xs:attribute name="gate" type="xs:string" use="optional"/>
 </xs:complexType>
</xs:element>

Each of the attributes is given a unique name. All of the attributes share the same type, string, since they will all contain text as their values. But note that, similar to the #REQUIRED and #IMPLIED keywords in the DTD, in the Schema we can use the use attribute with required or optional to specify whether an attribute has to be used.

Now we only have one remaining element to declare, seating, which also has attributes:

<xs:element name="seating">
 <xs:complexType>
 <xs:attribute name="class" type="xs:string" use="required"/>
 <xs:attribute name="seat" type="xs:string" use="optional"/>
 </xs:complexType>
</xs:element>

If we were to pull together these elements now, we would have an XML Schema that duplicates the functionality of the DTD. However, because we're working with an XML Schema, we can extend the base schema to add some new functionality.

Extending the DTD

We can do something to improve our base converted schema, and it's not complicated. Both the arriving and departing elements feature a date and a time attribute that stores information about the flight. Since the XML Schema Recommendation has both a date and a time datatype, we could use both in our schema, to reflect the content of those elements:

<xs:attribute name="date" type="xs:date" use="required"/>
<xs:attribute name="time" type="xs:time" use="required"/>

Now we're ready to bring it all together.

The Finished Schema

Bringing together all of the components yields the following XML Schema:

<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:annotation>
 <xs:documentation>
 A Simple Airline Ticket Itinerary XML Schema
 </xs:documentation>
</xs:annotation>

<xs:element name="itinerary">
 <xs:complexType>
 <xs:sequence>
  <xs:element name="ticket" maxOccurs="unbounded">
  <xs:complexType>
   <xs:sequence>
   <xs:element name="airline" type="xs:string"/>
   <xs:element name="flight" type="xs:string"/>
   <xs:element name="departing">
    <xs:complexType>
    <xs:attribute name="date" type="xs:date" use="required"/>
    <xs:attribute name="time" type="xs:time" use="required"/>
    <xs:attribute name="airport" type="xs:string" use="required"/>
    <xs:attribute name="gate" type="xs:string" use="optional"/>
    </xs:complexType>
   </xs:element>
   <xs:element name="arriving">
    <xs:complexType>
    <xs:attribute name="date" type="xs:date" use="required"/>
    <xs:attribute name="time" type="xs:time" use="required"/>
    <xs:attribute name="airport" type="xs:string" use="required"/>
    <xs:attribute name="gate" type="xs:string" use="optional"/>
    </xs:complexType>
   </xs:element>
   <xs:element name="seating">
    <xs:complexType>
    <xs:attribute name="class" type="xs:string" use="required"/>
    <xs:attribute name="seat" type="xs:string" use="optional"/>
    </xs:complexType>
   </xs:element>
   <xs:element name="miles" type="xs:string"/>
   <xs:element name="duration" type="xs:string"/>
   </xs:sequence>
  </xs:complexType>
  </xs:element>
 </xs:sequence>
 </xs:complexType>
</xs:element>

</xs:schema>

We can now associate the XML Schema with the instance document using the XML instance namespace and the noNamespaceSchemaLocation attribute. We use the noNamespaceSchemaLocation because we're not using a namespace in conjunction with this schema. We can also use the date and time elements using the properly formatted data to comply with the datatypes:

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

<itinerary xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:noNamespaceSchemaLocation="itinerary.xsd">
 <ticket>
 <airline>American</airline>
 <flight>4090</flight>
 <departing date="2001-04-02" time="06:45:00-05:00"
  airport="IND" gate="A20" />
 <arriving date="2001-04-02" time="07:52:00-05:00"
  airport="ORD" gate="B64" />
 <seating class="Coach" seat="D3"/>
 <miles>168</miles>
 <duration>1hr 7mn</duration>
 </ticket>
</itinerary>

As the complexity of the DTD increases, obviously so does the time required to convert the DTD to an XML Schema. However, because XML Schemas have increased functionality built in, the resulting XML Schema can sometimes be simpler.

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