level-one-core.html 104 KB

Raw Blame History Permalink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- Generated: Thu Oct  1 12:20:37 MET DST 1998 -->
<html lang='en'>
<head>
  <title>Document Object Model (Core) Level 1</title>
  <link rel='stylesheet' type='text/css' href='./spec.css'>
<link rel='next' href='level-one-html.html'>
<link rel='start' href='cover.html'>
<link rel='previous' href='introduction.html'>
</head>
<body bgcolor="#FFFFFF" text="#000000" link="#0000EE" vlink="#551A8B">
<div align='center' class='noprint'><i>REC-DOM-Level-1-19981001</i></div>
<div class='NOPRINT'>
<hr>
<table width='100%' cellpadding='0' class='navigation-bar'>
<tr>
<td width='30%' align='left'><a href='introduction.html'><img border='0' src='./images/back.jpg' alt='What is the Document Object Model?'></a></td>
<td width='30%' align='center'><a href='cover.html'><img border='0' src='./images/up.jpg' alt='REC-DOM-Level-1-19981001'></a></td>
<td width='30%' align='right'><a href='level-one-html.html'><img border='0' src='./images/forward.jpg' alt='Document Object Model (HTML) Level 1'></a></td>
</tr>
</table>
<hr>
</div>

<a name='ID-419945773'></a>

<h1 class='div1'>1. Document Object Model (Core) Level 1</h1><dl>
<dt><i>Editors</i></dt>
<dd>Mike Champion, ArborText (from November 20, 1997)</dd><dd>Steve Byrne, JavaSoft (until November 19, 1997)</dd><dd>Gavin Nicol, Inso EPS</dd><dd>Lauren Wood, SoftQuad, Inc.</dd></dl>

<!--NewPage--><!-- this is for html2ps -->
<div class='NOPRINT'>
<h2>Table of contents</h2>
<ul class='toc'>
<li class='tocline3'><a class='tocxref' href='#ID-1590626201'>1.1. Overview of the DOM Core Interfaces</a>
<ul class='toc'>
<li class='tocline4'><a class='tocxref' href='#ID-1590626202'>1.1.1. The DOM Structure Model</a></li>
<li class='tocline4'><a class='tocxref' href='#ID-249F15BA'>1.1.2. Memory Management</a></li>
<li class='tocline4'><a class='tocxref' href='#ID-45A944CB'>1.1.3. Naming Conventions</a></li>
<li class='tocline4'><a class='tocxref' href='#ID-1CED5498'>1.1.4. Inheritance vs Flattened Views of the API</a></li>
<li class='tocline4'><a class='tocxref' href='#ID-C74D1578'>1.1.5. The  DOMString  type</a></li>
<li class='tocline4'><a class='tocxref' href='#ID-5DFED1F0'>1.1.6. Case sensitivity in the DOM</a></li>
</ul></li>
<li class='tocline3'><a class='tocxref' href='#ID-BBACDC08'>1.2. Fundamental Interfaces</a>
<li class='tocline3'><a class='tocxref' href='#ID-E067D597'>1.2. Extended Interfaces</a>
</ul>
<br>
</div>

<a name='ID-1590626201'></a>
<h2 class='div2'>1.1. Overview of the DOM Core Interfaces</h2><p>This section defines a minimal set of objects and
	interfaces for accessing and manipulating document objects.
	The functionality specified in this section (the
	<em>Core</em> functionality) should be 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 population
	of a <a href='level-one-core.html#i-Document'><code>Document</code></a> object using only DOM API calls; creating
        the skeleton <a href='level-one-core.html#i-Document'><code>Document</code></a> and saving it persistently is left
        to the product that implements the DOM API.
<a name='ID-1590626202'></a>
<h3 class='div3'>1.1.1. The DOM Structure Model</h3><p>The DOM presents documents as a hierarchy of <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>
	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. The node types, and which node types they may have as
	children, are as follows:
        <ul>
<li><a href='level-one-core.html#i-Document'><code>Document</code></a> --  <a href='level-one-core.html#ID-745549614'><code>Element</code></a> (maximum of
	      one), <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a>, <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a>,
	      <a href='level-one-core.html#ID-412266927'><code>DocumentType</code></a> </li>
<li><a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a> --  <a href='level-one-core.html#ID-745549614'><code>Element</code></a>,
	      <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a>, <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a>,
	      <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>, <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a>,
	      <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> </li>
<li><a href='level-one-core.html#ID-412266927'><code>DocumentType</code></a> -- no children</li>
<li><a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> -- <a href='level-one-core.html#ID-745549614'><code>Element</code></a>,
	      <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a>, <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a>,
	      <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>, <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a>,
	      <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> </li>
<li><a href='level-one-core.html#ID-745549614'><code>Element</code></a> -- <a href='level-one-core.html#ID-745549614'><code>Element</code></a>,
	      <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>,  <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a>,
	      <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a>, <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a>,
	      <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a></li>
<li><a href='level-one-core.html#ID-637646024'><code>Attr</code></a> -- <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>,
	      <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a></li>
<li><a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a> --  no children</li>
<li><a href='level-one-core.html#ID-1728279322'><code>Comment</code></a> --  no children</li>
<li><a href='level-one-core.html#ID-1312295772'><code>Text</code></a> --  no children</li>
<li><a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a> --  no children</li>
<li><a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a> -- <a href='level-one-core.html#ID-745549614'><code>Element</code></a>,
	      <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a>, <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a>,
	      <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>, <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a>,
	      <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a></li>
<li><a href='level-one-core.html#ID-5431D1B9'><code>Notation</code></a> --  no children</li>
</ul>
 <p>The DOM also specifies a <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> interface to handle
	ordered lists of <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>s, such as the children of a
	<a href='level-one-core.html#ID-1950641247'><code>Node</code></a>, or the elements returned by the
	<code>Element.getElementsByTagName</code> method, and also a
	<a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a> interface to handle unordered sets of nodes
	referenced by their name attribute, such as the attributes of an
	<a href='level-one-core.html#ID-745549614'><code>Element</code></a>. <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a>s and
	<a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a>s in the DOM are "live", that is, changes to
	the underlying document structure are reflected in all relevant
	<a href='level-one-core.html#ID-536297177'><code>NodeList</code></a>s and <a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a>s.  For example, if
	a DOM user gets a <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> object containing the children
	of an <a href='level-one-core.html#ID-745549614'><code>Element</code></a>, then subsequently adds more children to
	that element (or removes children, or modifies them), those changes are
	automatically reflected in the <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> without further
	action on the user's part. Likewise changes to a <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> in
	the tree are reflected in all references to that <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> in
	<a href='level-one-core.html#ID-536297177'><code>NodeList</code></a>s and <a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a>s. <br>
<a name='ID-249F15BA'></a>
<h3 class='div3'>1.1.2. Memory Management</h3><p>Most of the APIs defined by this specification are <em>
	interfaces</em> rather than classes.  That means that
	an actual implementation need only expose methods with
	the defined names and specified operation, not actually
	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 <em>factory</em> methods
	that create instances of objects that implement the various
	interfaces.  In the DOM Level 1, objects implementing some
	interface "X" are created by a "createX()" method on the
	<a href='level-one-core.html#i-Document'><code>Document</code></a> interface; this is because all DOM objects live
	in the context of a specific Document.<p>The DOM Level 1 API does <em>not</em> define a standard
	way to create <a href='level-one-core.html#ID-102161490'><code>DOMImplementation</code></a> or <a href='level-one-core.html#i-Document'><code>Document</code></a>
	objects; actual DOM implementations must provide
	some proprietary way of bootstrapping these DOM interfaces, and
	then all other objects can be built from the Create methods on
	<a href='level-one-core.html#i-Document'><code>Document</code></a> (or by various other convenience methods).<p>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 platforms 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
	devised by the DOM Working Group (for ECMAScript and Java)
	require any memory management  methods, but DOM bindings for
	other languages (especially C or C++) probably will require
	such support. These extensions will be the responsibility of
	those adapting the DOM API to a specific language, not the DOM
	WG.
      <br>
<a name='ID-45A944CB'></a>
<h3 class='div3'>1.1.3. Naming Conventions</h3><p>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 <code>ECMAScript</code> have
	significant limitations in their ability to disambiguate names
	from different namespaces that makes it difficult to avoid naming
	conflicts with short, familiar names. So, DOM names tend to be
	long and quite descriptive in order to be unique across all
	environments.
      <p>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, we use
	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. <br>
