Home > Articles

The Details of the Document Object Model (DOM)

  • Print
  • + Share This
In this chapter from "XML Development with Java 2," the authors cover the details of the Document Object Model, focusing in particular on the DOMII APIs.
This chapter is from the book

This chapter is from the book

"The Document Object Model is an Applications Programming Interface for HTML and XML documents."
—W3C, Document Object Model Level 1 Specification

IN THIS CHAPTER

  • Defining the Document Object Model
  • DOM Core Level I
  • Creating Document Objects
  • Node Interface
  • NodeList and NamedNodeMap
  • Document Interface
  • Element Interface
  • Attr Interface
  • Additional Interfaces
  • Creating DOM Elements
  • DOM Level II
  • The DOM Core Defined
  • Implementation Anomalies

Defining the Document Object Model

The term "model" is one of those all-purpose terms that everyone uses. For our purposes, a model is a representation of an object. Models can be complete, incomplete, or somewhere in between. In the case of DOM, the model represents an XML document. An incomplete model only partially replicates the object it models, whereas a complete model mimics everything down to the smallest detail. In the DOM specification, each element of an XML document is represented, making the DOM a complete model. The DOM also defines a set of interfaces that developers, and perhaps others, can implement allowing concrete programmatic representations of XML documents. In essence, the DOM is three things:

  • Model— The DOM models an XML document. The DOM serves as a complete model representing each and every aspect of an XML object, allowing that object to be completely re-created from the model's data. The DOM Core Level I is a complete model providing for all the required manipulations. The DOM Core Specification says explicitly that "With the Document Object Model, programmers can build documents, navigate their structure, and add, modify, or delete elements and content."

  • Set of Requirements— The DOM is a set of requirements, defined by the W3C, that each implementation of the DOM must follow. The next section introduces and discusses the DOM implementation requirements.

  • Set of Object Definitions— The DOM is an object-oriented specification that specifies a set of interfaces, properties, and behaviors for each object. We will examine the interfaces in detail shortly. Examples of properties are getNodeName, getParentNode, and getChildNodes. DOM Object definitions also require that every DOM object follow certain behavioral patterns. An example of these patterns is that each object can have only one parent and can have zero or more children. The exception to this pattern is the root document, which does not have any parents.

At first glance, the DOM appears to be one more thing, an implementation. While individual companies may implement the DOM, the W3C specification provides no implementation. The specification leaves implementation to Sun, IBM, Oracle, or to any user. Anyone could, in fact, implement a DOM. Last time I checked, there were implementations for C++, Python, Perl, Smalltalk, Gecko, and a slew of other languages. For Java alone, companies such as Sun, Microsoft, Netscape, Oracle, IBM, Docuverse and others had all committed to supporting the DOM in one fashion or another and providing Java implementations. Let's now get back to what the W3C actually defined and how we might use it.

DOM Requirements

Because the W3C defines specifications rather than implementations, it needs to define the general requirement of any implementation. The following list, taken directly from the W3C's requirements document for DOM, defines each of these requirements. Let's now look at each to understand what they mean.

  • The Document Object Model (DOM) is an Applications Programming Interface (API) for HTML and XML— Simple enough, the DOM defines the APIs through which we access XML documents.

  • The Object Model is language neutral and platform independent— This is perhaps one of the most important aspects of the DOM, DOM specification is not dependent on any specific platform or language. As a result of the independence of the specification, developers are free to provide an implementation in any available language. All the DOM does is specify what interfaces, methods, attributes, and properties the DOM objects provide.

  • There will be a core DOM that is applicable to HTML, CSS and XML documents— Basically, the DOM Core supports only HTML, CSS, and XML. Don't expect to process some other language with the DOM.

  • The Object Model can be used to construct and deconstruct the document— Models typically vary in how complete they are. The DOM is defined to be complete. Anything that you can validly create can also be read later.

  • The Object Model will not preclude use by either agents external to the document content, or scripts embedded within the document— The DOM will not stop you from processing your XML document with some other method (perhaps SAX or your own parser).

  • Consistent naming conventions must be used through all levels of the Object Model— Properties are properties are properties! A good model is consistent and doesn't change its nomenclature for different objects or at different levels.

  • A visual UI component will not be required for a conforming implementation of the Object Model— The DOM is a programming API and is not designed around how a document is displayed. No requirements are imposed on how the developer presents DOM modeled documents.

  • The specific HTML, CSS or XML document object models will be driven by the underlying constructs of those languages— Simply put, DOM objects follow the ebb and flow of the thing they represent rather than force all documents to be represented in a generic format.

  • It must be possible to read in a document and write out a structurally isomorphic document— If you read in and write out a document, the end result will be the same as the starting result (assuming that you didn't change anything).

  • The Object Model will not expose the user to problems with security, validity, or privacy— DOM Implementors must not reply on platform, security, or language-specific mechanisms to process XML and HTML documents.

  • The Object Model will not preclude other mechanisms for manipulating documents— If you have another way for processing your documents, great! The DOM is not the only game in town. You aren't forced to use it if you don't want to!

In addition to the things the DOM is, there are a number of things that are beyond the scope of the DOM. The following list describes some of what the DOM specifically is not or does not provide for.

  • The DOM does not implement all of "Dynamic HTML," in particular, events— The DOM Core Level I does not specify everything under the sun but rather sets a sound foundation for processing XML. Events and other important but secondary concepts are left to Level II.

  • The DOM is not a binary specification— While the DOM specifies a number of interfaces, it does not require anything beyond source level compatibility between documents.

  • The DOM is not a way of persisting objects to XML— The DOM specifies how XML objects are represented via an API but leaves the external representation to XML. The primary focus of DOM is to define how objects can be used in programs, not how they are stored externally.

  • The DOM is not a set of data structures— While the DOM represents parent/child relationships, these relationships are logical and may be implemented as required.

  • The DOM does not define "the true inner semantics" of XML— While XML documents are represented as objects within DOM, their underlying semantics are defined by the XML language specification and not by the DOM itself. The DOM is simply a vehicle through which these semantics of an XML document can be manipulated.

  • The DOM, despite its name, does not compete with COM (The Component Object Model)— COM is a mechanism to specify binary interfaces and objects for runtime interoperability in much the same way the Common Object Request Broker Architecture (CORBA) does. The DOM specifies a number of logical objects and interfaces but does not specify any binary level compatibility.

  • + 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