Home > Articles

This chapter is from the book

Digging Deeper into Elements

To declare an element in a DTD, you must use an element declaration, which takes the following form:

<!ELEMENT ElementName Type>

The name of the element determines the name of the tag(s) used to mark up the element in a document and corresponds to ElementName in the element declaration. This name must be unique within the context of a DTD. The type of the element is specified in Type; XML supports four different types of elements, which are determined by the content contained within the element:

  • Empty—The element doesn’t contain any content (it can still contain attributes).
  • Element-only—The element only contains child elements.
  • Mixed—The element contains a combination of child elements and character data.
  • Any—The element contains any content allowed by the DTD.

The next few sections explore the different element types in more detail.

Peeking Inside Empty Elements

An empty element is an element that doesn’t contain any element content. An empty element can still contain information, but it must do so using attributes. Empty elements are declared using the following form:

<!ELEMENT ElementName EMPTY>

Following is an example of declaring an empty element using this form:

<!ELEMENT clothing EMPTY>

After an empty element is defined in a DTD, you can use it in a document in one of two ways:

  • With a start tag/end tag pair
  • With an empty tag

Following is an example of an empty element defined using a start tag/end tag pair:

<clothing></clothing>

Notice that no content appears between the tags; if any content did appear, even a single space, the document would be invalid. A more concise approach to defining empty elements is to use an empty tag. Following is an example of using an empty tag to define an empty element:

<clothing />

As you can see, an empty tag is somewhat of a combination of a start tag and end tag. In addition to being more concise, empty tags help to make it clear in a document that an element is empty and therefore can’t contain content. Remember that empty elements can still contain information in attributes. Following is an example of how you might use a few attributes with an empty element:

<clothing type="t-shirt" color="navy" size="xl" />

Housing Children with Element-Only Elements

An element-only element contains nothing but child elements. In other words, no text content is stored within an element-only element. An element is declared element-only by simply listing the child elements that can appear within the element, which is known as the element’s content model. Following is the form expected for declaring an element’s content model:

<!ELEMENT ElementName ContentModel>

The content model is specified using a combination of special element declaration symbols and child element names. The symbols describe the relationship between child elements and the container element. Within the content model, child elements are grouped into sequences or choice groups using parentheses (()). A sequence of child elements indicates the order of the elements, whereas a choice group indicates alternate possibilities for how the elements are used. Child elements within a sequence are separated by commas (,), whereas elements in a choice group are separated by pipes (|). Following are the different element declaration symbols used to establish the content model of elements:

  • Parentheses (())—Encloses a sequence or choice group of child elements
  • Comma (,)—Separates the items in a sequence, which establishes the order in which they must appear
  • Pipe (|)—Separates the items in a choice group of alternatives
  • No symbol—Indicates that a child element must appear exactly once
  • Question mark (?)—Indicates that a child element must appear exactly once or not at all
  • Plus sign (+)—Indicates that a child element must appear at least once
  • Asterisk (*)—Indicates that a child element can appear any number of times

Although I could use several paragraphs to try and explain these element declaration symbols, I think an example is much more explanatory. Following is the declaration for an element named resume that might be used in a resume markup language:

<!ELEMENT resume (intro, (education | experience+)+, hobbies?, references*)>

The resume element is pretty interesting because it demonstrates the usage of every element declaration symbol. The resume element is element-only, which is evident by the fact that it contains only child elements. The first child element is intro, which must appear exactly once within the resume element; this is because no symbols are used with it. The education or experience elements must then appear at least once, which is indicated by the plus sign just outside of the parentheses. Within the parentheses, the education element must appear exactly once, whereas the experience element must appear at least once but can also appear multiple times. The idea is to allow you to list part of your education followed by any relevant work experience; you may have worked multiple jobs following a single block of education. The hobby element can appear exactly once or not at all; all of your hobbies must be listed within a single hobby element. Finally, the references element can appear any number of times.

To get a practical feel for how element-only elements affect XML documents in the real world, take a look at the following line of code from the DTD for the RSS language:

<!ELEMENT item (title | link | description)*>