<a name='ID-1CED5498'></a>
<h3 class='div3'>1.1.4. Inheritance vs Flattened Views of the API</h3><p>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 <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> 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
	<a href='level-one-core.html#ID-1950641247'><code>Node</code></a> interface. Because many other users will find the
	inheritance hierarchy easier to understand than the
	"everything is a <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>" approach to the DOM, we also
	support the full higher-level interfaces for those who prefer a more
	object-oriented API. <p>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 <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> 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 <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> interface, we don't
	specify a completely redundant one). Thus, even though there
	is a generic <code>nodeName</code> attribute on the <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>
	interface, there is still a <code>tagName</code> attribute on the
	<a href='level-one-core.html#ID-745549614'><code>Element</code></a> interface; these two attributes must
	contain the same value, but the Working Group considers it
	worthwhile to support both, given the different constituencies
	the DOM API must satisfy. <br>
<a name='ID-C74D1578'></a>
<h3 class='div3'>1.1.5. The <code>DOMString</code> type</h3><p>To ensure interoperability, the DOM specifies the
      <code>DOMString</code> type as follows:

      <ul>
<li>A <code>DOMString</code> is a sequence of 16-bit
	  quantities. This may be expressed in IDL terms as:<pre class='eg'>


         typedef sequence&lt;unsigned short&gt; DOMString;
</pre>
</li>
<li>Applications must encode <code>DOMString</code> using UTF-16
        (defined in Appendix C.3 of [UNICODE] and Amendment 1 of
	[ISO-10646]).The UTF-16 encoding was chosen because of its widespread
        industry practice. Please note that for both HTML and XML, the document
        character set (and therefore the notation of numeric character
        references) is based on UCS-4. A single numeric character reference in
        a source document may therefore in some cases correspond to two array
        positions in a <code>DOMString</code> (a high surrogate and a low
        surrogate). <i><b>Note: </b>Even though the DOM defines the name of the string type to
        be <code>DOMString</code>, bindings may used different names. For,
        example for Java, <code>DOMString</code> is bound to the
	<code>String</code> type because it also uses UTF-16 as its
	encoding.</i><br></li>
</ul>
<i><b>Note: </b>As of August 1998, the OMG IDL specification included a
      <code>wstring</code> type. However, that definition did not meet the
      interoperability criteria of the DOM API since it relied on encoding
      negotiation to decide the width of a character.</i><br><br>
<a name='ID-5DFED1F0'></a>
<h3 class='div3'>1.1.6. Case sensitivity in the DOM</h3><p>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 takes place on a character
	code by character code basis, on the 16 bit value of a
	<code>DOMString</code>. As such, the DOM assumes that any
	normalizations will take place in the processor,
	<em>before</em> the DOM structures are built.<p>This then raises the issue of exactly what normalizations
	occur. The W3C I18N working group is in the process of
	defining exactly which normalizations are necessary for applications
	implementing the DOM.<br><br>
<a name='ID-BBACDC08'></a>
<h2 class='div2'>1.2. Fundamental Interfaces</h2><p>The interfaces within this section are considered
      <em>fundamental</em>, and must be fully implemented by all
      conforming implementations of the DOM, including all HTML DOM
      implementations.<dl>
<dt><b>Exception <i><a name='ID-17189187'>DOMException</a></i></b></dt>
<dd>
<p>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 situation, such as out-of-bound errors when using
      <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a>.
    <p>Implementations may raise other exceptions under other circumstances.
    For example, implementations may raise an implementation-dependent
    exception if a <code>null</code> argument is passed. <p>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.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
exception DOMException {
  unsigned short   code;
};

// ExceptionCode
const unsigned short      INDEX_SIZE_ERR     = 1;
const unsigned short      DOMSTRING_SIZE_ERR = 2;
const unsigned short      HIERARCHY_REQUEST_ERR = 3;
const unsigned short      WRONG_DOCUMENT_ERR = 4;
const unsigned short      INVALID_CHARACTER_ERR = 5;
const unsigned short      NO_DATA_ALLOWED_ERR = 6;
const unsigned short      NO_MODIFICATION_ALLOWED_ERR = 7;
const unsigned short      NOT_FOUND_ERR      = 8;
const unsigned short      NOT_SUPPORTED_ERR  = 9;
const unsigned short      INUSE_ATTRIBUTE_ERR = 10;

</pre>
</dd>
</dl>
<a name='ID-258A00AF'></a>
<dl><dt><b>Definition group <i>ExceptionCode</i></b></dt><dd>
<p>An integer indicating the type of error generated.<dl>
<dt><b>Defined Constants</b></dt>
<dd><table border='0'>
<tr><td><b>INDEX_SIZE_ERR</b></td><td>
<p>If index or size is negative, or greater than the
        allowed value</td></tr>
