Document Object Model (DOM) Level 3 Core Specification

Document Object Model (DOM) Level 3 Core Specification 1.0

WD-DOM-Level-3-Core-20020806

W3C Working Draft

06 August 2002 http://www.w3.org/2002/08/WD-DOM-Level-3-Core-20020806 PostScript file ZIP file http://www.w3.org/DOM/Group/drafts/DOM-Level-3-Core http://www.w3.org/2002/07/WD-DOM-Level-3-Core-20020731/ Arnaud Le Hors IBM Philippe Le Hégaret W3C, WG Chair Lauren Wood SoftQuad, Inc. (WG Chair emerata, for DOM Level 1 and 2) Gavin Nicol Inso EPS (for DOM Level 1) Jonathan Robie Texcel Research and Software AG (for DOM Level 1) Mike Champion ArborText and Software AG (for DOM Level 1 from November 20, 1997) Steve Byrne JavaSoft (for DOM Level 1 until November 19, 1997)

This specification defines the Document Object Model Core 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 Core Level 3 builds on the Document Object Model Core Level 2 .

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This document contains the Document Object Model Level 3 Core specification.

This is a Working Draft for review by W3C members and other interested parties.

It is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or members of the DOM Working Group.

Comments on this document are invited and are to be sent to the DOM IG mailing list w3c-dom-ig@w3.org. An archive is available at http://lists.w3.org/Archives/Member/w3c-dom-ig/.

This document has been produced as part of the W3C DOM Activity. The authors of this document are the DOM Working Group members.

Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page.

A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.

Created in electronic form.

English

$Revision: 1.8 $

Expanded Table of Contents Copyright Notice

This document is published under the . The bindings within this document are published under the . The software license requires "Notice of any changes or modifications to the W3C files, including the date changes were made." Consequently, modified versions of the DOM bindings must document that they do not conform to the W3C standard; in the case of the IDL definitions, the pragma prefix can no longer be 'w3c.org'; in the case of the Java language binding, the package names can no longer be in the 'org.w3c' package.

W3C Document Copyright Notice and License

This section is a copy of the W3C Document Notice and License and could be found at http://www.w3.org/Consortium/Legal/copyright-documents-19990405.

http://www.w3.org/Consortium/Legal/

Public documents on the W3C site are provided by the copyright holders under the following license. The software or Document Type Definitions (DTDs) associated with W3C specifications are governed by the Software Notice. By using and/or copying this document, or the W3C document from which this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that you use:

A link or URL to the original W3C document.

The pre-existing copyright notice of the original author, or if it doesn't exist, a notice of the form: "Copyright © [$date-of-document] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but a textual representation is permitted.)

If it exists, the STATUS of the W3C document.

When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.

No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional requirements (documented in the Copyright FAQ) are satisfied, the right to create modifications or derivatives is sometimes granted by the W3C to individuals complying with those requirements.

THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders.

W3C Software Copyright Notice and License

This section is a copy of the W3C Software Copyright Notice and License and could be found at http://www.w3.org/Consortium/Legal/copyright-software-19980720

http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, and modify this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:

The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

Any pre-existing intellectual property disclaimers. If none exist, then a notice of the following form: "Copyright © [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/."

Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

What is the Document Object Model? Philippe Le Hégaret W3C Lauren Wood SoftQuad Software Inc. (for DOM Level 2) Jonathan Robie Texcel (for DOM Level 1) Introduction

The Document Object Model (DOM) is an application programming interface (API) for valid HTML and well-formed XML documents. It defines the logical structure of documents and the way a document is accessed and manipulated. In the DOM specification, the term "document" is used in the broad sense - increasingly, XML is being used as a way of representing many different kinds of information that may be stored in diverse systems, and much of this would traditionally be seen as data rather than as documents. Nevertheless, XML presents this data as documents, and the DOM may be used to manage this data.

With the Document Object Model, programmers can build documents, navigate their structure, and add, modify, or delete elements and content. Anything found in an HTML or XML document can be accessed, changed, deleted, or added using the Document Object Model, with a few exceptions - in particular, the DOM interfaces for the XML internal and external subsets have not yet been specified.

As a W3C specification, one important objective for the Document Object Model is to provide a standard programming interface that can be used in a wide variety of environments and applications. The DOM is designed to be used with any programming language. In order to provide a precise, language-independent specification of the DOM interfaces, we have chosen to define the specifications in Object Management Group (OMG) IDL , as defined in the CORBA 2.3.1 specification . In addition to the OMG IDL specification, we provide language bindings for Java and ECMAScript (an industry-standard scripting language based on JavaScript and JScript ).

OMG IDL is used only as a language-independent and implementation-neutral way to specify interfaces. Various other IDLs could have been used (, , , ...). In general, IDLs are designed for specific computing environments. The Document Object Model can be implemented in any computing environment, and does not require the object binding runtimes generally associated with such IDLs.

What the Document Object Model is

The DOM is a programming API for documents. It is based on an object structure that closely resembles the structure of the documents it models. For instance, consider this table, taken from an XHTML document:

<table> <tbody> <tr> <td>Shady Grove</td> <td>Aeolian</td> </tr> <tr> <td>Over the River, Charlie</td> <td>Dorian</td> </tr> </tbody> </table>

A graphical representation of the DOM of the example table is:

In the DOM, documents have a logical structure which is very much like a tree; to be more precise, which is like a "forest" or "grove", which can contain more than one tree. Each document contains zero or one doctype nodes, one document element node, and zero or more comments or processing instructions; the document element serves as the root of the element tree for the document. However, the DOM does not specify that documents must be implemented as a tree or a grove, nor does it specify how the relationships among objects be implemented. The DOM is a logical model that may be implemented in any convenient manner. In this specification, we use the term structure model to describe the tree-like representation of a document. We also use the term "tree" when referring to the arrangement of those information items which can be reached by using "tree-walking" methods; (this does not include attributes). One important property of DOM structure models is structural isomorphism: if any two Document Object Model implementations are used to create a representation of the same document, they will create the same structure model, in accordance with the XML Information Set .

There may be some variations depending on the parser being used to build the DOM. For instance, the DOM may not contain white spaces in element content if the parser discards them.

The name "Document Object Model" was chosen because it is an "object model" in the traditional object oriented design sense: documents are modeled using objects, and the model encompasses not only the structure of a document, but also the behavior of a document and the objects of which it is composed. In other words, the nodes in the above diagram do not represent a data structure, they represent objects, which have functions and identity. As an object model, the DOM identifies:

the interfaces and objects used to represent and manipulate a document

the semantics of these interfaces and objects - including both behavior and attributes

the relationships and collaborations among these interfaces and objects

The structure of SGML documents has traditionally been represented by an abstract data model, not by an object model. In an abstract data model, the model is centered around the data. In object oriented programming languages, the data itself is encapsulated in objects that hide the data, protecting it from direct external manipulation. The functions associated with these objects determine how the objects may be manipulated, and they are part of the object model.

What the Document Object Model is not

This section is designed to give a more precise understanding of the DOM by distinguishing it from other systems that may seem to be like it.

The Document Object Model is not a binary specification. DOM programs written in the same language binding will be source code compatible across platforms, but the DOM does not define any form of binary interoperability.

The Document Object Model is not a way of persisting objects to XML or HTML. Instead of specifying how objects may be represented in XML, the DOM specifies how XML and HTML documents are represented as objects, so that they may be used in object oriented programs.

The Document Object Model is not a set of data structures; it is an object model that specifies interfaces. Although this document contains diagrams showing parent/child relationships, these are logical relationships defined by the programming interfaces, not representations of any particular internal data structures.

The Document Object Model does not define what information in a document is relevant or how information in a document is structured. For XML, this is specified by the XML Information Set . The DOM is simply an API to this information set.

The Document Object Model, despite its name, is not a competitor to the Component Object Model . COM, like CORBA, is a language independent way to specify interfaces and objects; the DOM is a set of interfaces and objects designed for managing HTML and XML documents. The DOM may be implemented using language-independent systems like COM or CORBA; it may also be implemented using language-specific bindings like the Java or ECMAScript bindings specified in this document.

Where the Document Object Model came from

The DOM originated as a specification to allow JavaScript scripts and Java programs to be portable among Web browsers. "Dynamic HTML" was the immediate ancestor of the Document Object Model, and it was originally thought of largely in terms of browsers. However, when the DOM Working Group was formed at W3C, it was also joined by vendors in other domains, including HTML or XML editors and document repositories. Several of these vendors had worked with SGML before XML was developed; as a result, the DOM has been influenced by SGML Groves and the HyTime standard. Some of these vendors had also developed their own object models for documents in order to provide an API for SGML/XML editors or document repositories, and these object models have also influenced the DOM.

Entities and the DOM Core

In the fundamental DOM interfaces, there are no objects representing entities. Numeric character references, and references to the pre-defined entities in HTML and XML, are replaced by the single character that makes up the entity's replacement. For example, in:

the "&" will be replaced by the character "&", and the text in the P element will form a single continuous sequence of characters. Since numeric character references and pre-defined entities are not recognized as such in CDATA sections, or in the SCRIPT and STYLE elements in HTML, they are not replaced by the single character they appear to refer to. If the example above were enclosed in a CDATA section, the "&" would not be replaced by "&"; neither would the <p> be recognized as a start tag. The representation of general entities, both internal and external, are defined within the extended (XML) interfaces of .

Note: When a DOM representation of a document is serialized as XML or HTML text, applications will need to check each character in text data to see if it needs to be escaped using a numeric or pre-defined entity. Failing to do so could result in invalid HTML or XML. Also, implementations should be aware of the fact that serialization into a character encoding ("charset") that does not fully cover ISO 10646 may fail if there are characters in markup or CDATA sections that are not present in the encoding.

Conformance

This section explains the different levels of conformance to DOM Level 3. DOM Level 3 consists of ? modules. It is possible to conform to DOM Level 3, or to a DOM Level 3 module.

An implementation is DOM Level 3 conformant if it supports the Core module defined in this document (see ). An implementation conforms to a DOM Level 3 module if it supports all the interfaces for that module and the associated semantics.

Here is the complete list of DOM Level 3.0 modules and the features used by them. Feature names are case-insensitive.

Core module

defines the feature "Core".

XML module

Defines the feature "XML".

Events module

defines the feature "Events" in .

User interface Events module

defines the feature "UIEvents" in .

Mouse Events module

defines the feature "MouseEvents" in .

Text Events module

defines the feature "TextEvents" in .

Mutation Events module

defines the feature "MutationEvents" in .

HTML Events module

defines the feature "HTMLEvents" in .

Load and Save module

defines the feature "LS" in .

XPath module

defines the feature "XPath" in .

A DOM implementation must not return true to the hasFeature(feature, version) method of the DOMImplementation interface for that feature unless the implementation conforms to that module. The version number for all features used in DOM Level 3.0 is "3.0".

DOM Interfaces and DOM Implementations

The DOM specifies interfaces which may be used to manage XML or HTML documents. It is important to realize that these interfaces are an abstraction - much like "abstract base classes" in C++, they are a means of specifying a way to access and manipulate an application's internal representation of a document. Interfaces do not imply a particular concrete implementation. Each DOM application is free to maintain documents in any convenient representation, as long as the interfaces shown in this specification are supported. Some DOM implementations will be existing programs that use the DOM interfaces to access software written long before the DOM specification existed. Therefore, the DOM is designed to avoid implementation dependencies; in particular,

Attributes defined in the IDL do not imply concrete objects which must have specific data members - in the language bindings, they are translated to a pair of get()/set() functions, not to a data member. Read-only attributes have only a get() function in the language bindings.

DOM applications may provide additional interfaces and objects not found in this specification and still be considered DOM conformant.

Because we specify interfaces and not the actual objects that are to be created, the DOM cannot know what constructors to call for an implementation. In general, DOM users call the createX() methods on the Document class to create document structures, and DOM implementations create their own internal representations of these structures in their implementations of the createX() functions.

The Level 2 interfaces were extended to provide both Level 2 and Level 3 functionality.

DOM implementations in languages other than Java or ECMAScript may choose bindings that are appropriate and natural for their language and run time environment. For example, some systems may need to create a Document3 class which inherits from a Document class and contains the new methods and attributes.

DOM Level 3 does not specify multithreading mechanisms.

Document Object Model Core Arnaud Le Hors IBM Philippe Le Hégaret W3C Gavin Nicol Inso EPS (for DOM Level 1) Lauren Wood SoftQuad, Inc. (for DOM Level 1) Mike Champion ArborText and Software AG (for DOM Level 1 from November 20, 1997) Steve Byrne JavaSoft (for DOM Level 1 until November 19, 1997) Overview of the DOM Core Interfaces

This section defines a set of objects and interfaces for accessing and manipulating document objects. The functionality specified in this section (the Core functionality) is sufficient to allow software developers and web script authors to access and manipulate parsed HTML and XML content inside conforming products. The DOM Core API also allows creation and population of a Document object using only DOM API calls. A solution for loading a Document and saving it persistently is proposed in .

The DOM Structure Model

The DOM presents documents as a hierarchy of Node objects that also implement other, more specialized interfaces. Some types of nodes may have child nodes of various types, and others are leaf nodes that cannot have anything below them in the document structure. For XML and HTML, the node types, and which node types they may have as children, are as follows:

Document -- Element (maximum of one), ProcessingInstruction, Comment, DocumentType (maximum of one)

DocumentFragment -- Element, ProcessingInstruction, Comment, Text, CDATASection, EntityReference

DocumentType -- no children

EntityReference -- Element, ProcessingInstruction, Comment, Text, CDATASection, EntityReference

Element -- Element, Text, Comment, ProcessingInstruction, CDATASection, EntityReference

Attr -- Text, EntityReference

ProcessingInstruction -- no children

Comment -- no children

Text -- no children

CDATASection -- no children

Entity -- Element, ProcessingInstruction, Comment, Text, CDATASection, EntityReference

Notation -- no children

The DOM also specifies a NodeList interface to handle ordered lists of Nodes, such as the children of a Node, or the elements returned by the getElementsByTagName method of the Element interface, and also a NamedNodeMap interface to handle unordered sets of nodes referenced by their name attribute, such as the attributes of an Element. NodeList and NamedNodeMap objects in the DOM are live; that is, changes to the underlying document structure are reflected in all relevant NodeList and NamedNodeMap objects. For example, if a DOM user gets a NodeList object containing the children of an Element, then subsequently adds more children to that element (or removes children, or modifies them), those changes are automatically reflected in the NodeList, without further action on the user's part. Likewise, changes to a Node in the tree are reflected in all references to that Node in NodeList and NamedNodeMap objects.

Finally, the interfaces Text, Comment, and CDATASection all inherit from the CharacterData interface.

Memory Management

Most of the APIs defined by this specification are interfaces rather than classes. That means that an implementation need only expose methods with the defined names and specified operation, not implement classes that correspond directly to the interfaces. This allows the DOM APIs to be implemented as a thin veneer on top of legacy applications with their own data structures, or on top of newer applications with different class hierarchies. This also means that ordinary constructors (in the Java or C++ sense) cannot be used to create DOM objects, since the underlying objects to be constructed may have little relationship to the DOM interfaces. The conventional solution to this in object-oriented design is to define factory methods that create instances of objects that implement the various interfaces. Objects implementing some interface "X" are created by a "createX()" method on the Document interface; this is because all DOM objects live in the context of a specific Document.

The Core DOM APIs are designed to be compatible with a wide range of languages, including both general-user scripting languages and the more challenging languages used mostly by professional programmers. Thus, the DOM APIs need to operate across a variety of memory management philosophies, from language bindings that do not expose memory management to the user at all, through those (notably Java) that provide explicit constructors but provide an automatic garbage collection mechanism to automatically reclaim unused memory, to those (especially C/C++) that generally require the programmer to explicitly allocate object memory, track where it is used, and explicitly free it for re-use. To ensure a consistent API across these platforms, the DOM does not address memory management issues at all, but instead leaves these for the implementation. Neither of the explicit language bindings defined by the DOM API (for ECMAScript and Java) require any memory management methods, but DOM bindings for other languages (especially C or C++) may require such support. These extensions will be the responsibility of those adapting the DOM API to a specific language, not the DOM Working Group.

Naming Conventions

While it would be nice to have attribute and method names that are short, informative, internally consistent, and familiar to users of similar APIs, the names also should not clash with the names in legacy APIs supported by DOM implementations. Furthermore, both OMG IDL and ECMAScript have significant limitations in their ability to disambiguate names from different namespaces that make it difficult to avoid naming conflicts with short, familiar names. So, DOM names tend to be long and descriptive in order to be unique across all environments.

The Working Group has also attempted to be internally consistent in its use of various terms, even though these may not be common distinctions in other APIs. For example, the DOM API uses the method name "remove" when the method changes the structural model, and the method name "delete" when the method gets rid of something inside the structure model. The thing that is deleted is not returned. The thing that is removed may be returned, when it makes sense to return it.

Inheritance vs. Flattened Views of the API

The DOM Core APIs present two somewhat different sets of interfaces to an XML/HTML document: one presenting an "object oriented" approach with a hierarchy of inheritance, and a "simplified" view that allows all manipulation to be done via the Node interface without requiring casts (in Java and other C-like languages) or query interface calls in COM environments. These operations are fairly expensive in Java and COM, and the DOM may be used in performance-critical environments, so we allow significant functionality using just the Node interface. Because many other users will find the inheritance hierarchy easier to understand than the "everything is a Node" approach to the DOM, we also support the full higher-level interfaces for those who prefer a more object-oriented API.