RSS is an XML-based language that is used to syndicate web sites so that applications and other web sites can obtain brief descriptions of new articles and other content. For example, Sports Illustrated (http://sportsillustrated.cnn.com/) offers RSS news feeds for all major sports. Other web sites can tap into these feeds or you can use an RSS aggregator application such as FeedDemon(http://www.feeddemon.com/), which allows you to view news feeds much like you view email in an email client.

Anyway, getting back to the RSS DTD, the previous line of code reveals that the item element can contain any combination of title, link, or description elements as long as there is no more than one of each. To see how this DTD translates into real XML code, check out the following excerpt from a real Sports Illustrated NFL news feed:

<item>
 <title>Titans’ trio of young WRs showing promise</title>
 <link>http://sportsillustrated.cnn.com/rssclick/2005/football/nfl/06/22/
 bc.fbn.titans.receivers.ap/index.html?section=si_nfl</link>
 <description>Read full story for latest details.</description>
</item>

As this code reveals, the item element contains exactly one each of title, link, and description elements. To see how this code affects a real web page, check out the syndicated NFL news feed on my web site in Figure 3.1.

Figure 3.1

Figure 3.1 The example syndicated NFL news feed is visible on my web site.

The figure reveals how the Tennessee Titans news story shown in the previous RSS code is syndicated and visible as an RSS news feed on my web site.

In the next section you see how the individual RSS elements mentioned here are defined in the RSS DTD. You also find out more details about how to syndicate news feeds and create your own in Hour 24, "Syndicating the Web with RSS News Feeds."

Combining Content and Children with Mixed Elements

Mixed elements are elements that contain both character data (text) and child elements. The simplest mixed element is also known as a text-only element because it contains only character data. Text-only elements are declared using the following form:

<!ELEMENT ElementName (#PCDATA)>

The content model for text-only elements consists solely of the symbol #PCDATA contained within parentheses, which indicates that an element contains Parsed Character DATA. Following is an example of a simple text-only element declaration:

<!ELEMENT hobbies (#PCDATA)>

This element might be used to mark up a list of hobbies in an XML document that helps to describe you to other people. Following is an example of how you might define the hobbies element in a document:

<hobbies>juggling, unicycling, tight-rope walking</hobbies>

Speaking of examples, the following code shows the title, link, and description elements from the RSS DTD that you learned about in the previous section:

<!ELEMENT title (#PCDATA)>
<!ELEMENT link (#PCDATA)>
<!ELEMENT description (#PCDATA)>

As you can see, these elements are all defined as text-only elements, which makes sense given the sample RSS data you saw in the previous section.

In reality, a text-only element is just a mixed element that doesn’t contain any child elements. Mixed elements that contain both text data and child elements are declared very much like element-only elements, with the addition of a few subtle requirements. More specifically, the content model for a mixed element must contain a repeating choice list of the following form:

<!ELEMENT ElementName (#PCDATA | ElementList)*>

If this looks a little confusing at first, don’t worry. Let’s break it down. The symbol #PCDATA at the start of the choice list indicates that the mixed element can contain character data. The remainder of the choice list contains child elements, and resembles a regular element-only content model. Additional #PCDATA symbols may be interspersed throughout the content model to indicate that character data appears throughout the child elements. An asterisk (*) must appear at the end of the content model’s choice list to indicate that the entire choice group is optional—this is a requirement of mixed elements. Also, although a mixed element declaration constrains the type of child elements allowed, it doesn’t constrain the order of the elements or the number of times they may appear.

Although mixed elements provide a considerable amount of flexibility, they lack the structure of element-only elements. So, with the exception of text-only elements, you’re better off using element-only elements instead of mixed elements whenever possible; you can often get the equivalent of a mixed element by declaring attributes on a text-only element.

Keeping Your Options Open with Any Elements

The any element is the most flexible element of all because it has virtually no structure. The any element is declared using the symbol ANY, and earns its name by being able to contain any declared element types, character data, or a mixture of both. You can think of the any element as a mixed element with a wide-open content model. Following is the form used to declare an any element:

<!ELEMENT ElementName ANY>

Not surprisingly, the lack of structure associated with the any element makes it something you should avoid at all costs in a production DTD. I mention a production (completed) DTD because the any element is typically used only during the development of a DTD for testing purposes.

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