/[suikacvs]/markup/xml/domdtdef/domdtdef-work.en.html
Suika

Diff of /markup/xml/domdtdef/domdtdef-work.en.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by wakaba, Sun Dec 2 04:25:43 2007 UTC revision 1.26 by wakaba, Sat Dec 8 13:49:56 2007 UTC
# Line 3  Line 3 
3  <head>  <head>
4  <title>DOM Document Type Definition Module</title>  <title>DOM Document Type Definition Module</title>
5  <link rel="stylesheet" href="http://suika.fam.cx/www/style/html/spec">  <link rel="stylesheet" href="http://suika.fam.cx/www/style/html/spec">
6    <link rel="stylesheet" href="http://suika.fam.cx/www/style/def/dom">
7  <link rel="license" href="http://suika.fam.cx/c/gnu/fdl">  <link rel="license" href="http://suika.fam.cx/c/gnu/fdl">
8  </head>  </head>
9  <body class="has-abstract">  <body class="has-abstract">
10    
11  <div class="header">  <div class="header">
12  <h1>DOM Document Type Definition Module</h1>  <h1>DOM Document Type Definition Module</h1>
13  <h2>Working Draft <time datetime=2007-12-01>1 December 2007</time></h2>  <h2>Working Draft <time datetime=2007-12-08>8 December 2007</time></h2>
14    
15  <dl class="versions-uri">  <dl class="versions-uri">
16  <dt>This Version</dt>  <dt>This Version</dt>
# Line 49  available at <code class="URI">&lt;<a Line 50  available at <code class="URI">&lt;<a
50  <div id="abstract" class="section">  <div id="abstract" class="section">
51  <h2>Abstract</h2>  <h2>Abstract</h2>
52    
53  <div class="ed issue">...</div>  <p>The <abbr>DOM</abbr> Document Type Definition module is a set of
54    <abbr>DOM</abbr> interfaces, including both new interfaces and modifications
55    to existing <abbr>DOM</abbr> interfaces, over which <abbr>DOM</abbr>
56    applications are able to access to the definitions of the document type.</p>
57  </div>  </div>
58    
59  <div id="status" class="section">  <div id="status" class="section">
# Line 79  normative version.</p> Line 82  normative version.</p>
82    
83  <p class=section-info>This section is <em>non$B!>(Bnormative</em>.</p>  <p class=section-info>This section is <em>non$B!>(Bnormative</em>.</p>
84    
85  <div class="issue ed">  <p>The <dfn id=term-dom-dtdef><abbr>DOM</abbr> Document Type Definition</dfn>
86  <p>This is a work-in-progress specification for DOM Document Type  module is a set of <abbr>DOM</abbr> interfaces, including both new
87  Definition module, as implemented by manakai and  interfaces and modifications to existing <abbr>DOM</abbr> interfaces,
88  <a href="http://suika.fam.cx/gate/2005/sw/DOM%20XML%20Document%20Type%20Definition">partially documented in the SuikaWiki</a>.</p>  over which <abbr>DOM</abbr> applications are able to access to the
89    definitions of the document type.</p>
90  <p>...</p>  
91    <p>Interfaces defined in this document are partially modeled and inspired by
92    early drafts of <abbr>DOM</abbr> Level 1
93    <cite class="bibref informative">[<a href="#ref-DOM1WD">DOM1WD</a>]</cite>,
94    <abbr>DOM</abbr> Level 3 Abstract Schemas <abbr>W3C</abbr> Note
95    <cite class="bibref informative">[<a href="#ref-DOM3AS">DOM3AS</a>]</cite>,
96    and <abbr>XML</abbr> Schema <abbr>API</abbr> specification
97    <cite class="bibref informative">[<a href="#ref-XSAPI">XSAPI</a>]</cite>, but
98    they are not compatible with any of them as a whole.</p>
99  </div>  </div>
100    
101  </div>  <div class="section" id=conformance>
102    <h2>Conformance Requirements</h2>
103    
104    <div class=section id=terminology>
105    <h3>Terminology</h3>
106    
107  <div class="section" id="terminology">  <p>All examples and notes in this specification are non$B!>(Bnormative,
108  <h2>Terminology</h2>  as are all sections explicitly marked non$B!>(Bnormative.  Everything
109    else in this specification is normative.</p>
110    
111  <p>The key words <q><em class="rfc2119">MUST</em></q>,  <p>The key words <q><em class="rfc2119">MUST</em></q>,
112  <q><em class="rfc2119">MUST NOT</em></q>,  <q><em class="rfc2119">MUST NOT</em></q>, and <q><em class=rfc2119>MAY</em></q>
113  <q><em class="rfc2119">SHOULD</em></q>,  in this document are to be interpreted as described in
 <q><em class="rfc2119">SHOULD NOT</em></q>, and  
 <q><em class=rfc2119>MAY</em></q> in this  
 document are to be interpreted as described in  
114  <a href="urn:ietf:rfc:2119"><abbr title="Request for Comments">RFC</abbr>  <a href="urn:ietf:rfc:2119"><abbr title="Request for Comments">RFC</abbr>
115  2119</a>  2119</a>
116  <cite class="bibref normative">[<a href="#ref-KEYWORDS">KEYWORDS</a>]</cite>.</p>  <cite class="bibref normative">[<a href="#ref-KEYWORDS">KEYWORDS</a>]</cite>.</p>
117    
118  <!-- Strictly speaking the paragraph below is not part of terminology. -->  <p>Conformance requirements phrased as algorithms or specific steps
119  <p>All examples and notes in this specification are non$B!>(Bnormative,  <em class=rfc2119>MAY</em> be implemented in any manner, so long as the end
120  as are all sections explicitly marked non$B!>(Bnormative.  Everything  result is equivalent.  Requirements phrased in the imperative as part of
121  else in this specification is normative.</p>  algorithms are to be interpreted with the meaning of the key word used in
122    introducing the algorithm.</p>
123    
124    <p>Sometimes an exception is phrased as being required to be raised.  As
125    specified in the <abbr>DOM</abbr> Core specification
126    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>,
127    when the value of the <code>strictErrorChecking</code> attribute of the
128    <a href="#Document"><code>Document</code></a> node is <code>false</code>,
129    then the exception is not have to be raised.</p>
130    
131    <p>Some conformance requirements are phrased as requirements on interfaces,
132    attributes, methods, or objects.  Such requirements are applied to
133    implementations.</p>
134    
135    <p>The construction <q>a <code><var>Foo</var></code> object</q>, where
136    <code><var>Foo</var></code> is an interface, is used instead of the more
137    accurate <q>an object implementing the interface
138    <code><var>Foo</var></code></q>.</p>
139    
140    <p>The construction <q>raise a <code><var>Bar</var></code></q>, where
141    <code><var>Bar</var></code> is an exception code, is used instead of the more
142    accurate <q>raise an exception implementing the interface
143    <code>DOMException</code>
144    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>
145    with its <code>code</code> attribute set to
146    <code><var>Bar</var></code></q>.</p>
147    
148    <p>The terms
149    <em id=live><a href="http://www.whatwg.org/specs/web-apps/current-work/#live">live</a></em>
150    and <em id=setting>setting</em> and <em id=getting>getting</em> of an attribute
151    is defined in the HTML5 specification
152    <cite class="bibref normative">[<a href="#ref-HTML5">HTML5</a>]</cite>.</p>
153    
154    <p>The term
155    <em id=read-only><a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-readonly-node">read$B!>(Bonly (node)</a></em>
156    is defined in the <abbr>DOM</abbr> Level 3 Core specification
157    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
158    
159    <p>The <em id=idl-fragment><abbr>IDL</abbr> fragments</em> in this document are
160    to be interpreted as described in the <cite>Language Bindings for
161    <abbr>DOM</abbr> Specifications</cite> specification
162    <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>.</p>
163    
164    <p>Some <abbr>IDL</abbr> fragments are presented as <i>patch</i> to an
165    <abbr>IDL</abbr> fragment defined in another document.  They are to be
166    interpreted as an instance of
167    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMembers"><code>InterfaceMembers</code></a>
168    <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>.
169    If the <abbr>IDL</abbr> fragment to which the <i>patch</i> is applied has any
170    instance of
171    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMember"><code>InterfaceMember</code></a>
172    with same
173    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#prod-identifier"><code>identifier</code></a>
174    part as that of any instance of
175    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMember"><code>InterfaceMember</code></a>
176    in the <i>patch</i>, then the former instance of
177    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMember"><code>InterfaceMember</code></a>
178    <em class=rfc2119>MUST</em> be ignored.</p>
179    </div>
180    
181    <div class=section id=conformance-categories>
182    <h3>Conformance Categories</h3>
183    
184    <p>There are several kinds of products that can be claim to conform to
185    this specification:</p>
186    <dl>
187    <dt id=category-dom-implementation><abbr>DOM</abbr> Implementation</dt>
188      <dd>A <abbr>DOM</abbr> implementation (or just written as
189      <q>implementation</q> in this document) provides a way to access
190      <abbr>DOM</abbr> trees for applications by implementing interfaces defined
191      by this and other documents.  Unless otherwise noted, requirements in this
192      document are applied to <abbr>DOM</abbr> implementations.  To implement
193      all the features in this document, the implementation have to implement
194      some version of <abbr>DOM</abbr> Core (e.g. <abbr>DOM</abbr> Level 3 Core
195      <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>)
196      with one or more language binding (e.g. ECMAScript and Java bindings
197      <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>
198      or Perl binding
199      <cite class="bibref normative">[<a href="#ref-DOMPERL">DOMPERL</a>]</cite>).
200      A conforming implementation <em class=rfc2119>MUST</em> also be a
201      <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#dfn-conforming-implementation">conforming
202      implementation</a> of the <abbr>IDL</abbr> fragments in this document, as
203      described in the <cite>Language Bindings for <abbr>DOM</abbr>
204      Specifications</cite> specification
205      <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>.</dd>
206    <dt id=category-xml-parser><abbr>XML</abbr> Parser (<abbr>XML</abbr> document
207    to <abbr>DOM</abbr> tree converter)</dt>
208      <dd>A software component that converts
209      <abbr>XML</abbr> 1.0 or 1.1 document
210      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
211      <a href="#ref-XML11">XML11</a>]</cite> (or fragment thereof) into a
212      <abbr>DOM</abbr> tree (or fragment thereof) in the context of this
213      document.  Note that this document does not define any particular way to
214      parse an <abbr>XML</abbr> document or to construct an <abbr>DOM</abbr>
215      document, but it defines constraints for such processing.</dd>
216    <dt id=category-xml-serializer><abbr>XML</abbr> Serializer (<abbr>DOM</abbr>
217    tree to <abbr>XML</abbr> document converter)</dt>
218      <dd>A software component that converts
219      <abbr>DOM</abbr> tree (or fragment thereof) into an <abbr>XML</abbr> 1.0 or
220      1.1 document (or fragment thereof).  Note that this document does not define
221      any particular way to serialize a <abbr>DOM</abbr> tree, but it defines
222      constraints for such processing.</dd>
223    <dt id=category-infoset-dom><abbr>XML</abbr> Information Set to
224    <abbr>DOM</abbr> Tree Converter</dt>
225      <dd>A software component that converts an <abbr>XML</abbr> information set
226      <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>
227      into a <abbr>DOM</abbr> tree.  Note that this documetn does not define
228      any particular way for the convertion, but it defines constraints for
229      such processing.</dd>
230    <dt id=category-dom-infoset><abbr>DOM</abbr> Tree to <abbr>XML</abbr>
231    Information Set Converter</dt>
232      <dd>A software component that converts a <abbr>DOM</abbr> tree into
233      an <abbr>XML</abbr> information set.  Note that this documetn does not define
234      any particular way for the convertion, but it defines constraints for
235      such processing.</dd>
236    </dl>
237    </div>
238    </div>
239    
240    <div class=section id=dom-dtdef>
241    <h2><abbr>DOM</abbr> Document Type Definition Module</h2>
242    
243    <p>The <abbr>DOM</abbr> Document Type Definition module, version 3.0,
244    introduces four interfaces:
245    <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a>,
246    <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>,
247    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
248    and <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>.
249    In addition, it modifies existing interfaces
250    <a href="#Node"><code>Node</code></a>,
251    <a href="#Document"><code>Document</code></a>,
252    <a href="#DocumentType"><code>DocumentType</code></a>,
253    <a href="#Entity"><code>Entity</code></a>, and
254    <a href="#Notation"><code>Notation</code></a>
255    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
256    
257    <div class=section id=features>
258    <h3>Feature String</h3>
259    
260    <p>In a <abbr>DOM</abbr> implementation that supports the version 3.0 of
261    the <abbr>DOM</abbr> Document Type Definition module, the
262    <code>hasFeature</code> method of a <code>DOMImplementation</code> object
263    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>
264    <em class=rfc2119>MUST</em> return <code>true</code> when the parameters are
265    set to
266    <dfn id=feature-XDoctype><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></dfn>
267    and <dfn id=feature-XDoctype-3.0><code>3.0</code></dfn> respectively.  Any
268    method that takes one or more feature names, with or without version number,
269    such as <code>hasFeature</code> or <code>getFeature</code>,
270    <em class=rfc2119>MUST</em> behave in a manner consistent with it.</p>
271    </div>
272    
273    <div class=section id=section-node>
274    <h3>Modifications to the <code id=Node>Node</code> Interface</h3>
275    
276    <p>The implementation of the
277    <a href="#Node"><code>Node</code></a> interface
278    <em class=rfc2119>MUST</em> be modified as the following
279    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
280    <pre class=idl><code>// Additions to the Node interface
281    
282    // Additions to the NodeType definition group
283    const unsigned short <a href="#ELEMENT_TYPE_DEFINITION_NODE">ELEMENT_TYPE_DEFINITION_NODE</a> = 81001;
284    const unsigned short <a href="#ATTRIBUTE_DEFINITION_NODE">ATTRIBUTE_DEFINITION_NODE</a> = 81002;
285    </pre>
286    
287    <p>This specification adds two new types (subinterfaces) of
288    <a href="#Node"><code>Node</code></a>: element type definition (node type
289    <a href="#ELEMENT_TYPE_DEFINITION_NODE"><code>ELEMENT_TYPE_DEFINITION_NODE</code></a>,
290    interface
291    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>) and
292    attribute definition (node type
293    <a href="#ATTRIBUTE_DEFINITION_NODE"><code>ATTRIBUTE_DEFINITION_NODE</code></a>,
294    interface
295    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>).  For
296    these kinds of nodes, methods and attributes in the
297    <a href="#Node"><code>Node</code></a> interface must behave as following:</p>
298    
299    <dl>
300    <dt><code id=attributes>attributes</code>,
301    <code id=localName>localName</code>,
302    <code id=manakaiLocalName>manakaiLocalName</code>
303    <cite class="bibref normative">[<a href="#ref-MANAKAI">MANAKAI</a>]</cite>,
304    <code id=namespaceURI>namespaceURI</code>, and
305    <code id=prefix>prefix</code></dt>
306      <dd>
307        <p>On getting, the attributes <em class=rfc2119>MUST</em> return
308        <code>null</code>.</p>
309      </dd>
310    <dt><code id=baseURI>baseURI</code></dt>
311      <dd>
312        <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
313        value of the <a href="#baseURI"><code>baseURI</code></a> attribute
314        of the node in the <code>ownerDocument</code> attribute of the node.
315        Note that the value might be <code>null</code>.</p>
316      </dd>
317    <dt><code id=cloneNode>cloneNode</code></dt>
318      <dd class=ed>
319        <p>A future version of the specification is expected to define the
320        behavior of the <a href="#cloneNode"><code>cloneNode</code></a> method
321        for those kinds of nodes.  In addition, it might revise behavior of
322        the method for <a href="#Entity"><code>Entity</code></a>,
323        <a href="#Notation"><code>Notation</code></a>, and/or
324        <a href="#DocumentType"><code>DocumentType</code></a> nodes.</p>
325      </dd>
326      <!--
327      <dd class=ed>@@ If Attr and AttributeDefinition is inconsistent, then ...</dd>
328      -->
329    <dt><code id=compareDocumentPosition>compareDocumentPosition</code></dt>
330      <dd class=ed>
331        <p>A future version of the specification is expected to define the
332        behavior of the method
333        for those kinds of nodes.  In addition, it might revise behavior of
334        the method for <a href="#Entity"><code>Entity</code></a>,
335        <a href="#Notation"><code>Notation</code></a>, and/or
336        <a href="#DocumentType"><code>DocumentType</code></a> nodes.</p>
337      </dd>
338    <dt><code id=isDefaultNamespace>isDefaultNamespace</code></dt>
339      <dd><p>When invoked, the method <em class=rfc2119>MUST</em> return
340      <code>false</code>.</p></dd>
341    <dt><code id=isEqualNode>isEqualNode</code></dt>
342      <dd><p>For the <a href="#isEqualNode"><code>isEqualNode</code></a> method,
343      following items are added to the list of conditions for equality:</p>
344    
345      <ul>
346      <li>
347        <p>If the nodes are <a href="#DocumentType"><code>DocumentType</code></a>
348        and at least one of them has the support for the feature
349        <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>:</p>
350        <ul>
351        <li>they are equal according to <abbr>DOM</abbr> Level 3 Core definition
352        <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>,
353        and
354        <li>either:
355          <ul><!--
356          <li>both of them does not support the feature
357          <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>,</li>-->
358          <li>exactly one of them support the feature
359          <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
360          and the <code>length</code> attribute of the <code>NamedNodeMap</code>
361          object in the <a href="#elementTypes"><code>elementTypes</code></a>
362          attribute of it is equal to <code>0</code>, or</li>
363          <li>both of them support the feature
364          <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
365          and the values of the
366          <a href="#elementTypes"><code>elementTypes</code></a> attributes are
367          equal (equality of the
368          <a href="#elementTypes"><code>elementTypes</code></a> attribute is same
369          as that for the <code>attributes</code> attribute).</li>
370          </ul>
371        </li>
372        </ul>
373      </li>
374    
375      <li><p>If the nodes are
376      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
377      the values of the
378      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
379      attributes are equal (equality of the
380      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
381      attribute is same as that for the <code>attributes</code> attribute).</p></li>
382    
383      <li><p>If the nodes are
384      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>,
385      the values of the <a href="#declaredType"><code>declaredType</code></a> and
386      the <a href="#defaultType"><code>defaultType</code></a> attributes are
387      equal respectively.</p></li>
388    
389      <li><p>If the nodes are
390      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>,
391      the values of the <code>DOMStringList</code> objects in the
392      <a href="#allowedTokens"><code>allowedTokens</code></a> attributes
393      are equal, i.e. their <code>length</code> attribute values are equal and
394      each string exists in a list is contained in another list (their indeces
395      may be different), with an additional constraint that the number of the
396      items that are equal to a string in a list is equal to the number
397      of the items equal to the string in another list.</p></li>
398      </ul></dd>
399    <dt><code id=lookupNamespaceURI>lookupNamespaceURI</code> and
400    <code id=lookupPrefix>lookupPrefix</code></dt>
401      <dd><p>When invoked, the methods <em class=rfc2119>MUST</em> return
402      <code>null</code>.</p></dd>
403    <dt><code id=nodeName>nodeName</code></dt>
404      <dd>
405        <p>If the node is an
406        <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>:
407        On getting, the attribute <em class=rfc2119>MUST</em> return the
408        name of the element type definition represented by the node.</p>
409    
410        <p>If the node is an
411        <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>:
412        On getting, the attribute <em class=rfc2119>MUST</em> return the
413        name of the attribute definition represented by the node.</p>
414      </dd>
415    <dt><code id=nodeType>nodeType</code></dt>
416      <dd>
417        <p>On getting, the attribute <!--<em class=rfc2119>MUST</em>--> returns
418        <!-- NOTE: No MUST, to avoid circular reference (nodeType==8100[12]
419        is defined that they MUST implement ElementType|AttributeDefinition). -->
420        <a href="#ELEMENT_TYPE_DEFINITION_NODE"><code>ELEMENT_TYPE_DEFINITION_NODE</code></a>
421        (if the node is an
422        <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>) or
423        <a href="#ATTRIBUTE_DEFINITION_NODE"><code>ATTRIBUTE_DEFINITION_NODE</code></a>
424        (if the node is an
425        <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>).</p>
426    
427        <!-- NodeType -->
428    <p>Two constants are added to the <code id=NodeType>NodeType</code>
429    definition group of the <a href="#Node"><code>Node</code></a> interface as
430    following:</p>
431    <table>
432    <thead>
433    <tr><th scope=col>Name<th scope=col>Value<th scope=col>Description</tr>
434    </thead>
435    <tbody>
436    <tr>
437    <th scope=row><dfn id=ELEMENT_TYPE_DEFINITION_NODE class=dom-const><code>ELEMENT_TYPE_DEFINITION_NODE</code></dfn>
438    <td><code>81001</code><td>The node is an
439    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>.</tr>
440    <tr>
441    <th scope=row><dfn id=ATTRIBUTE_DEFINITION_NODE class=dom-const><code>ATTRIBUTE_DEFINITION_NODE</code></dfn>
442    <td><code>81002</code><td>The node is an
443    <a href="#ElementTypeDefinition"><code>AttributeDefinition</code></a>.</tr>
444    </tbody>
445    </table>
446      </dd>
447    <dt><code id=nodeValue>nodeValue</code> and
448    <code id=textContent>textContent</code></dt>
449      <dd>
450        <p>If the node is an
451        <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>:
452        On getting, the attributes <em class=rfc2119>MUST</em> return
453        <code>null</code>.</p>
454    
455      <div class="note memo">
456      <p>Thus, on setting the attributes does nothing
457      <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
458      </div>
459    
460      <p>If the node is an
461      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>:
462      The attribute <em class=rfc2119>MUST</em> behave as if the node
463      were <code>Attr</code>
464      <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p></dd>
465    <dt><code id=normalize>normalize</code></dt>
466      <dd><p>When a <a href="#DocumentType"><code>DocumentType</code></a> is
467      normalized, any nodes in the <code>NamedNodeMap</code> object in the
468      <a href="#elementTypes"><code>elementTypes</code></a> attribute
469      <em class=rfc2119>MUST</em> be normalized as well.</p>
470    
471      <p>When an
472      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
473      is normalized, any nodes in the <code>NamedNodeMap</code> object in the
474      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
475      attribute <em class=rfc2119>MUST</em> be normalized as well.</p></dd>
476    </dl>
477    
478    </div>
479    
480    <div class=section id=section-document>
481    <h3>Modifications to the <code id=Document>Document</code> Interface</h3>
482    
483    <!--
484    <p>If an attempt is made to adopt an
485    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> or
486    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node,
487    the <code id=adoptNode>adoptNode</code> method <em class=rfc2119>MUST</em>
488    raise a <code>NOT_SUPPORTED_ERR</code> exception <span class=ed>@@
489    ref</span>.</p>
490    -->
491    
492    <div class=ed>
493    <p>Future version of the specification is expected to define what should
494    be done if <code>adoptNode</code> or <code>importNode</code> method have to
495    adopt or import an
496    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> or
497    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node.
498    In addition it might revise behavior of those methods for
499    <a href="#Entity"><code>Entity</code></a>,
500    <a href="#Notation"><code>Notation</code></a>, and/or
501    <a href="#DocumentType"><code>DocumentType</code></a> nodes.
502    Behavior of <code>normalizeDocument</code> method for these kinds of
503    nodes might also be defined in some day.</p>
504    </div>
505    
506    </div>
507    
508    <div class=section id=section-documentxdoctype>
509    <h3>The <code>DocumentXDoctype</code> Interface</h3>
510    
511    <p>The <a href="#Document"><code>Document</code></a> nodes
512    <em class=rfc2119>MUST</em> also implement the
513    <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a> interface.</p>
514    
515    <p>An instance of the
516    <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a>
517    interface <em class=rfc2119>MUST</em> be able to be obtained by using
518    binding$B!>(Bspecific casting methods on an instance of the
519    <a href="#Document"><code>Document</code></a> interface (if such
520    casting methods are available) or by using the method <code>getFeature</code>
521    with parameter values
522    <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
523    and <a href="#feature-XDoctype-3.0"><code>3.0</code></a> respectively (if the
524    <a href="#Document"><code>Document</code></a> node supports the
525    feature <code>Core</code> version <code>3.0</code>
526    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>).</p>
527    
528    <p>The <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a> interface
529    <em class=rfc2119>MUST</em> be implemented as the following
530    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
531    <pre class=idl><code>interface <dfn id=DocumentXDoctype><code>DocumentXDoctype</code></dfn> {
532      DocumentType <a href="#createDocumentTypeDefinition">createDocumentTypeDefinition</a>
533        (in DOMString <a href="#createDocumentTypeDefinition-name"><var>name</var></a>)
534        raises (DOMException);
535      <a href="#ElementTypeDefinition">ElementTypeDefinition</a> <a href="#createElementTypeDefinition">createElementTypeDefinition</a>
536        (in DOMString <a href="#createElementTypeDefinition-name"><var>name</var></a>)
537        raises (DOMException);
538      <a href="#AttributeDefinition">AttributeDefinition</a> <a href="#createAttributeDefinition">createAttributeDefinition</a>
539        (in DOMString <a href="#createAttributeDefinition-name"><var>name</var></a>)
540        raises (DOMException);
541      <a href="#Entity">Entity</a> <a href="#createGeneralEntity">createGeneralEntityDefinition</a>
542        (in DOMString <a href="#createGeneralEntity-name"><var>name</var></a>)
543        raises (DOMException);
544      <a href="#Notation">Notation</a> <a href="#createNotation">createNotation</a>
545        (in DOMString <a href="#createNotation-name"><var>name</var></a>)
546        raises (DOMException);
547    }</code></pre>
548    
549    <dl>
550    <dt><dfn id=createDocumentTypeDefinition class=dom-method><code>createDocumentTypeDefinition</code></dfn>,
551    method</dt>
552      <dd>
553        <p>This method creates a <code>DocumentType</code> node with the specified
554        name, belonging to the document.</p>
555        <p>The
556        <dfn id=createDocumentTypeDefinition-name class=dom-param><var>name</var></dfn>
557        parameter is the name of the document type.</p>
558    
559        <p>When invoked, the method <em class=rfc2119>MUST</em> create and
560        return a <a href="#DocumentType"><code>DocumentType</code></a> node with
561        the following attributes:</p>
562        <dl>
563        <dt><code>attributes</code>, <code>parentNode</code></dt>
564          <dd><code>null</code>.</dd>
565        <dt><a href="#elementTypes"><code>elementTypes</code></a>,
566        <a href="#entities"><code>entities</code></a>, and
567        <a href="#notations"><code>notations</code></a></dt>
568          <dd>Empty <code>NamedNodeMap</code> objects respectively.</dd>
569        <dt><code>childNodes</code></dt>
570          <dd>An empty <code>NodeList</code> object.</dd>
571        <dt><a href="#internalSubset"><code>internalSubset</code></a>,
572        <a href="#publicId"><code>publicId</code></a>, and
573        <a href="#systemId"><code>systemId</code></a></dt>
574          <dd>Empty strings.</dd>
575        <dt><code>nodeName</code></dt>
576          <dd><a href="#createDocumentTypeDefinition-name"><var>name</var></a>.</dd>
577        <dt><code>ownerDocument</code></dt>
578          <dd>The <a href="#Document"><code>Document</code></a> node over which the
579          method is invoked.</dd>
580        </dl>
581        <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
582        <a href="#read-only">read$B!>(Bonly</a>.</p>
583        <p>In addition, the method <em class=rfc2119>MUST</em> be marked as
584        containing five general entity declarations: <code>amp</code>,
585        <code>lt</code>, <code>gt</code>, <code>quot</code>, and
586        <code>apos</code>.</p>
587      </dd>
588    <dt><dfn id=createElementTypeDefinition class=dom-method><code>createElementTypeDefinition</code></dfn>,
589    method</dt>
590      <dd>
591        <p>This method creates a <code>ElementTypeDefinition</code> node with the
592        specified name, belonging to the document.</p>
593        <p>The <dfn id=createElementTypeDefinition-name class=dom-param><var>name</var></dfn>
594        parameter is the name of the element type defined by the element
595        type definition.</p>
596    
597        <p>When invoked, the method <em class=rfc2119>MUST</em> create and
598        return an
599        <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
600        node with the following attributes:</p>
601        <dl>
602        <dt><a href="#attributeDefinitions"><code>attributeDefinitions</code></a></dt>
603          <dd>An empty <code>NamedNodeMap</code> object.</dd>
604        <dt><code>childNodes</code></dt>
605          <dd>An empty <code>NodeList</code> object.</dd>
606        <dt><a href="#nodeName"><code>nodeName</code></a></dt>
607          <dd><a href="#createElementTypeDefinition-name"><var>name</var></a>.</dd>
608        <dt><code>ownerDocument</code></dt>
609          <dd>The <code>Document</code> node over which the method is invoked.</dd>
610        <dt><a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
611        and <code>parentNode</code></dt>
612          <dd><code>null</code>.</dd>
613        </dl>
614        <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
615        <a href="#read-only">read$B!>(Bonly</a>.</p>
616      </dd>
617    <dt><dfn id=createAttributeDefinition class=dom-method><code>createAttributeDefinition</code></dfn>,
618    method</dt>
619      <dd>
620        <p>This method creates a <code>AttributeDefinition</code> node with the
621        specified name, belonging to the document.</p>
622        <p>The <dfn id=createAttributeDefinition-name class=dom-param><var>name</var></dfn>
623        parameter is the name of the attribute defined by the attribute
624        definition.</p>
625    
626        <p>When invoked, the method <em class=rfc2119>MUST</em> create and
627        return an
628        <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
629        node with the following attributes:</p>
630        <dl>
631        <dt><a href="#allowedTokens"><code>allowedTokens</code></a></dt>
632          <dd>An empty <code>DOMStringList</code> object.</dd>
633        <dt><code>childNodes</code></dt>
634          <dd>An empty <code>NodeList</code> object.</dd>
635        <dt><a href="#declaredType"><code>declaredType</code></a></dt>
636          <dd><a href="#NO_TYPE_ATTR"><code>NO_TYPE_ATTR</code></a>.</dd>
637        <dt><a href="#defaultType"><code>defaultType</code></a></dt>
638          <dd><a href="#UNKNOWN_DEFAULT"><code>UNKNOWN_DEFAULT</code></a>.</dd>
639        <dt><a href="#nodeName"><code>nodeName</code></a></dt>
640          <dd><a href="#createAttributeDefinition-name"><var>name</var></a>.</dd>
641        <dt><code>ownerDocument</code></dt>
642          <dd>The <code>Document</code> node over which the method is invoked.</dd>
643        <dt><a href="#ownerElementTypeDefinition"><code>ownerElementTypeDefinition</code></a>
644        and <code>parentNode</code></dt>
645          <dd><code>null</code>.</dd>
646        </dl>
647        <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
648        <a href="#read-only">read$B!>(Bonly</a>.</p>
649    
650        <!-- This requirement, if not droped, should be part of xml-id spec.
651        <div class=ed>
652        <p>@@ Should we keep these statements?:
653    However, if the &lt;cfg::cfg|xml-id> configuration
654    parameter is set to <code>true</code> and the <var>name</var>
655    is <code>xml:id</code>, then the [CODE(DOMa)@en[[[declaredType]]]]
656    attribute is set to <code>ID_ATTR</code>.
657    [CODE(DOMa)@en[[[defaultType]]]]?</p>
658        </div>-->
659      </dd>
660    <dt><dfn id=createGeneralEntity class=dom-method><code>createGeneralEntity</code></dfn>,
661    method</dt>
662      <dd>
663        <p>This method creates a <a href="#Entity"><code>Entity</code></a> node
664        with the specified name, which represents a general entity, belonging to
665        the document.</p>
666        <p>The <dfn id=createGeneralEntity-name class=dom-param><var>name</var></dfn>
667        parameter is the name of the general entity.</p>
668    
669        <p>When invoked, the method <em class=rfc2119>MUST</em> create and return
670        an <a href="#Entity"><code>Entity</code></a> node with the following
671        attributes:</p>
672        <dl>
673        <dt><code>childNodes</code></dt>
674          <dd>An empty <code>NodeList</code> object.</dd>
675        <dt><code>manakaiDeclarationBaseURI</code>,
676        <code>manakaiEntityBaseURI</code>, and <code>manakaiEntityURI</code>
677        <cite class="bibref normative">[<a href="#ref-MANAKAI">MANAKAI</a>]</cite></dt>
678          <dd>No explicit value is set.</dd>
679        <dt><a href="#hasReplacementTree"><code>hasReplacementTree</code></a></dt>
680          <dd><code>false</code>.</dd>
681        <dt><code>nodeName</code></dt>
682          <dd><a href="#createGeneralEntity-name"><var>name</var></a>.</dd>
683          <dd>
684            <div class="note memo">
685              <p>It is not an error for
686              <a href="#createGeneralEntity-name"><var>name</var></a> matching
687              to the name of one of predefined general parsed entities in
688              <abbr>XML</abbr> or <abbr>HTML</abbr>.  For example,
689              <a href="#createGeneralEntity-name"><var>name</var></a> might be
690              <code>amp</code>, resulting in an
691              <a href="#Entity"><code>Entity</code></a> node
692              with its <code>nodeName</code> attribute set to <code>amp</code>.</p>
693            </div>
694          </dd>
695        <dt><a href="#notationName"><code>notationName</code></a>,
696        <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>,
697        and <code>parentNode</code></dt>
698          <dd><code>null</code>.</dd>
699        <dt><code>ownerDocument</code></dt>
700          <dd>The <code>Document</code> node over which the method is invoked.</dd>
701        <dt><a href="#publicId"><code>publicId</code></a> and
702        <a href="#systemId"><code>systemId</code></a></dt>
703          <dd><code>null</code>.</dd>
704          <dd class=ed>@@ publicId and systemId should be empty string?</dd>
705        </dl>
706      <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
707      <a href="#read-only">read$B!>(Bonly</a>.</p></dd>
708    <dt><dfn id=createNotation class=dom-method><code>createNotation</code></dfn>,
709    method</dt>
710      <dd>
711        <p>This method creates a <code>Notation</code> node with the
712        specified name, belonging to the document.</p>
713        <p>The <dfn id=createNotation-name class=dom-param><var>name</var></dfn>
714        parameter is the name of the notation.</p>
715    
716        <p>When invoked, the method <em class=rfc2119>MUST</em> create and return
717        a <code>Notation</code> node with the following attributes:</p>
718        <dl>
719        <dt><code>childNodes</code></dt>
720          <dd>An empty <code>NodeList</code> object.</dd>
721        <dt><code>manakaiDeclarationBaseURI</code>
722        <cite class="bibref normative">[<a href="#ref-MANAKAI">MANAKAI</a>]</cite></dt>
723          <dd>No explicit value is set.</dd>
724        <dt><code>nodeName</code></dt>
725          <dd><a href="#createNotation-name"><var>name</var></a>.</dd>
726        <dt><code>ownerDocument</code></dt>
727          <dd>The <code>Document</code> node over which the method is invoked.</dd>
728        <dt><a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
729        and <code>parentNode</code></dt>
730          <dd><code>null</code>.</dd>
731        <dt><a href="#publicId"><code>publicId</code></a> and
732        <a href="#systemId"><code>systemId</code></a></dt>
733          <dd><code>null</code>.</dd>
734          <dd class=ed>@@ publicId and systemId should be empty string?</dd>
735        </dl>
736      <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
737      <a href="#read-only">read$B!>(Bonly</a>.</p></dd>
738    </dl>
739    
740    <p>These methods <em class=rfc2119>MUST</em> raise an
741    <code>INVALID_CHARACTER_ERR</code> if <var>name</var> is <em>not</em> a legal
742    <code>Name</code>
743    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
744    <a href="#ref-XML11">XML11</a>]</cite> according to the <abbr>XML</abbr>
745    version specified in the <code>xmlVersion</code> attribute of the
746    <a href="#Document"><code>Document</code></a> node.</p>
747    
748    <div class="note memo">
749    <p>Non$B!>(B<abbr>XML</abbr> case is intentionally left unspecified for now,
750    since <abbr>DOM</abbr> Level 3 Core specification
751    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>
752    does not define it for <a href="#Document"><code>Document</code></a>
753    methods.</p>
754    
755    <p><var>name</var> does not have to be a namespace qualified name.</p>
756    </div>
757    
 <p><span class=ed>Algorithm is normative but non-normative</span>.  
 In addition, the order in which <a href="#errors">errors</a> are  
 raised is undefined.</p>  
758  </div>  </div>
759    
760    
761    <div class=section id=section-documenttype>
762    <h3>Modifications to the <code id=DocumentType>DocumentType</code>
763    Interface</h3>
764    
765    <p>A <a href="#DocumentType"><code>DocumentType</code></a> interface
766    <em class=rfc2119>MAY</em> contain zero or more
767    <code>ProcessingInstruction</code> nodes in the <code>NodeList</code> object
768    contained in the <code>childNodes</code> attribute of the
769    <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
770    
771    <p>If the <a href="#DocumentType"><code>DocumentType</code></a> node is created
772    during the process to create a <abbr>DOM</abbr> from an <abbr>XML</abbr>
773    document, the <code>NodeList</code> object in the <code>childNodes</code>
774    object <em class=rfc2119>MUST</em> contains the
775    <code>ProcessingInstruction</code> nodes representing the processing
776    instructions in the document type definition of the document processed
777    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
778    <a href="#ref-XML11">XML11</a>]</cite> by the <abbr>XML</abbr> processor.  If
779    the <a href="#DocumentType"><code>DocumentType</code></a> node is marked as
780    <a href="#read-only">read$B!>(Bonly</a>, then all the child nodes
781    <em class=rfc2119>MUST</em> also be marked as
782    <a href="#read-only">read$B!>(Bonly</a>.</p>
783    
784    <p>If a <a href="#DocumentType"><code>DocumentType</code></a> node is created
785    from a
786    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.doctype">document
787    type declaration information item</a>
788    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>,
789    the <code>NodeList</code> object in the <code>childNodes</code> attribute
790    of the node <em class=rfc2119>MUST</em> contain the
791    <code>ProcessingInstruction</code> nodes created from any
792    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.pi">processing
793    instruction information items</a> in the list in the [children] property of the
794    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.doctype">document
795    type declaration item</a> in the same order.</p>
796    
797    <p>If a <a href="#DocumentType"><code>DocumentType</code></a> node is mapped to
798    a document type declaration information item, the list in the [children]
799    property <em class=rfc2119>MUST</em> contain the processng instruction
800    information items created from the <code>ProcessingInstruction</code> nodes
801    in the <code>NodeList</code> object in the <code>childNodes</code> attribute
802    of the <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
803    
804    <p>The implementation of the
805    <a href="#DocumentType"><code>DocumentType</code></a> interface
806    <em class=rfc2119>MUST</em> be modified as the following
807    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
808    <pre class=idl><code>// Modifications to the DocumentType interface
809      attribute DOMString <a href="#publicId">publicId</a>;
810      attribute DOMString <a href="#systemId">systemId</a>;
811    
812      attribute DOMString <a href="#internalSubset">internalSubset</a>;
813    </code></pre>
814    
815    <p>The <code id=publicId>publicId</code> attribute and the
816    <code id=systemId>systemId</code> attribute of
817    <a href="#DocumentType"><code>DocumentType</code></a>,
818    <a href="#Entity"><code>Entity</code></a>, and
819    <a href="#Notation"><code>Notation</code></a> interfaces are no longer
820    read$B!>(Bonly.</p>
821    
822    <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
823    <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
824    <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it <em class=rfc2119>MUST</em>
825    set the specified value as the value associated to the attribute.  No
826    normalization, relative reference resolution, or lexical validation is
827    performed. <span class=ed>@@ If the new value is <code>null</code>, should an e
828    mpty string be set?</span></p>
829    
830    <div class="note memo">
831    <p>Setting an invalid identifier might make the node unserializable.
832    Setting a public identifier while leaveing system identifier unspecified
833    would also make the <a href="#DocumentType"><code>DocumentType</code></a>
834    or <a href="#Entity"><code>Entity</code></a> node unserializable.</p>
835    </div>
836    
837    <div class=ed>
838    <p>ISSUE: In HTML5, Firefox 1.5, and Opera 9, not specifying public or system identifier results in empty strings.</p>
839    </div>
840    
841    <p>The <code id=internalSubset>internalSubset</code> attribute of the
842    <a href="#DocumentType"><code>DocumentType</code></a> interface is no longer
843    read$B!>(Bonly.</p>
844    
845    <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
846    <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
847    <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it <em class=rfc2119>MUST</em>
848    set the specified value as the value associated to the attribute.  No
849    normalization, or lexical validation is performed.  <span class=ed>@@ If the
850    new value is <code>null</code>, should an empty string be set?</span></p>
851    
852    </div>
853    
854    <div class=section id=section-documenttypedefinition>
855    <h3>The <code>DocumentTypeDefinition</code> Interface</h3>
856    
857    <p>The <a href="#DocumentType"><code>DocumentType</code></a> nodes
858    <em class=rfc2119>MUST</em> also implement the
859    <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
860    interface.</p>
861    
862    <p>An instance of the
863    <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
864    interface <em class=rfc2119>MUST</em> be able to be obtained by using
865    binding$B!>(Bspecific casting methods on an instance of the
866    <a href="#DocumentType"><code>DocumentType</code></a> interface (if such
867    casting methods are available) or by using the method <code>getFeature</code>
868    with parameter values
869    <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
870    and <a href="#feature-XDoctype-3.0"><code>3.0</code></a> respectively (if the
871    <a href="#DocumentType"><code>DocumentType</code></a> node supports the
872    feature <code>Core</code> version <code>3.0</code>
873    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>).</p>
874    
875    <div class="note memo">
876    <p>This interface is a separated interface from the
877    <a href="#DocumentType"><code>DocumentType</code></a>, not a set of extensions
878    to the <a href="#DocumentType"><code>DocumentType</code></a>,
879    for the historical reason.</p>
880    
881    <p class=ed>Should the interface be merged with
882    <a href="#DocumentType"><code>DocumentType</code></a>?</p>
883    </div>
884    
885    <p>The
886    <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
887    interface <em class=rfc2119>MUST</em> be implemented as the following
888    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
889    <pre class=idl><code>interface <dfn id=DocumentTypeDefinition><code>DocumentTypeDefinition</code></dfn> {
890      readonly attribute NamedNodeMap <a href="#elementTypes">elementTypes</a>;
891      readonly attribute NamedNodeMap <a href="#generalEntities">generalEntities</a>;
892      readonly attribute NamedNodeMap <a href="#notations">notations</a>;
893    
894      <a href="#ElementTypeDefinition">ElementTypeDefinition</a> <a href="#getElementTypeDefinitionNode">getElementTypeDefinitionNode</a>
895        (in DOMString <a href="#getElementTypeDefinitionNode-name"><var>name</var></a>);
896      <a href="#Entity">Entity</a> <a href="#getGeneralEntityNode">getGeneralEntityNode</a>
897        (in DOMString <a href="#getGeneralEntityNode-name"><var>name</var></a>);
898      <a href="#Notation">Notation</a> <a href="#getNotationNode">getNotationNode</a>
899        (in DOMString <a href="#getNotationNode-name"><var>name</var></a>);
900    
901      void <a href="#setElementTypeDefinitionNode">setElementTypeDefinitionNode</a>
902        (in DOMString <a href="#setElementTypeDefinitionNode-node"><var>node</var></a>)
903        raises (DOMException);
904      void <a href="#setGeneralEntityNode">setGeneralEntityNode</a>
905        (in DOMString <a href="#setGeneralEntityNode-node"><var>node</var></a>)
906        raises (DOMException);
907      void <a href="#setNotationNode">setNotationNode</a>
908        (in DOMString <a href="#setNotationNode-node"><var>node</var></a>)
909        raises (DOMException);
910    }</code></pre>
911    
912    <dl>
913    <dt><dfn id=elementTypes class=dom-attr><code>elementTypes</code></dfn> of
914    type <code>NamedNodeMap</code>, read$B!>(Bonly</dt>
915      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
916      contains all the element type definitions belonging to the
917      <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
918    
919      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
920      <code>NamedNodeMap</code> object that contains all the
921      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
922      nodes belonging to the <code>DocumentType</code> node.  The
923      <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be read$B!>(Bonly
924      if and only if the node is <a href="#read-only">read$B!>(Bonly</a>.  The
925      <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be
926      <a href="#live">live</a>.</p>
927    
928      <p>If the <code>DocumentType</code> node is created during the process
929      to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document, the following
930      requirements are applied:  The <code>NamedNodeMap</code> object in the
931      <a href="#elementTypes"><code>elementType</code></a> attribute
932      <em class=rfc2119>MUST</em> be so transformed that the object contains
933      the <code>ElementTypeDefinition</code> nodes for the element types
934      whose name is presented as the <code>Name</code> of the element type or
935      attribute definition list declarations processed
936      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
937      <a href="#ref-XML11">XML11</a>]</cite> by the <abbr>XML</abbr>
938      processor.  If there are more than one element type declarations for an
939      element type, then the declarations other than the first one
940      <em class=rfc2119>MUST</em> be ignored for the purpose of constructing the
941      <code>NamedNodeMap</code> object.</p></dd>
942    <dt><dfn id=generalEntities class=dom-attr><code>generalEntities</code></dfn>
943    of type <code>NamedNodeMap</code>, read$B!>(Bonly</dt>
944      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
945      contains all the general entities belonging to the
946      <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
947      
948      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
949      same value as the <code id=entities>entities</code> attribute (defined in the
950      <a href="#DocumentType"><code>DocumentType</code></a> interface) of the same
951      node.</p>
952    
953      <div class="note memo">
954        <p>This attribute is part of the interface for historical reason.</p>
955      </div></dd>
956    <!--
957    All entities declared in the document type definition
958    contained in or referenced from the document entity
959    might not be exposed through this collection, depending
960    on the information provided by the XML processor for
961    the DOM implementation.  In particular, it might not
962    contain any entity if entity references are expanded
963    at the parse time.  An implementation [['''MUST NOT''']]
964    expose an [CODE(DOMi)@en[[[Entity]]]] node whose [CODE(DOMa)@en[[[nodeName]]]]
965    is equal to the name of one of five predefined general entities in
966    XML through the collection as the result of parsing of an XML
967    document that has no error.  Duplicate entity declarations are also discarded.
968    
969    The attribute [['''MUST''']] return the [CODE(DOMi)@en[[[NamedNodeMap]]]]
970    object that contains all the [CODE(DOMi)@en[[[Entity]]]] nodes
971    representing general entities belong to the node.  The returned
972    [CODE(DOMi)@en[[[NamedNodeMap]]]] object [['''MUST''']] be read-only if and only if
973    the node is read-only. Note that the [CODE(DOMi)@en[[[NamedNodeMap]]]] object is live
974    and therefore any change of read-only flag on the node is immediately
975    reflected by that of the object.
976    -->
977    <dt><dfn id=notations class=dom-attr><code>notations</code></dfn> of type
978    <code>notations</code>, read$B!>(Bonly</code>
979      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
980      contains all the notations belonging to the
981      <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
982      
983      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
984      same value as the <code>notations</code> attribute (defined in the
985      <a href="#DocumentType"><code>DocumentType</code></a> interface) of the same
986      node.</p>
987    
988      <div class="note memo">
989        <p>This attribute is part of the interface for historical reason.</p>
990        <p>Implementations are not required to implement the
991        <code>notations</code> attribute twice (for
992        <a href="#DocumentType"><code>DocumentType</code></a> and
993        <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
994        interfaces); they share exactly same definition.</p>
995      </div></dd>
996    <!--
997    If the [CODE(DOMi)@en[[[DocumentTypeDefinition]]]] node is
998    created from an XML document, duplicate notation declarations, if any, in DTD
999    [['''MUST NOT''']] result in a node in the [CODE(DOMi)@en[[[NamedNodeMap]]]]
1000    object and only the first declaration [['''MUST''']] be
1001    made available as a [CODE(DOMi)@en[[[Notation]]]] node.
1002    
1003    ;; This definition is based on one for the
1004    [CODE(DOMa)@en[[[notations]]]] attribute of the
1005    [CODE(DOMi)@en[[[DocumentType]]]] interface in DOM XML module.
1006    Since duplication is violation to the Validity Constraint,
1007    XML parsers might vary on how notations are notified to
1008    the application.  In particular, [CODE(InfoProp)@en[[[notations]]]]
1009    property of the document information item in XML Information Set
1010    is so defined that in case ''any'' notation is declared for
1011    multiple times then the property has no value.
1012    
1013    The attribute [['''MUST''']] return the [CODE(DOMi)@en[[[NamedNodeMap]]]]
1014    object that contains all the [CODE(DOMi)@en[[[Notation]]]] nodes
1015    representing notations belong to the node.  The returned
1016    [CODE(DOMi)@en[[[NamedNodeMap]]]] object [['''MUST''']] be read-only if and only if
1017    the node is read-only. Note that the [CODE(DOMi)@en[[[NamedNodeMap]]]] object is live
1018    and therefore any change of read-only flag on the node is immediately
1019    reflected by that of the object.
1020    -->
1021    <dt><dfn id=getElementTypeDefinitionNode class=dom-method><code>getElementTypeDefinitionNode</code></dfn>,
1022    method</dt>
1023      <dd><p>Returns the
1024      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1025      with the specified name.</p>
1026    
1027      <p>The
1028      <dfn id=getElementTypeDefinitionNode-name class=dom-param><var>name</var></dfn>
1029      parameter is the name of the element type.</p>
1030    
1031      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1032      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node,
1033      whose <a href="#nodeName"><code>nodeName</code></a> is equal to
1034      <a href="#getElementTypeDefinitionNode-name"><var>name</var></a>, in the
1035      <code>NamedNodeMap</code> object in the
1036      <a href="#elementTypes"><code>elementTypes</code></a> attribute of the
1037      node.  If there is no such node, it <em class=rfc2119>MUST</em> return
1038      <code>null</code>.</p></dd>
1039    <dt><dfn id=getGeneralEntityNode class=dom-method><code>getGeneralEntityNode</code></dfn>,
1040    method</dt>
1041      <dd><p>Returns the <a href="#Entity"><code>Entity</code></a> node
1042      with the specified name.</p>
1043    
1044      <p>The
1045      <dfn id=getGeneralEntityNode-name class=dom-param><var>name</var></dfn>
1046      parameter is the name of the general entity.</p>
1047    
1048      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1049      <a href="#Entity"><code>Entity</code></a> node,
1050      whose <a href="#nodeName"><code>nodeName</code></a> is equal to
1051      <a href="#getGeneralEntityNode-name"><var>name</var></a>, in the
1052      <code>NamedNodeMap</code> object in the
1053      <a href="#entities"><code>entities</code></a> attribute of the
1054      node.  If there is no such node, it <em class=rfc2119>MUST</em> return
1055      <code>null</code>.</p></dd>
1056    <dt><dfn id=getNotationNode class=dom-method><code>getNotationNode</code></dfn>,
1057    method</dt>
1058      <dd><p>Returns the <a href="#Notation"><code>Notation</code></a> node
1059      with the specified name.</p>
1060    
1061      <p>The
1062      <dfn id=getNotationNode-name class=dom-param><var>name</var></dfn>
1063      parameter is the name of the notation.</p>
1064    
1065      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1066      <a href="#Notation"><code>Notation</code></a> node,
1067      whose <a href="#nodeName"><code>nodeName</code></a> is equal to
1068      <a href="#getNotationNode-name"><var>name</var></a>, in the
1069      <code>NamedNodeMap</code> object in the
1070      <a href="#notations"><code>notations</code></a> attribute of the
1071      node.  If there is no such node, it <em class=rfc2119>MUST</em> return
1072      <code>null</code>.</p></dd>
1073    <dt><dfn id=setElementTypeDefinitionNode class=dom-method><code>setElementTypeDefinitionNode</code></dfn>,
1074    method</dt>
1075      <dd class=ed>@@</dd>
1076    <dt><dfn id=setGeneralEntityNode class=dom-method><code>setGeneralEntityNode</code></dfn>,
1077    method</dt>
1078      <dd class=ed>@@</dd>
1079    <dt><dfn id=setNotationNode class=dom-method><code>setNotationNode</code></dfn>,
1080    method</dt>
1081      <dd class=ed>@@</dd>
1082    </dl>
1083    
1084    <div class=ed>
1085    <p>A future version of this interface might define the
1086    <code>parameterEntities</code> and getter/setter for parameter entities.
1087    </div>
1088    
1089    </div>
1090    
1091    <div class=section id=section-elementtypedefinition>
1092    <h3>The <code>ElementTypeDefinition</code> Interface</h3>
1093    
1094    <p>The nodes of type
1095    <a href="#ELEMENT_TYPE_DEFINITION_NODE"><code>ELEMENT_TYPE_DEFINITION_NODE</code></a>
1096    represents an element type definition.  Such a node
1097    <em class=rfc2119>MUST</em> implement the
1098    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1099    interface, which extends the <a href="#Node"><code>Node</code></a>
1100    interface.</p>
1101    
1102    <p>An element type definition represents a definition of the element type.
1103    It is corresponding to the element type declaration in <abbr>DTD</abbr>.
1104    However, an
1105    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1106    does not represent the element type definition in <abbr>DTD</abbr> itself.  
1107    Even if there are more than one element type declarations for an element type
1108    in <abbr>DTD</abbr>, the result <abbr>DOM</abbr> will contain only an
1109    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1110    node for that element type.  In addition, if there are attribute definition
1111    declarations for an element type, even when there is no element type
1112    declaration for that element type, the <abbr>DOM</abbr> will contain an
1113    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1114    node for that element type.</p>
1115    
1116    <p>An <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1117    node cannot be a child of any node.  An
1118    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1119    cannot have any child node.</p>
1120    
1121    <p>The <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1122    interface <em class=rfc2119>MUST</em> be implemented as the following
1123    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1124    <pre class=idl><code>interface <dfn id=ElementTypeDefinition><code>ElementTypeDefinition</code></dfn> : <a href="#Node">Node</a> {
1125      readonly attribute <a href="#DocumentType">DocumentType</a> <a href="#ownerDocumentTypeDefinition">ownerDocumentTypeDefinition</a>;
1126    
1127      readonly attribute NamedNodeMap <a href="#attributeDefinitions">attributeDefinitions</a>;
1128      <a href="#AttributeDefinition">AttributeDefinition</a> <a href="#getAttributeDefinitionNode">getAttributeDefinitionNode</a>
1129        (in DOMString <a href="#getAttributeDefinitionNode-name"><var>name</var></a>);
1130      void <a href="#setAttributeDefinitionNode">setAttributeDefinitionNode</a>
1131        (in <a href="#AttributeDefinition">AttributeDefinition</a> <a href="#setAttributeDefinitionNode-node"><var>node</var></a>)
1132        raises (DOMException);
1133    }</code></pre>
1134    
1135    <dl>
1136    <dt><dfn id=ownerDocumentTypeDefinition class=dom-attr><code>ownerDocumentTypeDefinition</code></dfn>
1137    of type <a href="#DocumentType"><code>DocumentType</code></a>, read$B!>(Bonly</dt>
1138      <dd><p>The
1139      <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
1140      attribute of
1141      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
1142      <a href="#Entity"><code>Entity</code></a>, and
1143      <a href="#Notation"><code>Notation</code></a> interfaces contain the
1144      <a href="#DocumentType"><code>DocumentType</code></a> node to which the node
1145      is attached.</p>
1146    
1147      <p>On getting, the attribute <em class=rfc2119>MUST</em> return a
1148      <a href="#DocumentType"><code>DocumentType</code></a> node.  It
1149      <em class=rfc2119>MUST</em> be such a node that whose
1150      <a href="#elementTypes"><code>elementTypes</code></a> (for an
1151      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1152      node), <a href="#entities"><code>entities</code></a> (for an
1153      <a href="#Entity"><code>Entity</code></a> node), or
1154      <a href="#notations"><code>notations</code></a> (for a
1155      <a href="#Notation"><code>Notation</code></a> node) attribute contains the
1156      <code>NamedNodeMap</code> object that contains the node.  If there is no such
1157      a <a href="#DocumentType"><code>DocumentType</code></a> node,
1158      then <code>null</code> <em class=rfc2119>MUST</em> be returned.</p></dd>
1159    <dt><dfn id=attributeDefinitions class=dom-attr><code>attributeDefinitions</code></dfn>
1160    of type NamedNodeMap, read$B!>(Bonly</dt>
1161      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
1162      contains all the attribute definitions belonging to the
1163      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1164      node.</p>
1165    
1166      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
1167      <code>NamedNodeMap</code> object that contains all the
1168      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1169      belonging to the
1170      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node.
1171      The <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be
1172      read$B!>(Bonly if and only if the node is <a href="#read-only">read$B!>(Bonly</a>.  
1173      The <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be
1174      <a href="#live">live</a>.</p>
1175      
1176      <p>If the
1177      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1178      is created during the process to create a <abbr>DOM</abbr> from an
1179      <abbr>XML</abbr> document, the following requirements are applied:  The
1180      <code>NamedNodeMap</code> object in the
1181      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1182      attribute <em class=rfc2119>MUST</em> be so transformed that the object
1183      contains the
1184      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1185      corresponding to the attribute definitions in the attribute definition
1186      list declarations processed
1187      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1188      <a href="#ref-XML11">XML11</a>]</cite> by the <abbr>XML</abbr> processor and
1189      associated to the element type represented by the node.  If there are more
1190      than one attribute definitions for an attribute, then the definitions other
1191      than the first one <em class=rfc2119>MUST</em> be ignored for the purpose
1192      of constructing the <code>NamedNodeMap</code> object.</p></dd>
1193    <dt><dfn id=getAttributeDefinitionNode class=dom-method><code>getAttributeDefinitionNode</code></dfn>,
1194    method</dt>
1195      <dd><p>Return the
1196      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1197      with the specified name.</p>
1198    
1199      <p>The
1200      <dfn id=getAttributeDefinitionNode-name class=dom-param><var>name</var></dfn>
1201      parameter is the name of the attribute.</p>
1202    
1203      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1204      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node,
1205      whose <a href="#nodeName"><code>nodeName</code></a> attribute value is
1206      equal to <a href="#getAttributeDefinitionNode-name"><var>name</var></a>,
1207      in the <code>NamedNodeMap</code> in the
1208      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1209      attribute of the node.  If there is no such node, it
1210      <em class=rfc2119>MUST</em> return <code>null</code>.</p></dd>
1211    <dt><dfn id=setAttributeDefinitionNode class=dom-method><code>setAttributeDefinitionNode</code></dfn>,
1212    method</dt>
1213      <dd class=ed>@@</dd>
1214    </dl>
1215    
1216    <div class=ed>
1217    <p>A future version of the specification might define a set of attributes
1218    and methods for representing and accessing to the content model of the
1219    element type.</p>
1220    </div>
1221    </div>
1222    
1223    <div class=section id=section-attributedefinition>
1224    <h3>The <code>AttributeDefinition</code> Interface</h3>
1225    
1226    <p>The nodes of type
1227    <a href="#ATTRIBUTE_DEFINITION_NODE"><code>ATTRIBUTE_DEFINITION_NODE</code></a>
1228    represents an attribute definition.  Such a node
1229    <em class=rfc2119>MUST</em> implement the
1230    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> interface,
1231    which extends the <a href="#Node"><code>Node</code></a> interface.</p>
1232    
1233    <p>An attribute definition represents a definition of the attribute
1234    associated to an element type.  It is corresponding to the attribute definition
1235    in the attribute list declaration in <abbr>DTD</abbr>.  However, an
1236    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node does
1237    not represent the attribute definition in <abbr>DTD</abbr> itself.  Even if
1238    there are more than one attribute definitions for an attribute of an element
1239    type in <abbr>DTD</abbr>, the result <abbr>DOM</abbr> will contain only an
1240    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node for
1241    that attribute.</p>
1242    
1243    <p>An <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1244    node cannot be a child of any node.  An
1245    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1246    can have zero or more child nodes of same kinds as those allowed for
1247    <code>Attr</code> nodes
1248    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
1249    
1250    <p>The <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1251    interface <em class=rfc2119>MUST</em> be implemented as the following
1252    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1253    <pre class=idl><code>interface <dfn id=AttributeDefinition><code>AttributeDefinition</code></dfn> : <a href="#Node">Node</a> {
1254      <span class=comment>// <a href="#DeclaredValueType">DeclaredValueType</a></span>
1255      const unsigned short <a href="#NO_TYPE_ATTR">NO_TYPE_ATTR</a> = 0;
1256      const unsigned short <a href="#CDATA_ATTR">CDATA_ATTR</a> = 1;
1257      const unsigned short <a href="#ID_ATTR">ID_ATTR</a> = 2;
1258      const unsigned short <a href="#IDREF_ATTR">IDREF_ATTR</a> = 3;
1259      const unsigned short <a href="#IDREFS_ATTR">IDREFS_ATTR</a> = 4;
1260      const unsigned short <a href="#ENTITY_ATTR">ENTITY_ATTR</a> = 5;
1261      const unsigned short <a href="#ENTITIES_ATTR">ENTITIES_ATTR</a> = 6;
1262      const unsigned short <a href="#NMTOKEN_ATTR">NMTOKEN_ATTR</a> = 7;
1263      const unsigned short <a href="#NMTOKENS_ATTR">NMTOKENS_ATTR</a> = 8;
1264      const unsigned short <a href="#NOTATION_ATTR">NOTATION_ATTR</a> = 9;
1265      const unsigned short <a href="#ENUMERATION_ATTR">ENUMERATION_ATTR</a> = 10;
1266      const unsigned short <a href="#UNKNOWN_ATTR">UNKNOWN_ATTR</a> = 11;
1267    
1268      <span class=comment>// <a href="#DefaultValueType">DefaultValueType</a></span>
1269      const unsigned short <a href="#UNKNOWN_DEFAULT">UNKNOWN_DEFAULT</a> = 0;
1270      const unsigned short <a href="#FIXED_DEFAULT">FIXED_DEFAULT</a> = 1;
1271      const unsigned short <a href="#REQUIRED_DEFAULT">REQUIRED_DEFAULT</a> = 2;
1272      const unsigned short <a href="#IMPLIED_DEFAULT">IMPLIED_DEFAULT</a> = 3;
1273      const unsigned short <a href="#EXPLICIT_DEFAULT">EXPLICIT_DEFAULT</a> = 4;
1274      
1275      readonly attribute <a href="#ElementTypeDefinition">ElementTypeDefinition</a> <a href="#ownerElementTypeDefinition">ownerElementTypeDefinition</a>;
1276    
1277      readonly attribute unsigned short <a href="#declaredType">declaredType</a>;
1278      readonly attribute DOMStringList <a href="#allowedTokens">allowedTokens</a>;
1279      readonly attribute unsigned short <a href="#defaultType">defaultType</a>;
1280    }</code></pre>
1281    
1282    <dl>
1283    <dt><dfn id=ownerElementTypeDefinition class=dom-attr><code>ownerElementTypeDefinition</code></dfn>
1284    of type
1285    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
1286    read$B!>(Bonly</dt>
1287      <dd><p>The
1288      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> to
1289      which the <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1290      node belongs.</p>
1291    
1292      <p>On getting, the attribute <em class=rfc2119>MUST</em> return an
1293      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node.
1294      It <em class=rfc2119>MUST</em> be such a node that whose
1295      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1296      attribute contains the <code>NamedNodeMap</code> object that contains
1297      the <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1298      node.  If there is no such an
1299      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node,
1300      then <code>null</code> <em class=rfc2119>MUST</em> be returned.</p>
1301    <dt><dfn id=declaredType class=dom-attr><code>declaredType</code></dfn> of type
1302    <code>unsigned short</code></dt>
1303      <dd><p>The declared type
1304      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1305      <a href="#ref-XML11">XML11</a>]</cite> of the attribute.  It is expected that
1306      this attribute contains a value from the definition group
1307      <a href="#DeclaredValueType"><code>DeclaredValueType</code></a>.</p>
1308    
1309      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
1310      value associated to this attribute.</p>
1311    
1312      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1313      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the
1314      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1315      is <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1316      <em class=rfc2119>MUST</em> set the specified value as the value
1317      associated to this attribute.</p>
1318    
1319      <p>If the <code>AttributeDefinition</code> node is created during the process
1320      to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document, an
1321      appropriate value from the
1322      <a href="#DeclaredValueType"><code>DeclaredValueType</code></a> constant
1323      group <em class=rfc2119>MUST</em> be set to the attribute.</p>
1324    
1325      <!-- DeclaredValueType -->
1326    <p>The definition group
1327    <dfn id=DeclaredValueType><code>DeclaredValueType</code></dfn> contains
1328    integers indicating the declared type of attributes.  The definition
1329    group contains the following constants:</p>
1330    
1331    <table>
1332    <thead>
1333    <tr><th scope=col>Name<th scope=col>Value<th scope=col>Description</tr>
1334    </thead>
1335    <tbody>
1336    <tr>
1337    <th scope=row><dfn id=NO_TYPE_ATTR class=dom-const><code>NO_TYPE_ATTR</code>
1338    <td><code>0</code><td><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">No
1339    value</a>
1340    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>.</tr>
1341    <tr>
1342    <th scope=row><dfn id=CDATA_ATTR class=dom-const><code>CDATA_ATTR</code>
1343    <td><code>1</code><td><code>CDATA</code>
1344    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1345    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1346    <tr>
1347    <th scope=row><dfn id=ID_ATTR class=dom-const><code>ID_ATTR</code>
1348    <td><code>2</code><td><code>ID</code>
1349    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1350    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1351    <tr>
1352    <th scope=row><dfn id=IDREF_ATTR class=dom-const><code>IDREF_ATTR</code>
1353    <td><code>3</code><td><code>IDREF</code>
1354    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1355    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1356    <tr>
1357    <th scope=row><dfn id=IDREFS_ATTR class=dom-const><code>IDREFS_ATTR</code>
1358    <td><code>4</code><td><code>IDREFS</code>
1359    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1360    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1361    <tr>
1362    <th scope=row><dfn id=ENTITY_ATTR class=dom-const><code>ENTITY_ATTR</code>
1363    <td><code>5</code><td><code>ENTITY</code>
1364    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1365    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1366    <tr>
1367    <th scope=row><dfn id=ENTITIES_ATTR class=dom-const><code>ENTITIES_ATTR</code>
1368    <td><code>6</code><td><code>ENTITIES</code>
1369    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1370    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1371    <tr>
1372    <th scope=row><dfn id=NMTOKEN_ATTR class=dom-const><code>NMTOKEN_ATTR</code>
1373    <td><code>7</code><td><code>NMTOKEN</code>
1374    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1375    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1376    <tr>
1377    <th scope=row><dfn id=NMTOKENS_ATTR class=dom-const><code>NMTOKENS_ATTR</code>
1378    <td><code>8</code><td><code>NMTOKENS</code>
1379    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1380    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1381    <tr>
1382    <th scope=row><dfn id=NOTATION_ATTR class=dom-const><code>NOTATION_ATTR</code>
1383    <td><code>9</code><td><code>NOTATION</code>
1384    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1385    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1386    <tr>
1387    <th scope=row><dfn id=ENUMERATION_ATTR class=dom-const><code>ENUMERATION_ATTR</code>
1388    <td><code>10</code><td>Enumeration
1389    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1390    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1391    <tr>
1392    <th scope=row><dfn id=UNKNOWN_ATTR class=dom-const><code>UNKNOWN_ATTR</code>
1393    <td><code>11</code><td><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">Unknown</a>,
1394    because no declaration for the attribute has been read but the
1395    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.document">[all declaration processed]</a>
1396    property
1397    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>
1398    would be false.</tr>
1399    </tbody>
1400    </table>
1401    
1402    <p>If no attribute type information is available, or if the source
1403    of the information does not distinguish
1404    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">no
1405    value</a> and
1406    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">unknown</a>
1407    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>,
1408    then the value
1409    <a href="#NO_TYPE_ATTR"><code>NO_TYPE_ATTR</code></a>
1410    <em class=rfc2119>MUST</em> be used.</p>
1411    
1412    <div class="note memo">
1413    <p>An <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1414    created by the
1415    <a href="#createAttributeDefinition"><code>createAttributeDefinition</code></a>
1416    method has its <a href="#declaredType"><code>declaredType</code></a> attribute
1417    set to <a href="#NO_TYPE_ATTR"><code>NO_TYPE_ATTR</code></a>.</p>
1418    </div>
1419    
1420    <p>If the source of the information does not distinguish
1421    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">no
1422    value</a> and/or
1423    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">unknown</a>
1424    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite> and
1425    <code>CDATA</code>
1426    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1427    <a href="#ref-XML11">XML11</a>]</cite>, then the value
1428    <a href="#CDATA_ATTR"><code>CDATA_ATTR</code></a> <em class=rfc2119>MUST</em>
1429    be used.</p>
1430    
1431    <p>In Perl binding
1432    <cite class="bibref normative">[<a href="#ref-DOMPERL">DOMPERL</a>]</cite>, the
1433    <code>Attr</code> nodes <em class=rfc2119>MUST</em> implement the
1434    <a href="#DeclaredValueType"><code>DeclaredValueType</code></a>
1435    definition group.</p>
1436    
1437      </dd>
1438    <dt><dfn id=allowedTokens class=dom-attr><code>allowedTokens</code></dfn> of
1439    type <code>DOMStringList</code>, read$B!>(Bonly</dt>
1440      <dd><p>The list of allowed attribute values.</p>
1441    
1442      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
1443      <code>DOMStringList</code> object associated to this attribute.  The object
1444      <em class=rfc2119>MAY</em> contain zero or more ordered strings, consist of
1445      zero or more characters respectively, possibly with duplications.  The
1446      object <em class=rfc2119>MUST</em> be read$B!>(Bonly if and only if the node
1447      is <a href="#read-only">read$B!>(Bonly</a>.</p>
1448    
1449      <p>If the <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1450      node is created during the process to create a <abbr>DOM</abbr> from an
1451      <abbr>XML</abbr> document, the object <em class=rfc2119>MUST</em> contain
1452      the names or name tokens allowed for the attribute defined by the node.
1453      If the document is well$B!>(Bformed, the object will be empty unless
1454      the <a href="#declaredType"><code>declaredType</code></a> is
1455      <a href="#ENUMERATION_ATTR"><code>ENUMERATION_ATTR</code></a> or
1456      <a href="#NOTATION_ATTR"><code>NOTATION_ATTR</code></a>.</p>
1457    
1458      <p>If the <a href="#declaredType"><code>declaredType</code></a> is different
1459      from <a href="#ENUMERATION_ATTR"><code>ENUMERATION_ATTR</code></a> or
1460      <a href="#NOTATION_ATTR"><code>NOTATION_ATTR</code></a>, this attribute
1461      <em class=rfc2119>MUST</em> be ignored for the purpose of serializing
1462      into (part of) <abbr>XML</abbr> document.</p>
1463    
1464      <div class="note memo">
1465        <p>When serializing the node it should be noted that the object might
1466        be empty, might contain duplications, and might contain strings that are
1467        not names or name tokens.</p>
1468      </div></dd>
1469    <dt><dfn id=defaultType class=dom-attr><code>defaultType</code></dfn> of
1470    type <code>unsigned short</code></dt>
1471      <dd><p>The type of the default for the attribute.  It is expected that this
1472      attribute contains a value from the definition group
1473      <a href="#DefaultValueType"><code>DefaultValueType</code></a>.</p>
1474    
1475      <p>On getting, the attribute <em class=rfc2119>MUST</em> return
1476      the value associated to this attribute.</p>
1477    
1478      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1479      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the
1480      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1481      is <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1482      <em class=rfc2119>MUST</em> set the specified value as the value
1483      associated to this attribute.</p>
1484    
1485      <p>If the
1486      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node is
1487      created during the process to create a <abbr>DOM</abbr> from an
1488      <abbr>XML</abbr> document, an appropriate value from the
1489      <a href="#DefaultValueType"><code>DefaultValueType</code></a> definition
1490      group <em class=rfc2119>MUST</em> be set to the attribute.</p>
1491    
1492      <!-- DefaultValueType -->
1493      <p>The definition group
1494      <dfn id=DefaultValueType><code>DefaultValueType</code></dfn>
1495      contains integers indicating the type of the default for the attribute.
1496      The definition group contains the following constans:</p>
1497    
1498      <table>
1499      <thead>
1500      <tr><th scope=col>Name<th scope=col>Value<th scope=col>Description</tr>
1501      </thead>
1502      <tbody>
1503      <tr>
1504      <th scope=row><dfn id=UNKNOWN_DEFAULT class=dom-const><code>UNKNOWN_DEFAULT</code></dfn>
1505      <td><code>0</code><td>Unknown.</tr>
1506      <tr>
1507      <th scope=row><dfn id=FIXED_DEFAULT class=dom-const><code>FIXED_DEFAULT</code></dfn>
1508      <td><code>1</code><td>Provided explicitly and only the value is allowed.
1509      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1510      <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1511      <tr>
1512      <th scope=row><dfn id=REQUIRED_DEFAULT class=dom-const><code>REQUIRED_DEFAULT</code></dfn>
1513      <td><code>2</code><td>No default value and the attribute have to be
1514      explicitly specified.</tr>
1515      <tr>
1516      <th scope=row><dfn id=IMPLIED_DEFAULT class=dom-const><code>IMPLIED_DEFAULT</code></dfn>
1517      <td><code>3</code><td>Implied
1518      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1519      <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1520      <tr>
1521      <th scope=row><dfn id=EXPLICIT_DEFAULT class=dom-const><code>EXPLICIT_DEFAULT</code></dfn>
1522      <td><code>4</code><td>Provided explicitly.</tr>
1523      </tbody>
1524      </table>
1525    
1526      <p>If the source of the default type does not distinguish
1527      implied and unknown default types, then the value
1528      <a href="#IMPLIED_DEFAULT"><code>IMPLIED_DEFAULT</code></a>
1529      <em class=rfc2119>MUST</em> be used.</p>
1530    
1531      <div class="note memo">
1532      <p>An <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1533      node created by the
1534      <a href="#createAttributeDefinition"><code>createAttributeDefinition</code></a>
1535      method has its <a href="#defaultType"><code>defaultType</code></a>
1536      attribute set to
1537      <a href="#UNKNOWN_DEFAULT"><code>UNKNOWN_DEFAULT</code></a>.</p>
1538      </div></dd>
1539    </dl>
1540    
1541    </div>
1542    
1543    <div class=section id=section-entity>
1544    <h3>Modifications to the <code id=Entity>Entity</code> Interface</h3>
1545    
1546    <p>The implementation of the <a href="#Entity"><code>Entity</code></a>
1547    interface <em class=rfc2119>MUST</em> be modified as the following
1548    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1549    <pre class=idl><code>// Modifications to the Entity interface
1550      attribute DOMString <a href="#publicId">publicId</a>;
1551      attribute DOMString <a href="#systemId">systemId</a>;
1552      attribute DOMString <a href="#notationName">notationName</a>;
1553    
1554      // Additions to the Entity interface
1555      attribute DOMString <a href="#hasReplacementTree">hasReplacementTree</a>;
1556      readonly attribute <a href="#DocumentType">DocumentType</a> <a href="#ownerDocumentTypeDefinition">ownerDocumentTypeDefinition</a>;
1557    
1558      attribute boolean <a href="#isExternallyDeclared">isExternallyDeclared</a>;
1559    </code></pre>
1560    
1561    <p>The <code id=notationName>notationName</code> attribute of the
1562    <a href="#Entity"><code>Entity</code></a> interface is no longer
1563    read$B!>(Bonly.</p>
1564    
1565    <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1566    <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
1567    <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it <em class=rfc2119>MUST</em>
1568    set the specified value as the value associated to the attribute.  No lexical
1569    validation is performed.  The new value <em class=rfc2119>MAY</em> be
1570    <code>null</code>.</p>
1571    
1572    <dl>
1573    <dt><dfn id=hasReplacementTree class=dom-attr><code>hasReplacementTree</code></dfn>
1574    of type boolean</dt>
1575      <dd><p>Whether the structure of the replacement text of the entity
1576      is available via the <code>NodeList</code> object in the
1577      <code>childNodes</code> attribute of the entity.</p>
1578    
1579      <p>On getting, the attribute <em class=rfc2119>MUST</em> return
1580      the value associated to this attribute.</p>
1581    
1582      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1583      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
1584      <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1585      <em class=rfc2119>MUST</em> set the specified value as the
1586      value associated to this attribute.</p>
1587    
1588      <div class="note memo">
1589      <p>The attribute can be set to <code>false</code> even if the
1590      <a href="#Entity"><code>Entity</code></a> node has any child node.
1591      If the attribute is set to <code>false</code>, then any child node of
1592      the <a href="#Entity"><code>Entity</code></a> node ought to be ignored,
1593      say, for the purpose of serialization.</p>
1594      </div>
1595    
1596      <p>When an <code>EntityReference</code> node is created by cloning
1597      the replacement subtree of the <a href="#Entity"><code>Entity</code></a>
1598      node, if the attribute is set to <code>false</code>, then any descendant
1599      of the node <em class=rfc2119>MUST</em> be ignored.</p>
1600    
1601      <p>If the <a href="#Entity"><code>Entity</code></a> node is created during
1602      the process to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document,
1603      the following requirements are applied:  If the entity is an unparsed
1604      entity, then the attribute <em class=rfc2119>MUST</em> be set to
1605      <code>false</code>.  Otherwise, if the entity is an external entity whose
1606      replacement text is not available, or whose replacement text is not converted
1607      to a replacement tree, then the attribute <em class=rfc2119>MUST</em> be set
1608      to <code>false</code>.  Otherwise, the attribute
1609      <em class=rfc2119>MUST</em> be set to <code>true</code>.</p>
1610    
1611      <div class="note memo">
1612      <p>An <a href="#Entity"><code>Entity</code></a> node created by the
1613      <a href="#createGeneralEntity"><code>createGeneralEntity</code></a> method
1614      has its <a href="#hasReplacementTree"><code>hasReplacementTree</code></a>
1615      attribute set to <code>false</code>.</p>
1616      </div></dd>
1617    <dt><dfn id=isExternallyDeclared class=dom-attr><code>isExternallyDeclared</code></dfn>
1618    of type boolean</dt>
1619      <dd><p>Whether the entity is declared by an external entity declaration or
1620      not.  If the value is <code>true</code>, the entity is declared in an entity
1621      declaration in the external subset entity or in an external parameter entity.
1622      If the value is <code>false</code>, the entity is declared in an entity
1623      declaration in the internal subset, or the node is created in memory.</p>
1624    
1625      <p>On getting, the attribute <em class=rfc2119>MUST</em> return
1626      the value associated to this attribute.</p>
1627    
1628      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1629      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
1630      <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1631      <em class=rfc2119>MUST</em> set the specified value as the value associated
1632      to this attribute.</p>
1633    
1634      <p>If the <a href="#Entity"><code>Entity</code></a> node is created during
1635      the process to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document,
1636      the following requirements are applied:  If the entity is an unparsed
1637      entity, then the attribute <em class=rfc2119>MUST</em> be set to
1638      <code>false</code>.  Otherwise, i.e. the entity is a parsed entity, then the
1639      attribute <em class=rfc2119>MUST</em> be set to the value of whether the
1640      entity is declared by an external markup declaration or not.</p></dd>
1641    </dl>
1642    </div>
1643    
1644    <div class=section id=section-notation>
1645    <h3>Modifications to the <code id=Notation>Notation</code> Interface</h3>
1646    
1647    <p>The implementation of the <a href="#Notation"><code>Notation</code></a>
1648    interface <em class=rfc2119>MUST</em> be modified as the following
1649    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1650    <pre class=idl><code>// Modifications to the Notation interface
1651      attribute DOMString <a href="#publicId">publicId</a>;
1652      attribute DOMString <a href="#systemId">systemId</a>;
1653    
1654      // Addition to the Notation interface
1655      readonly attribute <a href="#DocumentType">DocumentType</a> <a href="#ownerDocumentTypeDefinition">ownerDocumentTypeDefinition</a>;
1656    </code></pre>
1657    </div>
1658    
1659    </div>
1660    
1661  <div id="references" class="section reference">  <div id="references" class="section reference">
1662  <h2>References</h2>  <h2>References</h2>
# Line 122  raised is undefined.</p> Line 1666  raised is undefined.</p>
1666    
1667  <dl>  <dl>
1668  <dt id=ref-DOM3CORE>DOM3CORE</dt>  <dt id=ref-DOM3CORE>DOM3CORE</dt>
1669    <dd class=ed>@@ W3C DOM Level 3 Core</dd>    <dd><cite><a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407">Document
1670  <dt id=ref-DOMDTDEF>DOMDTDEF</dt>    Object Model (<abbr>DOM</abbr>) Level 3 Core Specification, Version
1671    <dd class=ed>@@ manakai's extension to DOM for document type definitions</dd>    1.0</a></cite>, <abbr>W3C</abbr> Recommendation, <time datetime=2004-04-07>7
1672      April 2004</time>.  <em>This</em> version of the specification is referenced.
1673      The latest version of the specification is available at
1674      <code class=uri>&lt;<a href="http://www.w3.org/TR/DOM-Level-3-Core">http://www.w3.org/TR/DOM-Level-3-Core</a>></code>.</dd>
1675    <dt id=ref-DOMBIND>DOMBIND</dt>
1676      <dd><cite><a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/">Language
1677      Bindings for <abbr>DOM</abbr> Specifications</a></cite>, <abbr>W3C</abbr>
1678      Working Draft, <time datetime=2007-10-17>17 October 2007</time>.  
1679      <em>This</em> version of the specification is referenced.  The latest version
1680      of the specification is available at
1681      <code class=uri>&lt;<a href="http://www.w3.org/TR/DOM-Bindings/">http://www.w3.org/TR/DOM-Bindings/</a>></code>.</dd>
1682    <dt id=ref-DOMPERL>DOMPERL</dt>
1683      <dd><cite><a href="http://suika.fam.cx/gate/2005/sw/manakai/DOM%20Perl%20Binding">manakai's
1684      <abbr>DOM</abbr> Perl Binding</a></cite>, editor's draft.  Work in
1685      progress.</dd>
1686    <dt id=ref-HTML5>HTML5</dt>
1687      <dd><cite><a href="http://whatwg.org/html5"><abbr>HTML</abbr> 5</a></cite>,
1688      <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr>
1689      Working Draft.  Work in progress.</dd>
1690    <dt id=ref-INFOSET>INFOSET</dt>
1691      <dd><cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204"><abbr>XML</abbr>
1692      Information Set (Second Edition)</a></cite>, <abbr>W3C</abbr> Recommendation,
1693      <time datetime=2004-02-04>4 February 2004</time>.  <em>This</em> version of
1694      the specification is referenced.  The latest version of the specification is
1695      available at
1696      <code class=uri>&lt;<a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>></code>.</dd>
1697  <dt id="ref-KEYWORDS">KEYWORDS</dt>  <dt id="ref-KEYWORDS">KEYWORDS</dt>
1698    <dd><cite><a href="urn:ietf:rfc:2119">Key words for use in    <dd><cite><a href="urn:ietf:rfc:2119">Key words for use in
1699    <abbr>RFCs</abbr> to Indicate Requirement Levels</a></cite>,    <abbr>RFCs</abbr> to Indicate Requirement Levels</a></cite>,
# Line 133  raised is undefined.</p> Line 1702  raised is undefined.</p>
1702    14</a>, <abbr title="Request for Comments">RFC</abbr> 2119,    14</a>, <abbr title="Request for Comments">RFC</abbr> 2119,
1703    <time datetime=1997-03>March 1997</time>.    <time datetime=1997-03>March 1997</time>.
1704    <em>This</em> version of the specification is referenced.</dd>    <em>This</em> version of the specification is referenced.</dd>
1705  <dt id=ref-INFOSET>INFOSET</dt>  <dt id=ref-MANAKAI>MANAKAI</dt>
1706    <dd class=ed>@@</dd>    <dd><cite><a href="http://suika.fam.cx/gate/2005/sw/manakai/DOM%20Extensions">
1707  <dt id=ref-XML10">XML10</dt>    manakai's <abbr>DOM</abbr> Extensions</a></cite>, editor's draft.  Work in
1708      progress.</dd>
1709    <dt id=ref-XML10>XML10</dt>
1710    <dd><cite><a href="http://www.w3.org/TR/2006/REC-xml-20060816">Extensible    <dd><cite><a href="http://www.w3.org/TR/2006/REC-xml-20060816">Extensible
1711    Markup Language (<abbr>XML</abbr>) 1.0 (Fourth Edition)</a></cite>,    Markup Language (<abbr>XML</abbr>) 1.0 (Fourth Edition)</a></cite>,
1712    <abbr>W3C</abbr> Recommendation, <time datetime=2006-08-16>16 August    <abbr>W3C</abbr> Recommendation, <time datetime=2006-08-16>16 August
1713    2006</time>, edited in place <time datetime=2006-09-29>29 September    2006</time>, edited in place <time datetime=2006-09-29>29 September
1714    2006</time>.  Tje latest version of the specification is available at    2006</time>.  <em>This</em> version of the specification is referenced.  The
1715    <code class=uri>&lt;<a href="http://www.w3.org/TR/xml">http://www.w3.org/TR/xml</a>&gt;</code>.    latest version of the specification is available at
1716    <em>This</em> version of the specification is referenced.</dd>    <code class=uri>&lt;<a href="http://www.w3.org/TR/xml">http://www.w3.org/TR/xml</a>&gt;</code>.</dd>
1717  <dt id=ref-XML11>XML11</dt>  <dt id=ref-XML11>XML11</dt>
1718    <dd class=ed>@@</dd>    <dd><cite><a href="http://www.w3.org/TR/2006/REC-xml11-20060816/">Extensible
1719      Markup Language (<abbr>XML</abbr>) 1.1 (Second Edition)</a></cite>,
1720      <abbr>W3C</abbr> Recommendation, <time datetime=2006-08-16>16 August
1721      2006</time>, edited in place <time datetime=2006-09-29>29 September
1722      2006</time>.  <em>This</em> version of the specification is referenced.  The
1723      latest version of the specification is available at
1724      <code class=uri>&lt;<a href="http://www.w3.org/TR/xml11">http://www.w3.org/TR/xml11</a>></code>.</dd>
1725  </dl>  </dl>
1726  </div>  </div>
1727    
1728  <div id="informative-references" class="section informative reference">  <div id="informative-references" class="section informative reference">
1729  <h3>Non$B!>(Bnormative References</h3>  <h3>Non$B!>(Bnormative References</h3>
1730    
1731  <dl class=ed>  <dl>
1732  <dt id=ref-CSS>CSS</dt>  <dt id=ref-DOM1WD>DOM1WD</dt>
1733    <dd><cite><a href="http://www.w3.org/TR/2007/CR-CSS21-20070719">Cascading    <dd><cite><a href="http://www.w3.org/TR/WD-DOM-971209/">Document Object
1734    Style Sheets Level 2 Revision 1 (<abbr>CSS</abbr> 2.1)    Model Specification</a></cite>, <abbr>W3C</abbr> Working Draft,
1735    Specification</a></cite>,    <time datetime=1997-12-09>9 December 1998</time>.</dd>
1736    <abbr title="World Wide Web Consortium">W3C</abbr> Candidate    <dd><cite><a href="http://www.w3.org/TR/WD-DOM-19980318/">Document Object
1737    Recommendation, <time datetime=2007-07-19>19 July 2007</time>.    Model Specification</a></cite>, <abbr>W3C</abbr> Working Draft,
1738    Work in progress.  The latest version of the specification is    <time datetime=1998-03-18>18 March 1998</time>.</dd>
1739    available at    <dd><cite><a href="http://www.w3.org/TR/1998/WD-DOM-19980416/">Document
1740    <code class=URI>&lt;<a href="http://www.w3.org/TR/CSS21">http://www.w3.org/TR/CSS21</a>></code>.</dd>    Object Model Specification, Version 1.0</a></cite>, <abbr>W3C</abbr> Working
1741  <dt id=ref-CSSOM>CSSOM</dt>    Draft, <time datetime=1998-04-16>16 April 1998</time>.</dd>
1742    <dd><cite><a href="http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?rev=1.55&amp;content-type=text/html;%20charset=utf-8">Cascading  <dt id=ref-DOM3AS>DOM3AS</dt>
1743    Style Sheets Object Model (<abbr>CSSOM</abbr>)</a></cite>,    <dd><cite><a href="http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725/">Document
1744    <abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft,    Object Model (<abbr>DOM</abbr>) Level 3 Abstract Schemas Specification,
1745    <time datetime=2007-06-18>18 June 2007</time>.  Work in progress.    Version 1.0</a></cite>, <abbr>W3C</abbr> Note, <time datetime=2002-07-25>25
1746    The latest Editor's Draft of the specification is available at    July 2002</time>.  The latest version of the specification is available at
1747    <code class=URI>&lt;<a href="http://dev.w3.org/csswg/cssom/Overview.html">http://dev.w3.org/csswg/cssom/Overview.html</a>></code>.</dd>    <code class=uri>&lt;<a href="http://www.w3.org/TR/DOM-Level-3-AS">http://www.w3.org/TR/DOM-Level-3-AS</a>></code>.</dd>
1748  <dt id=ref-HTML5>HTML5</dt>  <dt id=ref-XSAPI>XSAPI</dt>
1749    <dd><cite><a href="http://whatwg.org/html5"><abbr>HTML</abbr> 5</a></cite>,    <dd><cite><a href="http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040309/"><abbr>XML</abbr>
1750    <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr>    Schema <abbr>API</abbr></a></cite>, <abbr>W3C</abbr> Member Submission,
1751    Working Draft.  Work in progress.</dd>    <time datetime=2004-03-09>9 March 2004</time>.  The latest version of the
1752  <dt id=ref-SAPI>SAPI</dt>    specification is available at
1753    <dd><cite><a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/selectors-api/Overview.html?rev=1.28&amp;content-type=text/html;%20charset=utf-8">Selectors <abbr>API</abbr></a></cite>,    <code class=uri>&lt;<a href="http://www.w3.org/Submission/xmlschema-api/">http://www.w3.org/Submission/xmlschema-api/</a>></code>.</dd>
   <abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft,  
   <time datetime=2007-08-29>29 August 2007</time>.  Work in progress.  
   The latest Editor's Draft of the specification is available at  
   <code class=URI>&lt;<a href="http://dev.w3.org/2006/webapi/selectors-api/Overview.html">http://dev.w3.org/2006/webapi/selectors-api/Overview.html</a>></code>.  
   The latest published version of the specification is available at  
   <code class=URI>&lt;<a href="http://www.w3.org/TR/selectors-api/">http://www.w3.org/TR/selectors-api/</a>></code>.</dd>  
 <dt id=XBL2>XBL2</dt>  
   <dd><cite><a href="http://www.mozilla.org/projects/xbl/xbl2.html"><abbr>XBL</abbr>  
   2.0</a></cite>, Mozilla.org, <time datetime=2007-03-15>15 Mar 2007</time>.  
   Work in progress.  The latest  
   <abbr title="World Wide Web Consortium">W3C</abbr>$B!>(Bpublished  
   version of the specification is available at  
   <code class=URI>&lt;<a href="http://www.w3.org/TR/xbl/">http://www.w3.org/TR/xbl/</a>></code>.</dd>  
 <dt id=ref-XML5>XML5</dt>  
   <dd class=ed>@@</dd>  
1754  </dl>  </dl>
1755  </div>  </div>
1756    

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.26

admin@suikawiki.org
ViewVC Help
Powered by ViewVC 1.1.24