This specification defines the Document Object Model Level 3 XPath. It
provides simple functionalities to access a DOM tree using
This is a
Individuals or organizations are also invited to send a message to the public mailing list if they intend to produce an implementation of this module.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time.
This document has been produced as part of the
An
Patent disclosures relevant to this specification may be found
on the Working Group's
Created in electronic form.
$Revision: 1.1 $
Copyright © 2004
This document is published under the
This section is a copy of the W3C® Document
Notice and License and could be found at
Copyright © 2004
http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231
Public documents on the W3C site are provided by the copyright holders under the following license. 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 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
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 (hypertext is preferred, but a
textual representation is permitted) of the form:
"Copyright © [$date-of-document]
When space permits, inclusion of the full text of this
No right to create modifications or derivatives of W3C documents is
granted pursuant to this license. However, if additional requirements
(documented in the
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.
This section is a copy of the W3C® Software
Copyright Notice and License and could be found at
Copyright © 2004
http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
This work (and included software, documentation such as READMEs, 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 copy, modify, and distribute 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:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices,
or terms and conditions. If none exist, the
Notice of any changes or modifications to the 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.
This section is a copy of the W3C® Short Software
Notice and could be found at
Copyright © 2004
Copyright © [$date-of-software]
[1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
XPath 1.0
This specification was created to map between the Document Object
Model's representation of the W3C Information Set and XPath's
This section presents a mapping between the Document Object Model
The DOM model uses Element nodes to represent
The DOM model uses Attr nodes to represent ownerElement which can be used as XPath
defines an attribute's parent.
XPath 1.0 does not make available the namespace attributes of an
element. The DOM implementation of XPath 1.0 using these defined
interfaces never directly returns Attr nodes of namespace
attributes, but returned Element nodes still contain them.
The XPath model expects namespace nodes for each in-scope namespace to
be attached to each Element where they are in-scope. The DOM
implementation of XPath produces a new node of type
XPATH_NAMESPACE_NODE, defined in the
XPathNamespace interface, to properly preserve identity and
ordering in a way that is compatible with XPath. This node type is only
visible using the XPath evaluation methods.
The set of in-scope namespaces of an element is the default xml namespace combined with the contributions of namespace attributes of the current and all ancestor elements. In addition to explicit namespace attributes, any element has an implicit declaration of its own prefix, if any, or if no prefix then of the default namespace, which is enforced during namespace serialization, fixup, and lookup, which must be added to the set of in-scope namespaces when generating namespace nodes for an element. This causes the set of namespace nodes to be consistent with serialization, fixup, and lookup of namespaces in DOM Level 3.
The XPath model relies on the XML Information Set Text nodes due to cdata sections, entity
references, etc. Instead of returning multiple nodes where XPath sees a
single logical text node, only the first non-empty DOM Text
or CDATASection node of any logical XPath text will be
returned in the node set. Applications using XPath in an environment
with fragmented text nodes must manually gather the text of a single
logical text node possibly from multiple nodes beginning with the first
Text node or CDATASection node returned by the
implementation.
In an attempt to better implement the XML Information Set, DOM Level
3 Core wholeText on the Text interface for
retrieving the whole text for replaceWholeText for
replacing those nodes.
The DOM model may represent EntityReference nodes.
XPath 1.0 does not preserve corresponding information.
Where the node represents an unexpanded entity reference, it is skipped as dictated by the XPath specifications for all infoset items besides those specifically processed.
Where there is a hierarchy underneath the node, these nodes are processed as though they were siblings of the entity reference, as is consistent with the rest of the DOM specification.
EntityReference nodes found within a DOM hierarchy are
never returned as a node of the result, but returned nodes may contain
or be contained within an EntityReference node. Text may be
split partially inside and partially outside of an
EntityReference node, but this is solved by handling
Text nodes as described in the previous section.
The DOM model uses Comment nodes to represent
The DOM model uses ProcessingInstruction nodes to
represent
The XPathNamespace nodes. Element nodes occur before their
children. The attribute nodes and namespace nodes of an element occur
before the children of the element. The namespace nodes are defined to
occur before the attribute nodes. The relative order of namespace nodes
is implementation-dependent. The relative order of attribute nodes is
implementation-dependent. The compareTreePosition method on
the Node interface defined in the DOM Core must compare the
XPathNamespace nodes using this extended document order if
the XPath DOM module is supported.
It is possible that in future versions of XPath, the order of namespace nodes or other aspects of document order may change incompatibly.
This section explains conformance to DOM Level 3 XPath Module.
A DOM implementation must not return true to
hasFeature("xpath", "3.0") unless the implementation
conforms to that module. As documented in null or empty string is
passed in for the second parameter, then conformance is still
required to some version of the DOM XPath Module or
false must be returned.
A conformant
implementation is DOM Level 3 XPath must support all the interfaces
as specified in that specification. In addition to implementing the
interfaces in the DOM XPath Module, a conforming implementation must
correctly implement each part of the XPath 1.0 specification when
evaluating expressions including Location Paths, Expressions, the
Core Function Library, and the mapping between DOM and the XPath 1.0
data model described in the DOM Level 3 XPath Module. The XPath
id()function must return the corresponding element, if
any, returned by the DOM method
Document.getElementById.
After meeting the requirements for conformance, a conforming implementation may implement additional functions and variables. Applications which evaluate expressions using these extensions will not necessarily be portable to other implementations of the DOM Level 3 XPath Module.
An implementation is DOM Level 3 XPath conformant if it supports
the Core module defined in
A DOM application may use the hasFeature(feature,
version) method of the DOMImplementation
interface with parameter values "XPath" and "3.0" (respectively)
to determine whether or not the XPath module is supported by the
implementation. In order to fully support this module, an
implementation must also support the "Core" feature defined in the
DOM Level 2 Core specification
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 the
feature used in this document is "3.0".
A new exception has been created for exceptions specific to these XPath interfaces.
If the expression has a syntax error or otherwise is not a legal
expression according to the rules of the specific
XPathEvaluator or contains specialized extension functions
or variables not supported by this implementation.
If the expression cannot be converted to return the specified type.
The evaluation of XPath expressions is provided by
XPathEvaluator. In a DOM
implementation which supports the XPath 3.0 feature, as described
above, the XPathEvaluator interface will be implemented
on the same object which implements the Document
interface permitting it to be obtained by the usual binding-specific
method such as casting or by using the DOM Level 3 getInterface method.
In this case the implementation obtained from the Document supports the
XPath DOM module and is compatible with the XPath 1.0 specification.
Evaluation of expressions with specialized extension functions or
variables may not work in all implementations and is, therefore, not
portable. XPathEvaluator implementations may be available
from other sources that could provide specific support for specialized
extension functions or variables as would be defined by other
specifications.
Creates a parsed XPath expression with resolved namespaces.
This is useful when an expression will be reused in an application
since it makes it possible to compile the expression string into a
more efficient internal form and preresolve all
The XPath expression string to be parsed.
The resolver permits translation of all
prefixes, including the xml namespace prefix,
within the XPath expression into appropriate null, any DOMException being
thrown with the code NAMESPACE_ERR.
The compiled form of the XPath expression.
INVALID_EXPRESSION_ERR: Raised if the expression is not
legal according to the rules of the
XPathEvaluator.
NAMESPACE_ERR: Raised if the expression contains
XPathNSResolver.
Adapts any DOM node to resolve namespaces so that an XPath
expression can be easily evaluated relative to the context of
the node where it appeared within the document. This adapter
works like the DOM Level 3 method lookupNamespaceURI
on nodes in resolving the namespaceURI from a given prefix
using the current information available in the node's
hierarchy at the time lookupNamespaceURI is called. also
correctly resolving the implicit xml prefix.
The node to be used as a context for namespace resolution.
XPathNSResolver which resolves namespaces with respect to
the definitions in scope for a specified node.
Evaluates an XPath expression string and returns a result of the specified type if possible.
The XPath expression string to be parsed and evaluated.
The context is context node for the evaluation
of this XPath expression. If the XPathEvaluator was obtained
by casting the Document then this must be owned by
the same document and must be a Document,
Element, Attribute, Text,
CDATASection, Comment,
ProcessingInstruction, or XPathNamespace
node. If the context node is a Text or a
CDATASection, then the context is interpreted as the
whole logical text node as seen by XPath, unless the node is
empty in which case it may not serve as the XPath context.
The resolver permits translation of all
prefixes, including the xml namespace prefix,
within the XPath expression into appropriate null, any DOMException being
thrown with the code NAMESPACE_ERR.
If a specific type is specified, then the
result will be returned as the corresponding type.
For XPath 1.0 results, this must be one of the codes of the
XPathResult interface.
The result specifies a specific result object
which may be reused and returned by this method. If this is specified
as nullor the implementation does not reuse the specified
result, a new result object will be constructed and returned.
For XPath 1.0 results, this object will be of type
XPathResult.
The result of the evaluation of the XPath expression.
For XPath 1.0 results, this object will be of type
XPathResult.
INVALID_EXPRESSION_ERR: Raised if the expression is not
legal according to the rules of the
XPathEvaluatori
TYPE_ERR: Raised if the result cannot be converted to return the specified type.
NAMESPACE_ERR: Raised if the expression contains
XPathNSResolver.
WRONG_DOCUMENT_ERR: The Node is from a document that is
not supported by this XPathEvaluator.
NOT_SUPPORTED_ERR: The Node is not a type permitted as an
XPath context node or the request type is not permitted by this
XPathEvaluator.
The XPathExpression interface represents a parsed
and resolved XPath expression.
Evaluates this XPath expression and returns a result.
The context is context node for the evaluation
of this XPath expression.
If the XPathEvaluator was obtained
by casting the Document then this must be owned by
the same document and must be a Document,
Element, Attribute, Text,
CDATASection, Comment,
ProcessingInstruction, or XPathNamespace
node.
If the context node is a Text or a
CDATASection, then the context is interpreted as the
whole logical text node as seen by XPath, unless the node is
empty in which case it may not serve as the XPath context.
If a specific type is specified, then the
result will be coerced to return the specified type relying
on XPath conversions and fail if the desired coercion is not
possible. This must be one of the type codes of
XPathResult.
The result specifies a specific result object
which may be reused and returned by this method. If this is specified
as nullor the implementation does not reuse the specified
result, a new result object will be constructed and returned.
For XPath 1.0 results, this object will be of type
XPathResult.
The result of the evaluation of the XPath expression.
For XPath 1.0 results, this object will be of type
XPathResult.
TYPE_ERR: Raised if the result cannot be converted to return the specified type.
WRONG_DOCUMENT_ERR: The Node is from a document that is
not supported by the XPathEvaluator that created this
XPathExpression.
NOT_SUPPORTED_ERR: The Node is not a type permitted as an
XPath context node or the request type is not permitted by this
XPathExpression.
The XPathNSResolver interface permit
prefix strings in the expression to be properly bound to
namespaceURI strings. XPathEvaluator can
construct an implementation of XPathNSResolver from a
node, or the interface may be implemented by any application.
Look up the null or
empty argument, because the result of doing this is undefined.
The prefix to look for.
Returns the associated null if none is found.
The XPathResult interface represents the result
of the evaluation of an XPath 1.0 expression within the context
of a particular node. Since
evaluation of an XPath expression can result in various result
types, this object makes it possible to discover and manipulate
the type and value of the result.
An integer indicating what type of result this is.
If a specific type is specified, then the
result will be returned as the corresponding type, using
This code does not represent a specific type. An evaluation of an XPath expression will never produce this type. If this type is requested, then the evaluation returns whatever type naturally results from evaluation of the expression.
If the natural result is a node
set when ANY_TYPE was requested, then
UNORDERED_NODE_ITERATOR_TYPE is always the
resulting type. Any other representation of a node set
must be explicitly requested.
The result is a
The result is a
The result is a
The result is a
This is the default type returned if the result is a
node set and ANY_TYPE is requested.
The result is a node set as defined by
The result is a
The result is a
The result is a nullif the node set is empty. Document
modification does not invalidate the node, but may mean that
the result node no longer corresponds to the current
document. This is a convenience that permits optimization
since the implementation can stop once any node in
the resulting set has been found.
If there is more than one node in the actual result, the single node returned might not be the first in document order.
The result is a null if the node set is
empty. Document modification does not invalidate the node,
but may mean that the result node no longer corresponds to
the current document. This is a convenience that permits
optimization since the implementation can stop once the
first node in document order of the resulting set has been
found.
If there are more than one node in the actual result, the single node returned will be the first in document order.
A code representing the type of this result, as defined by the type constants.
The value of this number result. If the native double type of the DOM binding does not directly support the exact IEEE 754 result of the XPath expression, then it is up to the definition of the binding to specify how the XPath number is converted to the native binding number.
TYPE_ERR: raised if resultType is not NUMBER_TYPE.
The value of this string result.
TYPE_ERR: raised if resultType is not STRING_TYPE.
The value of this boolean result.
TYPE_ERR: raised if resultType is not BOOLEAN_TYPE.
The value of this single node result, which may be null.
TYPE_ERR: raised if resultType is not
ANY_UNORDERED_NODE_TYPE or
FIRST_ORDERED_NODE_TYPE.
Signifies that the iterator has become invalid.
True if resultType is
UNORDERED_NODE_ITERATOR_TYPE or
ORDERED_NODE_ITERATOR_TYPE and the
document has been modified since this result was
returned.
The number of nodes in the result snapshot. Valid values
for snapshotItem indices are 0 to
snapshotLength-1 inclusive.
TYPE_ERR: raised if resultType is not
UNORDERED_NODE_SNAPSHOT_TYPE or
ORDERED_NODE_SNAPSHOT_TYPE.
Iterates and returns the next node from the node set
or nullif there are no more nodes.
Returns the next node.
TYPE_ERR: raised if resultType is not
UNORDERED_NODE_ITERATOR_TYPE or
ORDERED_NODE_ITERATOR_TYPE.
INVALID_STATE_ERR: The document has been mutated since the result was returned.
Returns the indexth item in the snapshot collection.
If index is greater than or equal to the number of nodes
in the list, this method returns null. Unlike the
iterator result, the snapshot does not become invalid, but may
not correspond to the current document if it is mutated.
Index into the snapshot collection.
The node at the indexth position in the
NodeList, or null if that is not a
valid index.
TYPE_ERR: raised if resultType is not
UNORDERED_NODE_SNAPSHOT_TYPE or
ORDERED_NODE_SNAPSHOT_TYPE.
The XPathNamespace interface is returned by
XPathResult interfaces to represent
the XPath namespace node type that DOM lacks.
There is no public constructor for this node type. Attempts to
place it into a hierarchy or a NamedNodeMap result in a
DOMException with the code
HIERARCHY_REQUEST_ERR. This node is
NO_MODIFICATION_ALLOWED_ERR.
The core specification describes attributes of the
Node interface that are different for different
node types but does not describe XPATH_NAMESPACE_NODE,
so here is a description of those attributes for this node type.
All attributes of Node not described in this section
have a null or false value.
ownerDocument matches the ownerDocument of the
ownerElement even if the element is later adopted.
nodeName is always the string "#namespace".
prefix is the prefix of the namespace
represented by the node.
localName is the same as prefix.
nodeType is equal to XPATH_NAMESPACE_NODE.
namespaceURI is the namespace URI of the namespace
represented by the node.
nodeValue is the same as namespaceURI.
adoptNode, cloneNode, and
importNode fail on this node type by raising a
DOMException with the code NOT_SUPPORTED_ERR.
In future versions of the XPath specification, the definition of a namespace node may be changed incomatibly, in which case incompatible changes to field values may be required to implement versions beyond XPath 1.0.
An integer indicating which type of node this is.
There is currently only one type of node which is specific to XPath. The numbers in this list must not collide with the values assigned to core node types.
The node is a Namespace.
The Element on which the namespace was in scope
when it was requested. This does not change on a returned
namespace node
even if the document changes such that the namespace goes out of
scope on that
This appendix contains the complete OMG IDL
The IDL files are also available as:
This appendix contains the complete Java
The Java files are also available as
This appendix contains the complete ECMAScript
The parameter resolver of the method
XPathEvaluator.evaluate is specified as an object
that implements the XPathNSResolver
interface. ECMAScript users can also pass to this method a
function which returns a String and takes a
String parameter instead of the
resolver parameter.
Many people contributed to the DOM specifications (Level 1, 2 or 3), including participants of the DOM Working Group and the DOM Interest Group. We especially thank the following:
Andrew Clover, 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 and invited expert), 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.,
Thanks to all those who have helped to improve this specification by sending suggestions and corrections (Please, keep bugging us with your issues!).
Special thanks to the
This specification was written in XML. The HTML, OMG IDL, Java and ECMAScript bindings were all produced automatically.
Thanks to Joe English, author of
After DOM Level 1, we used
Thanks also to Jan Kärrman, author of
Some 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.
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.
An
An
An
The process by which an
The process by which an
A
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.
The
A
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
A
When new releases of specifications are released, some older
features may be marked as being
A
There is only one document element in a Document. This
element node is a child of the Document node. See
There is an ordering,
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".
The programming language defined by the ECMA-262 standard
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
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
The object to which an
Two nodes are
Two nodes are NodeList objects, and the pairs of
equivalent attributes must in fact be deeply equivalent.
Two NodeList objects are
Two NamedNodeMap objects are
Two DocumentType nodes are NamedNodeMap
objects.
An information item is an abstract representation of some
component of an XML document. See the
Text
or CDATASection nodes that can be visited
sequentially in Element,
Comment, or ProcessingInstruction
nodes.
A
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.
The HyperText Markup Language (
An Interface Definition Language (
Companies, organizations, and individuals that claim to support the Document Object Model as an API for their products.
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
Also known as the
An
A programming
An object is
A
A
A
A
A
A node is a
An
A
A node in a DOM tree is
A
A
The
A
Two nodes are
When string matching is required, it is to occur as
though the comparison was between 2 sequences of code points
from
A document is
The target node is the node representing the
The process by which an
An information item such as an
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
A document is
See initial structure model.
A node is a
Extensible Markup Language (
See
An
For the latest version of any W3C specification please consult the list of
DOM Requirements for DOM Level 3in
OMG IDL Syntax and Semanticsdefined in