In practice, this means that there is a certain amount of redundancy in the API. The Working Group considers the "inheritance" approach the primary view of the API, and the full set of functionality on Node to be "extra" functionality that users may employ, but that does not eliminate the need for methods on other interfaces that an object-oriented analysis would dictate. (Of course, when the O-O analysis yields an attribute or method that is identical to one on the Node interface, we don't specify a completely redundant one.) Thus, even though there is a generic nodeName attribute on the Node interface, there is still a tagName attribute on the Element interface; these two attributes must contain the same value, but the it is worthwhile to support both, given the different constituencies the DOM API must satisfy.

The DOMString type

To ensure interoperability, the DOM specifies the following:

A DOMString is a sequence of 16-bit units.

Applications must encode DOMString using UTF-16 (defined in and Amendment 1 of ).

The UTF-16 encoding was chosen because of its widespread industry practice. Note that for both HTML and XML, the document character set (and therefore the notation of numeric character references) is based on UCS . A single numeric character reference in a source document may therefore in some cases correspond to two 16-bit units in a DOMString (a high surrogate and a low surrogate).

Even though the DOM defines the name of the string type to be DOMString, bindings may use different names. For example for Java, DOMString is bound to the String type because it also uses UTF-16 as its encoding.

As of August 2000, the OMG IDL specification () included a wstring type. However, that definition did not meet the interoperability criteria of the DOM API since it relied on negotiation to decide the width and encoding of a character.

The DOMTimeStamp type

To ensure interoperability, the DOM specifies the following:

A DOMTimeStamp represents a number of milliseconds.

unsigned long long

Even though the DOM uses the type DOMTimeStamp, bindings may use different types. For example for Java, DOMTimeStamp is bound to the long type. In ECMAScript, DOMTimeStamp is bound to the Date type because the range of the integer type is too small.

The DOMUserData type

To ensure interoperability, the DOM specifies the following:

A DOMUserData represents a reference to an application object.

Object

Even though the DOM uses the type DOMUserData, bindings may use different types. For example, in Java DOMUserData is bound to the Object type, while in ECMAScript DOMUserData is bound to any type.

What does DOMUserData map to in ECMAScript?

"any type"

The DOMObject type

To ensure interoperability, the DOM specifies the following:

A DOMObject represents a reference to an application object.

Object

Even though the DOM uses the type DOMObject, bindings may use different types. For example, in Java and ECMAScript DOMObject is bound to the Object type.

String comparisons in the DOM

The DOM has many interfaces that imply string matching. HTML processors generally assume an uppercase (less often, lowercase) normalization of names for such things as elements, while XML is explicitly case sensitive. For the purposes of the DOM, string matching is performed purely by binary comparison of the 16-bit units of the DOMString. In addition, the DOM assumes that any case normalizations take place in the processor, before the DOM structures are built.

The W3C Text normalization, as defined in , is assumed to happen at serialization time. The DOM Level 3 Load and Save module provides a serialization mechanism (see the DOMWriter interface, section 2.3.1) and defines the "ls-normalize-characters" to assure that text is serialized in the W3C Text Normalization form. Other serialization mechanisms built on top of the DOM Level 3 Core also have to assure that text is serialized in the W3C Text Normalization form.

We need to review the case sensitivity of methods and attributes and how it fits with XML and HTML. Current wording is not clear at all ...

XML Namespaces

The DOM Level 2 (and higher) supports XML namespaces by augmenting several interfaces of the DOM Level 1 Core to allow creating and manipulating elements and attributes associated to a namespace.

As far as the DOM is concerned, special attributes used for declaring XML namespaces are still exposed and can be manipulated just like any other attribute. However, nodes are permanently bound to namespace URIs as they get created. Consequently, moving a node within a document, using the DOM, in no case results in a change of its namespace prefix or namespace URI. Similarly, creating a node with a namespace prefix and namespace URI, or changing the namespace prefix of a node, does not result in any addition, removal, or modification of any special attributes for declaring the appropriate XML namespaces. Namespace validation is not enforced; the DOM application is responsible. In particular, since the mapping between prefixes and namespace URIs is not enforced, in general, the resulting document cannot be serialized naively. For example, applications may have to declare every namespace in use when serializing a document.

In general, the DOM implementation (and higher) doesn't perform any URI normalization or canonicalization. The URIs given to the DOM are assumed to be valid (e.g., characters such as white spaces are properly escaped), and no lexical checking is performed. Absolute URI references are treated as strings and compared literally. How relative namespace URI references are treated is undefined. To ensure interoperability only absolute namespace URI references (i.e., URI references beginning with a scheme name and a colon) should be used. Applications that wish to have no namespace should use the value null as the namespaceURI parameter of methods. If they pass an empty string the DOM implementation turns it into a null.

In the DOM, all namespace declaration attributes are by definition bound to the namespace URI: "http://www.w3.org/2000/xmlns/". These are the attributes whose namespace prefix or qualified name is "xmlns". Although, at the time of writing, this is not part of the XML Namespaces specification , it is planned to be incorporated in a future revision.

In a document with no namespaces, the child list of an EntityReference node is always the same as that of the corresponding Entity. This is not true in a document where an entity contains unbound namespace prefixes. In such a case, the descendants of the corresponding EntityReference nodes may be bound to different namespace URIs, depending on where the entity references are. Also, because, in the DOM, nodes always remain bound to the same namespace URI, moving such EntityReference nodes can lead to documents that cannot be serialized. This is also true when the DOM Level 1 method createEntityReference of the Document interface is used to create entity references that correspond to such entities, since the descendants of the returned EntityReference are unbound. The DOM Level 2 does not support any mechanism to resolve namespace prefixes. For all of these reasons, use of such entities and entity references should be avoided or used with extreme care. A future Level of the DOM may include some additional support for handling these.

The new methods, such as createElementNS and createAttributeNS of the Document interface, are meant to be used by namespace aware applications. Simple applications that do not use namespaces can use the DOM Level 1 methods, such as createElement and createAttribute. Elements and attributes created in this way do not have any namespace prefix, namespace URI, or local name.

Given that the property [in-scope namespaces] defined in is not accessible from DOM Level 3 Core, the properties [prefix] and [namespace name] defined by the Namespace Information Item in are not accessible from DOM Level 3 Core. However, does provide a way to access them.

DOM Level 1 methods are namespace ignorant. Therefore, while it is safe to use these methods when not dealing with namespaces, using them and the new ones at the same time should be avoided. DOM Level 1 methods solely identify attribute nodes by their nodeName. On the contrary, the DOM Level 2 methods related to namespaces, identify attribute nodes by their namespaceURI and localName. Because of this fundamental difference, mixing both sets of methods can lead to unpredictable results. In particular, using setAttributeNS, an element may have two attributes (or more) that have the same nodeName, but different namespaceURIs. Calling getAttribute with that nodeName could then return any of those attributes. The result depends on the implementation. Similarly, using setAttributeNode, one can set two attributes (or more) that have different nodeNames but the same prefix and namespaceURI. In this case getAttributeNodeNS will return either attribute, in an implementation dependent manner. The only guarantee in such cases is that all methods that access a named item by its nodeName will access the same item, and all methods which access a node by its URI and local name will access the same node. For instance, setAttribute and setAttributeNS affect the node that getAttribute and getAttributeNS, respectively, return.

Base URIs

The DOM Level 3 adds support for the [base URI] property defined in by providing a new attribute on the Node interface that exposes this information. However, unlike the namespaceURI attribute, the baseURI attribute is not a static piece of information that every node carries. Instead, it is a value that is dynamically computed according to . This means its value depends on the location of the node in the tree and moving the node from one place to another in the tree may affect its value. Other changes, such as adding or changing an xml:base attribute on the node being queried or one of its ancestors may also affect its value.

One consequence of this it that when external entity references are expanded while building a Document one may need to add, or update it if one already exists, an xml:base attribute to the Element nodes originally contained in the entity being expanded so that the baseURI returns the correct value. In the case of ProcessingInstruction nodes originally contained in the entity being expanded the information is lost. handles elements as described here and generates a warning in the latter case.

This does not work for PIs.

Info is lost, a warning is generated (Telcon 29 Apr 2002)

Mixed DOM implementations

As new XML vocabularies are developed, those defining the vocabularies are also beginning to define specialized APIs for manipulating XML instances of those vocabularies. This is usually done by extending the DOM to provide interfaces and methods that perform operations frequently needed their users. For example, the MathML and SVG specifications are developing DOM extensions to allow users to manipulate instances of these vocabularies using semantics appropriate to images and mathematics (respectively) as well as the generic DOM XML semantics. Instances of SVG or MathML are often embedded in XML documents conforming to a different schema such as XHTML.

While the XML Namespaces Recommendation provides a mechanism for integrating these documents at the syntax level, it has become clear that the DOM Level 2 Recommendation is not rich enough to cover all the issues that have been encountered in having these different DOM implementations be used together in a single application. DOM Level 3 deals with the requirements brought about by embedding fragments written according to a specific markup language (the embedded component) in a document where the rest of the markup is not written according to that specific markup language (the host document). It does not deal with fragments embedded by reference or linking.

A DOM implementation supporting DOM Level 3 Core should be able to collaborate with subcomponents implementing specific DOMs to assemble a compound document that can be traversed and manipulated via DOM interfaces as if it were a seamless whole.

The normal typecast operation on an object should support the interfaces expected by legacy code for a given document type. Typecasting techniques may not be adequate for selecting between multiple DOM specializations of an object which were combined at run time, because they may not all be part of the same object as defined by the binding's object model. Conflicts are most obvious with the Document object, since it is shared as owner by the rest of the document. In a homogeneous document, elements rely on the Document for specialized services and construction of specialized nodes. In a heterogeneous document, elements from different modules expect different services and APIs from the same Document object, since there can only be one owner and root of the document hierarchy.

Bootstrapping

Because previous versions of the DOM specification only defined a set of interfaces, applications had to rely on some implementation dependent code to start from. However, hard-coding the application to a specific implementation prevents the application from running on other implementations and from using the most-suitable implementation of the environment. At the same time, implementations may also need to load modules or perform other setup to efficiently adapt to different and sometimes mutually-exclusive feature sets.

To solve these problems this specification introduces a DOMImplementationRegistry object with a function that lets an application find an implementation, based on the specific features it requires. How this object is found and what it exactly looks like is not defined here, because this cannot be done in a language-independent manner. Instead, each language binding defines its own way of doing this. See and for specifics.

In all cases, though, the DOMImplementationRegistry provides a getDOMImplementation method accepting a features string, which is passed to every known DOMImplementationSource until a suitable DOMImplementation is found and returned. This method is the same as the one found on the DOMImplementationSource interface defined below.

Any number of DOMImplementationSource objects can be registered. A source may return one or more DOMImplementation singletons or construct new DOMImplementation objects, depending upon whether the requested features require specialized state in the DOMImplementation object.

Is this not generic enough?

Yes. (F2F 31 Jul 2001)

Should the method getDOMImplementation be called byFeature instead?

No. (F2F 31 Jul 2001)

Fundamental Interfaces

The interfaces within this section are considered fundamental, and must be fully implemented by all conforming implementations of the DOM, including all HTML DOM implementations , unless otherwise specified.

A DOM application may use the hasFeature(feature, version) method of the DOMImplementation interface with parameter values "Core" and "3.0" (respectively) to determine whether or not this module is supported by the implementation. Any implementation that conforms to DOM Level 3 or a DOM Level 3 module must conform to the Core module. Please refer to additional information about conformance in this specification. The DOM Level 3 Core module is backward compatible with the DOM Level 2 Core module, i.e. a DOM Level 3 Core implementation who returns true for "Core" with the version number "3.0" must also return true for this feature when the version number is "2.0", "" or, null.

DOM operations only raise exceptions in "exceptional" circumstances, i.e., when an operation is impossible to perform (either for logical reasons, because data is lost, or because the implementation has become unstable). In general, DOM methods return specific error values in ordinary processing situations, such as out-of-bound errors when using NodeList.

Implementations should raise other exceptions under other circumstances. For example, implementations should raise an implementation-dependent exception if a null argument is passed when null was not expected.

Some languages and object systems do not support the concept of exceptions. For such systems, error conditions may be indicated using native error reporting mechanisms. For some bindings, for example, methods may return error codes similar to those listed in the corresponding method descriptions.

unsigned short

An integer indicating the type of error generated.

Other numeric codes are reserved for W3C for possible future use.

If index or size is negative, or greater than the allowed value

If the specified range of text does not fit into a DOMString

If any node is inserted somewhere it doesn't belong

If a node is used in a different document than the one that created it (that doesn't support it)

If an invalid or illegal character is specified, such as in a name. See production 2 in the XML specification for the definition of a legal character, and production 5 for the definition of a legal name character.

If data is specified for a node which does not support data

If an attempt is made to modify an object where modifications are not allowed

If an attempt is made to reference a node in a context where it does not exist

If the implementation does not support the requested type of object or operation.

If an attempt is made to add an attribute that is already in use elsewhere

If an attempt is made to use an object that is not, or is no longer, usable.

If an invalid or illegal string is specified.

If an attempt is made to modify the type of the underlying object.

If an attempt is made to create or change an object in a way which is incorrect with regard to namespaces.

If a parameter or an operation is not supported by the underlying object.

If a call to a method such as insertBefore or removeChild would make the Node invalid with respect to "partial validity", this exception would be raised and the operation would not be done. This code is used in . Refer to this specification for further information.

This interface permits a DOM implementer to supply one or more implementations, based upon requested features. Each implemented DOMImplementationSource object is listed in the binding-specific list of available sources so that its DOMImplementation objects are made available.

A method to request a DOM implementation.

A string that specifies which features are required. This is a space separated list in which each feature is specified by its name optionally followed by a space and a version number. This is something like: "XML 1.0 Traversal Events 2.0"

An implementation that has the desired features, or null if this source has none.

The DOMImplementation interface provides a number of methods for performing operations that are independent of any particular instance of the document object model.

Test if the DOM implementation implements a specific feature.

The name of the feature to test (case-insensitive). The values used by DOM features are defined throughout the DOM Level 3 specifications and listed in the section. The name must be an XML name. To avoid possible conflicts, as a convention, names referring to features defined outside the DOM specification should be made unique.

This is the version number of the feature to test. In Level 3, the string can be either "3.0", "2.0" or "1.0". If the version is null or empty string, supporting any version of the feature causes the method to return true.

true if the feature is implemented in the specified version, false otherwise.

Creates an empty DocumentType node. Entity declarations and notations are not made available. Entity reference expansions and default attribute additions do not occur. It is expected that a future version of the DOM will provide a way for populating a DocumentType.

The qualified name of the document type to be created.

The external subset public identifier.

The external subset system identifier.

A new DocumentType node with Node.ownerDocument set to null.

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NAMESPACE_ERR: Raised if the qualifiedName is malformed.

NOT_SUPPORTED_ERR: May be raised by DOM implementations which do not support the "XML" feature, if they choose not to support this method.

Other features introduced in the future, by the DOM WG or in extensions defined by other groups, may also demand support for this method; please consult the definition of the feature to see if it requires this method.

Creates a DOM Document object of the specified type with its document element.

Note that based on the DocumentType given to create the document, the implementation may instantiate specialized Document objects that support additional features than the "Core", such as "HTML" . On the other hand, setting the DocumentType after the document was created makes this very unlikely to happen. Alternatively, specialized Document creation methods, such as createHTMLDocument , can be used to obtain specific types of Document objects.

The namespace URI of the document element to create or null.

The qualified name of the document element to be created or null.

The type of document to be created or null.

When doctype is not null, its Node.ownerDocument attribute is set to the document being created.

A new Document object with its document element. If the NamespaceURI, qualifiedName, and doctype are null, the returned Document is empty with no document element.

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NAMESPACE_ERR: Raised if the qualifiedName is malformed, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName is null and the namespaceURI is different from null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace" , or if the DOM implementation does not support the "XML" feature but a non-null namespace URI was provided, since namespaces were defined by XML.

WRONG_DOCUMENT_ERR: Raised if doctype has already been used with a different document or was created from a different implementation.

NOT_SUPPORTED_ERR: May be raised by DOM implementations which do not support the "XML" feature, if they choose not to support this method.

This method makes available a DOMImplementation's specialized interface (see ).

The name of the feature requested (case-insensitive).

Returns an alternate DOMImplementation which implements the specialized APIs of the specified feature, if any, or null if there is no alternate DOMImplementation object which implements interfaces associated with that feature. Any alternate DOMImplementation returned by this method must delegate to the primary core DOMImplementation and not return results inconsistent with the primary DOMImplementation

DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfill this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object. DocumentFragment is such an object.

Furthermore, various operations -- such as inserting nodes as children of another Node -- may take DocumentFragment objects as arguments; this results in all the child nodes of the DocumentFragment being moved to the child list of this node.

The children of a DocumentFragment node are zero or more nodes representing the tops of any sub-trees defining the structure of the document. DocumentFragment nodes do not need to be well-formed XML documents (although they do need to follow the rules imposed upon well-formed XML parsed entities, which can have multiple top nodes). For example, a DocumentFragment might have only one child and that child node could be a Text node. Such a structure model represents neither an HTML document nor a well-formed XML document.

When a DocumentFragment is inserted into a Document (or indeed any other Node that may take children) the children of the DocumentFragment and not the DocumentFragment itself are inserted into the Node. This makes the DocumentFragment very useful when the user wishes to create nodes that are siblings; the DocumentFragment acts as the parent of these nodes so that the user can use the standard methods from the Node interface, such as insertBefore and appendChild.

The properties [notations] and [unparsed entities] defined by the Document Information Item in are accessible through the DocumentType interface. The property [all declarations processed] is not accessible through the DOM API.

The Document interface represents the entire HTML or XML document. Conceptually, it is the root of the document tree, and provides the primary access to the document's data.

Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document, the Document interface also contains the factory methods needed to create these objects. The Node objects created have a ownerDocument attribute which associates them with the Document within whose context they were created.

The Document Type Declaration (see DocumentType) associated with this document. For HTML documents as well as XML documents without a document type declaration this returns null.

This provides direct access to the DocumentType node, child node of this Document. This node can be set at document creation time and later changed through the use of child nodes manipulation methods, such as insertBefore, or replaceChild. Note, however, that while some implementations may instantiate different types of Document objects supporting additional features than the "Core", such as "HTML" , based on the DocumentType specified at creation time, changing it afterwards is very unlikely to result in a change of the features supported.

The DOMImplementation object that handles this document. A DOM application may use objects from multiple implementations.

This is a convenience attribute that allows direct access to the child node that is the document element of the document.

This attribute represents the property [document element] defined in .

Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.

In addition, if there are known attributes with default values, Attr nodes representing them are automatically created and attached to the element.

To create an element with a qualified name and namespace URI, use the createElementNS method.

The name of the element type to instantiate. For XML, this is case-sensitive, otherwise it depends on the case-sentivity of the markup language in use. In that case, the name is mapped to the canonical form of that markup by the DOM implementation.

A new Element object with the nodeName attribute set to tagName, and localName, prefix, and namespaceURI set to null.

INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character.

Creates an empty DocumentFragment object.

A new DocumentFragment.

Creates a Text node given the specified string.

The data for the node.

The new Text object.

Creates a Comment node given the specified string.

The data for the node.

The new Comment object.

Creates a CDATASection node whose value is the specified string.

The data for the CDATASection contents.

The new CDATASection object.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Creates a ProcessingInstruction node given the specified name and data strings.

The target part of the processing instruction.

The data for the node.

The new ProcessingInstruction object.

INVALID_CHARACTER_ERR: Raised if the specified target contains an illegal character.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Creates an Attr of the given name. Note that the Attr instance can then be set on an Element using the setAttributeNode method.

To create an attribute with a qualified name and namespace URI, use the createAttributeNS method.

The name of the attribute.

A new Attr object with the nodeName attribute set to name, and localName, prefix, and namespaceURI set to null. The value of the attribute is the empty string.

INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character.

Creates an EntityReference object. In addition, if the referenced entity is known, the child list of the EntityReference node is made the same as that of the corresponding Entity node.

If any descendant of the Entity node has an unbound namespace prefix, the corresponding descendant of the created EntityReference node is also unbound; (its namespaceURI is null). The DOM Level 2 does not support any mechanism to resolve namespace prefixes.

The name of the entity to reference.

The new EntityReference object.

INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Returns a NodeList of all the Elements with a given tag name in document order.

The name of the tag to match on. The special value "*" matches all tags. For XML, this is case-sensitive, otherwise it depends on the case-sentivity of the markup language in use.

A new NodeList object containing all the matched Elements.

Imports a node from another document to this document. The returned node has no parent; (parentNode is null). The source node is not altered or removed from the original document; this method creates a new copy of the source node.

For all nodes, importing a node creates a node object owned by the importing document, with attribute values identical to the source node's nodeName and nodeType, plus the attributes related to namespaces (prefix, localName, and namespaceURI). As in the cloneNode operation, the source node is not altered. User data associated to the imported node is not carried over. However, if any UserDataHandlers has been specified along with the associated data these handlers will be called with the appropriate parameters before this method returns.

Additional information is copied as appropriate to the nodeType, attempting to mirror the behavior expected if a fragment of XML or HTML source was copied from one document to another, recognizing that the two documents may have different DTDs in the XML case. The following list describes the specifics for each type of node. ATTRIBUTE_NODE

The ownerElement attribute is set to null and the specified flag is set to true on the generated Attr. The descendants of the source Attr are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

Note that the deep parameter has no effect on Attr nodes; they always carry their children with them when imported.

DOCUMENT_FRAGMENT_NODE

If the deep option was set to true, the descendants of the source DocumentFragment are recursively imported and the resulting nodes reassembled under the imported DocumentFragment to form the corresponding subtree. Otherwise, this simply generates an empty DocumentFragment.

DOCUMENT_NODE

Document nodes cannot be imported.

DOCUMENT_TYPE_NODE

DocumentType nodes cannot be imported.

ELEMENT_NODE

Specified attribute nodes of the source element are imported, and the generated Attr nodes are attached to the generated Element. Default attributes are not copied, though if the document being imported into defines default attributes for this element name, those are assigned. If the importNode deep parameter was set to true, the descendants of the source element are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

ENTITY_NODE

Entity nodes can be imported, however in the current release of the DOM the DocumentType is readonly. Ability to add these imported nodes to a DocumentType will be considered for addition to a future release of the DOM.

On import, the publicId, systemId, and notationName attributes are copied. If a deep import is requested, the descendants of the the source Entity are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

ENTITY_REFERENCE_NODE

Only the EntityReference itself is copied, even if a deep import is requested, since the source and destination documents might have defined the entity differently. If the document being imported into provides a definition for this entity name, its value is assigned.

NOTATION_NODE

Notation nodes can be imported, however in the current release of the DOM the DocumentType is readonly. Ability to add these imported nodes to a DocumentType will be considered for addition to a future release of the DOM.

On import, the publicId and systemId attributes are copied.

Note that the deep parameter has no effect on this type of nodes since they cannot have any children.

PROCESSING_INSTRUCTION_NODE

The imported node copies its target and data values from those of the source node.

Note that the deep parameter has no effect on this type of nodes since they cannot have any children.

TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE

These three types of nodes inheriting from CharacterData copy their data and length attributes from those of the source node.

Note that the deep parameter has no effect on these types of nodes since they cannot have any children.

The node to import.

If true, recursively import the subtree under the specified node; if false, import only the node itself, as explained above. This has no effect on nodes that cannot have any children, and on Attr, and EntityReference nodes.

The imported node that belongs to this Document.

NOT_SUPPORTED_ERR: Raised if the type of node being imported is not supported.

INVALID_CHARACTER_ERR: Raised if one the imported names contain an illegal character. This may happen when importing an XML 1.1 element into an XML 1.0 document, for instance.

Creates an element of the given qualified name and namespace URI.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the element to create.

The qualified name of the element type to instantiate.

A new Element object with the following attributes:

Attribute	Value
`Node.nodeName`	`qualifiedName`
`Node.namespaceURI`	`namespaceURI`
`Node.prefix`	prefix, extracted from `qualifiedName`, or `null` if there is no prefix
`Node.localName`	local name, extracted from `qualifiedName`
`Element.tagName`	`qualifiedName`

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Creates an attribute of the given qualified name and namespace URI.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to create.

The qualified name of the attribute to instantiate.

A new Attr object with the following attributes:

Attribute	Value
`Node.nodeName`	qualifiedName
`Node.namespaceURI`	`namespaceURI`
`Node.prefix`	prefix, extracted from `qualifiedName`, or `null` if there is no prefix
`Node.localName`	local name, extracted from `qualifiedName`
`Attr.name`	`qualifiedName`
`Node.nodeValue`	the empty string

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NAMESPACE_ERR: Raised if the qualifiedName is malformed per the Namespaces in XML specification, if the qualifiedName has a prefix and the namespaceURI is null, if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace", if the qualifiedName or its prefix is "xmlns" and the namespaceURI is different from "http://www.w3.org/2000/xmlns/", or if the namespaceURI is "http://www.w3.org/2000/xmlns/" and neither the qualifiedName nor its prefix is "xmlns".

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Returns a NodeList of all the Elements with a given local name and namespace URI in document order.

The namespace URI of the elements to match on. The special value "*" matches all namespaces.

The local name of the elements to match on. The special value "*" matches all local names.

A new NodeList object containing all the matched Elements.

Returns the Element that has an ID attribute with the given value. If no such element exists, this returns null. If more than one element has an ID attribute with that value, what is returned is undefined.

To define an attribute of type ID see the setIdAttribute method and its siblings on Element. To query whether an attribute is of type ID see isId on Attr.

Attributes with the name "ID" or "id" are not of type ID unless so defined.

The unique id value for an element.

The matching element or null if there is none.

An attribute specifying the actual encoding of this document. This is null otherwise.

This attribute represents the property [character encoding scheme] defined in .

An attribute specifying, as part of the XML declaration, the encoding of this document. This is null when unspecified.

An attribute specifying, as part of the XML declaration, whether this document is standalone.

This attribute represents the property [standalone] defined in .

An attribute specifying, as part of the XML declaration, the version number of this document. This is null when unspecified.

This attribute represents the property [version] defined in .

NOT_SUPPORTED_ERR: Raised if the version is set to a value that is not supported by this Document.

An attribute specifying whether errors checking is enforced or not. When set to false, the implementation is free to not test every possible error case normally defined on DOM operations, and not raise any DOMException. In case of error, the behavior is undefined. This attribute is true by defaults.

This attribute allows applications to specify a DOMErrorHandler to be called in the event that an error is encountered while performing an operation on a document. Note that not all methods use this mechanism, see the description of each method for details.

The location of the document or null if undefined.

Beware that when the Document supports the feature "HTML" , the href attribute of the HTML BASE element takes precedence over this attribute.

Changes the ownerDocument of a node, its children, as well as the attached attribute nodes if there are any. If the node has a parent it is first removed from its parent child list. This effectively allows moving a subtree from one document to another. The following list describes the specifics for each type of node. ATTRIBUTE_NODE

The ownerElement attribute is set to null and the specified flag is set to true on the adopted Attr. The descendants of the source Attr are recursively adopted.

DOCUMENT_FRAGMENT_NODE

The descendants of the source node are recursively adopted.

DOCUMENT_NODE

Document nodes cannot be adopted.

DOCUMENT_TYPE_NODE

DocumentType nodes cannot be adopted.

ELEMENT_NODE

Specified attribute nodes of the source element are adopted, and the generated Attr nodes. Default attributes are discarded, though if the document being adopted into defines default attributes for this element name, those are assigned. The descendants of the source element are recursively adopted.

ENTITY_NODE

Entity nodes cannot be adopted.

ENTITY_REFERENCE_NODE

Only the EntityReference node itself is adopted, the descendants are discarded, since the source and destination documents might have defined the entity differently. If the document being imported into provides a definition for this entity name, its value is assigned.

NOTATION_NODE

Notation nodes cannot be adopted.

PROCESSING_INSTRUCTION_NODE, TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE

These nodes can all be adopted. No specifics.

Should this method simply return null when it fails? How "exceptional" is failure for this method?

Stick with raising exceptions only in exceptional circumstances, return null on failure (F2F 19 Jun 2000).

Can an entity node really be adopted?

No, neither can Notation nodes (Telcon 13 Dec 2000).

Does this affect keys and hashCode's of the adopted subtree nodes?

If so, what about readonly-ness of key and hashCode?

if not, would appendChild affect keys/hashCodes or would it generate exceptions if key's are duplicate?

Both keys and hashcodes have been dropped.

The node to move into this document.

The adopted node, or null if this operation fails, such as when the source node comes from a different implementation.

NOT_SUPPORTED_ERR: Raised if the source node is of type DOCUMENT, DOCUMENT_TYPE.

NO_MODIFICATION_ALLOWED_ERR: Raised when the source node is readonly.

This method acts as if the document was going through a save and load cycle, putting the document in a "normal" form. The actual result depends on the features being set and governing what operations actually take place. See setNormalizationFeature for details.

Noticeably this method normalizes Text nodes, makes the document "namespace wellformed", according to the algorithm described below in pseudo code, by adding missing namespace declaration attributes and adding or changing namespace prefixes, updates the replacement tree of EntityReference nodes, normalizes attribute values, etc.

Mutation events, when supported, are generated to reflect the changes occuring on the document.

See for details on how namespace declaration attributes and prefixes are normalized.

Any other name? Joe proposes normalizeNamespaces.

normalizeDocument. (F2F 26 Sep 2001)

How specific should this be? Should we not even specify that this should be done by walking down the tree?

Very. See above.

What does this do on attribute nodes?

Doesn't do anything (F2F 1 Aug 2000).

How does it work with entity reference subtree which may be broken?

This doesn't affect entity references which are not visited in this operation (F2F 1 Aug 2000).

Should this really be on Node?

Yes, but this only works on Document, Element, and DocumentFragment. On other types it is a no-op. (F2F 1 Aug 2000).

No. Now that it does much more than simply fixing namespaces it only makes sense on Document (F2F 26 Sep 2001).

What happens with read-only nodes?

What/how errors should be reported? Are there any?

Through the error reporter.

Should this be optional?

No.

What happens with regard to mutation events?

Mutation events are fired as expected. (F2F 28 Feb 2002).

Query whether setting a feature to a specific value is supported.

The feature name has the same form as a DOM hasFeature string.

The name of the feature to check.

The requested state of the feature (true or false).

true if the feature could be successfully set to the specified value, or false if the feature is not recognized or the requested value is not supported. This does not change the current value of the feature itself.

Set the state of a feature.

Need to specify the list of features.

Feature names are valid XML names. Implementation specific features (extensions) should choose an implementation specific prefix to avoid name collisions. The following lists feature names that are recognized by all implementations. However, it is sometimes possible for a Document to recognize a feature but not to support setting its value. The following list of recognized features indicates the definitions of each feature state, if setting the state to true or false must be supported or is optional and, which state is the default one:

"canonical-form" true

[optional]

Canonicalize the document according to the rules specified in . Note that this is limited to what can be represented in the DOM. In particular, there is no way to specify the order of the attributes in the DOM.

What happen to other features? are they ignored? if yes, how do you know if a feature is ignored?

false

[required] (default)

Do not canonicalize the document.

"cdata-sections" true

[required] (default)

Keep CDATASection nodes in the document.

Name does not work really well in this case. ALH suggests renaming this to "cdata-sections". It works for both load and save.

Renamed as suggested. (Telcon 27 Jan 2002).

false

[required]

Transform CDATASection nodes in the document into Text nodes. The new Text node is then combined with any adjacent Text node.

"comments" true

[required] (default)

Keep Comment nodes in the document.

false

[required]

Discard Comment nodes in the Document.

"datatype-normalization" true

[required]

Let the validation process do its datatype normalization that is defined in the used schema language. Note that this does not affect the DTD normalization operation which always takes place, in accordance to .

We should define "datatype normalization".

DTD normalization always apply because it's part of XML 1.0. Clarify the spec. (Telcon 27 Jan 2002).

false

[required] (default)

Disable datatype normalization. The XML 1.0 attribute value normalization always occurs though.

"discard-default-content" true

[required] (default)

Use whatever information available to the implementation (i.e. XML schema, DTD, the specified flag on Attr nodes, and so on) to decide what attributes and content should be discarded or not. Note that the specified flag on Attr nodes in itself is not always reliable, it is only reliable when it is set to false since the only case where it can be set to false is if the attribute was created by the implementation. The default content won't be removed if an implementation does not have any information available.

How does exactly work? What's the comment about level 1 implementations?

Remove "Level 1" (Telcon 16 Jan 2002).

false

[required]

Keep all attributes and all content.

"entities" true

[required]

Keep EntityReference and Entity nodes in the document.

How does that interact with expand-entity-references? ALH suggests consolidating the two to a single feature called "entity-references" that is used both for load and save.

Consolidate both features into a single feature called 'entities'. (Telcon 27 Jan 2002).

false

[required] (default)

Remove all EntityReference and Entity nodes from the document, putting the entity expansions directly in their place. Text nodes are into "normal" form. Only EntityReference nodes to non-defined entities are kept in the document.

"infoset" true

[required]

Only keep in the document the information defined in the XML Information Set .

This forces the following features to false: namespace-declarations, validate-if-schema, entities, datatype-normalization, cdata-sections.

This forces the following features to true: whitespace-in-element-content, comments.

Other features are not changed unless explicity specified in the description of the features.

Note that querying this feature with getFeature returns true only if the individual features specified above are appropriately set.

Name doesn't work well here. ALH suggests renaming this to limit-to-infoset or match-infoset, something like that.

Renamed 'infoset' (Telcon 27 Jan 2002).

false

Setting infoset to false has no effect.

Shouldn't we change this to setting the relevant options back to their default value?

No, this is more like a convenience function, it's better to keep it simple. (F2F 28 Feb 2002).

"namespaces" true

[required] (default)

Perform the namespace processing as defined in .

false

[optional]

Do not perform the namespace processing.

"namespace-declarations" true

[required] (default)

Include namespace declaration attributes, specified or defaulted from the schema or the DTD, in the document. See also the section Declaring Namespaces in .

false

[required]

Discard all namespace declaration attributes. The Namespace prefixes are retained even if this feature is set to false.

"normalize-characters" true

[optional]

Perform the W3C Text Normalization of the characters in the document.

false

[required] (default)

Do not perform character normalization.

"split-cdata-sections" true

[required] (default)

Split CDATA sections containing the CDATA section termination marker ']]>'. When a CDATA section is split a warning is issued.

false

[required]

Signal an error if a CDATASection contains an unrepresentable character.

"validate" true

[optional]

Require the validation against a schema (i.e. XML schema, DTD, any other type or representation of schema) of the document as it is being normalized as defined by . If validation errors are found, or no schema was found, the error handler is notified. Note also that no datatype normalization (i.e. non-XML 1.0 normalization) is done according to the schema used unless the feature datatype-normalization is true.

validate-if-schema and validate are mutually exclusive, setting one of them to true will set the other one to false.

false

[required] (default)

Only XML 1.0 non-validating processing must be done. Note that validation might still happen if validate-if-schema is true.

"validate-if-schema" true

[optional]

Enable validation only if a declaration for the document element can be found (independently of where it is found, i.e. XML schema, DTD, or any other type or representation of schema). If validation errors are found, the error handler is notified. Note also that no datatype normalization (i.e. non-XML 1.0 normalization) is done according to the schema used unless the feature datatype-normalization is true.

validate-if-schema and validate are mutually exclusive, setting one of them to true will set the other one to false.

How does that interact with the notion of active AS?

If document has AS model, than it "has a schema", thus validation will be performed against the active AS model. (Telcon 16 Jan 2002).

false

[required] (default)

No validation should be performed if the document has a schema. Note that validation must still happen if validate is true.

"whitespace-in-element-content" true

[required] (default)

Keep all white spaces in the document.

How does this feature interact with "validate" and Text.isWhitespaceInElementContent.

false

[optional]

Discard white space in element content while normalizing. The implementation is expected to use the isWhitespaceInElementContent flag on Text nodes to determine if a text node should be written out or not.

The name of the feature to set.

The requested state of the feature (true or false).

NOT_SUPPORTED_ERR: Raised when the feature name is recognized but the requested value cannot be set.

NOT_FOUND_ERR: Raised when the feature name is not recognized.

Look up the value of a feature.

The feature name has the same form as a DOM hasFeature string. The recognized features are the same as the ones defined for setNormalizationFeature.

The name of the feature to look up.

The current state of the feature (true or false).

NOT_FOUND_ERR: Raised when the feature name is not recognized.

Rename an existing node. When possible this simply changes the name of the given node, otherwise this creates a new node with the specified name and replaces the existing node with the new node as described below. This only applies to nodes of type ELEMENT_NODE and ATTRIBUTE_NODE.

When a new node is created, the following operations are performed: the new node is created, any registered event listener is registered on the new node, any user data attached to the old node is removed from that node, the old node is removed from its parent if it has one, the children are moved to the new node, if the renamed node is an Element its attributes are moved to the new node, the new node is inserted at the position the old node used to have in its parent's child nodes list if it has one, the user data that was attached to the old node is attach to the new node, the user data event NODE_RENAMED is fired.

When the node being renamed is an Element only the specified attributes are moved, default attributes originated from the DTD are updated according to the new element name. In addition, the implementation may update default attributes from other schemas. Applications should use normalizeDocument() to guarantee these attributes are up-to-date.

When the node being renamed is an Attr that is attached to an Element, the node is first removed from the Element attributes map. Then, once renamed, either by modifying the existing node or creating a new one as described above, it is put back.

In addition, when the implementation supports the feature "MutationEvents", each mutation operation involved in this method fires the appropriate event, and in the end the event DOMElementNameChanged or DOMAttributeNameChanged is fired.

Should this throw a HIERARCHY_REQUEST_ERR?

No. (F2F 28 Feb 2002).

The node to rename.

The new namespaceURI.

The new qualified name.

The renamed node. This is either the specified node or the new node that was created to replace the specified node.

NOT_SUPPORTED_ERR: Raised when the type of the specified node is neither ELEMENT_NODE nor ATTRIBUTE_NODE.

WRONG_DOCUMENT_ERR: Raised when the specified node was created from a different document than this document.

NAMESPACE_ERR: Raised if the qualifiedName is malformed per the Namespaces in XML specification, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace" . Also raised, when the node being renamed is an attribute, if the qualifiedName, or its prefix, is "xmlns" and the namespaceURI is different from "http://www.w3.org/2000/xmlns/".

The Node interface is the primary datatype for the entire Document Object Model. It represents a single node in the document tree. While all objects implementing the Node interface expose methods for dealing with children, not all objects implementing the Node interface may have children. For example, Text nodes may not have children, and adding children to such nodes results in a DOMException being raised.

The attributes nodeName, nodeValue and attributes are included as a mechanism to get at node information without casting down to the specific derived interface. In cases where there is no obvious mapping of these attributes for a specific nodeType (e.g., nodeValue for an Element or attributes for a Comment), this returns null. Note that the specialized interfaces may contain additional and more convenient mechanisms to get and set the relevant information.

An integer indicating which type of node this is.

Numeric codes up to 200 are reserved to W3C for possible future use.

The node is an Element.

The node is an Attr.

The node is a Text node.

The node is a CDATASection.

The node is an EntityReference.

The node is an Entity.

The node is a ProcessingInstruction.

The node is a Comment.

The node is a Document.

The node is a DocumentType.

The node is a DocumentFragment.

The node is a Notation.

The values of nodeName, nodeValue, and attributes vary according to the node type as follows:

Interface nodeName nodeValue attributes

Attr name of attribute value of attribute null

CDATASection "#cdata-section" content of the CDATA Section null

Comment "#comment" content of the comment null

Document "#document" null null

DocumentFragment "#document-fragment" null null

DocumentType document type name null null

Element tag name null NamedNodeMap

Entity entity name null null

EntityReference name of entity referenced null null

Notation notation name null null

ProcessingInstruction target entire content excluding the target null

Text "#text" content of the text node null

Interface	nodeName	nodeValue	attributes
Attr	name of attribute	value of attribute	null
CDATASection	`"#cdata-section"`	content of the CDATA Section	null
Comment	`"#comment"`	content of the comment	null
Document	`"#document"`	null	null
DocumentFragment	`"#document-fragment"`	null	null
DocumentType	document type name	null	null
Element	tag name	null	NamedNodeMap
Entity	entity name	null	null
EntityReference	name of entity referenced	null	null
Notation	notation name	null	null
ProcessingInstruction	target	entire content excluding the target	null
Text	`"#text"`	content of the text node	null

The name of this node, depending on its type; see the table above.

The value of this node, depending on its type; see the table above. When it is defined to be null, setting it has no effect, including if the node is read-only.

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

DOMSTRING_SIZE_ERR: Raised when it would return more characters than fit in a DOMString variable on the implementation platform.

A code representing the type of the underlying object, as defined above.

The parent of this node. All nodes, except Attr, Document, DocumentFragment, Entity, and Notation may have a parent. However, if a node has just been created and not yet added to the tree, or if it has been removed from the tree, this is null.

When the node is an Element, a ProcessingInstruction, an EntityReference, a CharacterData, a Comment, or a DocumentType, this attribute represents the properties [parent] defined in .

A NodeList that contains all children of this node. If there are no children, this is a NodeList containing no nodes.

When the node is a Document, or an Element, and if the NodeList does not contain EntityReference or CDATASection nodes, this attribute represents the properties [children] defined in .

The first child of this node. If there is no such node, this returns null.

The last child of this node. If there is no such node, this returns null.

The node immediately preceding this node. If there is no such node, this returns null.

The node immediately following this node. If there is no such node, this returns null.

A NamedNodeMap containing the attributes of this node (if it is an Element) or null otherwise.

If no namespace declaration appear in the attributes, this attribute represents the property [attributes] defined in . If namespace declarations appear in the attributes, this attribute combines the properties [attributes] and [namespace attributes] defined in .

The Document object associated with this node. This is also the Document object used to create new nodes. When this node is a Document or a DocumentType which is not used with any Document yet, this is null.

Inserts the node newChild before the existing child node refChild. If refChild is null, insert newChild at the end of the list of children.

If newChild is a DocumentFragment object, all of its children are inserted, in the same order, before refChild. If the newChild is already in the tree, it is first removed.

The node to insert.

The reference node, i.e., the node before which the new node must be inserted.

The node being inserted.

HIERARCHY_REQUEST_ERR: Raised if this node is of a type that does not allow children of the type of the newChild node, or if the node to insert is one of this node's ancestors or this node itself, or if this node if of type Document and the DOM application attempts to insert a second DocumentType or Element node.

WRONG_DOCUMENT_ERR: Raised if newChild was created from a different document than the one that created this node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly or if the parent of the node being inserted is readonly.

NOT_FOUND_ERR: Raised if refChild is not a child of this node.

NOT_SUPPORTED_ERR: if this node if of type Document, this exception might be raised if the DOM implementation doesn't support the insertion of a DocumentType or Element node.

Replaces the child node oldChild with newChild in the list of children, and returns the oldChild node.

If newChild is a DocumentFragment object, oldChild is replaced by all of the DocumentFragment children, which are inserted in the same order. If the newChild is already in the tree, it is first removed.

The new node to put in the child list.

The node being replaced in the list.

The node replaced.

HIERARCHY_REQUEST_ERR: Raised if this node is of a type that does not allow children of the type of the newChild node, or if the node to put in is one of this node's ancestors or this node itself.

WRONG_DOCUMENT_ERR: Raised if newChild was created from a different document than the one that created this node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node or the parent of the new node is readonly.

NOT_FOUND_ERR: Raised if oldChild is not a child of this node.

NOT_SUPPORTED_ERR: if this node if of type Document, this exception might be raised if the DOM implementation doesn't support the replacement of the DocumentType child or Element child.

Removes the child node indicated by oldChild from the list of children, and returns it.

The node being removed.

The node removed.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if oldChild is not a child of this node.

NOT_SUPPORTED_ERR: if this node if of type Document, this exception might be raised if the DOM implementation doesn't support the removal of the DocumentType child or the Element child.

Adds the node newChild to the end of the list of children of this node. If the newChild is already in the tree, it is first removed.

The node to add.

If it is a DocumentFragment object, the entire contents of the document fragment are moved into the child list of this node

The node added.

HIERARCHY_REQUEST_ERR: Raised if this node is of a type that does not allow children of the type of the newChild node, or if the node to append is one of this node's ancestors or this node itself.

WRONG_DOCUMENT_ERR: Raised if newChild was created from a different document than the one that created this node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly or if the previous parent of the node being inserted is readonly.

Returns whether this node has any children.

true if this node has any children, false otherwise.

Returns a duplicate of this node, i.e., serves as a generic copy constructor for nodes. The duplicate node has no parent; (parentNode is null.) and no user data. User data associated to the imported node is not carried over. However, if any UserDataHandlers has been specified along with the associated data these handlers will be called with the appropriate parameters before this method returns.

Cloning an Element copies all attributes and their values, including those generated by the XML processor to represent defaulted attributes, but this method does not copy any children it contains unless it is a deep clone. This includes text contained in an the Element since the text is contained in a child Text node. Cloning an Attribute directly, as opposed to be cloned as part of an Element cloning operation, returns a specified attribute (specified is true). Cloning an Attribute always clones its children, since they represent its value, no matter whether this is a deep clone or not. Cloning an EntityReference automatically constructs its subtree if a corresponding Entity is available, no matter whether this is a deep clone or not. Cloning any other type of node simply returns a copy of this node.

Note that cloning an immutable subtree results in a mutable copy, but the children of an EntityReference clone are readonly. In addition, clones of unspecified Attr nodes are specified. And, cloning Document, DocumentType, Entity, and Notation nodes is implementation dependent.

If true, recursively clone the subtree under the specified node; if false, clone only the node itself (and its attributes, if it is an Element).

The duplicate node.

Puts all Text nodes in the full depth of the sub-tree underneath this Node, including attribute nodes, into a "normal" form where only structure (e.g., elements, comments, processing instructions, CDATA sections, and entity references) separates Text nodes, i.e., there are neither adjacent Text nodes nor empty Text nodes. This can be used to ensure that the DOM view of a document is the same as if it were saved and re-loaded, and is useful when operations (such as XPointer lookups) that depend on a particular document tree structure are to be used.

In cases where the document contains CDATASections, the normalize operation alone may not be sufficient, since XPointers do not differentiate between Text nodes and CDATASection nodes.

Tests whether the DOM implementation implements a specific feature and that feature is supported by this node.

The name of the feature to test. This is the same name which can be passed to the method hasFeature on DOMImplementation.

This is the version number of the feature to test. In Level 2, version 1, this is the string "2.0". If the version is not specified, supporting any version of the feature will cause the method to return true.

Returns true if the specified feature is supported on this node, false otherwise.

The namespace URI of this node, or null if it is unspecified.

When the node is Element, or Attr, this attribute represents the properties [namespace name] defined in .

This is not a computed value that is the result of a namespace lookup based on an examination of the namespace declarations in scope. It is merely the namespace URI given at creation time.

For nodes of any type other than ELEMENT_NODE and ATTRIBUTE_NODE and nodes created with a DOM Level 1 method, such as createElement from the Document interface, this is always null.

Per the Namespaces in XML Specification an attribute does not inherit its namespace from the element it is attached to. If an attribute is not explicitly given a namespace, it simply has no namespace.

The namespace prefix of this node, or null if it is unspecified.

When the node is Element, or Attr, this attribute represents the properties [prefix] defined in .

Note that setting this attribute, when permitted, changes the nodeName attribute, which holds the qualified name, as well as the tagName and name attributes of the Element and Attr interfaces, when applicable.

Note also that changing the prefix of an attribute that is known to have a default value, does not make a new attribute with the default value and the original prefix appear, since the namespaceURI and localName do not change.

For nodes of any type other than ELEMENT_NODE and ATTRIBUTE_NODE and nodes created with a DOM Level 1 method, such as createElement from the Document interface, this is always null.

INVALID_CHARACTER_ERR: Raised if the specified prefix contains an illegal character.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NAMESPACE_ERR: Raised if the specified prefix is malformed per the Namespaces in XML specification, if the namespaceURI of this node is null, if the specified prefix is "xml" and the namespaceURI of this node is different from "http://www.w3.org/XML/1998/namespace", if this node is an attribute and the specified prefix is "xmlns" and the namespaceURI of this node is different from "http://www.w3.org/2000/xmlns/", or if this node is an attribute and the qualifiedName of this node is "xmlns" .

Returns the local part of the qualified name of this node.

When the node is Element, or Attr, this attribute represents the properties [local name] defined in .

For nodes of any type other than ELEMENT_NODE and ATTRIBUTE_NODE and nodes created with a DOM Level 1 method, such as createElement from the Document interface, this is always null.

Returns whether this node (if it is an element) has any attributes.

true if this node has any attributes, false otherwise.

The absolute base URI of this node or null if undefined. This value is computed according to . However, when the Document supports the feature "HTML" , the base URI is computed using first the value of the href attribute of the HTML BASE element if any, and the value of the documentURI attribute from the Document interface otherwise.

When the node is an Element, a Document or a a ProcessingInstruction, this attribute represents the properties [base URI] defined in . When the node is a Notation, an Entity, or an EntityReference, this attribute represents the properties [declaration base URI] in the .

How will this be affected by resolution of relative namespace URIs issue?

It's not.

Should this only be on Document, Element, ProcessingInstruction, Entity, and Notation nodes, according to the infoset? If not, what is it equal to on other nodes? Null? An empty string? I think it should be the parent's.

No.

Should this be read-only and computed or and actual read-write attribute?

Read-only and computed (F2F 19 Jun 2000 and teleconference 30 May 2001).

If the base HTML element is not yet attached to a document, does the insert change the Document.baseURI?

Yes. (F2F 26 Sep 2001)

A bitmask indicating the relative document position of a node with respect to another node.

Should we use fewer bits?

No. Simpler that way.

How does a node compare to itself?

SAME_NODE and EQUIVALENT. (F2F 26 Sep 2001)

Used for Attr nodes that are not part of the tree.

Change "Tree" to "Document". (F2F 30 Apr 2002)

The node precedes the reference node.

The node follows the reference node.

The node is an ancestor of the reference node.

The node is a descendant of the reference node.

The two nodes have an equivalent position. This is the case of two attributes that have the same ownerElement, and two nodes that are the same.

The two nodes are the same. Two nodes that are the same have an equivalent position, though the reverse may not be true.

The two nodes are disconnected, they do not have any common ancestor. This is the case of two nodes that are not in the same document.

Compares a node with this node with regard to their position in the document and according to the document order. Even though attribute nodes are not part of the document tree, in this method an attribute node is considered to be the descendant of its owner element. Also, when present, entity reference nodes are considered to precede and be the ancestors of their children.

Should this method be optional?

No.

Need reference for namespace nodes.

No, instead avoid referencing them directly.

Used for Attr nodes that are not part of the tree.

Change "Tree" to "Document". (F2F 30 Apr 2002)

The node to compare against this node.

Returns how the given node is positioned relatively to this node.

This attribute returns the text content of this node and its descendants. When it is defined to be null, setting it has no effect. When set, any possible children this node may have are removed and replaced by a single Text node containing the string this attribute is set to. On getting, no serialization is performed, the returned string does not contain any markup. No whitespace normalization is performed, the returned string does not contain the element content whitespaces . Similarly, on setting, no parsing is performed either, the input string is taken as pure textual content.

The string returned is made of the text content of this node depending on its type, as defined below:

Node type Content

ELEMENT_NODE, ENTITY_NODE, ENTITY_REFERENCE_NODE, DOCUMENT_FRAGMENT_NODE concatenation of the textContent attribute value of every child node, excluding COMMENT_NODE and PROCESSING_INSTRUCTION_NODE nodes. This is the empty string if the node has no children.

ATTRIBUTE_NODE, TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE, PROCESSING_INSTRUCTION_NODE nodeValue

DOCUMENT_NODE, DOCUMENT_TYPE_NODE, NOTATION_NODE null

Node type	Content
ELEMENT_NODE, ENTITY_NODE, ENTITY_REFERENCE_NODE, DOCUMENT_FRAGMENT_NODE	concatenation of the `textContent` attribute value of every child node, excluding COMMENT_NODE and PROCESSING_INSTRUCTION_NODE nodes. This is the empty string if the node has no children.
ATTRIBUTE_NODE, TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE, PROCESSING_INSTRUCTION_NODE	`nodeValue`
DOCUMENT_NODE, DOCUMENT_TYPE_NODE, NOTATION_NODE	null

Should any whitespace normalization be performed? MS' text property doesn't but what about "ignorable whitespace"?

Does not perform any whitespace normalization and ignores "ignorable whitespace".

Should this be two methods instead?

No. Keep it a read write attribute.

What about the name? MS uses text and innerText. text conflicts with HTML DOM.

Keep the current name, MS has a different name and different semantic.

Should this be optional?

No.

Setting the text property on a Document, Document Type, or Notation node is an error for MS. How do we expose it? Exception? Which one?

(teleconference 23 May 2001) consistency with nodeValue. Remove Document from the list.

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

DOMSTRING_SIZE_ERR: Raised when it would return more characters than fit in a DOMString variable on the implementation platform.

Returns whether this node is the same node as the given one.

This method provides a way to determine whether two Node references returned by the implementation reference the same object. When two Node references are references to the same object, even if through a proxy, the references may be used completely interchangeably, such that all attributes have the same values and calling the same DOM method on either reference always has exactly the same effect.

Do we really want to make this different from equals?

Yes, change name from isIdentical to isSameNode. (Telcon 4 Jul 2000).

Is this really needed if we provide a unique key?

Yes, because the key is only unique within a document. (F2F 2 Mar 2001).

Definition of 'sameness' is needed.

The node to test against.

Returns true if the nodes are the same, false otherwise.

Look up the prefix associated to the given namespace URI, starting from this node. The default namespace declarations are ignored by this method.

See for details on the algorithm used by this method.

Should this be optional?

No.

How does the lookup work? Is it based on the prefix of the nodes, the namespace declaration attributes, or a combination of both?

See .

The namespace URI to look for.

Returns an associated namespace prefix if found or null if none is found. If more than one prefix are associated to the namespace prefix, the returned namespace prefix is implementation dependent.

This method checks if the specified namespaceURI is the default namespace or not.

The namespace URI to look for.

true if the specified namespaceURI is the default namespace, false otherwise.

Look up the namespace URI associated to the given prefix, starting from this node.

See for details on the algorithm used by this method.

Name? May need to change depending on ending of the relative namespace URI reference nightmare.

No need.

Should this be optional?

No.

How does the lookup work? Is it based on the namespaceURI of the nodes, the namespace declaration attributes, or a combination of both?

See .

The prefix to look for. If this parameter is null, the method will return the default namespace URI if any.

Returns the associated namespace URI or null if none is found.

Tests whether two nodes are equal.

This method tests for equality of nodes, not sameness (i.e., whether the two nodes are references to the same object) which can be tested with Node.isSameNode. All nodes that are the same will also be equal, though the reverse may not be true.

Two nodes are equal if and only if the following conditions are satisfied:

The two nodes are of the same type.

The following string attributes are equal: nodeName, localName, namespaceURI, prefix, nodeValue, baseURI. This is: they are both null, or they have the same length and are character for character identical.

The attributes NamedNodeMaps are equal. This is: they are both null, or they have the same length and for each node that exists in one map there is a node that exists in the other map and is equal, although not necessarily at the same index.

The childNodes NodeLists are equal. This is: they are both null, or they have the same length and contain equal nodes at the same index. Note that normalization can affect equality; to avoid this, nodes should be normalized before being compared.

For two DocumentType nodes to be equal, the following conditions must also be satisfied:

The following string attributes are equal: publicId, systemId, internalSubset.

The entities NamedNodeMaps are equal.

The notations NamedNodeMaps are equal.

On the other hand, the following do not affect equality: the ownerDocument attribute, the specified attribute for Attr nodes, the isWhitespaceInElementContent attribute for Text nodes, as well as any user data or event listeners registered on the nodes.

Should this be optional?

No.

Should the deep parameter be dropped?

Yes (Telcon Apr 3, 2002).

The node to compare equality with.

If the nodes, and possibly subtrees are equal, true otherwise false.

This method makes available a Node's specialized interface (see ).

What are the relations between Node.isSupported and Node3.getInterface?

Should we rename this method (and also DOMImplementation.getInterface?)?

getInterface can return a node that doesn't actually support the requested interface and will lead to a cast exception. Other solutions are returning null or throwing an exception.

The name of the feature requested (case-insensitive).

Returns an alternate Node which implements the specialized APIs of the specified feature, if any, or null if there is no alternate Node which implements interfaces associated with that feature. Any alternate Node returned by this method must delegate to the primary core Node and not return results inconsistent with the primary core Node such as key, attributes, childNodes, etc.

Associate an object to a key on this node. The object can later be retrieved from this node by calling getUserData with the same key.

The key to associate the object to.

The object to associate to the given key, or null to remove any existing association to that key.

The handler to associate to that key, or null.

Returns the DOMUserData previously associated to the given key on this node, or null if there was none.

Retrieves the object associated to a key on a this node. The object must first have been set to this node by calling setUserData with the same key.

The key the object is associated to.

Returns the DOMUserData associated to the given key on this node, or null if there was none.

The NodeList interface provides the abstraction of an ordered collection of nodes, without defining or constraining how this collection is implemented. NodeList objects in the DOM are live.

The items in the NodeList are accessible via an integral index, starting from 0.

Returns the indexth item in the collection. If index is greater than or equal to the number of nodes in the list, this returns null.

Index into the collection.

The node at the indexth position in the NodeList, or null if that is not a valid index.

The number of nodes in the list. The range of valid child node indices is 0 to length-1 inclusive.

Objects implementing the NamedNodeMap interface are used to represent collections of nodes that can be accessed by name. Note that NamedNodeMap does not inherit from NodeList; NamedNodeMaps are not maintained in any particular order. Objects contained in an object implementing NamedNodeMap may also be accessed by an ordinal index, but this is simply to allow convenient enumeration of the contents of a NamedNodeMap, and does not imply that the DOM specifies an order to these Nodes.

NamedNodeMap objects in the DOM are live.

Retrieves a node specified by name.

The nodeName of a node to retrieve.

A Node (of any type) with the specified nodeName, or null if it does not identify any node in this map.

Adds a node using its nodeName attribute. If a node with that name is already present in this map, it is replaced by the new one. Replacing a node by itself has no effect.

As the nodeName attribute is used to derive the name which the node must be stored under, multiple nodes of certain types (those that have a "special" string value) cannot be stored as the names would clash. This is seen as preferable to allowing nodes to be aliased.

A node to store in this map. The node will later be accessible using the value of its nodeName attribute.

If the new Node replaces an existing node the replaced Node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if arg was created from a different document than the one that created this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

INUSE_ATTRIBUTE_ERR: Raised if arg is an Attr that is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

HIERARCHY_REQUEST_ERR: Raised if an attempt is made to add a node doesn't belong in this NamedNodeMap. Examples would include trying to insert something other than an Attr node into an Element's map of attributes, or a non-Entity node into the DocumentType's map of Entities.

Removes a node specified by name. When this map contains the attributes attached to an element, if the removed attribute is known to have a default value, an attribute immediately appears containing the default value as well as the corresponding namespace URI, local name, and prefix when applicable.

The nodeName of the node to remove.

The node removed from this map if a node with such a name exists.

NOT_FOUND_ERR: Raised if there is no node named name in this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

Returns the indexth item in the map. If index is greater than or equal to the number of nodes in this map, this returns null.

Index into this map.

The node at the indexth position in the map, or null if that is not a valid index.

The number of nodes in this map. The range of valid child node indices is 0 to length-1 inclusive.

Retrieves a node specified by local name and namespace URI.

Documents which do not support the "XML" feature will permit only the DOM Level 1 calls for creating/setting elements and attributes. Hence, if you specify a non-null namespace URI, these DOMs will never find a matching node.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the node to retrieve.

The local name of the node to retrieve.

A Node (of any type) with the specified local name and namespace URI, or null if they do not identify any node in this map.

Adds a node using its namespaceURI and localName. If a node with that namespace URI and that local name is already present in this map, it is replaced by the new one. Replacing a node by itself has no effect.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

A node to store in this map. The node will later be accessible using the value of its namespaceURI and localName attributes.

If the new Node replaces an existing node the replaced Node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if arg was created from a different document than the one that created this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

INUSE_ATTRIBUTE_ERR: Raised if arg is an Attr that is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Removes a node specified by local name and namespace URI. A removed attribute may be known to have a default value when this map contains the attributes attached to an element, as returned by the attributes attribute of the Node interface. If so, an attribute immediately appears containing the default value as well as the corresponding namespace URI, local name, and prefix when applicable.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the node to remove.

The local name of the node to remove.

The node removed from this map if a node with such a local name and namespace URI exists.

NOT_FOUND_ERR: Raised if there is no node with the specified namespaceURI and localName in this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

The CharacterData interface extends Node with a set of attributes and methods for accessing character data in the DOM. For clarity this set is defined here rather than on each object that uses these attributes and methods. No DOM objects correspond directly to CharacterData, though Text and others do inherit the interface from it. All offsets in this interface start from 0.

As explained in the DOMString interface, text strings in the DOM are represented in UTF-16, i.e. as a sequence of 16-bit units. In the following, the term 16-bit units is used whenever necessary to indicate that indexing on CharacterData is done in 16-bit units.

The character data of the node that implements this interface. The DOM implementation may not put arbitrary limits on the amount of data that may be stored in a CharacterData node. However, implementation limits may mean that the entirety of a node's data may not fit into a single DOMString. In such cases, the user may call substringData to retrieve the data in appropriately sized pieces.

When the CharacterData is a Text, or a CDATASection, this attribute contains the property [character code] defined in . When the CharacterData is a Comment, this attribute contains the property [content] defined by the Comment Information Item in .

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

DOMSTRING_SIZE_ERR: Raised when it would return more characters than fit in a DOMString variable on the implementation platform.

The number of 16-bit units that are available through data and the substringData method below. This may have the value zero, i.e., CharacterData nodes may be empty.

Extracts a range of data from the node.

Start offset of substring to extract.

The number of 16-bit units to extract.

The specified substring. If the sum of offset and count exceeds the length, then all 16-bit units to the end of the data are returned.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data, or if the specified count is negative.

DOMSTRING_SIZE_ERR: Raised if the specified range of text does not fit into a DOMString.

Append the string to the end of the character data of the node. Upon success, data provides access to the concatenation of data and the DOMString specified.

The DOMString to append.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Insert a string at the specified 16-bit unit offset.

The character offset at which to insert.

The DOMString to insert.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Remove a range of 16-bit units from the node. Upon success, data and length reflect the change.

The offset from which to start removing.

The number of 16-bit units to delete. If the sum of offset and count exceeds length then all 16-bit units from offset to the end of the data are deleted.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data, or if the specified count is negative.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Replace the characters starting at the specified 16-bit unit offset with the specified string.

The offset from which to start replacing.

The number of 16-bit units to replace. If the sum of offset and count exceeds length, then all 16-bit units to the end of the data are replaced; (i.e., the effect is the same as a remove method call with the same range, followed by an append method invocation).

The DOMString with which the range must be replaced.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data, or if the specified count is negative.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

The Attr interface represents an attribute in an Element object. Typically the allowable values for the attribute are defined in a document type definition.

Attr objects inherit the Node interface, but since they are not actually child nodes of the element they describe, the DOM does not consider them part of the document tree. Thus, the Node attributes parentNode, previousSibling, and nextSibling have a null value for Attr objects. The DOM takes the view that attributes are properties of elements rather than having a separate identity from the elements they are associated with; this should make it more efficient to implement such features as default attributes associated with all elements of a given type. Furthermore, Attr nodes may not be immediate children of a DocumentFragment. However, they can be associated with Element nodes contained within a DocumentFragment. In short, users and implementors of the DOM need to be aware that Attr nodes have some things in common with other objects inheriting the Node interface, but they also are quite distinct.

The attribute's effective value is determined as follows: if this attribute has been explicitly assigned any value, that value is the attribute's effective value; otherwise, if there is a declaration for this attribute, and that declaration includes a default value, then that default value is the attribute's effective value; otherwise, the attribute does not exist on this element in the structure model until it has been explicitly added. Note that the nodeValue attribute on the Attr instance can also be used to retrieve the string version of the attribute's value(s).

In XML, where the value of an attribute can contain entity references, the child nodes of the Attr node may be either Text or EntityReference nodes (when these are in use; see the description of EntityReference for discussion). Because the DOM Core is not aware of attribute types, it treats all attribute values as simple strings, even if the DTD or schema declares them as having tokenized types.

The DOM implementation does not perform any attribute value normalization. While it is expected that the value and nodeValue attributes of an Attr node initially return the normalized value, this may not be the case after mutation. This is true, independently of whether the mutation is performed by setting the string value directly or by changing the Attr child nodes. In particular, this is true when character entity references are involved, given that they are not represented in the DOM and they impact attribute value normalization.

The properties [attribute type] and [references] defined in are not accessible from DOM Level 3 Core.

Returns the name of this attribute.

True if this attribute was explicitly given a value in the instance document, false otherwise. If the user changes the value of this attribute node (even if it ends up having the same value as the default value) then this is set to true. Removing attributes for which a default value is defined in the DTD generates a new attribute with the default value and this set to false. The implementation may handle attributes with default values from other schemas similarly but applications should use normalizeDocument() to guarantee this information is up-to-date.

This attribute is based on the property [specified] defined .

On retrieval, the value of the attribute is returned as a string. Character and general entity references are replaced with their values. See also the method getAttribute on the Element interface.

On setting, this creates a Text node with the unparsed contents of the string. I.e. any characters that an XML processor would recognize as markup are instead treated as literal text. See also the method setAttribute on the Element interface.

If the value does contain the normalized attribute value, this attribute represents the property [normalized value] defined in .

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

The Element node this attribute is attached to or null if this attribute is not in use.

This attribute represents the property [owner element] defined in .

Returns whether this attribute is known to be of type ID or not. When it is and its value is unique, the ownerElement of this attribute can be retrieved using getElementById on Document.

This translates to getIsId() in Java. Is that ok?

The Element interface represents an element in an HTML or XML document. Elements may have attributes associated with them; since the Element interface inherits from Node, the generic Node interface attribute attributes may be used to retrieve the set of all attributes for an element. There are methods on the Element interface to retrieve either an Attr object by name or an attribute value by name. In XML, where an attribute value may contain entity references, an Attr object should be retrieved to examine the possibly fairly complex sub-tree representing the attribute value. On the other hand, in HTML, where all attributes have simple string values, methods to directly access an attribute value can safely be used as a convenience.

In DOM Level 2, the method normalize is inherited from the Node interface where it was moved.

The property [in-scope namespaces] defined in are not accessible from DOM Level 3 Core. However, does provide a way to access the property [in-scope namespaces].

The name of the element. For example, in: <elementExample id="demo"> ... </elementExample> , tagName has the value "elementExample". Note that this is case-preserving in XML, as are all of the operations of the DOM. The HTML DOM returns the tagName of an HTML element in the canonical uppercase form, regardless of the case in the source HTML document.

Retrieves an attribute value by name.

The name of the attribute to retrieve.

The Attr value as a string, or the empty string if that attribute does not have a specified or default value.

Adds a new attribute. If an attribute with that name is already present in the element, its value is changed to be that of the value parameter. This value is a simple string; it is not parsed as it is being set. So any markup (such as syntax to be recognized as an entity reference) is treated as literal text, and needs to be appropriately escaped by the implementation when it is written out. In order to assign an attribute value that contains entity references, the user must create an Attr node plus any Text and EntityReference nodes, build the appropriate subtree, and use setAttributeNode to assign it as the value of an attribute.

To set an attribute with a qualified name and namespace URI, use the setAttributeNS method.

The name of the attribute to create or alter.

Value to set in string form.

INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Removes an attribute by name. If a default value for the removed attribute is defined in the DTD, a new attribute immediately appears with the default value as well as the corresponding namespace URI, local name, and prefix when applicable. The implementation may handle default values from other schemas similarly but applications should use normalizeDocument() to guarantee this information is up-to-date.

If no attribute with this name is found, this method has no effect.

To remove an attribute by local name and namespace URI, use the removeAttributeNS method.

The name of the attribute to remove.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Retrieves an attribute node by name.

To retrieve an attribute node by qualified name and namespace URI, use the getAttributeNodeNS method.

The name (nodeName) of the attribute to retrieve.

The Attr node with the specified name (nodeName) or null if there is no such attribute.

Adds a new attribute node. If an attribute with that name (nodeName) is already present in the element, it is replaced by the new one. Replacing an attribute node by itself has no effect.

To add a new attribute node with a qualified name and namespace URI, use the setAttributeNodeNS method.

The Attr node to add to the attribute list.

If the newAttr attribute replaces an existing attribute, the replaced Attr node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if newAttr was created from a different document than the one that created the element.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

INUSE_ATTRIBUTE_ERR: Raised if newAttr is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

Removes the specified attribute node. If a default value for the removed Attr node is defined in the DTD, a new node immediately appears with the default value as well as the corresponding namespace URI, local name, and prefix when applicable. The implementation may handle default values from other schemas similarly but applications should use normalizeDocument() to guarantee this information is up-to-date.

The Attr node to remove from the attribute list.

The Attr node that was removed.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if oldAttr is not an attribute of the element.

Returns a NodeList of all descendant Elements with a given tag name, in document order.

The name of the tag to match on. The special value "*" matches all tags.

A list of matching Element nodes.

Retrieves an attribute value by local name and namespace URI.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to retrieve.

The local name of the attribute to retrieve.

The Attr value as a string, or the empty string if that attribute does not have a specified or default value.

Adds a new attribute. If an attribute with the same local name and namespace URI is already present on the element, its prefix is changed to be the prefix part of the qualifiedName, and its value is changed to be the value parameter. This value is a simple string; it is not parsed as it is being set. So any markup (such as syntax to be recognized as an entity reference) is treated as literal text, and needs to be appropriately escaped by the implementation when it is written out. In order to assign an attribute value that contains entity references, the user must create an Attr node plus any Text and EntityReference nodes, build the appropriate subtree, and use setAttributeNodeNS or setAttributeNode to assign it as the value of an attribute.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to create or alter.

The qualified name of the attribute to create or alter.

The value to set in string form.

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Removes an attribute by local name and namespace URI. If a default value for the removed attribute is defined in the DTD, a new attribute immediately appears with the default value as well as the corresponding namespace URI, local name, and prefix when applicable. The implementation may handle default values from other schemas similarly but applications should use normalizeDocument() to guarantee this information is up-to-date.

If no attribute with this local name and namespace URI is found, this method has no effect.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to remove.

The local name of the attribute to remove.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Retrieves an Attr node by local name and namespace URI.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to retrieve.

The local name of the attribute to retrieve.

The Attr node with the specified attribute local name and namespace URI or null if there is no such attribute.

Adds a new attribute. If an attribute with that local name and that namespace URI is already present in the element, it is replaced by the new one. Replacing an attribute node by itself has no effect.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The Attr node to add to the attribute list.

If the newAttr attribute replaces an existing attribute with the same local name and namespace URI, the replaced Attr node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if newAttr was created from a different document than the one that created the element.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

INUSE_ATTRIBUTE_ERR: Raised if newAttr is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Returns a NodeList of all the descendant Elements with a given local name and namespace URI in document order.

The namespace URI of the elements to match on. The special value "*" matches all namespaces.

The local name of the elements to match on. The special value "*" matches all local names.

A new NodeList object containing all the matched Elements.

Returns true when an attribute with a given name is specified on this element or has a default value, false otherwise.

The name of the attribute to look for.

true if an attribute with the given name is specified on this element or has a default value, false otherwise.

Returns true when an attribute with a given local name and namespace URI is specified on this element or has a default value, false otherwise.

Per , applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to look for.

The local name of the attribute to look for.

true if an attribute with the given local name and namespace URI is specified or has a default value on this element, false otherwise.

Declares the attribute specified by name to be of type ID. If the value of the specified attribute is unique then this element node can later be retrieved using getElementById on Document. Note, however, that this simply affects this node and does not change any grammar that may be in use.

To specify an attribute by local name and namespace URI, use the setIdAttributeNS method.

The name of the attribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if the specified node is not an attribute of this element.

removeAttribute is a no-op if the attribute does not exist. Does it matter?

removeAttribute is fine as a no-op because the application gets the right result. This isn't true here. So keep the exception. (Telcon 2002 June 12)

Declares the attribute specified by local name and namespace URI to be of type ID. If the value of the specified attribute is unique then this element node can later be retrieved using getElementById on Document. Note, however, that this simply affects this node and does not change any grammar that may be in use.

The namespace URI of the attribute.

The local name of the attribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if the specified node is not an attribute of this element.

removeAttributeNS is a no-op if the attribute does not exist. Does it matter?

removeAttributeNS is fine as a no-op because the application gets the right result. This isn't true here. So keep the exception. (Telcon 2002 June 12)

Declares the attribute specified by node to be of type ID. If the value of the specified attribute is unique then this element node can later be retrieved using getElementById on Document. Note, however, that this simply affects this node and does not change any grammar that may be in use.

The attribute node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if the specified node is not an attribute of this element.

The Text interface inherits from CharacterData and represents the textual content (termed character data in XML) of an Element or Attr. If there is no markup inside an element's content, the text is contained in a single object implementing the Text interface that is the only child of the element. If there is markup, it is parsed into the information items (elements, comments, etc.) and Text nodes that form the list of children of the element.

When a document is first made available via the DOM, there is only one Text node for each block of text. Users may create adjacent Text nodes that represent the contents of a given element without any intervening markup, but should be aware that there is no way to represent the separations between these nodes in XML or HTML, so they will not (in general) persist between DOM editing sessions. The normalize method on Node merges any such adjacent Text objects into a single node for each block of text.

Breaks this node into two nodes at the specified offset, keeping both in the tree as siblings. After being split, this node will contain all the content up to the offset point. A new node of the same type, which contains all the content at and after the offset point, is returned. If the original node had a parent node, the new node is inserted as the next sibling of the original node. When the offset is equal to the length of this node, the new node has no data.

The 16-bit unit offset at which to split, starting from 0.

The new node, of the same type as this node.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Returns whether this text node contains whitespace in element content, often abusively called "ignorable whitespace".

This attribute represents the property [element content whitespace] defined in .

Returns all text of Text nodes logically-adjacent text nodes to this node, concatenated in document order.

Substitutes the a specified text for the text of the current node and all logically-adjacent text nodes.

This method returns the node in the hierarchy which received the replacement text, which is null if the text was empty or is the current node if the current node is not read-only or otherwise is a new node of the same type as the current node inserted at the site of the replacement. All logically-adjacent text nodes are removed including the current node unless it was the recipient of the replacement text.

Where the nodes to be removed are read-only descendants of an EntityReference, the EntityReference must be removed instead of the read-only nodes. If any EntityReference to be removed has descendants that are not EntityReference, Text, or CDATASection nodes, the replaceWholeText method must fail before performing any modification of the document, raising a DOMException with the code NO_MODIFICATION_ALLOWED_ERR.

The content of the replacing Text node.

The Text node created with the specified content.

NO_MODIFICATION_ALLOWED_ERR: Raised if one of the Text nodes being replaced is readonly.

This interface inherits from CharacterData and represents the content of a comment, i.e., all the characters between the starting ''. Note that this is the definition of a comment in XML, and, in practice, HTML, although some HTML tools may implement the full SGML comment structure.

When associating an object to a key on a node using setUserData the application can provide a handler that gets called when the node the object is associated to is being cloned, imported, or renamed. This can be used by the application to implement various behaviors regarding the data it associates to the DOM nodes. This interface defines that handler.

An integer indicating the type of operation being performed on a node.

The node is cloned.

The node is imported.

The node is deleted.

The node is renamed.

This method is called whenever the node for which this handler is registered is imported or cloned.

Specifies the type of operation that is being performed on the node.

Specifies the key for which this handler is being called.

Specifies the data for which this handler is being called.

Specifies the node being cloned, imported, or renamed. This is null when the node is being deleted.

Specifies the node newly created if any, or null.

DOMError is an interface that describes an error.

An integer indicating the severity of the error.

The severity of the error described by the DOMError is warning

The severity of the error described by the DOMError is error

The severity of the error described by the DOMError is fatal error

The severity of the error, either SEVERITY_WARNING, SEVERITY_ERROR, or SEVERITY_FATAL_ERROR.

An implementation specific string describing the error that occured.

A DOMString indicating which related data is expected in relatedData. Users should refer to the specification of the error in order to find its DOMString type and relatedData definitions if any.

As an example, does not keep the [baseURI] property defined on a Processing Instruction information item. Therefore, the DOMBuilder generates a SEVERITY_WARNING with type "infoset-baseURI" and the lost [baseURI] property represented as a DOMString in the relatedData attribute.

The related platform dependent exception if any.

exception is a reserved word, we need to rename it.

Change to "relatedException". (F2F 26 Sep 2001)

The related Error.type dependent data if any.

The location of the error.

DOMErrorHandler is a callback interface that the DOM implementation can call when reporting errors that happens while processing XML data, or when doing some other processing (e.g. validating a document).

The application that is using the DOM implementation is expected to implement this interface.

How does one register an error handler in the core? Passed as an argument to super-duper-normalize or registered on the DOMImplementation?

Document interface has an attribute errorHandler.

This method is called on the error handler when an error occures.

The error object that describes the error, this object may be reused by the DOM implementation across multiple calls to the handleEvent method.

If the handleError method returns true the DOM implementation should continue as if the error didn't happen when possible, if the method returns false then the DOM implementation should stop the current processing when possible.

DOMLocator is an interface that describes a location (e.g. where an error occured).

The line number this locator is pointing to, or -1 if there is no column number available.

The column number this locator is pointing to, or -1 if there is no column number available.

The byte or character offset into the input source this locator is pointing to. If the input source is a file or a byte stream then this is the byte offset into that stream, but if the input source is a character media then the offset is the character offset. The value is -1 if there is no offset available.

The node this locator is pointing to, or null if no node is available.

The URI this locator is pointing to, or null if no URI is available.

Extended Interfaces

The interfaces defined here form part of the DOM Core specification, but objects that expose these interfaces will never be encountered in a DOM implementation that deals only with HTML.

The interfaces found within this section are not mandatory. A DOM application may use the hasFeature(feature, version) method of the DOMImplementation interface with parameter values "XML" and "3.0" (respectively) to determine whether or not this module is supported by the implementation. In order to fully support this module, an implementation must also support the "Core" feature defined in . Please refer to additional information about in this specification. The DOM Level 3 XML module is backward compatible with the DOM Level 2 XML and DOM Level 1 XML modules, i.e. a DOM Level 3 XML implementation who returns true for "XML" with the version number "3.0" must also return true for this feature when the version number is "2.0", "1.0", "" or, null.

CDATA sections are used to escape blocks of text containing characters that would otherwise be regarded as markup. The only delimiter that is recognized in a CDATA section is the "]]>" string that ends the CDATA section. CDATA sections cannot be nested. Their primary purpose is for including material such as XML fragments, without needing to escape all the delimiters.

The DOMString attribute of the Text node holds the text that is contained by the CDATA section. Note that this may contain characters that need to be escaped outside of CDATA sections and that, depending on the character encoding ("charset") chosen for serialization, it may be impossible to write out some characters as part of a CDATA section.

The CDATASection interface inherits from the CharacterData interface through the Text interface. Adjacent CDATASection nodes are not merged by use of the normalize method of the Node interface.

Because no markup is recognized within a CDATASection, character numeric references cannot be used as an escape mechanism when serializing. Therefore, action needs to be taken when serializing a CDATASection with a character encoding where some of the contained characters cannot be represented. Failure to do so would not produce well-formed XML.

One potential solution in the serialization process is to end the CDATA section before the character, output the character using a character reference or entity reference, and open a new CDATA section for any further characters in the text node. Note, however, that some code conversion libraries at the time of writing do not return an error or exception when a character is missing from the encoding, making the task of ensuring that data is not corrupted on serialization more difficult.

Each Document has a doctype attribute whose value is either null or a DocumentType object. The DocumentType interface in the DOM Core provides an interface to the list of entities that are defined for the document, and little else because the effect of namespaces and the various XML schema efforts on DTD representation are not clearly understood as of this writing.

The DOM Level 2 doesn't support editing DocumentType nodes. DocumentType nodes are read-only.

The property [children] defined by the Document Type Declaration Information Item in is not accessible from DOM Level 3 Core.

The name of DTD; i.e., the name immediately following the DOCTYPE keyword.

A NamedNodeMap containing the general entities, both external and internal, declared in the DTD. Parameter entities are not contained. Duplicates are discarded. For example in: <!DOCTYPE ex SYSTEM "ex.dtd" [ <!ENTITY foo "foo"> <!ENTITY bar "bar"> <!ENTITY bar "bar2"> <!ENTITY % baz "baz"> ]> <ex/> the interface provides access to foo and the first declaration of bar but not the second declaration of bar or baz. Every node in this map also implements the Entity interface.

The DOM Level 2 does not support editing entities, therefore entities cannot be altered in any way.

A NamedNodeMap containing the notations declared in the DTD. Duplicates are discarded. Every node in this map also implements the Notation interface.

The DOM Level 2 does not support editing notations, therefore notations cannot be altered in any way.

This attribute represents the property [notations] defined by the Document Information Item in .

The public identifier of the external subset.

This attribute represents the property [public identifier] defined by the Document Type Declaration Information Item in .

The system identifier of the external subset. This may be an absolute URI or not.

This attribute represents the property [system identifier] defined by the Document Type Declaration Information Item in .

The internal subset as a string, or null if there is none. This is does not contain the delimiting square brackets.

The actual content returned depends on how much information is available to the implementation. This may vary depending on various parameters, including the XML processor used to build the document.

This interface represents a notation declared in the DTD. A notation either declares, by name, the format of an unparsed entity (see section 4.7 of the XML 1.0 specification ), or is used for formal declaration of processing instruction targets (see section 2.6 of the XML 1.0 specification ). The nodeName attribute inherited from Node is set to the declared name of the notation.

The DOM Core does not support editing Notation nodes; they are therefore readonly.

A Notation node does not have any parent.

adds a namespaceURI for notations?

No. 1- notations are attached to a DocumentType. 2- what would be the key for notations in namednodemap?

The public identifier of this notation. If the public identifier was not specified, this is null.

This attribute represents the property [public identifier] defined by the Notation Information Item in .

The system identifier of this notation. If the system identifier was not specified, this is null. This may be an absolute URI or not.

This attribute represents the property [system identifier] defined by the Notation Information Item in .

This interface represents a known entity, either parsed or unparsed, in an XML document. Note that this models the entity itself not the entity declaration.

The nodeName attribute that is inherited from Node contains the name of the entity.

An XML processor may choose to completely expand entities before the structure model is passed to the DOM; in this case there will be no EntityReference nodes in the document tree.

XML does not mandate that a non-validating XML processor read and process entity declarations made in the external subset or declared in external parameter entities. This means that parsed entities declared in the external subset need not be expanded by some classes of applications, and that the replacement text of the entity may not be available. When the replacement text is available, the corresponding Entity node's child list represents the structure of that replacement value. Otherwise, the child list is empty.

The DOM Level 2 does not support editing Entity nodes; if a user wants to make changes to the contents of an Entity, every related EntityReference node has to be replaced in the structure model by a clone of the Entity's contents, and then the desired changes must be made to each of those clones instead. Entity nodes and all their descendants are readonly.

An Entity node does not have any parent.

If the entity contains an unbound namespace prefix, the namespaceURI of the corresponding node in the Entity node subtree is null. The same is true for EntityReference nodes that refer to this entity, when they are created using the createEntityReference method of the Document interface. The DOM Level 2 does not support any mechanism to resolve namespace prefixes.

The properties [notation name] and [notation] defined in are not accessible from DOM Level 3 Core.

The public identifier associated with the entity if specified, and null otherwise.

This attribute represents the property [public identifier] defined by the Unparsed Entity Information Item in .

The system identifier associated with the entity if specified, and null otherwise. This may be an absolute URI or not.

This attribute represents the property [system identifier] defined by the Unparsed Entity Information Item in .

For unparsed entities, the name of the notation for the entity. For parsed entities, this is null.

An attribute specifying the actual encoding of this entity, when it is an external parsed entity. This is null otherwise.

An attribute specifying, as part of the text declaration, the encoding of this entity, when it is an external parsed entity. This is null otherwise.

An attribute specifying, as part of the text declaration, the version number of this entity, when it is an external parsed entity. This is null otherwise.

EntityReference nodes may be used to represent an entity reference in the tree. Note that character references and references to predefined entities are considered to be expanded by the HTML or XML processor so that characters are represented by their Unicode equivalent rather than by an entity reference. Moreover, the XML processor may completely expand references to entities while building the Document, instead of providing EntityReference nodes. If it does provide such nodes, then for an EntityReference node that represents a reference to a known entity an Entity exists, and the subtree of the EntityReference node is a copy of the Entity node subtree. However, the latter may not be true when an entity contains an unbound namespace prefix. In such a case, because the namespace prefix resolution depends on where the entity reference is, the descendants of the EntityReference node may be bound to different namespace URIs. When an EntityReference node represents a reference to an unknown entity, its content is empty.

As for Entity nodes, EntityReference nodes and all their descendants are readonly.

The properties [system identifier] and [public identifier] defined by the Unexpanded Entity Reference Information Item in are accessible through the Entity interface. The property [all declarations processed] is not accessible through the DOM API.

EntityReference nodes may cause element content and attribute value normalization problems when, such as in XML 1.0 and XML Schema, the normalization is be performed after entity reference are expanded.

The ProcessingInstruction interface represents a "processing instruction", used in XML as a way to keep processor-specific information in the text of the document.

The property [notation] defined in is not accessible from DOM Level 3 Core.

The target of this processing instruction. XML defines this as being the first token following the markup that begins the processing instruction.

This attribute represents the property [target] defined in .

The content of this processing instruction. This is from the first non white space character after the target to the character immediately preceding the ?>.

This attribute represents the property [content] defined by the Processing Instruction Information Item in .

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

Changes Arnaud Le Hors IBM Philippe Le Hégaret W3C Changes between DOM Level 2 Core and DOM Level 3 Core

To be completed...

Changes between DOM Level 1 Core and DOM Level 2 Core OMG IDL

The DOM Level 2 specifications are now using Corba 2.3.1 instead of Corba 2.2.

Type DOMString

The definition of DOMString in IDL is now a valuetype.

Changes to DOM Level 1 Core interfaces and exceptions Interface Attr

The Attr interface has one new attribute: ownerElement.

Interface Document

The Document interface has five new methods: importNode, createElementNS, createAttributeNS, getElementsByTagNameNS and getElementById.

Interface NamedNodeMap

The NamedNodeMap interface has three new methods: getNamedItemNS, setNamedItemNS, removeNamedItemNS.

Interface Node

The Node interface has two new methods: isSupported and hasAttributes.

normalize, previously in the Element interface, has been moved in the Node interface.

The Node interface has three new attributes: namespaceURI, prefix and localName.

The ownerDocument attribute was specified to be null when the node is a Document. It now is also null when the node is a DocumentType which is not used with any Document yet.

Interface DocumentType

The DocumentType interface has three attributes: publicId, systemId and internalSubset.

Interface DOMImplementation

The DOMImplementation interface has two new methods: createDocumentType and createDocument.

Interface Element

The Element interface has eight new methods: getAttributeNS, setAttributeNS, removeAttributeNS, getAttributeNodeNS, setAttributeNodeNS, getElementsByTagNameNS, hasAttribute and hasAttributeNS.

The method normalize is now inherited from the Node interface where it was moved.

Exception DOMException

The DOMException has five new exception codes: INVALID_STATE_ERR, SYNTAX_ERR, INVALID_MODIFICATION_ERR, NAMESPACE_ERR and INVALID_ACCESS_ERR.

New features New types DOMTimeStamp

The DOMTimeStamp type was added to the Core module.

Namespaces Algorithms Arnaud Le Hors IBM Elena Litani IBM Namespace normalization

Namespace declaration attributes and prefixes are normalized as part of the normalizeDocument method of the Document interface as if the following method described in pseudo code was called on the document element. void Element.normalizeNamespaces() { if ( Element's namespaceURI != null ) { if ( Element's prefix/namespace pair (or default namespace, if no prefix) are within the scope of a binding ) { ==> do nothing, declaration in scope is inherited See example 1 } else { ==> Create a local namespace declaration attr for this namespace, with Element's current prefix (or a default namespace, if no prefix). If there's a conflicting local declaration already present, change its value to use this namespace. See example 2 // NOTE that this may break other nodes within this Element's // subtree, if they're already using this prefix. // They will be repaired when we reach them. } } else { // Element has no namespace URI: if ( Element has a colon in its name ) { // DOM Level 1 node ==> if in process of validation against a namespace aware schema (i.e XML Schema) report a fatal error: the processor can not recover in this situation. Otherwise, report an error: no namespace fixup will be performed on this node. } else { // Element has no namespace URI // Element has no pseudo-prefix if ( default Namespace in scope is "no namespace" ) { ==> do nothing, we're fine as we stand } else { if ( there's a conflicting local default namespace declaration already present ) { ==> change its value to use this empty namespace. See example 3 } else { ==> Set the default namespace to "no namespace" by creating or changing a local declaration attribute: xmlns="". See example 4 } // NOTE that this may break other nodes within this Element's // subtree, if they're already using the default namespaces. // They will be repaired when we reach them. } } } //////// EXAMINE AND POLISH THE ATTRS //////// for ( all DOM Level 2 valid local namespace declaration attributes of Element ) { if (the namespace declaration is invalid) { // Note: The prefix xmlns is used only to declare namespace bindings and // is by definition bound to the namespace name http://www.w3.org/2000/xmlns/. // It must not be declared. No other prefix may be bound to this namespace name. ==> Report an error. } else { ==> Record the namespace declaration } } for ( all non-namespace Attrs of Element ) { if ( Attr[i] has a namespace URI ) { if ( attribute has no prefix (default namespace decl does not apply to attributes) OR attribute prefix is not declared OR conflict: attribute has a prefix that conficlicts with a binding already active in scope) { if (namespaceURI matches an in scope declaration of one or more prefixes) { // pick the most local binding available; // if there is more than one pick one arbitrarily ==> change attribute's prefix. } else { if (the current prefix is not null and it has no in scope declaration) { ==> declare this prefix } else { // find a prefix following the pattern "NS" +index (starting at 1) // make sure this prefix is not declared in the current scope. // create a local namespace declaration attribute ==> change attribute's prefix. } } } else { // Attr[i] has no namespace URI if ( Attr[i] has a colon in its name ) { // DOM Level 1 node ==> if in process of validation against a namespace aware schema (i.e XML Schema) report a fatal error: the processor can not recover in this situation. Otherwise, report an error: no namespace fixup will be performed on this node. } else { // attr has no namespace URI and no prefix // no action is required, since attrs don't use default ==> do nothing } } } // end for-all-Attrs // do this recursively for ( all child elements of Element ) { childElement.normalizeNamespaces() } } // end Element.normalizeNamespaces

Namespace Prefix Lookup

The following describes in pseudo code the algorithm used in the lookupPrefix method of the Node interface. Before returning found prefix the algorithm needs to make sure that the prefix is not redefined on an element from which the lookup started.

Note: this method ignores all default namespace declarations. To look up default namespace use isDefaultNamespace method. DOMString lookupPrefix(in DOMString specifiedNamespaceURI) { short type = this.getNodeType(); switch (type) { case Node.ELEMENT_NODE: { return lookupNamespacePrefix(namespaceURI, this); } case Node.DOCUMENT_NODE: { return getDocumentElement().lookupNamespacePrefix(namespaceURI); } case Node.ENTITY_NODE : case Node.NOTATION_NODE: case Node.DOCUMENT_FRAGMENT_NODE: case Node.DOCUMENT_TYPE_NODE: return null; // type is unknown case Node.ATTRIBUTE_NODE: { if ( Attr has an owner Element ) { return ownerElement.lookupNamespacePrefix(namespaceURI) } return null; } default: { if (Node has an ancestor Element ) // EntityReferences may have to be skipped to get to it { return ancestor.lookupNamespacePrefix(namespaceURI); } return null; } } } DOMString lookupNamespacePrefix(DOMString namespaceURI, Element originalElement){ if ( Element has namespace and Element's namespace == namespaceURI and Element has prefix and originalElement.lookupNamespaceURI(prefix) == namespaceURI) { return Element's prefix; } if (Element has attributes) { if (Attr's namespaceURI == "http://www.w3.org/2000/xmlns/" Attr's prefix == "xmlns" and Attr's value == namespaceURI and originalElement.lookupNamespaceURI(Attr's localname) == namespaceURI) { return Attr's localname; } } if (Node has an ancestor Element ) // EntityReferences may have to be skipped to get to it { return ancestor.lookupNamespacePrefix(namespaceURI, originalElement); } return null; }

Isn't the name the opposite of what it stands for?

No.

How does one differentiate the case where it's the default namespace (prefix == null) from the case where the namespaceURI was not found?

Not applicable. The method ignores default namespace declarations. To lookup default namespace use isDefaultNamespace.

How does one specify this is for an attribute and therefore the default namespace is not applicable?

Not applicable. The default namespace declarations are ignored.

Default Namespace Lookup

The following describes in pseudo code the algorithm used in the isDefaultNamespace method of the Node interface. boolean isDefaultNamespace(in DOMString specifiedNamespaceURI) { switch (nodeType) { case ELEMENT_NODE: if ( Element has no prefix ) { return (Element's namespaceURI == specifiedNamespaceURI) } else if ( Element has an Attr and Attr's namespaceURI == "http://www.w3.org/2000/xmlns/" and Attr's localName == "xmlns" ) { return (Attr's value == specifiedNamespaceURI) } if ( Element has an ancestor Element ) // EntityReferences may have to be skipped to get to it { return ancestorElement.isDefaultNamespace(specifiedNamespaceURI) } else { return unknown (false) } case DOCUMENT_NODE: return documentElement.isDefaultNamespace(specifiedNamespaceURI) case ENTITY_NODE: case NOTATION_NODE: case DOCUMENT_TYPE_NODE: case DOCUMENT_FRAGMENT_NODE: return unknown (false); case ATTRIBUTE_NODE: if ( Attr has an owner Element ) { return ownerElement.isDefaultNamespace(specifiedNamespaceURI) } else { return unknown (false) } default: if ( Node has an ancestor Element ) // EntityReferences may have to be skipped to get to it { return ancestorElement.isDefaultNamespace(specifiedNamespaceURI) } else { return unknown (false) } } }

What should algorithm return if the parameter - namespaceURI - is null?

If *null* as passed as a parameter the function returns true if default namespace is not available. Otherwise, if default namespace is available, return false.

Namespace URI Lookup

The following describes in pseudo code the algorithm used in the lookupNamespaceURI method of the Node interface. DOMString lookupNamespaceURI(in DOMString specifiedPrefix) { switch (nodeType) { case ELEMENT_NODE: { if ( Element's namespace URI != null and Element's prefix == specifiedPrefix ) { // Note: prefix could be "null" in this case we are looking for default namespace return Element's namespace URI } else if ( Element has an Attr and Attr's namespaceURI == "http://www.w3.org/2000/xmlns/") { if (Attr's prefix == "xmlns" and Attr's localName == specifiedPrefix ) // non default namespace { return (Attr's value) } else if (speficiedPrefix == null and Attr's name == "xmlns") // default namespace { return (Attr's value) } } if ( Element has an ancestor Element ) // EntityReferences may have to be skipped to get to it { return ancestorElement.lookupNamespaceURI(specifiedPrefix) } return null; } case DOCUMENT_NODE: return documentElement.lookupNamespaceURI(specifiedPrefix) case ENTITY_NODE: case NOTATION_NODE: case DOCUMENT_TYPE_NODE: case DOCUMENT_FRAGMENT_NODE: return unknown (null) case ATTRIBUTE_NODE: if (Attr has an owner Element) { return ownerElement.lookupNamespaceURI(specifiedPrefix) } else { return unknown (null) } default: if (Node has an ancestor Element) // EntityReferences may have to be skipped to get to it { return ancestorElement.lookupNamespaceURI(specifiedPrefix) } else { return unknown (null) } } }

How does one look for the default namespace?

use lookupNamespaceURI(null)

Accessing code point boundaries Mark Davis IBM Lauren Wood SoftQuad Software Inc. Introduction

This appendix is an informative, not a normative, part of the Level 2 DOM specification.

Characters are represented in Unicode by numbers called code points (also called scalar values). These numbers can range from 0 up to 1,114,111 = 10FFFF₁₆ (although some of these values are illegal). Each code point can be directly encoded with a 32-bit code unit. This encoding is termed UCS-4 (or UTF-32). The DOM specification, however, uses UTF-16, in which the most frequent characters (which have values less than FFFF₁₆) are represented by a single 16-bit code unit, while characters above FFFF₁₆ use a special pair of code units called a surrogate pair. For more information, see or the Unicode Web site.

While indexing by code points as opposed to code units is not common in programs, some specifications such as XPath (and therefore XSLT and XPointer) use code point indices. For interfacing with such formats it is recommended that the programming language provide string processing methods for converting code point indices to code unit indices and back. Some languages do not provide these functions natively; for these it is recommended that the native String type that is bound to DOMString be extended to enable this conversion. An example of how such an API might look is supplied below.

Since these methods are supplied as an illustrative example of the type of functionality that is required, the names of the methods, exceptions, and interface may differ from those given here.

Methods

Extensions to a language's native String class or interface

Returns the UTF-16 offset that corresponds to a UTF-32 offset. Used for random access.

You can always round-trip from a UTF-32 offset to a UTF-16 offset and back. You can round-trip from a UTF-16 offset to a UTF-32 offset and back if and only if the offset16 is not in the middle of a surrogate pair. Unmatched surrogates count as a single UTF-16 value.

UTF-32 offset.

UTF-16 offset

if offset32 is out of bounds.

Returns the UTF-32 offset corresponding to a UTF-16 offset. Used for random access. To find the UTF-32 length of a string, use: len32 = findOffset32(source, source.length());

If the UTF-16 offset is into the middle of a surrogate pair, then the UTF-32 offset of the end of the pair is returned; that is, the index of the char after the end of the pair. You can always round-trip from a UTF-32 offset to a UTF-16 offset and back. You can round-trip from a UTF-16 offset to a UTF-32 offset and back if and only if the offset16 is not in the middle of a surrogate pair. Unmatched surrogates count as a single UTF-16 value.

UTF-16 offset

UTF-32 offset

if offset16 is out of bounds.

IDL Definitions

This appendix contains the complete OMG IDL for the Level 3 Document Object Model Core definitions.

The IDL files are also available as: http://www.w3.org/2002/08/WD-DOM-Level-3-Core-20020806/idl.zip

Java Language Binding

This appendix contains the complete Java bindings for the Level 3 Document Object Model Core.

The Java files are also available as http://www.w3.org/2002/08/WD-DOM-Level-3-Core-20020806/java-binding.zip

Java Binding Extension

This section defines the DOMImplementationRegistry object, discussed in , for Java.

The DOMImplementationRegistry is first initialized by the application or the implementation, depending on the context, through the Java system property "org.w3c.dom.DOMImplementationSourceList". The value of this property is a space separated list of names of available classes implementing the DOMImplementationSource interface.

/** * This class holds the list of registered DOMImplementations. The contents * of the registry are drawn from the System Property * <code>org.w3c.dom.DOMImplementationSourceList</code>, which must contain a * white-space delimited sequence of the names of classes implementing * <code>DOMImplementationSource</code>. * Applications may also register DOMImplementationSource * implementations by using a method on this class. They may then * query instances of the registry for implementations supporting * specific features.</p> * * <p>This provides an application with an implementation-independent * starting point. * * @see DOMImplementation * @see DOMImplementationSource */ package org.w3c.dom; import java.lang.reflect.Method; import java.lang.reflect.InvocationTargetException; import java.lang.ClassLoader; import java.lang.String; import java.util.StringTokenizer; import java.util.Enumeration; import java.util.Hashtable; import org.w3c.dom.DOMImplementationSource; import org.w3c.dom.DOMImplementation; public class DOMImplementationRegistry { // The system property to specify the DOMImplementationSource class names. public final static String PROPERTY = "org.w3c.dom.DOMImplementationSourceList"; private Hashtable sources; // deny construction by other classes private DOMImplementationRegistry() { } // deny construction by other classes private DOMImplementationRegistry(Hashtable srcs) { sources = srcs; } /* * This method queries the System property * <code>org.w3c.dom.DOMImplementationSourceList</code>. If it is * able to read and parse the property, it attempts to instantiate * classes according to each space-delimited substring. Any * exceptions it encounters are thrown to the application. An application * must call this method before using the class. * @return an initialized instance of DOMImplementationRegistry */ public static DOMImplementationRegistry newInstance() throws ClassNotFoundException, InstantiationException, IllegalAccessException { Hashtable sources = new Hashtable(); // fetch system property: String p = System.getProperty(PROPERTY); if (p != null) { StringTokenizer st = new StringTokenizer(p); while (st.hasMoreTokens()) { String sourceName = st.nextToken(); // Use context class loader, falling back to Class.forName // if and only if this fails... Object source = getClass(sourceName).newInstance(); sources.put(sourceName, source); } } return new DOMImplementationRegistry(sources); } /** * Return the first registered implementation that has the desired * features, or null if none is found. * * @param features A string that specifies which features are required. * This is a space separated list in which each feature is * specified by its name optionally followed by a space * and a version number. * This is something like: "XML 1.0 Traversal Events 2.0" * @return An implementation that has the desired features, or * <code>null</code> if this source has none. */ public DOMImplementation getDOMImplementation(String features) throws ClassNotFoundException, InstantiationException, IllegalAccessException, ClassCastException { Enumeration names = sources.keys(); String name = null; while(names.hasMoreElements()) { name = (String)names.nextElement(); DOMImplementationSource source = (DOMImplementationSource) sources.get(name); DOMImplementation impl = source.getDOMImplementation(features); if (impl != null) { return impl; } } return null; } /** * Register an implementation. */ public void addSource(DOMImplementationSource s) throws ClassNotFoundException, InstantiationException, IllegalAccessException { String sourceName = s.getClass().getName(); sources.put(sourceName, s); } private static Class getClass (String className) throws ClassNotFoundException, IllegalAccessException, InstantiationException { Method m = null; ClassLoader cl = null; try { m = Thread.class.getMethod("getContextClassLoader", null); } catch (NoSuchMethodException e) { // Assume that we are running JDK 1.1, use the current ClassLoader cl = DOMImplementationRegistry.class.getClassLoader(); } if (cl == null ) { try { cl = (ClassLoader) m.invoke(Thread.currentThread(), null); } catch (IllegalAccessException e) { // assert(false) throw new UnknownError(e.getMessage()); } catch (InvocationTargetException e) { // assert(e.getTargetException() instanceof SecurityException) throw new UnknownError(e.getMessage()); } } if (cl == null) { // fall back to Class.forName return Class.forName(className); } try { return cl.loadClass(className); } catch (ClassNotFoundException e) { return Class.forName(className); } } }

With this, the first line of an application typically becomes something like (modulo exception handling):

DOMImplementation impl = DOMImplementationRegistry.getDOMImplementation("XML 1.0");

Should this provides for handling more than one implementation at a time?

Yes.

Should this be even simpler and force the implementation to provide this class (and not necessarily rely on any system property)?

No.

This requires all DOMImplementationSources to be pre-instantiated.

Proposed: It's ok.

Some people may like to be able to enumerate available implementations. DOMImplementation objects may be too dynamic to enumerate. We should explore any significant use case that cannot be solved by this proposal.

No real need. Additional features can be used to further differentiate implementations.

A space-separated feature string may not be the optimal way to pass a feature list. It was motivated by the lack of an array construct.

Proposed: It's ok.

Should "*" given as the version number be interpreted as "any version". hasFeature() does not allow this, it requires a specific version to be given.

No. (telcon xxxx)

Other Core interfaces ECMAScript Language Binding

This appendix contains the complete ECMAScript binding for the Level 3 Document Object Model Core definitions.

ECMAScript Binding Extension

This section defines the DOMImplementationRegistry object, discussed in , for ECMAScript.

Objects that implements the DOMImplementationRegistry interface DOMImplementationRegistry is a global variable which has the following functions: getDOMImplementation(features)

This method returns the first registered object that implements the DOMImplementation interface and has the desired features, or null if none is found.

The features parameter is a String.

sources

This property is an Array. It contains all registered objects that implement the DOMImplementationSource interface.

Other Core interfaces Acknowledgements

Many people contributed to the DOM specifications (Level 1, 2 or 3), including members of the DOM Working Group and the DOM Interest Group. We especially thank the following:

Andrew Watson (Object Management Group), Andy Heninger (IBM), Angel Diaz (IBM), Arnaud Le Hors (W3C and IBM), Ashok Malhotra (IBM and Microsoft), Ben Chang (Oracle), Bill Smith (Sun), Bill Shea (Merrill Lynch), Bob Sutor (IBM), Chris Lovett (Microsoft), Chris Wilson (Microsoft), David Brownell (Sun), David Ezell (Hewlett Packard Company), David Singer (IBM), Dimitris Dimitriadis (Improve AB), Don Park (invited), Elena Litani (IBM), Eric Vasilik (Microsoft), Gavin Nicol (INSO), Ian Jacobs (W3C), James Clark (invited), James Davidson (Sun), Jared Sorensen (Novell), Jeroen van Rotterdam (X-Hive Corporation), Joe Kesselman (IBM), Joe Lapp (webMethods), Joe Marini (Macromedia), Johnny Stenback (Netscape/AOL), Jon Ferraiolo (Adobe), Jonathan Marsh (Microsoft), Jonathan Robie (Texcel Research and Software AG), Kim Adamson-Sharpe (SoftQuad Software Inc.), Lauren Wood (SoftQuad Software Inc., former Chair), Laurence Cable (Sun), Mark Davis (IBM), Mark Scardina (Oracle), Martin Dürst (W3C), Mary Brady (NIST), Mick Goulish (Software AG), Mike Champion (Arbortext and Software AG), Miles Sabin (Cromwell Media), Patti Lutsky (Arbortext), Paul Grosso (Arbortext), Peter Sharpe (SoftQuad Software Inc.), Phil Karlton (Netscape), Philippe Le Hégaret (W3C, W3C team contact and former Chair), Ramesh Lekshmynarayanan (Merrill Lynch), Ray Whitmer (iMall, Excite@Home, and Netscape/AOL, Chair), Rezaur Rahman (Intel), Rich Rollman (Microsoft), Rick Gessner (Netscape), Rick Jelliffe (invited), Rob Relyea (Microsoft), Scott Isaacs (Microsoft), Sharon Adler (INSO), Steve Byrne (JavaSoft), Tim Bray (invited), Tim Yu (Oracle), Tom Pixley (Netscape/AOL), Vidur Apparao (Netscape), Vinod Anupam (Lucent).

Thanks to all those who have helped to improve this specification by sending suggestions and corrections (Please, keep bugging us with your issues!).

Production Systems

This specification was written in XML. The HTML, OMG IDL, Java and ECMAScript bindings were all produced automatically.

Thanks to Joe English, author of cost, which was used as the basis for producing DOM Level 1. Thanks also to Gavin Nicol, who wrote the scripts which run on top of cost. Arnaud Le Hors and Philippe Le Hégaret maintained the scripts.

After DOM Level 1, we used Xerces as the basis DOM implementation and wish to thank the authors. Philippe Le Hégaret and Arnaud Le Hors wrote the Java programs which are the DOM application.

Thanks also to Jan Kärrman, author of html2ps, which we use in creating the PostScript version of the specification.

Glossary Arnaud Le Hors W3C Robert S. Sutor IBM Research (for DOM Level 1)

Several of the following term definitions have been borrowed or modified from similar definitions in other W3C or standards documents. See the links within the definitions for more information.

16-bit unit

The base unit of a DOMString. This indicates that indexing on a DOMString occurs in units of 16 bits. This must not be misunderstood to mean that a DOMString can store arbitrary 16-bit units. A DOMString is a character string encoded in UTF-16; this means that the restrictions of UTF-16 as well as the other relevant restrictions on character strings must be maintained. A single character, for example in the form of a numeric character reference, may correspond to one or two 16-bit units.

ancestor

An ancestor node of any node A is any node above A in a tree model, where "above" means "toward the root."

API

An API is an Application Programming Interface, a set of functions or methods used to access some functionality.

bubbling phase

The process by which an event can be handled by one of the event observers after being handled by the target node.

capture phase

The process by which an event can be handled by one of the event observers before being handled by the target node.

child

A child is an immediate descendant node of a node.

client application

A [client] application is any software that uses the Document Object Model programming interfaces provided by the hosting implementation to accomplish useful work. Some examples of client applications are scripts within an HTML or XML document.

COM

COM is Microsoft's Component Object Model , a technology for building applications from binary software components.

content model

The content model is a simple grammar governing the allowed types of the child elements and the order in which they appear. See Element Content in XML .

context

A context specifies an access pattern (or path): a set of interfaces which give you a way to interact with a model. For example, imagine a model with different colored arcs connecting data nodes. A context might be a sheet of colored acetate that is placed over the model allowing you a partial view of the total information in the model.

convenience

A convenience method is an operation on an object that could be accomplished by a program consisting of more basic operations on the object. Convenience methods are usually provided to make the API easier and simpler to use or to allow specific programs to create more optimized implementations for common operations. A similar definition holds for a convenience property.

cooked model

A model for a document that represents the document after it has been manipulated in some way. For example, any combination of any of the following transformations would create a cooked model:

Expansion of internal text entities.

Expansion of external entities.

Model augmentation with style-specified generated text.

Execution of style-specified reordering.

Execution of scripts.

A browser might only be able to provide access to a cooked model, while an editor might provide access to a cooked or the initial structure model (also known as the uncooked model) for a document.

CORBA

CORBA is the Common Object Request Broker Architecture from the OMG . This architecture is a collection of objects and libraries that allow the creation of applications containing objects that make and receive requests and responses in a distributed environment.

cursor

A cursoris an object representation of a node. It may possess information about context and the path traversed to reach the node.

data model

A data model is a collection of descriptions of data structures and their contained fields, together with the operations or functions that manipulate them.

deprecation

When new releases of specifications are released, some older features may be marked as being deprecated. This means that new work should not use the features and that although they are supported in the current release, they may not be supported or available in future releases.

descendant

A descendant node of any node A is any node below A in a tree model, where "below" means "away from the root."

document element

There is only one document element in a Document. This element node is a child of the Document node. See Well-Formed XML Documents in XML .

document order

There is an ordering, document order, defined on all the nodes in the document corresponding to the order in which the first character of the XML representation of each node occurs in the XML representation of the document after expansion of general entities. Thus, the document element node will be the first node. Element nodes occur before their children. Thus, document order orders element nodes in order of the occurrence of their start-tag in the XML (after expansion of entities). The attribute nodes of an element occur after the element and before its children. The relative order of attribute nodes is implementation-dependent.

DOM Level 0

The term "DOM Level 0" refers to a mix (not formally specified) of HTML document functionalities offered by Netscape Navigator version 3.0 and Microsoft Internet Explorer version 3.0. In some cases, attributes or methods have been included for reasons of backward compatibility with "DOM Level 0".

ECMAScript

The programming language defined by the ECMA-262 standard . As stated in the standard, the originating technology for ECMAScript was JavaScript . Note that in the ECMAScript binding, the word "property" is used in the same sense as the IDL term "attribute."

element

Each document contains one or more elements, the boundaries of which are either delimited by start-tags and end-tags, or, for empty elements by an empty-element tag. Each element has a type, identified by name, and may have a set of attributes. Each attribute has a name and a value. See Logical Structures in XML .

event

An event is the representation of some asynchronous occurrence (such as a mouse click on the presentation of the element, or the removal of child node from an element, or any of unthinkably many other possibilities) that gets associated with an event target.

event observer

An ancestor of the target node.

event target

The object to which an event is targeted.

equivalence

Two nodes are equivalent if they have the same node type and same node name. Also, if the nodes contain data, that must be the same. Finally, if the nodes have attributes then collection of attribute names must be the same and the attributes corresponding by name must be equivalent as nodes.

Two nodes are deeply equivalent if they are equivalent, the child node lists are equivalent are equivalent as NodeList objects, and the pairs of equivalent attributes must in fact be deeply equivalent.

Two NodeList objects are equivalent if they have the same length, and the nodes corresponding by index are deeply equivalent.

Two NamedNodeMap objects are equivalent if they have the same length, they have same collection of names, and the nodes corresponding by name in the maps are deeply equivalent.

Two DocumentType nodes are equivalent if they are equivalent as nodes, have the same names, and have equivalent entities and attributes NamedNodeMap objects.

information item

An information item is an abstract representation of some component of an XML document. See the for details.

logically-adjacent text nodes

Logically-adjacent text nodes are Text or CDataSection nodes that may be visited sequentially in document order without entering, exiting, or passing over Element, Comment, or ProcessingInstruction nodes.

hosting implementation

A [hosting] implementation is a software module that provides an implementation of the DOM interfaces so that a client application can use them. Some examples of hosting implementations are browsers, editors and document repositories.

HTML

The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications.

IDL

An Interface Definition Language (IDL) is used to define the interfaces for accessing and operating upon objects. Examples of IDLs are the Object Management Group's IDL , Microsoft's IDL , and Sun's Java IDL .

implementor

Companies, organizations, and individuals that claim to support the Document Object Model as an API for their products.

inheritance

In object-oriented programming, the ability to create new classes (or interfaces) that contain all the methods and properties of another class (or interface), plus additional methods and properties. If class (or interface) D inherits from class (or interface) B, then D is said to be derived from B. B is said to be a base class (or interface) for D. Some programming languages allow for multiple inheritance, that is, inheritance from more than one class or interface.

initial structure model

Also known as the raw structure model or the uncooked model, this represents the document before it has been modified by entity expansions, generated text, style-specified reordering, or the execution of scripts. In some implementations, this might correspond to the "initial parse tree" for the document, if it ever exists. Note that a given implementation might not be able to provide access to the initial structure model for a document, though an editor probably would.

interface

An interface is a declaration of a set of methods with no information given about their implementation. In object systems that support interfaces and inheritance, interfaces can usually inherit from one another.

language binding

A programming language binding for an IDL specification is an implementation of the interfaces in the specification for the given language. For example, a Java language binding for the Document Object Model IDL specification would implement the concrete Java classes that provide the functionality exposed by the interfaces.

live

An object is live if any change to the underlying document structure is reflected in the object.

local name

A local name is the local part of a qualified name. This is called the local part in Namespaces in XML .

method

A method is an operation or function that is associated with an object and is allowed to manipulate the object's data.

model

A model is the actual data representation for the information at hand. Examples are the structural model and the style model representing the parse structure and the style information associated with a document. The model might be a tree, or a directed graph, or something else.

namespace prefix

A namespace prefix is a string that associates an element or attribute name with a namespace URI in XML. See namespace prefix in Namespaces in XML .

namespace URI

A namespace URI is a URI that identifies an XML namespace. This is called the namespace name in Namespaces in XML .

object model

An object model is a collection of descriptions of classes or interfaces, together with their member data, member functions, and class-static operations.

parent

A parent is an immediate ancestor node of a node.

partially valid

A node in a DOM tree is partially valid if it is well formed (this part is for comments and processing instructions) and its immediate children are those expected by the content model. The node may be missing trailing required children yet still be considered partially valid.

qualified name

A qualified name is the name of an element or attribute defined as the concatenation of a local name (as defined in this specification), optionally preceded by a namespace prefix and colon character. See Qualified Names in Namespaces in XML .

read only node

A read only node is a node that is immutable. This means its list of children, its content, and its attributes, when it is an element, cannot be changed in any way. However, a read only node can possibly be moved, when it is not itself contained in a read only node.

root node

The root node is a node that is not a child of any other node. All other nodes are children or other descendants of the root node.

sibling

Two nodes are siblings if they have the same parent node.

string comparison

When string matching is required, it is to occur as though the comparison was between 2 sequences of code points from .

tag valid document

A document is tag valid if all begin and end tags are properly balanced and nested.

target node

The target node is the node representing the event target to which an event is targeted using the DOM event flow defined in .

target phase

The process by which an event can be handled by the event target.

token

An information item such as an XML Name which has been tokenized.

tokenized

The description given to various information items (for example, attribute values of various types, but not including the StringType CDATA) after having been processed by the XML processor. The process includes stripping leading and trailing white space, and replacing multiple space characters by one. See the definition of tokenized type.

type valid document

A document is type valid if it conforms to an explicit DTD.

uncooked model

See initial structure model.

well-formed document

A document is well-formed if it is tag valid and entities are limited to single elements (i.e., single sub-trees).

XML

Extensible Markup Language (XML) is an extremely simple dialect of SGML which is completely described in this document. The goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.

XML name

See XML name in the XML specification ().

XML namespace

An XML namespace is a collection of names, identified by a URI reference , which are used in XML documents as element types and attribute names.

References

For the latest version of any W3C specification please consult the list of W3C Technical Reports available at http://www.w3.org/TR.

Canonical XML Version 1.0, J. Boyer, Editor. World Wide Web Consortium, 15 March 2001. This version of the Canonical XML Recommendation is http://www.w3.org/TR/2001/REC-xml-c14n-20010315. The latest version of Canonical XML is available at http://www.w3.org/TR/xml-c14n. Character Model for the World Wide Web 1.0, M. D¨rst, et al., Editors. World Wide Web Consortium, January 2001. This version of the Character Model for the World Wide Web Specification is http://www.w3.org/TR/2002/WD-charmod-20020220. The latest version of Character Model is available at http://www.w3.org/TR/charmod. The Microsoft Component Object Model, Microsoft Corporation. Available at http://www.microsoft.com/com. The Common Object Request Broker: Architecture and Specification, version 2. Object Management Group. The latest version of CORBA version 2.0 is available at http://www.omg.org/technology/documents/formal/corba_2.htm. Cascading Style Sheets, level 2 Specification, B. Bos, H. Wium Lie, C. Lilley, and I. Jacobs, Editors. World Wide Web Consortium, 12 May 1998. This version of the Cascading Style Sheets Recommendation is http://www.w3.org/TR/1998/REC-CSS2-19980512. The latest version of Cascading Style Sheets is available at http://www.w3.org/TR/REC-CSS2. DOM Level 1 Specification, V. Apparao, et al., Editors. World Wide Web Consortium, 1 October 1998. This version of the DOM Level 1 Recommendation is http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001. The latest version of DOM Level 1 is available at http://www.w3.org/TR/REC-DOM-Level-1. Document Object Model Level 3 Abstract Schemas Specification, B. Chang, E. Litani, J. Kesselman, R. Rahman, Editors. World Wide Web Consortium, June 2002. This version of the DOM Level 3 Abstract Schemas Specification is http://www.w3.org/DOM/Group/drafts/DOM-Level-3-AS. The latest version of DOM Level 3 Abstract Schemas is available at http://www.w3.org/TR/DOM-Level-3-AS. Document Object Model Level 2 Core Specification, A. Le Hors, et al., Editors. World Wide Web Consortium, 13 November 2000. This version of the DOM Level 2 Core Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113. The latest version of DOM Level 2 Core is available at http://www.w3.org/TR/DOM-Level-2-Core. Document Object Model Level 3 Core Specification, A. Le Hors, et al., Editors. World Wide Web Consortium, January 2002. This version of the Document Object Model Level 3 Core Specification is http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020114. The latest version of DOM Level 3 Core is available at http://www.w3.org/TR/DOM-Level-3-Core. Document Object Model Level 2 Events Specification, T. Pixley, Editor. World Wide Web Consortium, 13 November 2000. This version of the Document Object Model Level 2 Events Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113. The latest version of Document Object Model Level 2 Events is available at http://www.w3.org/TR/DOM-Level-2-Events. Document Object Model Level 3 Events Specification, T. Pixley, Editor. World Wide Web Consortium, February 2002. This version of the Document Object Model Level 3 Events Specification is http://www.w3.org/DOM/Group/drafts/DOM-Level-3-Events. The latest version of Document Object Model Level 3 Events is available at http://www.w3.org/TR/DOM-Level-3-Events. Document Object Model Level 3 Load and Save Specification, J. Stenback, A. Heninger, Editors. World Wide Web Consortium, July 2002. This version of the DOM Level 3 Load and Save Specification is http://www.w3.org/DOM/Group/drafts/DOM-Level-3-LS. The latest version of DOM Level 3 Load and Save is available at http://www.w3.org/TR/DOM-Level-3-LS. Document Object Model Level 2 HTML Specification, J. Stenback, et al., Editors. World Wide Web Consortium, December 2001. This version of the Document Object Model Level 2 HTML Specification is http://www.w3.org/TR/2001/WD-DOM-Level-2-HTML-20011210. The latest version of Document Object Model Level 2 HTML is available at http://www.w3.org/TR/DOM-Level-2-HTML. DOM Requirements for DOM Level 3 in DOM Requirements for DOM Level 3, B. Chang, et al., Editors. World Wide Web Consortium, April 2001. This version of the DOM Requirements for DOM Level 3 is http://www.w3.org/TR/2001/WD-DOM-Requirements-20010419/#Level3. The latest version of DOM Requirements is available at http://www.w3.org/TR/DOM-Requirements. Document Object Model Level 2 Style Sheets and CSS Specification, C. Wilson, P. Le Hégaret, V. Apparao, Editors. World Wide Web Consortium, 13 November 2000. This version of the Document Object Model Level 2 Style Sheets and CSS Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113. The latest version of Document Object Model Level 2 Style Sheets and CSS is available at http://www.w3.org/TR/DOM-Level-2-Style. Document Object Model Level 2 Traversal and Range Specification, J. Kesselman, J. Robie, M. Champion, P. Sharpe, V. Apparao, L. Wood, Editors. World Wide Web Consortium, 13 November 2000. This version of the Document Object Model Level 2 Traversal and Range Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113. The latest version of Document Object Model Level 2 Traversal and Range is available at http://www.w3.org/TR/DOM-Level-2-Traversal-Range. Document Object Model Level 3 Validation Specification, B. Chang, J. Kesselman, R. Rahman, Editors. World Wide Web Consortium, July 2002. This version of the DOM Level 3 Validation Specification is http://www.w3.org/DOM/Group/drafts/DOM-Level-3-Val. The latest version of DOM Level 3 Validation is available at http://www.w3.org/TR/DOM-Level-3-Val. Document Object Model Level 2 Views Specification, A. Le Hors, L. Cable, Editors. World Wide Web Consortium, 13 November 2000. This version of the Document Object Model Level 2 Views Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113. The latest version of Document Object Model Level 2 Views is available at http://www.w3.org/TR/DOM-Level-2-Views. Document Object Model Level 3 XPath Specification, R. Whitmer, Editor. World Wide Web Consortium, February 2002. This version of the Document Object Model Level 3 XPath Specification is http://www.w3.org/DOM/Group/drafts/DOM-Level-3-XPath. The latest version of Document Object Model Level 3 XPath is available at http://www.w3.org/TR/DOM-Level-3-XPath. ECMAScript Language Specification, Third Edition. European Computer Manufacturers Association, December 1999. This version of the ECMAScript Language is available at http://www.ecma.ch/ecma1/STAND/ECMA-262.HTM. HTML 4.01 Specification, D. Raggett, A. Le Hors, and I. Jacobs, Editors. World Wide Web Consortium, 17 December 1997, revised 24 April 1998, revised 24 December 1999. This version of the HTML 4.01 Recommendation is http://www.w3.org/TR/1998/REC-html40-19980424. The latest version of HTML 4 is available at http://www.w3.org/TR/html4. ISO/IEC 10646-1993 (E). Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane. [Geneva]: International Organization for Standardization, 1993 (plus amendments AM 1 through AM 7). The Java Language Specification, J. Gosling, B. Joy, and G. Steele, Authors. Addison-Wesley, September 1996. Available at http://java.sun.com/docs/books/jls Java IDL. Sun Microsystems. Available at http://java.sun.com/products/jdk/1.2/docs/guide/idl JavaScript Resources. Netscape Communications Corporation. Available at http://developer.netscape.com/tech/javascript/resources.html Java API for XML Processing (JAXP). Sun Microsystems. Available at http://java.sun.com/xml/xml_jaxp.html JScript Resources. Microsoft. Available at http://msdn.microsoft.com/scripting/default.htm Mathematical Markup Language (MathML) Version 2.0, D. Carlisle, P. Ion, R. Miner, N. Poppelier, Editors. World Wide Web Consortium, 21 February 2001. This version of the Math 2.0 Recommendation is http://www.w3.org/TR/2001/REC-MathML2-20010221. The latest version of MathML 2.0 is available at http://www.w3.org/TR/MathML2. MIDL Language Reference. Microsoft. Available at http://msdn.microsoft.com/library/psdk/midl/mi-laref_1r1h.htm. OMG IDL Syntax and Semantics defined in The Common Object Request Broker: Architecture and Specification, version 2, Object Management Group. The latest version of CORBA version 2.0 is available at http://www.omg.org/technology/documents/formal/corba_2.htm. Uniform Resource Identifiers (URI): Generic Syntax, T. Berners-Lee, R. Fielding, L. Masinter, Authors. Internet Engineering Task Force, August 1998. Available at http://www.ietf.org/rfc/rfc2396.txt. Hypertext Transfer Protocol -- HTTP/1.1, R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, Authors. Internet Engineering Task Force, June 1999. Available at http://www.ietf.org/rfc/rfc2616.txt. XML Media Types, M. Murata, S. St.Laurent, D. Kohn, Editors. Internet Engineering Task Force, January 2001. Available at http://www.ietf.org/rfc/rfc3023.txt. Simple API for XML, D. Megginson and D. Brownell, Maintainers. Available at http://www.saxproject.org/ Scalable Vector Graphics (SVG) 1.0 Specification, J. Ferraiolo, Editor. World Wide Web Consortium, 4 September 2001. This version of the SVG 1.0 Recommendation is http://www.w3.org/TR/2001/REC-SVG-20010904. The latest version of SVG 1.0 is available at http://www.w3.org/TR/SVG. The Unicode Standard, Version 2.0.. The Unicode Consortium, 1996. Reading, Mass.: Addison-Wesley Developers Press. ISBN 0-201-48345-9. The Unicode Standard, Version 3.0.. The Unicode Consortium, 2000. Reading, Mass.: Addison-Wesley Developers Press. ISBN 0-201-61633-5. XHTML 1.0: The Extensible HyperText Markup Language, S. Pemberton, et al., Authors. World Wide Web Consortium, 26 January 2000, revised 1 August 2002. This version of the XHTML 1.0 Recommendation is http://www.w3.org/TR/2002/REC-xhtml1-20020801. The latest version of XHTML 1.0 is available at http://www.w3.org/TR/xhtml10. W3C (World Wide Web Consortium) XHTML 1.1 - Module-base XHTML, May 2001. Available at http://www.w3.org/TR/2001/REC-xhtml11-20010531 W3C (World Wide Web Consortium) XQuery 1.0 and XML Path 2.0 Data Model, June 2001. Available at http://www.w3.org/TR/query-datamodel Extensible Markup Language (XML) 1.0 (Second Edition), T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 10 February 1998, revised 6 October 2000. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2000/REC-xml-20001006. The latest version of XML 1.0 is available at http://www.w3.org/TR/REC-xml. XML 1.1, J. Cowan, Editor. World Wide Web Consortium, 13 December 2001. This version of the XML 1.1 Specification is http://www.w3.org/TR/2001/WD-xml11-20011213. The latest version of XML 1.1 is available at http://www.w3.org/TR/xml11. XML Base, J. Marsh, Editor. World Wide Web Consortium, June 2001. This version of the XML Base Recommendation is http://www.w3.org/TR/2001/REC-xmlbase-20010627. The latest version of XML Base is available at http://www.w3.org/TR/xmlbase. XML Information Set, J. Cowan and R. Tobin, Editors. World Wide Web Consortium, 24 October 2001. This version of the XML Information Set Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The latest version of XML Information Set is available at http://www.w3.org/TR/xml-infoset. XML Events, S. McCarron, S. Pemberton, and T.V. Raman, Editors. World Wide Web Consortium, October 2001. This version of the XML Events specification is http://www.w3.org/TR/2001/WD-xml-events-20011026. The latest version of XML Events is available at http://www.w3.org/TR/xml-events. Namespaces in XML, T. Bray, D. Hollander, and A. Layman, Editors. World Wide Web Consortium, 14 January 1999. This version of the XML Information Set Recommendation is http://www.w3.org/TR/1999/REC-xml-names-19990114. The latest version of Namespaces in XML is available at http://www.w3.org/TR/REC-xml-names. XML Schema Part 0: Primer, D. Fallside, Editor. World Wide Web Consortium, 2 May 2001. This version of the XML Part 0 Recommendation is http://www.w3.org/TR/2001/REC-xmlschema-0-20010502. The latest version of XML Schema Part 0 is available at http://www.w3.org/TR/xmlschema-0. XML Schema Part 1: Structures, H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 2 May 2001. This version of the XML Part 1 Recommendation is http://www.w3.org/TR/2001/REC-xmlschema-1-20010502. The latest version of XML Schema Part 1 is available at http://www.w3.org/TR/xmlschema-1. XML Schema Part 2: Datatypes, P. Byron and Ashok Malhotra, Editors. World Wide Web Consortium, 2 May 2001. This version of the XML Part 2 Recommendation is http://www.w3.org/TR/2001/REC-xmlschema-2-20010502. The latest version of XML Schema Part 2 is available at http://www.w3.org/TR/xmlschema-2. W3C (World Wide Web Consortium) Associating Style Sheets with XML documents Version 1.0, June 1999. Available at http://www.w3.org/1999/06/REC-xml-stylesheet-19990629 XML Path Language (XPath) Version 1.0, J. Clark and S. DeRose, Editors. World Wide Web Consortium, 16 November 1999. This version of the XPath 1.0 Recommendation is http://www.w3.org/TR/1999/REC-xpath-19991116. The latest version of XPath 1.0 is available at http://www.w3.org/TR/xpath. XML Pointer Language (XPointer) Version 1.0, S. DeRose, E. Maler, and R. Daniel Jr., Editors. World Wide Web Consortium, September 2001. This version of the XPath 1.0 Specification is http://www.w3.org/TR/2001/WD-xptr-20010911. The latest version of XPointer 1.0 is available at http://www.w3.org/TR/xptr. Index