<tr><td><b>DOMSTRING_SIZE_ERR</b></td><td>
<p>If the specified range of text does not fit into a DOMString</td></tr>
<tr><td><b>HIERARCHY_REQUEST_ERR</b></td><td>
<p>If any node is inserted somewhere it doesn't belong</td></tr>
<tr><td><b>WRONG_DOCUMENT_ERR</b></td><td>
<p>If a node is used in a different document than the one that
       created it (that doesn't support it)</td></tr>
<tr><td><b>INVALID_CHARACTER_ERR</b></td><td>
<p>If an invalid character is specified, such as in a name.</td></tr>
<tr><td><b>NO_DATA_ALLOWED_ERR</b></td><td>
<p>If data is specified for a node which does not support data</td></tr>
<tr><td><b>NO_MODIFICATION_ALLOWED_ERR</b></td><td>
<p>If an attempt is made to modify an object where modifications are not allowed</td></tr>
<tr><td><b>NOT_FOUND_ERR</b></td><td>
<p>If an attempt was made to reference a node in a context where it does not exist</td></tr>
<tr><td><b>NOT_SUPPORTED_ERR</b></td><td>
<p>If the implementation does not support the type of object requested</td></tr>
<tr><td><b>INUSE_ATTRIBUTE_ERR</b></td><td>
<p>If an attempt is made to add an attribute that is already inuse elsewhere</td></tr>
</table>
</dd></dl>
</dl>
</dd>
</dl>

<dl>
<dt><b>Interface <i><a name='ID-102161490'>DOMImplementation</a></i></b></dt>
<dd>
<p>The <code>DOMImplementation</code> interface provides a
      number of methods for performing operations that are independent
      of any particular instance of the document object model. <p>The DOM Level 1 does not specify a way of creating a
      document instance, and hence document creation is an operation
      specific to an implementation. Future Levels of the DOM specification
      are expected to provide methods for creating documents directly.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface DOMImplementation {
  boolean                   hasFeature(in DOMString feature,
                                       in DOMString version);
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-5CED94D7'></a><a name='method-hasFeature'>hasFeature</a></code></dt>
<dd>
<div class='method'>
Test if the DOM implementation implements a
	   specific feature.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>feature</code><td><td>
<p>The package name of the feature to
	    test. In Level 1, the legal values are "HTML" and
	"XML" (case-insensitive).</td></tr>
<tr><td valign='top'><code>version</code><td><td>
<p>This is the version number of the package name to
	test.  In Level 1, this is the string "1.0".
	If the version is not specified, supporting any version of the
        feature will cause the method to return <code>true</code>.
	</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
<code>true</code> if the feature is implemented in the specified
	version, <code>false</code> otherwise.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-B63ED1A3'>DocumentFragment</a></i></b></dt>
<dd>
<p><code>DocumentFragment</code> is a "lightweight" or
      "minimal" <a href='level-one-core.html#i-Document'><code>Document</code></a> 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 <a href='level-one-core.html#i-Document'><code>Document</code></a> object could fulfil this role,
      a <a href='level-one-core.html#i-Document'><code>Document</code></a> object can potentially be a heavyweight
      object, depending on the underlying implementation. What is really
      needed for this is a very lightweight object.
      <code>DocumentFragment</code> is such an object.<p>Furthermore, various operations -- such as inserting nodes as
      children of another <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> -- may take
      <code>DocumentFragment</code> objects as arguments;  this
      results in all the child nodes of the <code>DocumentFragment</code>
      being moved to the child list of this node.<p>The children of a <code>DocumentFragment</code> node are zero
      or more nodes representing the tops of any sub-trees defining
      the structure of the document. <code>DocumentFragment</code> 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 <code>DocumentFragment</code> might have only one child and
      that child node could be a <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> node. Such a structure model
      represents neither an HTML document nor a well-formed XML document.
      <p>When a <code>DocumentFragment</code> is inserted into a
      <a href='level-one-core.html#i-Document'><code>Document</code></a> (or indeed any other <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> that may take children)
      the children of the <code>DocumentFragment</code> and not the <code>DocumentFragment</code>
      itself are inserted into the <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>. This makes the <code>DocumentFragment</code>
      very useful when the user wishes to create nodes that are siblings;
      the <code>DocumentFragment</code> acts as the parent of these nodes so that the
      user can use the standard methods from the <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>
      interface, such as <code>insertBefore()</code> and
      <code>appendChild()</code>.


<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface DocumentFragment : Node {
};

</pre>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='i-Document'>Document</a></i></b></dt>
<dd>
<p>The <code>Document</code> 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.<p>Since elements, text nodes, comments, processing instructions,
      etc. cannot exist outside the context of a
      <code>Document</code>, the <code>Document</code> interface also
      contains the factory methods needed to create these objects.
      The <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> objects created have a <code>ownerDocument</code>
      attribute which associates them with the <code>Document</code> within whose
      context they were created.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Document : Node {
  readonly attribute  DocumentType         doctype;
  readonly attribute  DOMImplementation    implementation;
  readonly attribute  Element              documentElement;
  Element                   createElement(in DOMString tagName)
                                          raises(DOMException);
  DocumentFragment          createDocumentFragment();
  Text                      createTextNode(in DOMString data);
  Comment                   createComment(in DOMString data);
  CDATASection              createCDATASection(in DOMString data)
                                               raises(DOMException);
  ProcessingInstruction     createProcessingInstruction(in DOMString target,
                                                        in DOMString data)
                                                        raises(DOMException);
  Attr                      createAttribute(in DOMString name)
                                            raises(DOMException);
  EntityReference           createEntityReference(in DOMString name)
                                                  raises(DOMException);
  NodeList                  getElementsByTagName(in DOMString tagname);
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-B63ED1A31'></a><a name='attribute-doctype'>doctype</a></code></dt>
<dd>
The Document Type Declaration (see <a href='level-one-core.html#ID-412266927'><code>DocumentType</code></a>)
	associated with
	this document. For HTML documents as well as XML documents without a
	document type declaration this returns <code>null</code>. The DOM Level
        1 does not support editing the Document Type Declaration, therefore
	<code>docType</code> cannot be altered in any way.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-1B793EBA'></a><a name='attribute-implementation'>implementation</a></code></dt>
<dd>
The <a href='level-one-core.html#ID-102161490'><code>DOMImplementation</code></a> object that handles this
	document. A DOM application may use objects from multiple
        implementations.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-87CD092'></a><a name='attribute-documentElement'>documentElement</a></code></dt>
<dd>
This is a convenience attribute that allows direct
	access to the child node that is the root element of  the
	document. For HTML documents, this is the element with
	the tagName "HTML".</dd>
</dl>

</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-2141741547'></a><a name='method-createElement'>createElement</a></code></dt>
<dd>
<div class='method'>
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.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>tagName</code><td><td>
<p>The name of the element type to
	    instantiate. For XML, this is case-sensitive. For HTML, the
            <code>tagName</code> parameter may be provided in any case,
            but it must be mapped to the canonical uppercase form by
            the DOM implementation.
        </td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
A new <a href='level-one-core.html#ID-745549614'><code>Element</code></a> object.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INVALID_CHARACTER_ERR: Raised if the specified name contains
	an invalid character.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-35CB04B5'></a><a name='method-createDocumentFragment'>createDocumentFragment</a></code></dt>
<dd>
<div class='method'>
Creates an empty <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a> object.

<dl>
<dt><b>Return Value</b></dt>
<dd>
A new <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>.</dd>
</dl>
<br>
This method has no parameters.<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-1975348127'></a><a name='method-createTextNode'>createTextNode</a></code></dt>
<dd>
<div class='method'>
Creates a <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> node given the specified
	string.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>data</code><td><td>
<p>The data for the node.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The new <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> object.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-1334481328'></a><a name='method-createComment'>createComment</a></code></dt>
<dd>
<div class='method'>
Creates a <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a> node given the specified
	string.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>data</code><td><td>
<p>The data for the node.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The new <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a> object.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-D26C0AF8'></a><a name='method-createCDATASection'>createCDATASection</a></code></dt>
<dd>
<div class='method'>
Creates a <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a> node whose value  is
	the specified string.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>data</code><td><td>
<p>The data for the <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a> contents.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The new <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a> object.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NOT_SUPPORTED_ERR: Raised if this document is an HTML
	document.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-135944439'></a><a name='method-createProcessingInstruction'>createProcessingInstruction</a></code></dt>
<dd>
<div class='method'>
Creates a <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a> node given
	the specified name and data strings.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>target</code><td><td>
<p>The target part of the processing instruction.</td></tr>
<tr><td valign='top'><code>data</code><td><td>
<p>The data for the node.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The new <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a> object.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INVALID_CHARACTER_ERR: Raised if an invalid character is specified.<p>NOT_SUPPORTED_ERR: Raised if this document is an HTML document.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-1084891198'></a><a name='method-createAttribute'>createAttribute</a></code></dt>
<dd>
<div class='method'>
Creates an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> of the given name.
	Note that the <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> instance
	can then be set on an <a href='level-one-core.html#ID-745549614'><code>Element</code></a> using the
	<code>setAttribute</code> method.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the attribute.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
A new <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> object.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INVALID_CHARACTER_ERR: Raised if the specified name contains
	an invalid character.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-392B75AE'></a><a name='method-createEntityReference'>createEntityReference</a></code></dt>
<dd>
<div class='method'>
Creates an EntityReference object.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the entity to reference. </td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The new <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> object.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INVALID_CHARACTER_ERR: Raised if the specified name contains
	an invalid character.<p>NOT_SUPPORTED_ERR: Raised if this document is an HTML document. </dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-A6C9094'></a><a name='method-getElementsByTagName'>getElementsByTagName</a></code></dt>
<dd>
<div class='method'>
Returns a <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> of all the <a href='level-one-core.html#ID-745549614'><code>Element</code></a>s
	with a given tag name in the order in which they would be encountered
        in a preorder traversal of the <code>Document</code> tree.

<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>tagname</code><td><td>
<p>The name of the tag to match on. The special value "*"
	    matches all tags.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
A new <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> object containing
	  all the matched <a href='level-one-core.html#ID-745549614'><code>Element</code></a>s.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-1950641247'>Node</a></i></b></dt>
<dd>
<p>The <code>Node</code> 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
      <code>Node</code> interface expose methods for dealing with
      children, not all objects implementing the <code>Node</code>
      interface may have children. For example, <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>
      nodes may not have children, and adding children to such nodes
      results in a <a href='level-one-core.html#ID-17189187'><code>DOMException</code></a> being raised.
      <p>The attributes <code>nodeName</code>, <code>nodeValue</code>
        and <code>attributes</code> 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
	<code>nodeType</code> (e.g., <code>nodeValue</code> for an Element
        or <code>attributes</code>
	for a Comment), this returns <code>null</code>. Note that the
	specialized interfaces may contain
	additional and more convenient mechanisms to get and set the relevant
	information.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Node {
  // NodeType
  const unsigned short      ELEMENT_NODE       = 1;
  const unsigned short      ATTRIBUTE_NODE     = 2;
  const unsigned short      TEXT_NODE          = 3;
  const unsigned short      CDATA_SECTION_NODE = 4;
  const unsigned short      ENTITY_REFERENCE_NODE = 5;
  const unsigned short      ENTITY_NODE        = 6;
  const unsigned short      PROCESSING_INSTRUCTION_NODE = 7;
  const unsigned short      COMMENT_NODE       = 8;
  const unsigned short      DOCUMENT_NODE      = 9;
  const unsigned short      DOCUMENT_TYPE_NODE = 10;
  const unsigned short      DOCUMENT_FRAGMENT_NODE = 11;
  const unsigned short      NOTATION_NODE      = 12;

  readonly attribute  DOMString            nodeName;
           attribute  DOMString            nodeValue;
                                                 // raises(DOMException) on setting
                                                 // raises(DOMException) on retrieval
  readonly attribute  unsigned short       nodeType;
  readonly attribute  Node                 parentNode;
  readonly attribute  NodeList             childNodes;
  readonly attribute  Node                 firstChild;
  readonly attribute  Node                 lastChild;
  readonly attribute  Node                 previousSibling;
  readonly attribute  Node                 nextSibling;
  readonly attribute  NamedNodeMap         attributes;
  readonly attribute  Document             ownerDocument;
  Node                      insertBefore(in Node newChild,
                                         in Node refChild)
                                         raises(DOMException);
  Node                      replaceChild(in Node newChild,
                                         in Node oldChild)
                                         raises(DOMException);
  Node                      removeChild(in Node oldChild)
                                        raises(DOMException);
  Node                      appendChild(in Node newChild)
                                        raises(DOMException);
  boolean                   hasChildNodes();
  Node                      cloneNode(in boolean deep);
};

</pre>
</dd>
</dl>
<a name='ID-1841493061'></a>
<dl><dt><b>Definition group <i>NodeType</i></b></dt><dd>
<p>An integer indicating which type of node this is.<dl>
<dt><b>Defined Constants</b></dt>
<dd><table border='0'>
<tr><td><b>ELEMENT_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-745549614'><code>Element</code></a>.</td></tr>
<tr><td><b>ATTRIBUTE_NODE</b></td><td>
<p>The node is an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a>.</td></tr>
<tr><td><b>TEXT_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> node.</td></tr>
<tr><td><b>CDATA_SECTION_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-667469212'><code>CDATASection</code></a>.</td></tr>
<tr><td><b>ENTITY_REFERENCE_NODE</b></td><td>
<p>The node is an <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a>.</td></tr>
<tr><td><b>ENTITY_NODE</b></td><td>
<p>The node is an <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a>.</td></tr>
<tr><td><b>PROCESSING_INSTRUCTION_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-1004215813'><code>ProcessingInstruction</code></a>.</td></tr>
<tr><td><b>COMMENT_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-1728279322'><code>Comment</code></a>.</td></tr>
<tr><td><b>DOCUMENT_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#i-Document'><code>Document</code></a>.</td></tr>
<tr><td><b>DOCUMENT_TYPE_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-412266927'><code>DocumentType</code></a>.</td></tr>
<tr><td><b>DOCUMENT_FRAGMENT_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>.</td></tr>
<tr><td><b>NOTATION_NODE</b></td><td>
<p>The node is a <a href='level-one-core.html#ID-5431D1B9'><code>Notation</code></a>.</td></tr>
</table>
</dd></dl>
</dl>
<p>The values of <code>nodeName</code>, <code>nodeValue</code>,
    and <code>attributes</code> vary according to the node type as follows:
    <table width='90%' border='1' cellpadding=''><tr><td bgcolor='#cfcfcf'><b></b></td><td bgcolor='#cfcfcf'><b>nodeName</b></td><td bgcolor='#cfcfcf'><b>nodeValue</b></td><td bgcolor='#cfcfcf'><b>attributes</b></td></tr>
<tr><td valign='top'>Element</td><td valign='top'>tagName</td><td valign='top'>null</td><td valign='top'>NamedNodeMap</td></tr>
<tr><td valign='top'>Attr</td><td valign='top'>name of attribute</td><td valign='top'>value of attribute</td><td valign='top'>null</td></tr>
<tr><td valign='top'>Text</td><td valign='top'>#text</td><td valign='top'>content of the text node</td><td valign='top'>null</td></tr>
<tr><td valign='top'>CDATASection</td><td valign='top'>#cdata-section</td><td valign='top'>content of the CDATA Section</td><td valign='top'>null</td></tr>
<tr><td valign='top'>EntityReference</td><td valign='top'>name of entity referenced</td><td valign='top'>null</td><td valign='top'>null</td></tr>
<tr><td valign='top'>Entity</td><td valign='top'>entity name</td><td valign='top'>null</td><td valign='top'>null</td></tr>
<tr><td valign='top'>ProcessingInstruction</td><td valign='top'>target</td><td valign='top'>entire content excluding the target</td><td valign='top'>null</td></tr>
<tr><td valign='top'>Comment</td><td valign='top'>#comment</td><td valign='top'>content of the comment</td><td valign='top'>null</td></tr>
<tr><td valign='top'>Document</td><td valign='top'>#document</td><td valign='top'>null</td><td valign='top'>null</td></tr>
<tr><td valign='top'>DocumentType</td><td valign='top'>document type name</td><td valign='top'>null</td><td valign='top'>null</td></tr>
<tr><td valign='top'>DocumentFragment</td><td valign='top'>#document-fragment</td><td valign='top'>null</td><td valign='top'>null</td></tr>
<tr><td valign='top'>Notation</td><td valign='top'>notation name</td><td valign='top'>null</td><td valign='top'>null</td></tr>
</table>


<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-F68D095'></a><a name='attribute-nodeName'>nodeName</a></code></dt>
<dd>
The name of this node, depending on its type; see the table above.
      </dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-F68D080'></a><a name='attribute-nodeValue'>nodeValue</a></code></dt>
<dd>
The value of this node, depending on its type; see the table above.
<dl>
<dt><b>Exceptions on setting</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised when the node is
	    readonly.</dd></dl>
</dd>
</dl>

<dl>
<dt><b>Exceptions on retrieval</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>DOMSTRING_SIZE_ERR: Raised when it would return more
	    characters than fit in a <code>DOMString</code> variable on the
	    implementation platform.</dd></dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-111237558'></a><a name='attribute-nodeType'>nodeType</a></code></dt>
<dd>
A code representing the type of the underlying object, as defined
	above.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-1060184317'></a><a name='attribute-parentNode'>parentNode</a></code></dt>
<dd>
The parent of this node. All nodes,
	except <a href='level-one-core.html#i-Document'><code>Document</code></a>, <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>, and
        <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> 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 <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-1451460987'></a><a name='attribute-childNodes'>childNodes</a></code></dt>
<dd>
A <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> that contains all
	children of this node. If there are no children, this is a
	<a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> containing no nodes. The content of the
	returned <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> is "live" in the
	sense that, for instance, changes to the children of the node object
	that it	was created from are immediately reflected in the nodes
	returned by the <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> accessors; it is not a
	static snapshot of the content of the node. This is true for every
	<a href='level-one-core.html#ID-536297177'><code>NodeList</code></a>, including the ones returned by the
	<code>getElementsByTagName</code> method.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-169727388'></a><a name='attribute-firstChild'>firstChild</a></code></dt>
<dd>
The first child of this node. If there is no such
	node, this returns <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-61AD09FB'></a><a name='attribute-lastChild'>lastChild</a></code></dt>
<dd>
The last child of this node. If there is no such
	node, this returns <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-640FB3C8'></a><a name='attribute-previousSibling'>previousSibling</a></code></dt>
<dd>
The node immediately preceding this node. If there is no
        such node, this returns <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-6AC54C2F'></a><a name='attribute-nextSibling'>nextSibling</a></code></dt>
<dd>
The node immediately following this node. If there is no
        such node, this returns <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-84CF096'></a><a name='attribute-attributes'>attributes</a></code></dt>
<dd>
A <a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a> containing the
	attributes of this node (if it is an <a href='level-one-core.html#ID-745549614'><code>Element</code></a>) or
	<code>null</code> otherwise. </dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='node-ownerDoc'></a><a name='attribute-ownerDocument'>ownerDocument</a></code></dt>
<dd>
The <a href='level-one-core.html#i-Document'><code>Document</code></a> object associated with this node. This
	is also the <a href='level-one-core.html#i-Document'><code>Document</code></a> object used to create new nodes. When
	this node is a <a href='level-one-core.html#i-Document'><code>Document</code></a> this is <code>null</code>.</dd>
</dl>

</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-952280727'></a><a name='method-insertBefore'>insertBefore</a></code></dt>
<dd>
<div class='method'>
Inserts the node <code>newChild</code> before the
	existing child node <code>refChild</code>. If
	<code>refChild</code> is <code>null</code>, insert
	<code>newChild</code> at the end of the list of children.<p>
If <code>newChild</code> is a <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>
        object, all of its children are inserted, in the same order, before
	<code>refChild</code>. If the <code>newChild</code> is already in the
	tree, it is first removed.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>newChild</code><td><td>
<p>The node to insert.</td></tr>
<tr><td valign='top'><code>refChild</code><td><td>
<p>The reference node, i.e., the node before which
	the new node must be inserted.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node being inserted.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>HIERARCHY_REQUEST_ERR: Raised if this node is of a type
	that does not allow children of the type of the <code>newChild</code>
	node, or if the node to insert is one of this node's ancestors.<p>WRONG_DOCUMENT_ERR: Raised if <code>newChild</code> was created from
	a different document than the one that created this node.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.<p>NOT_FOUND_ERR: Raised if <code>refChild</code> is not a child
	    of this node.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-785887307'></a><a name='method-replaceChild'>replaceChild</a></code></dt>
<dd>
<div class='method'>
Replaces the child node <code>oldChild</code> with
	<code>newChild</code> in the list of children, and returns the
	<code>oldChild</code> node. If the <code>newChild</code> is already in
	the tree, it is first removed.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>newChild</code><td><td>
<p>The new node to put in the child list.</td></tr>
<tr><td valign='top'><code>oldChild</code><td><td>
<p>The node being replaced in the list.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node replaced.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>HIERARCHY_REQUEST_ERR: Raised if this node is of a type
	that does not allow children of the type of the <code>newChild</code>
	node, or it the node to put in is one of this node's ancestors.<p>WRONG_DOCUMENT_ERR: Raised if <code>newChild</code> was created from
	a different document than the one that created this node.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.<p>NOT_FOUND_ERR: Raised if <code>oldChild</code> is not a
	child of this node.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-1734834066'></a><a name='method-removeChild'>removeChild</a></code></dt>
<dd>
<div class='method'>
Removes the child node indicated by <code>oldChild</code> from
	the list of children, and returns it.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>oldChild</code><td><td>
<p>The node being removed.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node removed.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is
	readonly.<p>NOT_FOUND_ERR: Raised if <code>oldChild</code> is not a child
	    of this node.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-184E7107'></a><a name='method-appendChild'>appendChild</a></code></dt>
<dd>
<div class='method'>
Adds the node <code>newChild</code> to the end of the list of
	children of this node. If the <code>newChild</code> is already in the
	tree, it is first removed.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>newChild</code><td><td>
<p>The node to add.<p>If it is a
	<a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>
        object, the entire contents of the document fragment are moved
	into the child list of this node</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node added.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>HIERARCHY_REQUEST_ERR: Raised if this node is of a type
	that does not allow children of the type of the <code>newChild</code>
	node, or if the node to append is one of this node's ancestors.<p>WRONG_DOCUMENT_ERR: Raised if <code>newChild</code> was created from
	a different document than the one that created this node.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-810594187'></a><a name='method-hasChildNodes'>hasChildNodes</a></code></dt>
<dd>
<div class='method'>
 This is a convenience method to allow easy determination
	of whether a node has any children.
<dl>
<dt><b>Return Value</b></dt>
<dd>
 <code>true</code> if the node has any children,
	<code>false</code> if the node has no children.</dd>
</dl>
<br>
This method has no parameters.<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-3A0ED0A4'></a><a name='method-cloneNode'>cloneNode</a></code></dt>
<dd>
<div class='method'>
Returns a duplicate of this node, i.e., serves
	as a generic copy constructor for nodes. The duplicate node has no
	parent (<code>parentNode</code> returns <code>null</code>.).<p>
Cloning an <a href='level-one-core.html#ID-745549614'><code>Element</code></a> copies
	all attributes and their values, including those generated by the
	XML processor to represent defaulted attributes, but this method does
        not copy any text it contains unless it is a deep clone, since the text
        is contained in a child <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> node. Cloning any other type of
	node simply returns a copy of this node.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>deep</code><td><td>
<p>If <code>true</code>, recursively clone the subtree under the
	specified node; if <code>false</code>, clone only the node itself (and
	its attributes, if it is an <a href='level-one-core.html#ID-745549614'><code>Element</code></a>).
	</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The duplicate node.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-536297177'>NodeList</a></i></b></dt>
<dd>
<p>The <code>NodeList</code> interface provides the abstraction of an
      ordered collection of nodes, without defining or
      constraining how this collection is implemented.<p>The items in the <code>NodeList</code> are accessible via an
      integral index, starting from 0.

<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface NodeList {
  Node                      item(in unsigned long index);
  readonly attribute  unsigned long        length;
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-844377136'></a><a name='method-item'>item</a></code></dt>
<dd>
<div class='method'>
Returns the <code>index</code>th item in the collection.
	If <code>index</code> is greater than or equal to the number
	of nodes in the list, this returns <code>null</code>.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>index</code><td><td>
<p>Index into the collection.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node at the <code>index</code>th position in the
	  <code>NodeList</code>, or <code>null</code> if that is not a
	  valid index.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-203510337'></a><a name='attribute-length'>length</a></code></dt>
<dd>
The number of nodes in the list. The range of valid child node
	indices is 0 to <code>length-1</code> inclusive. </dd>
</dl>

</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-1780488922'>NamedNodeMap</a></i></b></dt>
<dd>
<p>Objects implementing the <code>NamedNodeMap</code> interface are
      used to represent collections of nodes that can be accessed by name. Note
      that <code>NamedNodeMap</code> does not inherit from
      <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a>; <code>NamedNodeMap</code>s are not maintained in
      any particular order. Objects contained in an object implementing
      <code>NamedNodeMap</code> may also be accessed by an ordinal index, but
      this is simply to allow convenient enumeration of the contents of a
      <code>NamedNodeMap</code>, and does not imply that the DOM specifies an
      order to these Nodes.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface NamedNodeMap {
  Node                      getNamedItem(in DOMString name);
  Node                      setNamedItem(in Node arg)
                                         raises(DOMException);
  Node                      removeNamedItem(in DOMString name)
                                            raises(DOMException);
  Node                      item(in unsigned long index);
  readonly attribute  unsigned long        length;
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-1074577549'></a><a name='method-getNamedItem'>getNamedItem</a></code></dt>
<dd>
<div class='method'>
Retrieves a node specified by name.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>Name of a node to retrieve.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
A <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> (of any type) with the specified
	  name, or <code>null</code> if the specified name did not
	  identify any node in the map. </dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-1025163788'></a><a name='method-setNamedItem'>setNamedItem</a></code></dt>
<dd>
<div class='method'>
Adds a node using its <code>nodeName</code> attribute. <p>
As the <code>nodeName</code> 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.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>arg</code><td><td>
<p>A node to store in a named node map. The node will
	later be accessible using the value of the
	<code>nodeName</code> attribute of the node. If a node with that
	name is already present in the map, it is replaced
	by the new one.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
If the new <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> replaces an existing node with the
	  same name  the previously existing <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> is returned,
	  otherwise <code>null</code> is returned.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>WRONG_DOCUMENT_ERR: Raised if <code>arg</code> was created from a different
	document than the one that created the <code>NamedNodeMap</code>.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this
	<code>NamedNodeMap</code> is readonly.<p>INUSE_ATTRIBUTE_ERR: Raised if <code>arg</code> is an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a>
	that is already an attribute of another <a href='level-one-core.html#ID-745549614'><code>Element</code></a> object. The
	DOM user must explicitly clone <a href='level-one-core.html#ID-637646024'><code>Attr</code></a>
	nodes to re-use them in other elements.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-D58B193'></a><a name='method-removeNamedItem'>removeNamedItem</a></code></dt>
<dd>
<div class='method'>
Removes a node specified by name. If the removed
    node is an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> with a default value it is immediately
    replaced.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of a node to remove.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node removed from the map or <code>null</code>
	    if no node with such a name exists.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NOT_FOUND_ERR: Raised if there is no node named
	<code>name</code> in the map.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-349467F9'></a><a name='method-item'>item</a></code></dt>
<dd>
<div class='method'>
Returns the <code>index</code>th item in the map.
	If <code>index</code> is greater than or equal to the number
	of nodes in the map, this returns <code>null</code>.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>index</code><td><td>
<p>Index into the map.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The node at the <code>index</code>th position in the
	  <code>NamedNodeMap</code>, or <code>null</code> if that is not a
	  valid index.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-6D0FB19E'></a><a name='attribute-length'>length</a></code></dt>
<dd>
The number of nodes in the map. The range of valid child node
	indices is 0 to <code>length-1</code> inclusive. </dd>
</dl>

</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-FF21A306'>CharacterData</a></i></b></dt>
<dd>
<p>The <code>CharacterData</code> 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 <code>CharacterData</code>,
	 though <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> and
	others do inherit the interface from it. All <code>offset</code>s in
	this interface start from 0.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface CharacterData : Node {
           attribute  DOMString            data;
                                 // raises(DOMException) on setting
                                 // raises(DOMException) on retrieval
  readonly attribute  unsigned long        length;
  DOMString                 substringData(in unsigned long offset,
                                          in unsigned long count)
                                          raises(DOMException);
  void                      appendData(in DOMString arg)
                                       raises(DOMException);
  void                      insertData(in unsigned long offset,
                                       in DOMString arg)
                                       raises(DOMException);
  void                      deleteData(in unsigned long offset,
                                       in unsigned long count)
                                       raises(DOMException);
  void                      replaceData(in unsigned long offset,
                                        in unsigned long count,
                                        in DOMString arg)
                                        raises(DOMException);
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-72AB8359'></a><a name='attribute-data'>data</a></code></dt>
<dd>
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
        <code>CharacterData</code> node. However, implementation limits may
	mean that the entirety of a node's data may not fit into a single
	<code>DOMString</code>. In such cases, the user may call
	<code>substringData</code> to retrieve the data in appropriately sized
	pieces.
<dl>
<dt><b>Exceptions on setting</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised when the node is
	    readonly.</dd></dl>
</dd>
</dl>

<dl>
<dt><b>Exceptions on retrieval</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>DOMSTRING_SIZE_ERR: Raised when it would return more
	    characters than fit in a <code>DOMString</code> variable on the
	    implementation platform.</dd></dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-7D61178C'></a><a name='attribute-length'>length</a></code></dt>
<dd>
The number of characters that
    are available through <code>data</code> and the
    <code>substringData</code> method below.  This may have the value zero,
    i.e., <code>CharacterData</code> nodes may be empty.</dd>
</dl>

</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-6531BCCF'></a><a name='method-substringData'>substringData</a></code></dt>
<dd>
<div class='method'>
Extracts a range of data from the node.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>offset</code><td><td>
<p>Start offset of substring to extract.</td></tr>
<tr><td valign='top'><code>count</code><td><td>
<p>The number of characters to extract.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The specified substring. If the sum of
	    <code>offset</code> and <code>count</code> exceeds the
            <code>length</code>, then all characters to the end of the data are
            returned.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INDEX_SIZE_ERR: Raised if the specified offset is negative or
	greater than the number of characters in <code>data</code>, or if the
	  specified <code>count</code> is negative.<p>DOMSTRING_SIZE_ERR: Raised if the specified range of text does
	not fit into a <code>DOMString</code>.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-32791A2F'></a><a name='method-appendData'>appendData</a></code></dt>
<dd>
<div class='method'>
Append the string to the end of the character data of the node.
	Upon success, <code>data</code> provides access to the concatenation of
	<code>data</code> and the <code>DOMString</code> specified.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>arg</code><td><td>
<p>The <code>DOMString</code> to append.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is
	readonly.</dd></dl>
</dd>
</dl>
<br>
This method returns nothing.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-3EDB695F'></a><a name='method-insertData'>insertData</a></code></dt>
<dd>
<div class='method'>
Insert a string at the specified character offset.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>offset</code><td><td>
<p>The character offset at which to insert.</td></tr>
<tr><td valign='top'><code>arg</code><td><td>
<p>The <code>DOMString</code> to insert.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INDEX_SIZE_ERR: Raised if the specified offset is negative or
	greater than the number of characters in <code>data</code>.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.</dd></dl>
</dd>
</dl>
<br>
This method returns nothing.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-7C603781'></a><a name='method-deleteData'>deleteData</a></code></dt>
<dd>
<div class='method'>
Remove a range of characters from the node. Upon success,
	<code>data</code> and <code>length</code> reflect the change.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>offset</code><td><td>
<p>The offset from which to remove characters.</td></tr>
<tr><td valign='top'><code>count</code><td><td>
<p>The number of characters to delete. If the sum of
	<code>offset</code> and <code>count</code> exceeds
	<code>length</code> then all characters from <code>offset</code>
	to the end of the data are deleted.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INDEX_SIZE_ERR: Raised if the specified offset is negative or
	greater than the number of characters in <code>data</code>, or if the
	  specified <code>count</code> is negative.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.</dd></dl>
</dd>
</dl>
<br>
This method returns nothing.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-E5CBA7FB'></a><a name='method-replaceData'>replaceData</a></code></dt>
<dd>
<div class='method'>
Replace the characters starting at the specified character
	offset with the specified string.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>offset</code><td><td>
<p>The offset from which to start replacing.</td></tr>
<tr><td valign='top'><code>count</code><td><td>
<p>The number of characters to replace. If the sum of
	    <code>offset</code> and <code>count</code> exceeds
	    <code>length</code>, then all characters to the end of the data
	    are replaced (i.e., the effect is the same as a
	    <code>remove</code> method call with the same range, followed
	    by an <code>append</code> method invocation).</td></tr>
<tr><td valign='top'><code>arg</code><td><td>
<p>The <code>DOMString</code> with which the range must
	    be replaced.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INDEX_SIZE_ERR: Raised if the specified offset is negative or
	greater than the number of characters in <code>data</code>, or if the
	  specified <code>count</code> is negative.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.</dd></dl>
</dd>
</dl>
<br>
This method returns nothing.<br>
</div>

</dd>
</dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-637646024'>Attr</a></i></b></dt>
<dd>
<p>
The <code>Attr</code> interface represents an attribute in an <a href='level-one-core.html#ID-745549614'><code>Element</code></a> object.
Typically the allowable values for the attribute are defined in a document
type definition.<p><code>Attr</code> objects inherit the <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>
   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 <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> attributes <code>parentNode</code>,
   <code>previousSibling</code>, and <code>nextSibling</code> have a
   null value for <code>Attr</code> 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, <code>Attr</code>
   nodes may not be immediate children of a <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>.
   However, they can be associated with <a href='level-one-core.html#ID-745549614'><code>Element</code></a> nodes contained within
   a <a href='level-one-core.html#ID-B63ED1A3'><code>DocumentFragment</code></a>.
   In short, users and implementors of the DOM need to be aware that
   <code>Attr</code> nodes have some things in
   common with other objects inheriting the <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> interface,
   but they also are quite distinct.<p> 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 <code>nodeValue</code>
   attribute on the <code>Attr</code> instance can also be used to
   retrieve the string version of the attribute's value(s). <p>In XML, where the value of an attribute can contain entity references,
    the child nodes of the <code>Attr</code> node provide a representation in
    which entity references are not expanded. These child nodes may be either
    <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> or <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> nodes. Because the
    attribute type may be unknown, there are no tokenized attribute values.

<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Attr : Node {
  readonly attribute  DOMString            name;
  readonly attribute  boolean              specified;
           attribute  DOMString            value;
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-1112119403'></a><a name='attribute-name'>name</a></code></dt>
<dd>
Returns the name of this attribute. </dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-862529273'></a><a name='attribute-specified'>specified</a></code></dt>
<dd>
If this attribute was explicitly given a value in the original
    document, this is <code>true</code>; otherwise, it is <code>false</code>.
    Note that the implementation is in charge of this attribute, not the
    user. If the user changes the value of the attribute (even if it ends up
    having the same value as the default value) then the <code>specified</code>
    flag is automatically flipped to <code>true</code>.  To re-specify the
    attribute as the default value from the DTD, the user must delete the
    attribute. The implementation will then make a new attribute available
    with <code>specified</code> set to <code>false</code> and the default value
    (if one exists).<p>
In summary:
<ul>
<li> If the attribute has an assigned value in the document then
    <code>specified</code> is <code>true</code>, and the value is the
    assigned value.
</li>
<li> If the attribute has no assigned value in the document and has
    a default value in the DTD, then  <code>specified</code> is <code>false</code>,
    and the value is the default value in the DTD.</li>
<li> If the attribute has no assigned value in the document and has
    a value of #IMPLIED in the DTD, then the  attribute does not appear
    in the structure model of the document.
</li>
</ul>

</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-221662474'></a><a name='attribute-value'>value</a></code></dt>
<dd>
On retrieval, the value of the attribute is returned as a
	string. Character and general entity references are replaced with their
	values.<p>
On setting, this creates a <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> node with the unparsed
	contents of the string.</dd>
</dl>

</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-745549614'>Element</a></i></b></dt>
<dd>
<p>By far the vast majority of objects (apart from text)
      that authors encounter when traversing a document
      are <code>Element</code> nodes.
      Assume the following XML document:
<pre class='code-block'>

&lt;elementExample id="demo"&gt;
  &lt;subelement1/&gt;
  &lt;subelement2&gt;&lt;subsubelement/&gt;&lt;/subelement2&gt;
&lt;/elementExample&gt;
</pre>

    <p>When represented using DOM, the top node is an <code>Element</code> node
      for "elementExample", which contains two child <code>Element</code>
      nodes, one for "subelement1" and one
      for "subelement2". "subelement1" contains no
      child nodes.<p>Elements may have attributes associated with them; since the
    <code>Element</code> interface inherits from <a href='level-one-core.html#ID-1950641247'><code>Node</code></a>, the generic
    <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> interface method <code>getAttributes</code> may be used
    to retrieve the set of all attributes for an element.  There are methods on
    the <code>Element</code> interface to retrieve either an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a>
    object by name or an attribute value by name. In XML, where an attribute
    value may contain entity references, an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> 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.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Element : Node {
  readonly attribute  DOMString            tagName;
  DOMString                 getAttribute(in DOMString name);
  void                      setAttribute(in DOMString name,
                                         in DOMString value)
                                         raises(DOMException);
  void                      removeAttribute(in DOMString name)
                                            raises(DOMException);
  Attr                      getAttributeNode(in DOMString name);
  Attr                      setAttributeNode(in Attr newAttr)
                                             raises(DOMException);
  Attr                      removeAttributeNode(in Attr oldAttr)
                                                raises(DOMException);
  NodeList                  getElementsByTagName(in DOMString name);
  void                      normalize();
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-104682815'></a><a name='attribute-tagName'>tagName</a></code></dt>
<dd>
The name of the element. For example, in:
<pre class='code-block'>

&lt;elementExample id="demo"&gt;
        ...
&lt;/elementExample&gt; ,
</pre>

     <code>tagName</code> has the value
     <code>"elementExample"</code>. Note that this is
     case-preserving in XML, as are all of the operations of the DOM.
     The HTML DOM returns the <code>tagName</code> of an HTML element
     in the canonical uppercase form, regardless of the case in the
     source HTML document. </dd>
</dl>

</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-666EE0F9'></a><a name='method-getAttribute'>getAttribute</a></code></dt>
<dd>
<div class='method'>
Retrieves an attribute value by name.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the attribute to retrieve.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> value as a string, or the empty
	string if that attribute does not have a specified or default value.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-F68F082'></a><a name='method-setAttribute'>setAttribute</a></code></dt>
<dd>
<div class='method'>
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 <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node plus any <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> and
      <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> nodes, build the appropriate subtree, and
      use <code>setAttributeNode</code> to assign it as the value of an
      attribute.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the attribute to create or alter.</td></tr>
<tr><td valign='top'><code>value</code><td><td>
<p>Value to set in string form.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INVALID_CHARACTER_ERR: Raised if the specified name contains
	an invalid character.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.</dd></dl>
</dd>
</dl>
<br>
This method returns nothing.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-6D6AC0F9'></a><a name='method-removeAttribute'>removeAttribute</a></code></dt>
<dd>
<div class='method'>
Removes an attribute by name. If the removed attribute
	has a default value it is immediately replaced.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the attribute to remove.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is
	readonly.</dd></dl>
</dd>
</dl>
<br>
This method returns nothing.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-217A91B8'></a><a name='method-getAttributeNode'>getAttributeNode</a></code></dt>
<dd>
<div class='method'>
Retrieves an <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node by name.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the attribute to retrieve.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node with the specified attribute
	  name or <code>null</code> if there is no such attribute.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-887236154'></a><a name='method-setAttributeNode'>setAttributeNode</a></code></dt>
<dd>
<div class='method'>
Adds a new attribute. If an attribute with that
	name is already present in the element, it is replaced
	by the new one.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>newAttr</code><td><td>
<p>The <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node to add to the attribute
	    list.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
If the <code>newAttr</code> attribute replaces
	an existing attribute with the same name, the
	previously existing <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node is returned, otherwise
	<code>null</code> is returned.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>WRONG_DOCUMENT_ERR: Raised if <code>newAttr</code> was
	created from a different document than the one that created the
	element.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.<p>INUSE_ATTRIBUTE_ERR: Raised if <code>newAttr</code> is already
	an attribute of another <code>Element</code> object. The
	DOM user must explicitly clone <a href='level-one-core.html#ID-637646024'><code>Attr</code></a>
	nodes to re-use them in other elements.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-D589198'></a><a name='method-removeAttributeNode'>removeAttributeNode</a></code></dt>
<dd>
<div class='method'>
Removes the specified attribute.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>oldAttr</code><td><td>
<p>The <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node to remove from the attribute
	list. If the removed <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> has a default value it is
	immediately replaced.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The <a href='level-one-core.html#ID-637646024'><code>Attr</code></a> node that was removed.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is
	readonly.<p>NOT_FOUND_ERR: Raised if <code>oldAttr</code> is not an attribute of
	the element.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-1938918D'></a><a name='method-getElementsByTagName'>getElementsByTagName</a></code></dt>
<dd>
<div class='method'>
Returns a <a href='level-one-core.html#ID-536297177'><code>NodeList</code></a> of all descendant elements with a
	given tag name, in the order in which they would be encountered in a
	preorder traversal of the <code>Element</code> tree.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>name</code><td><td>
<p>The name of the tag to match on. The special value "*"
	    matches all tags.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
A list of matching <code>Element</code> nodes.</dd>
</dl>
<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>

<dl>
<dt><code class='method-name'><a name='ID-162CF083'></a><a name='method-normalize'>normalize</a></code></dt>
<dd>
<div class='method'>
Puts all <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> nodes in the full depth of the
        sub-tree underneath this <code>Element</code> into a "normal" form
	where only markup (e.g., tags, comments, processing instructions, CDATA
	sections, and entity references) separates <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> nodes,
	i.e., there are no adjacent <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> 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.<br>
This method has no parameters.<br>
This method returns nothing.<br>
This method raises no exceptions.<br>
</div>

</dd>
</dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-1312295772'>Text</a></i></b></dt>
<dd>
<p>The <code>Text</code> interface represents the textual
      content (termed <a href='http://www.w3.org/TR/REC-xml#syntax'>character
      data</a>
 in XML) of an <a href='level-one-core.html#ID-745549614'><code>Element</code></a> or <a href='level-one-core.html#ID-637646024'><code>Attr</code></a>.
      If there is no markup inside an element's content, the text is contained
      in a single object implementing the <code>Text</code> interface that
      is the only child of the element. If there is markup, it is parsed into
      a list of elements and <code>Text</code> nodes that form the list of
      children of the element.<p>When a document is first made available via the DOM, there is
      only one <code>Text</code> node for each block of text. Users may create
      adjacent <code>Text</code> 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 <code>normalize()</code>
      method on <a href='level-one-core.html#ID-745549614'><code>Element</code></a> merges any such adjacent <code>Text</code>
      objects into a single node for each block of text; this is
      recommended before employing operations that depend on a particular
      document structure, such as navigation with <code>XPointers.</code>

<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Text : CharacterData {
  Text                      splitText(in unsigned long offset)
                                      raises(DOMException);
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Methods</b></dt>
<dd>

<dl>
<dt><code class='method-name'><a name='ID-38853C1D'></a><a name='method-splitText'>splitText</a></code></dt>
<dd>
<div class='method'>
Breaks this <code>Text</code> node into two Text nodes at the
	specified offset, keeping both in the tree as siblings. This node then
	only contains all the content up to the <code>offset</code> point. And
	a new <code>Text</code> node, which is inserted as the next sibling of
	this node, contains all the content at and after the
	<code>offset</code> point.
<dl>
<dt><b>Parameters</b></dt>
<dd>
<table border='0'>
<tr><td valign='top'><code>offset</code><td><td>
<p>The offset at which to split, starting from 0.</td></tr>
</table>
</dd>
</dl>

<dl>
<dt><b>Return Value</b></dt>
<dd>
The new <code>Text</code> node.</dd>
</dl>

<dl>
<dt><b>Exceptions</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>INDEX_SIZE_ERR: Raised if the specified offset is negative or
	greater than the number of characters in <code>data</code>.<p>NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.</dd></dl>
</dd>
</dl>
<br>
</div>

</dd>
</dl>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-1728279322'>Comment</a></i></b></dt>
<dd>
<p>This represents the content of a comment, i.e., all the
      characters between the starting '<code>&lt;!--</code>' and
      ending '<code>--&gt;</code>'. 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.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Comment : CharacterData {
};

</pre>
</dd>
</dl>
</dd>
</dl>

<br>
<a name='ID-E067D597'></a>
<h2 class='div2'>1.3. Extended Interfaces</h2><p>The interfaces defined here form part of the DOM Level 1
	  Core  specification, but objects that  expose these
	  interfaces will never be encountered in a DOM implementation
	  that deals only with HTML. As such, HTML-only DOM
	  implementations do not need to have objects that implement
	  these interfaces.
<dl>
<dt><b>Interface <i><a name='ID-667469212'>CDATASection</a></i></b></dt>
<dd>
<p>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 "]]&gt;" string
	that ends the CDATA section. CDATA sections can not be
	nested. The primary purpose is for including
      material such as XML fragments, without needing to escape all
      the delimiters.<p>The <code>DOMString</code> attribute of the
      <a href='level-one-core.html#ID-1312295772'><code>Text</code></a> node holds the text that is contained by the CDATA
      section. Note that this <em>may</em> 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.<p> The <code>CDATASection</code> interface inherits the
      <a href='level-one-core.html#ID-FF21A306'><code>CharacterData</code></a> interface through the <a href='level-one-core.html#ID-1312295772'><code>Text</code></a>
      interface. Adjacent <code>CDATASections</code> nodes are not merged by
      use of the Element.normalize() method.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface CDATASection : Text {
};

</pre>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-412266927'>DocumentType</a></i></b></dt>
<dd>
<p>Each <a href='level-one-core.html#i-Document'><code>Document</code></a> has a <code>doctype</code> attribute
        whose value is either <code>null</code> or a <code>DocumentType</code>
        object. The <code>DocumentType</code> interface in the DOM Level 1 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 scheme efforts on DTD
      representation are not clearly understood as of this writing.<p>The DOM Level 1 doesn't support editing <code>DocumentType</code>
      nodes.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface DocumentType : Node {
  readonly attribute  DOMString            name;
  readonly attribute  NamedNodeMap         entities;
  readonly attribute  NamedNodeMap         notations;
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-1844763134'></a><a name='attribute-name'>name</a></code></dt>
<dd>
The name of DTD; i.e., the name immediately
	following the <code>DOCTYPE</code> keyword.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-1788794630'></a><a name='attribute-entities'>entities</a></code></dt>
<dd>
A <a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a> containing the general entities, both
	external and internal, declared in the DTD. Duplicates are discarded.
	For example in:
<pre class='code-block'>
&lt;!DOCTYPE ex SYSTEM "ex.dtd" [
  &lt;!ENTITY foo "foo"&gt;
  &lt;!ENTITY bar "bar"&gt;
  &lt;!ENTITY % baz "baz"&gt;
]&gt;
&lt;ex/&gt;</pre>

	the interface provides access to <code>foo</code> and
	<code>bar</code> but not <code>baz</code>. Every node in this map
	also implements the <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a> interface.<p>
The DOM Level 1 does not support editing entities, therefore
        <code>entities</code> cannot be altered in any way.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-D46829EF'></a><a name='attribute-notations'>notations</a></code></dt>
<dd>
A <a href='level-one-core.html#ID-1780488922'><code>NamedNodeMap</code></a> containing  the
	notations declared in the DTD. Duplicates are discarded. Every node in
	this map also implements the <a href='level-one-core.html#ID-5431D1B9'><code>Notation</code></a> interface.<p>
The DOM Level 1 does not support editing notations, therefore
        <code>notations</code> cannot be altered in any way.</dd>
</dl>

</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-5431D1B9'>Notation</a></i></b></dt>
<dd>
<p>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 <code>nodeName</code> attribute inherited from
    <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> is set to the declared name of the notation.<p>The DOM Level 1 does not support editing <code>Notation</code>
      nodes; they are therefore readonly.<p>A <code>Notation</code> node does not have any parent.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Notation : Node {
  readonly attribute  DOMString            publicId;
  readonly attribute  DOMString            systemId;
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-54F2B4D0'></a><a name='attribute-publicId'>publicId</a></code></dt>
<dd>
The public identifier of this notation. If the
	public identifier was not specified, this is <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-E8AAB1D0'></a><a name='attribute-systemId'>systemId</a></code></dt>
<dd>
The system identifier of this notation. If the
	system identifier was not specified, this is <code>null</code>.</dd>
</dl>

</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-527DCFF2'>Entity</a></i></b></dt>
<dd>
<p>This interface represents an entity, either parsed or
      unparsed, in an XML document. Note that this models the entity
      itself <em>not</em> the entity declaration. <code>Entity</code>
      declaration modeling has been left for a later Level of the DOM
      specification.<p>The <code>nodeName</code> attribute that is inherited from
      <a href='level-one-core.html#ID-1950641247'><code>Node</code></a> contains the name of the entity.<p>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 <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> nodes in the document tree.<p>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 value of the entity may not be available. When the
      replacement value is available, the corresponding
      <code>Entity</code> node's child list represents the structure of
      that replacement text. Otherwise, the child list is empty.<p>The resolution of the children of the <code>Entity</code> (the
      replacement value) may be lazily evaluated; actions by the user (such as
      calling the <code>childNodes</code> method on the
      <code>Entity</code> Node) are assumed to trigger the evaluation.
    <p>The DOM Level 1 does not support editing <code>Entity</code>
      nodes; if a user wants to make changes to the contents of an
      <code>Entity</code>, every related <a href='level-one-core.html#ID-11C98490'><code>EntityReference</code></a> node
      has to be replaced in the structure model by a clone of the
      <code>Entity</code>'s contents, and then the desired changes must be made
      to each of those clones instead. All the descendants of an
      <code>Entity</code> node are readonly.<p>An <code>Entity</code> node does not have any parent.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface Entity : Node {
  readonly attribute  DOMString            publicId;
  readonly attribute  DOMString            systemId;
  readonly attribute  DOMString            notationName;
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-D7303025'></a><a name='attribute-publicId'>publicId</a></code></dt>
<dd>
The public identifier associated with the entity, if
	specified. If the public identifier was not specified, this
	is <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-D7C29F3E'></a><a name='attribute-systemId'>systemId</a></code></dt>
<dd>
The system identifier associated with the entity, if
	specified. If the system identifier was not specified, this
	is <code>null</code>.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-6ABAEB38'></a><a name='attribute-notationName'>notationName</a></code></dt>
<dd>
For unparsed entities, the name of the notation for the
	entity. For parsed entities, this is <code>null</code>. </dd>
</dl>

</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-11C98490'>EntityReference</a></i></b></dt>
<dd>
<p>
      <code>EntityReference</code> objects may be inserted into the
      structure model when an entity reference is in the source document,
      or when the user wishes to insert an entity reference. 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
      structure model, instead of providing <code>EntityReference</code>
      objects. If it does provide such objects, then for a given
      <code>EntityReference</code> node, it may be that there is no
      <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a> node representing the referenced entity;
      but if such an <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a> exists, then the child list of the
      <code>EntityReference</code> node is the same as that of the
      <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a> node. As with the <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a> node, all
      descendants of the <code>EntityReference</code> are readonly.<p>The resolution of the children of the <code>EntityReference</code> (the
      replacement value of the referenced <a href='level-one-core.html#ID-527DCFF2'><code>Entity</code></a>) may be lazily
      evaluated; actions by the user (such as calling the
      <code>childNodes</code> method on the <code>EntityReference</code> node)
      are assumed to trigger the evaluation.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface EntityReference : Node {
};

</pre>
</dd>
</dl>
</dd>
</dl>


<dl>
<dt><b>Interface <i><a name='ID-1004215813'>ProcessingInstruction</a></i></b></dt>
<dd>
<p>The <code>ProcessingInstruction</code> interface
      represents a  "processing instruction", used in XML
      as a way to keep processor-specific information in the text of the
      document.
<dl>
<dt><b>IDL Definition</b></dt>
<dd>
<pre class='idl-code'>
interface ProcessingInstruction : Node {
  readonly attribute  DOMString            target;
           attribute  DOMString            data;
                                      // raises(DOMException) on setting
};

</pre>
</dd>
</dl>

<dl>
<dt><b>Attributes</b></dt>
<dd>

<dl>
<dt><code class='attribute-name'><a name='ID-1478689192'></a><a name='attribute-target'>target</a></code></dt>
<dd>
The target of this processing instruction. XML defines this as
	being the first token following the markup that begins the processing
	instruction.</dd>
</dl>


<dl>
<dt><code class='attribute-name'><a name='ID-837822393'></a><a name='attribute-data'>data</a></code></dt>
<dd>
The content of this processing instruction. This
	is from the first non white space character after the target
	to the character immediately preceding the <code>?&gt;</code>.
<dl>
<dt><b>Exceptions on setting</b></dt>
<dd>
<dl><dt><a href='level-one-core.html#ID-17189187'><code>DOMException</code></a></dt><dd>
<p>NO_MODIFICATION_ALLOWED_ERR: Raised when the node is
	    readonly.</dd></dl>
</dd>
</dl>
</dd>
</dl>

</dd>
</dl>
</dd>
</dl>

<br><div class='NOPRINT'>
<hr>
<table width='100%' cellpadding='0' class='navigation-bar'>
<tr>
<td width='30%' align='left'><a href='introduction.html'><img border='0' src='./images/back.jpg' alt='What is the Document Object Model?'></a></td>
<td width='30%' align='center'><a href='cover.html'><img border='0' src='./images/up.jpg' alt='REC-DOM-Level-1-19981001'></a></td>
<td width='30%' align='right'><a href='level-one-html.html'><img border='0' src='./images/forward.jpg' alt='Document Object Model (HTML) Level 1'></a></td>
</tr>
</table>
<hr>
</div>
</body>
</html>