Three updated working draft specifications have been released by the W3C Document Object Model (DOM) Working Group. The W3C Document Object Model is "a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model provides a standard set of objects for representing HTML and XML documents, a standard model of how these objects can be combined, and a standard interface for accessing and manipulating them. Vendors can support the DOM as an interface to their proprietary data structures and APIs, and content authors can write to the standard DOM interfaces rather than product-specific APIs, thus increasing interoperability on the Web." The updated Document Object Model (DOM) Requirements specification covers principally DOM Level 3 Requirements (Core, Content Models and Validation Use Cases and Requirements, Load and Save Requirements, Embedded DOM Requirements, XPath DOM Draft Requirements). The Document Object Model (DOM) Level 3 Events Specification Version 1.0 defines the Document Object Model Events Level 3 which builds on the Document Object Model Events Level 2. The three appendices document IDL Definitions, a Java Language Binding, and an ECMA Script Language Binding. The updated version 1.0 Document Object Model (DOM) Level 3 Content Models and Load and Save Specification has two major sections: (1) one "describes the optional DOM Level 3 Content Model (CM) feature; this module provides a representation for XML content models, e.g., DTDs and XML Schemas, together with operations on the content models, and how such information within the content models could be applied to XML documents used in both the document-editing and CM-editing worlds. (2) the second specifies an API for loading XML source documents into a DOM representation and for saving a DOM representation as a XML document."

Document Object Model (DOM) Requirements. W3C Working Draft 19-April-2001. Edited by Ben Chang, Oracle; Mike Champion, Software AG; James Davidson, Sun; Angel Diaz, IBM; Andy Heninger, IBM; Joe Kesselman, IBM; Philippe Le Hégaret, W3C, chair; Arnaud Le Hors, IBM; Tom Pixley, Netscape Communications Corporation; Jared Sorensen, Novell, Inc.; Ray Whitmer, Netscape Communications Corporation Lauren Wood, SoftQuad Software Inc. Latest version URL: http://www.w3.org/TR/DOM-Requirements. "This document contains the requirements for the Document Object Model, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model provides a standard set of objects for representing HTML and XML documents, a standard model of how these objects can be combined, and a standard interface for accessing and manipulating them. Vendors can support the DOM as an interface to their proprietary data structures and APIs, and content authors can write to the standard DOM interfaces rather than product-specific APIs, thus increasing interoperability on the Web."

Document Object Model (DOM) Level 3 Events Specification Version 1.0. W3C Working Draft 10-April-2001. Edited by Tom Pixley (Netscape Communications Corporation). Latest version URL: http://www.w3.org/TR/DOM-Level-3-Events. "This specification defines the Document Object Model Events Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2... The goal of the DOM Level 3 Events specification is to expand upon the functionality specified in the DOM Level 2 Event Specification. The specification does this by adding new interfaces which are complimentary to the interfaces defined in the DOM Level 2 Event Specification as well as adding new event modules to those already defined. This specification requires the previously designed interfaces in order to be functional. It is not designed to be standalone. These interfaces are not designed to supercede the interfaces already provided but instead to add to the functionality contained within them."

Document Object Model (DOM) Level 3 Content Models and Load and Save Specification. W3C Working Draft 19-April-2001. Edited by: Ben Chang, Oracle; Andy Heninger, IBM; Joe Kesselman, IBM; Rezaur Rahman, Intel Corporation. Latest version URL: http://www.w3.org/TR/DOM-Level-3-CMLS. "This specification defines the Document Object Model Content Models and Load and Save Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Content Models and Load and Save Level 3 builds on the Document Object Model Core Level 3. [1] This 'Content Models' chapter describes the optional DOM Level 3 Content Model (CM) feature. This module provides a representation for XML content models, e.g., DTDs and XML Schemas, together with operations on the content models, and how such information within the content models could be applied to XML documents used in both the document-editing and CM-editing worlds. It also provides additional tests for well-formedness of XML documents, including Namespace well-formedness. A DOM application can use the hasFeature method of theDOMImplementation interface to determine whether a given DOM supports these capabilities or not. One feature string for the CM-editing interfaces listed in this section is '"CM-EDIT' and another feature string for document-editing interfaces is 'CM-DOC'. This chapter interacts strongly with the Load and Save chapter, which is also under development in DOM Level 3. Not only will that code serialize/deserialize content models, but it may also wind up defining its well-formedness and validity checks in terms of what is defined in this chapter. In addition, the CM and Load/Save functional areas will share a common error-reporting mechanism allowing user-registered error callbacks. Note that this may not imply that the parser actually calls the DOM's validation code -- it may be able to achieve better performance via its own -- but the appearance to the user should probably be 'as if' the DOM has been asked to validate the document, and parsers should probably be able to validate newly loaded documents in terms of a previously loaded DOM CM... [2] Load and Save Requirements DOM Level 3 will provide an API for loading XML source documents into a DOM representation and for saving a DOM representation as a XML document. Some environments, such as the Java platform or COM, have their own ways to persist objects to streams and to restore them. There is no direct relationship between these mechanisms and the DOM load/save mechanism. This specification defines how to serialize documents only to and from XML format."