/[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.1 by wakaba, Sun Dec 2 04:19:12 2007 UTC revision 1.28 by wakaba, Sun Dec 9 10:03:20 2007 UTC
# Line 1  Line 1 
1  <!DOCTYPE html>  <!DOCTYPE html>
2  <html lang="en" class="formal-specification status-work-in-progress">  <html lang="en" class="formal-specification status-work-in-progress">
3  <head>  <head>
4  <title>manakai's XML Conformance Checking</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">
 <style>  
   a[id]::before {  
     content: "[" attr(id) "]";  
     color: gray;  
     font-size: 70%;  
     font-family: Courier New, monospace;  
     vertical-align: 60%;  
   }  
 </style>  
8  </head>  </head>
9  <body class="has-abstract">  <body class="has-abstract">
10    
11  <div class="header">  <div class="header">
12  <h1>manakai's <abbr>XML</abbr> Conformance Checking</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>
17    <dd><code class="URI">&lt;<a href="http://suika.fam.cx/www/markup/xml/xmlcc/xmlcc-work"    <dd><code class="URI">&lt;<a href="http://suika.fam.cx/www/markup/xml/domdtdef/domdtdef-work"
18        >http://suika.fam.cx/www/markup/xml/xmlcc/xmlcc-work</a>&gt;</code></dd>        >http://suika.fam.cx/www/markup/xml/domdtdef/domdtdef-work</a>&gt;</code></dd>
19  <dt>Latest Version</dt>  <dt>Latest Version</dt>
20    <dd><code class="URI">&lt;<a href="http://suika.fam.cx/www/markup/xml/xmlcc/xmlcc"    <dd><code class="URI">&lt;<a href="http://suika.fam.cx/www/markup/xml/domdtdef/domdtdef"
21        >http://suika.fam.cx/www/markup/xml/xmlcc/xmlcc</a>&gt;</code></dd>        >http://suika.fam.cx/www/markup/xml/domdtdef/domdtdef</a>&gt;</code></dd>
22  <dt>Latest Working Draft</dt>  <dt>Latest Working Draft</dt>
23    <dd><code class="URI">&lt;<a href="http://suika.fam.cx/www/markup/xml/xmlcc/xmlcc-work"    <dd><code class="URI">&lt;<a href="http://suika.fam.cx/www/markup/xml/domdtdef/domdtdef-work"
24        >http://suika.fam.cx/www/markup/xml/xmlcc/xmlcc-work</a>&gt;</code></dd>        >http://suika.fam.cx/www/markup/xml/domdtdef/domdtdef-work</a>&gt;</code></dd>
25  <!-- <dt>Previous Version</dt> -->  <!-- <dt>Previous Version</dt> -->
26  <dt>Version History</dt>  <dt>Version History</dt>
27    <dd><code class=URI>&lt;<a href="http://suika.fam.cx/gate/cvs/markup/xml/xmlcc/xmlcc-work.en.html">http://suika.fam.cx/gate/cvs/markup/xml/xmlcc/xmlcc-work.en.html</a>&gt;</code></dd>    <dd><code class=URI>&lt;<a href="http://suika.fam.cx/gate/cvs/markup/xml/domdtdef/domdtdef-work.en.html">http://suika.fam.cx/gate/cvs/markup/xml/domdtdef/domdtdef-work.en.html</a>&gt;</code></dd>
28  </dl>  <dt id=author>Author</dt>
 <dl class="authors" id="author">  
 <dt>Author</dt>  
29    <dd><a href="http://suika.fam.cx/~wakaba/who?" rel="author"    <dd><a href="http://suika.fam.cx/~wakaba/who?" rel="author"
30        lang=ja>Wakaba</a>        lang=ja>Wakaba</a>
31    <code class="mail">&lt;<a href="mailto:w@suika.fam.cx" rel="author"    <code class="mail">&lt;<a href="mailto:w@suika.fam.cx" rel="author"
# Line 60  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">
60  <h2>Status of This Document</h2>  <h2>Status of This Document</h2>
61    
62  <p class=section-info><em>This section describes the status of this document  <p class=section-info>This section describes the status of this document at the
63  at the time of its publication.  Other documents  time of its publication.  Other documents might supersede this document.</p>
 might supersede this document.</em></p>  
64    
65  <p>This document is a working draft, produced as part of the  <p>This document is a working draft, produced as part of the
 <a href="http://suika.fam.cx/www/markup/html/whatpm/readme">Whatpm</a>  
 subproject of the  
66  <a href="http://suika.fam.cx/www/manakai-core/doc/web/">manakai</a>  <a href="http://suika.fam.cx/www/manakai-core/doc/web/">manakai</a>
67  project.  It might be updated, replaced, or obsoleted by  project.  It might be updated, replaced, or obsoleted by
68  other documents at any time.  It is inappropriate to  other documents at any time.  It is inappropriate to
# Line 82  cite this document as other than <q>work Line 71  cite this document as other than <q>work
71  <p>Comments on this document are welcome and  <p>Comments on this document are welcome and
72  may be sent to the <a href="#author">author</a>.</p>  may be sent to the <a href="#author">author</a>.</p>
73    
74  <p>Translations of thie document might be available.  <p>Translations of this document might be available.
75  The English version of the document is the only  The English version of the document is the only
76  normative version.</p>  normative version.</p>
77  </div>  </div>
# Line 92  normative version.</p> Line 81  normative version.</p>
81    
82  <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>
83    
84  <div class="issue ed">...</div>  <p>The <dfn id=term-dom-dtdef><abbr>DOM</abbr> Document Type Definition</dfn>
85    module is a set of <abbr>DOM</abbr> interfaces, including both new
86    interfaces and modifications to existing <abbr>DOM</abbr> interfaces,
87    over which <abbr>DOM</abbr> applications are able to access to the
88    definitions of the document type.</p>
89    
90    <p>Interfaces defined in this document are partially modeled and inspired by
91    early drafts of <abbr>DOM</abbr> Level 1
92    <cite class="bibref informative">[<a href="#ref-DOM1WD">DOM1WD</a>]</cite>,
93    <abbr>DOM</abbr> Level 3 Abstract Schemas <abbr>W3C</abbr> Note
94    <cite class="bibref informative">[<a href="#ref-DOM3AS">DOM3AS</a>]</cite>,
95    and <abbr>XML</abbr> Schema <abbr>API</abbr> specification
96    <cite class="bibref informative">[<a href="#ref-XSAPI">XSAPI</a>]</cite>, but
97    they are not compatible with any of them as a whole.</p>
98    </div>
99    
100    <div class="section" id=conformance>
101    <h2>Conformance Requirements</h2>
102    
103  </div>  <div class=section id=terminology>
104    <h3>Terminology</h3>
105    
106  <div class="section" id="terminology">  <p>All examples and notes in this specification are non$B!>(Bnormative,
107  <h2>Terminology</h2>  as are all sections explicitly marked non$B!>(Bnormative.  Everything
108    else in this specification is normative.</p>
109    
110  <p>The key words <q><em class="rfc2119">MUST</em></q>,  <p>The key words <q><em class="rfc2119">MUST</em></q>,
111  <q><em class="rfc2119">MUST NOT</em></q>,  <q><em class="rfc2119">MUST NOT</em></q>, and <q><em class=rfc2119>MAY</em></q>
112  <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  
113  <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>
114  2119</a>  2119</a>
115  <cite class="bibref normative">[<a href="#ref-KEYWORDS">KEYWORDS</a>]</cite>.</p>  <cite class="bibref normative">[<a href="#ref-KEYWORDS">KEYWORDS</a>]</cite>.</p>
116    
117  <!-- Strictly speaking the paragraph below is not part of terminology. -->  <p>Conformance requirements phrased as algorithms or specific steps
118  <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
119  as are all sections explicitly marked non$B!>(Bnormative.  Everything  result is equivalent.  Requirements phrased in the imperative as part of
120  else in this specification is normative.</p>  algorithms are to be interpreted with the meaning of the key word used in
121    introducing the algorithm.</p>
122  <p><span class=ed>Algorithm is normative but non-normative</span>.  
123  In addition, the order in which <a href="#errors">errors</a> are  <p>Sometimes an exception is phrased as being required to be raised.  As
124  raised is undefined.</p>  specified in the <abbr>DOM</abbr> Core specification
125    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>,
126    when the value of the <code>strictErrorChecking</code> attribute of the
127    <a href="#Document"><code>Document</code></a> node is <code>false</code>,
128    then the exception is not have to be raised.</p>
129    
130    <p>Some conformance requirements are phrased as requirements on interfaces,
131    attributes, methods, or objects.  Such requirements are applied to
132    implementations.</p>
133    
134    <p>The construction <q>a <code><var>Foo</var></code> object</q>, where
135    <code><var>Foo</var></code> is an interface, is used instead of the more
136    accurate <q>an object implementing the interface
137    <code><var>Foo</var></code></q>.</p>
138    
139    <p>The construction <q>raise a <code><var>Bar</var></code></q>, where
140    <code><var>Bar</var></code> is an exception code, is used instead of the more
141    accurate <q>raise an exception implementing the interface
142    <code>DOMException</code>
143    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>
144    with its <code>code</code> attribute set to
145    <code><var>Bar</var></code></q>.</p>
146    
147    <p>The terms
148    <em id=live><a href="http://www.whatwg.org/specs/web-apps/current-work/#live">live</a></em>
149    and <em id=setting>setting</em> and <em id=getting>getting</em> of an attribute
150    is defined in the HTML5 specification
151    <cite class="bibref normative">[<a href="#ref-HTML5">HTML5</a>]</cite>.</p>
152    
153    <p>The term
154    <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>
155    is defined in the <abbr>DOM</abbr> Level 3 Core specification
156    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
157    
158    <p>The <em id=idl-fragment><abbr>IDL</abbr> fragments</em> in this document are
159    to be interpreted as described in the <cite>Language Bindings for
160    <abbr>DOM</abbr> Specifications</cite> specification
161    <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>.</p>
162    
163    <p>Some <abbr>IDL</abbr> fragments are presented as <i>patch</i> to an
164    <abbr>IDL</abbr> fragment defined in another document.  They are to be
165    interpreted as an instance of
166    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMembers"><code>InterfaceMembers</code></a>
167    <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>.
168    If the <abbr>IDL</abbr> fragment to which the <i>patch</i> is applied has any
169    instance of
170    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMember"><code>InterfaceMember</code></a>
171    with same
172    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#prod-identifier"><code>identifier</code></a>
173    part as that of any instance of
174    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMember"><code>InterfaceMember</code></a>
175    in the <i>patch</i>, then the former instance of
176    <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#proddef-InterfaceMember"><code>InterfaceMember</code></a>
177    <em class=rfc2119>MUST</em> be ignored.</p>
178  </div>  </div>
179    
180    <div class=section id=conformance-categories>
181    <h3>Conformance Categories</h3>
182    
183  <div class=section id=error-categories>  <p>There are several kinds of products that can be claim to conform to
184  <h2>Error Classification</h2>  this specification:</p>
185    <dl>
186    <dt id=category-dom-implementation><abbr>DOM</abbr> Implementation</dt>
187      <dd>A <abbr>DOM</abbr> implementation (or just written as
188      <q>implementation</q> in this document) provides a way to access
189      <abbr>DOM</abbr> trees for applications by implementing interfaces defined
190      by this and other documents.  Unless otherwise noted, requirements in this
191      document are applied to <abbr>DOM</abbr> implementations.  To implement
192      all the features in this document, the implementation have to implement
193      some version of <abbr>DOM</abbr> Core (e.g. <abbr>DOM</abbr> Level 3 Core
194      <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>)
195      with one or more language binding (e.g. ECMAScript and Java bindings
196      <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>
197      or Perl binding
198      <cite class="bibref normative">[<a href="#ref-DOMPERL">DOMPERL</a>]</cite>).
199      A conforming implementation <em class=rfc2119>MUST</em> also be a
200      <a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/#dfn-conforming-implementation">conforming
201      implementation</a> of the <abbr>IDL</abbr> fragments in this document, as
202      described in the <cite>Language Bindings for <abbr>DOM</abbr>
203      Specifications</cite> specification
204      <cite class="bibref normative">[<a href="#ref-DOMBIND">DOMBIND</a>]</cite>.</dd>
205    <dt id=category-xml-parser><abbr>XML</abbr> Parser (<abbr>XML</abbr> document
206    to <abbr>DOM</abbr> tree converter)</dt>
207      <dd>A software component that converts
208      <abbr>XML</abbr> 1.0 or 1.1 document
209      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
210      <a href="#ref-XML11">XML11</a>]</cite> (or fragment thereof) into a
211      <abbr>DOM</abbr> tree (or fragment thereof) in the context of this
212      document.  Note that this document does not define any particular way to
213      parse an <abbr>XML</abbr> document or to construct an <abbr>DOM</abbr>
214      document, but it defines constraints for such processing.</dd>
215    <dt id=category-xml-serializer><abbr>XML</abbr> Serializer (<abbr>DOM</abbr>
216    tree to <abbr>XML</abbr> document converter)</dt>
217      <dd>A software component that converts
218      <abbr>DOM</abbr> tree (or fragment thereof) into an <abbr>XML</abbr> 1.0 or
219      1.1 document (or fragment thereof).  Note that this document does not define
220      any particular way to serialize a <abbr>DOM</abbr> tree, but it defines
221      constraints for such processing.</dd>
222    <dt id=category-infoset-dom><abbr>XML</abbr> Information Set to
223    <abbr>DOM</abbr> Tree Converter</dt>
224      <dd>A software component that converts an <abbr>XML</abbr> information set
225      <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>
226      into a <abbr>DOM</abbr> tree.  Note that this document does not define
227      any particular way for the conversion, but it defines constraints for
228      such processing.</dd>
229    <dt id=category-dom-infoset><abbr>DOM</abbr> Tree to <abbr>XML</abbr>
230    Information Set Converter</dt>
231      <dd>A software component that converts a <abbr>DOM</abbr> tree into
232      an <abbr>XML</abbr> information set.  Note that this document does not define
233      any particular way for the conversion, but it defines constraints for
234      such processing.</dd>
235    </dl>
236    </div>
237    </div>
238    
239  <p class=ed>If a <code>Document</code> node has no  <div class=section id=dom-dtdef>
240  xml-well-formedness-error, entity-error, and unknown-error,  <h2><abbr>DOM</abbr> Document Type Definition Module</h2>
 then it is well-formed.  If a well-formed <code>Document</code>  
 node has no xml-validity-error, it is valid.</p>  
241    
242  <div class="note memo">  <p>The <abbr>DOM</abbr> Document Type Definition module, version 3.0,
243  <p>A well$B!>(Bformed <code>Document</code> can be safely serialized  introduces four interfaces:
244  into a well$B!>(Bformed XML document.  A valid <code>Document</code>  <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a>,
245  can be easily serialized into a valid XML document.</p>  <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>,
246    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
247    and <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>.
248    In addition, it modifies existing interfaces
249    <a href="#Node"><code>Node</code></a>,
250    <a href="#Document"><code>Document</code></a>,
251    <a href="#DocumentType"><code>DocumentType</code></a>,
252    <a href="#Entity"><code>Entity</code></a>, and
253    <a href="#Notation"><code>Notation</code></a>
254    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
255    
256    <div class=section id=features>
257    <h3>Feature String</h3>
258    
259    <p>In a <abbr>DOM</abbr> implementation that supports the version 3.0 of
260    the <abbr>DOM</abbr> Document Type Definition module, the
261    <code>hasFeature</code> method of a <code>DOMImplementation</code> object
262    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>
263    <em class=rfc2119>MUST</em> return <code>true</code> when the parameters are
264    set to
265    <dfn id=feature-XDoctype><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></dfn>
266    and <dfn id=feature-XDoctype-3.0><code>3.0</code></dfn> respectively.  Any
267    method that takes one or more feature names, with or without version number,
268    such as <code>hasFeature</code> or <code>getFeature</code>,
269    <em class=rfc2119>MUST</em> behave in a manner consistent with it.</p>
270  </div>  </div>
271    
272  <p class=ed>To be a conforming <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-validating">validating XML processor</a>,  <div class=section id=section-node>
273  ...</p>  <h3>Modifications to the <code id=Node>Node</code> Interface</h3>
274    
275  <p>Errors are classified into these  <p>The implementation of the
276  <dfn id=error-category title="error category">error categories</dfn>:</p>  <a href="#Node"><code>Node</code></a> interface
277    <em class=rfc2119>MUST</em> be modified as the following
278    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
279    <pre class=idl><code>// Additions to the Node interface
280    
281    // Additions to the NodeType definition group
282    const unsigned short <a href="#ELEMENT_TYPE_DEFINITION_NODE">ELEMENT_TYPE_DEFINITION_NODE</a> = 81001;
283    const unsigned short <a href="#ATTRIBUTE_DEFINITION_NODE">ATTRIBUTE_DEFINITION_NODE</a> = 81002;
284    </pre>
285    
286    <p>This specification adds two new types (subinterfaces) of
287    <a href="#Node"><code>Node</code></a>: element type definition (node type
288    <a href="#ELEMENT_TYPE_DEFINITION_NODE"><code>ELEMENT_TYPE_DEFINITION_NODE</code></a>,
289    interface
290    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>) and
291    attribute definition (node type
292    <a href="#ATTRIBUTE_DEFINITION_NODE"><code>ATTRIBUTE_DEFINITION_NODE</code></a>,
293    interface
294    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>).  For
295    these kinds of nodes, methods and attributes in the
296    <a href="#Node"><code>Node</code></a> interface must behave as following:</p>
297    
298  <dl id=errors>  <dl>
299  <dt><dfn id=entity-error><code>entity-error</code></dfn></dt>  <dt><code id=attributes>attributes</code>,
300    <code id=localName>localName</code>,
301    <code id=namespaceURI>namespaceURI</code>, and
302    <code id=prefix>prefix</code></dt>
303      <dd>
304        <p>On getting, the attributes <em class=rfc2119>MUST</em> return
305        <code>null</code>.</p>
306      </dd>
307    <dt><code id=baseURI>baseURI</code></dt>
308    <dd>    <dd>
309      <p class=ed>@@</p>      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
310      <div class="note memo">      value of the <a href="#baseURI"><code>baseURI</code></a> attribute
311        <p>This <span class=ed>algorithm</span> does not support      of the node in the <code>ownerDocument</code> attribute of the node.
312        <abbr>DOM</abbr> tree with one or more <code>EntityReference</code>      Note that the value might be <code>null</code>.</p>
313        nodes.  It is expected that any entity references are expanded    </dd>
314        at the parse time and any unexpandable entity references  <dt><code id=cloneNode>cloneNode</code></dt>
315        make parse time errors raised so that never result in    <dd class=ed>
316        <abbr>DOM</abbr> tree with <code>EntityReference</code> nodes.</p>      <p>A future version of the specification is expected to define the
317      </div>      behavior of the <a href="#cloneNode"><code>cloneNode</code></a> method
318        for those kinds of nodes.  In addition, it might revise behavior of
319        the method for <a href="#Entity"><code>Entity</code></a>,
320        <a href="#Notation"><code>Notation</code></a>, and/or
321        <a href="#DocumentType"><code>DocumentType</code></a> nodes.</p>
322    </dd>    </dd>
323  <dt><dfn id=round-trip-error><code>round-trip-error</code></dfn></dt>    <!--
324    <dd class=ed>@@</dd>    <dd class=ed>@@ If Attr and AttributeDefinition is inconsistent, then ...</dd>
325  <dt><dfn id=round-trip-warning><code>round-trip-warning</code></dfn></dt>    -->
326    <dt><code id=compareDocumentPosition>compareDocumentPosition</code></dt>
327      <dd class=ed>
328        <p>A future version of the specification is expected to define the
329        behavior of the method
330        for those kinds of nodes.  In addition, it might revise behavior of
331        the method for <a href="#Entity"><code>Entity</code></a>,
332        <a href="#Notation"><code>Notation</code></a>, and/or
333        <a href="#DocumentType"><code>DocumentType</code></a> nodes.</p>
334      </dd>
335    <dt><code id=isDefaultNamespace>isDefaultNamespace</code></dt>
336      <dd><p>When invoked, the method <em class=rfc2119>MUST</em> return
337      <code>false</code>.</p></dd>
338    <dt><code id=isEqualNode>isEqualNode</code></dt>
339      <dd><p>For the <a href="#isEqualNode"><code>isEqualNode</code></a> method,
340      following items are added to the list of conditions for equality:</p>
341    
342      <ul>
343      <li>
344        <p>If the nodes are <a href="#DocumentType"><code>DocumentType</code></a>
345        and at least one of them has the support for the feature
346        <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>:</p>
347        <ul>
348        <li>they are equal according to <abbr>DOM</abbr> Level 3 Core definition
349        <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>,
350        and
351        <li>either:
352          <ul><!--
353          <li>both of them does not support the feature
354          <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>,</li>-->
355          <li>exactly one of them support the feature
356          <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
357          and the <code>length</code> attribute of the <code>NamedNodeMap</code>
358          object in the <a href="#elementTypes"><code>elementTypes</code></a>
359          attribute of it is equal to <code>0</code>, or</li>
360          <li>both of them support the feature
361          <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
362          and the values of the
363          <a href="#elementTypes"><code>elementTypes</code></a> attributes are
364          equal (equality of the
365          <a href="#elementTypes"><code>elementTypes</code></a> attribute is same
366          as that for the <code>attributes</code> attribute).</li>
367          </ul>
368        </li>
369        </ul>
370      </li>
371    
372      <li><p>If the nodes are
373      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
374      the values of the
375      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
376      attributes are equal (equality of the
377      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
378      attribute is same as that for the <code>attributes</code> attribute).</p></li>
379    
380      <li><p>If the nodes are
381      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>,
382      the values of the <a href="#declaredType"><code>declaredType</code></a> and
383      the <a href="#defaultType"><code>defaultType</code></a> attributes are
384      equal respectively.</p></li>
385    
386      <li><p>If the nodes are
387      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>,
388      the values of the <code>DOMStringList</code> objects in the
389      <a href="#allowedTokens"><code>allowedTokens</code></a> attributes
390      are equal, i.e. their <code>length</code> attribute values are equal and
391      each string exists in a list is contained in another list (their indecies
392      may be different), with an additional constraint that the number of the
393      items that are equal to a string in a list is equal to the number
394      of the items equal to the string in another list.</p></li>
395      </ul></dd>
396    <dt><code id=manakaiLocalName>manakaiLocalName</code>
397    <cite class="bibref normative">[<a href="#ref-MANAKAI">MANAKAI</a>]</cite></dt>
398      <dd><p class=section-info>This entry is applied only to implementations
399      that support this attribute.</p>
400    
401      <p>On getting, the attributes <em class=rfc2119>MUST</em> return
402      <code>null</code>.</p></dd>
403    <dt><code id=lookupNamespaceURI>lookupNamespaceURI</code> and
404    <code id=lookupPrefix>lookupPrefix</code></dt>
405      <dd><p>When invoked, the methods <em class=rfc2119>MUST</em> return
406      <code>null</code>.</p></dd>
407    <dt><code id=nodeName>nodeName</code></dt>
408    <dd>    <dd>
409      <p>A <a href="#round-trip-warning"><code>round-trip-warning</code></a>      <p>If the node is an
410      will be raised when a construct, which might not be restored to the same      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>:
411      construct when it is serialized and then re-parsed by a conforming      On getting, the attribute <em class=rfc2119>MUST</em> return the
412      processor, is encountered.</p>      name of the element type definition represented by the node.</p>
413      <div class="example memo">  
414        <p>For a <code>Comment</code> node a      <p>If the node is an
415        <a href="#round-trip-warning"><code>round-trip-warning</code></a> will      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>:
416        be raised, since <abbr>XML</abbr> processors are not required to      On getting, the attribute <em class=rfc2119>MUST</em> return the
417        report texts of comments for applications.</p>      name of the attribute definition represented by the node.</p>
     </div>  
418    </dd>    </dd>
419  <dt class=ed><dfn id=unknown-error><code>unknown-error</code></dfn>?</dt>  <dt><code id=nodeType>nodeType</code></dt>
   <dd class=ed>@@</dd>  
 <dt><dfn id=xml-misc-error><code>xml-misc-error</code></dt>  
   <dd>An <abbr>XML</abbr> <i>error</i> (<abbr>XML</abbr> 1.0  
   <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>  
   <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-error">error</a> /  
   <abbr>XML</abbr> 1.1  
   <cite class="bibref normative">[<a href="#ref-XML11">XML11</a>]</cite>  
   <a href="@@/#dt-error">error</a>)  
   that is not classified to any other <a href="#error-category">error  
   category</a>.</dd>  
 <dt><dfn id=xml-misc-fatal-error><code>xml-misc-fatal-error</code></dt>  
   <dd>An <abbr>XML</abbr> <i>fatal error</i> (<abbr>XML</abbr> 1.0  
   <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>  
   <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-fatal">fatal  
   error</a> / <abbr>XML</abbr> 1.1  
   <cite class="bibref normative">[<a href="#ref-XML11">XML11</a>]</cite>  
   <a href="@@/#dt-fatal">fatal error</a>)  
   that is not classified to any other <a href="#error-category">error  
   category</a>. <span class=ed>@@ What errors fall into this category?</span></dd>  
 <dt><dfn id=xml-misc-recommendation><code>xml-misc-recommendation</code></dfn></dt>  
420    <dd>    <dd>
421      <p>An      <p>On getting, the attribute <!--<em class=rfc2119>MUST</em>--> returns
422      <a href="#xml-misc-recommendation"><code>xml-misc-recommendation</code></a>      <!-- NOTE: No MUST, to avoid circular reference (nodeType==8100[12]
423      will be raised if a <em class=rfc2119>SHOULD</em>$B!>(Blevel requirement      is defined that they MUST implement ElementType|AttributeDefinition). -->
424      in <abbr>XML</abbr> specification is not met.</p>      <a href="#ELEMENT_TYPE_DEFINITION_NODE"><code>ELEMENT_TYPE_DEFINITION_NODE</code></a>
425        (if the node is an
426        <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>) or
427        <a href="#ATTRIBUTE_DEFINITION_NODE"><code>ATTRIBUTE_DEFINITION_NODE</code></a>
428        (if the node is an
429        <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>).</p>
430    
431        <!-- NodeType -->
432    <p>Two constants are added to the <code id=NodeType>NodeType</code>
433    definition group of the <a href="#Node"><code>Node</code></a> interface as
434    following:</p>
435    <table>
436    <thead>
437    <tr><th scope=col>Name<th scope=col>Value<th scope=col>Description</tr>
438    </thead>
439    <tbody>
440    <tr>
441    <th scope=row><dfn id=ELEMENT_TYPE_DEFINITION_NODE class=dom-const><code>ELEMENT_TYPE_DEFINITION_NODE</code></dfn>
442    <td><code>81001</code><td>The node is an
443    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>.</tr>
444    <tr>
445    <th scope=row><dfn id=ATTRIBUTE_DEFINITION_NODE class=dom-const><code>ATTRIBUTE_DEFINITION_NODE</code></dfn>
446    <td><code>81002</code><td>The node is an
447    <a href="#ElementTypeDefinition"><code>AttributeDefinition</code></a>.</tr>
448    </tbody>
449    </table>
450    </dd>    </dd>
451  <dt><dfn id=xml-validity-error><code>xml-validity-error</code></dfn></dt>  <dt><code id=nodeValue>nodeValue</code> and
452    <dd>A violation of validity constraint in XML document.</dd>  <code id=textContent>textContent</code></dt>
453  <dt><dfn id=xml-well-formedness-error><code>xml-well-formedness-error</code></dfn></dt>    <dd>
454    <dd><p>If an <code>xml-well-formedness-error</code> is raised,      <p>If the node is an
455    it would not be possible to generate an XML serialization that      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>:
456    would match to the appropriate production rule and that would not      On getting, the attributes <em class=rfc2119>MUST</em> return
457    violate to any well$B!>(Bformedness constraint in XML      <code>null</code>.</p>
458    specification <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,  
459    <a href="#ref-XML11">XML11</a>]</cite>.</p></dd>    <div class="note memo">
460      <p>Thus, on setting the attributes does nothing
461      <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
462      </div>
463    
464      <p>If the node is an
465      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>:
466      The attribute <em class=rfc2119>MUST</em> behave as if the node
467      were <code>Attr</code>
468      <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p></dd>
469    <dt><code id=normalize>normalize</code></dt>
470      <dd><p>When a <a href="#DocumentType"><code>DocumentType</code></a> is
471      normalized, any nodes in the <code>NamedNodeMap</code> object in the
472      <a href="#elementTypes"><code>elementTypes</code></a> attribute
473      <em class=rfc2119>MUST</em> be normalized as well.</p>
474    
475      <p>When an
476      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
477      is normalized, any nodes in the <code>NamedNodeMap</code> object in the
478      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
479      attribute <em class=rfc2119>MUST</em> be normalized as well.</p></dd>
480  </dl>  </dl>
481    
 <div class=ed><p>@@ TODO: #dt-atuseroption at user option  
 (MAY or MUST), #dt-compat for compatibility,  
 #dt-interop for interoperability</p></div>  
   
482  </div>  </div>
483    
484  <div class=section id=parsing-xml>  <div class=section id=section-document>
485  <h2>Parsing <abbr>XML</abbr> Document</h2>  <h3>Modifications to the <code id=Document>Document</code> Interface</h3>
   
 <ul>  
 <li>If the <abbr>XML</abbr> document does not begin with an  
 <abbr>XML</abbr> declaration, then raise an  
 <a href="#xml-misc-recommentation" id=xmr-xml-decl><code>xml-misc-recommendation</code></a>.</li>  
 <li>If the replacement text of an entity declaration is  
 <code>&lt;</code>, then raise an  
 <a href="#xml-misc-warning" id=xmw-entity-value-lt><code>xml-misc-warning</code></a>.<!--  
 "strongly advised to avoid" in a Note in Section 2.3 of [XML10], [XML11].  
 --></li>  
 <li>If there is an element type declaration whose <code>Name</code>  
 value is already declared, then raise an  
 <a href="#xml-validity-error" id=vc-edunique><code>xml-validity-error</code></a>.</li>  
 <li>If attribute definition whose <code>Name</code> is  
 <code>xml:space</code> has <span class=ed>declared type different from  
 (default|preserve), (default), or (preserve)</span>, then raise an  
 <a href="#xml-misc-error" id=xme-ad-xml-space><code>xml-misc-error</code></a>.  
 <span class=ed>@@ duplication with  
 <a href="#xml-at-xml-space">#xml-at-xml-space</a>.<!--  
 <!ATTLIST e xml:space CDATA #IMPLIED xml:space CDATA #IMPLIED> --></span></li>  
 <li>If an empty-element tag is used for an element which is <em>not</em>  
 declared <code>EMPTY</code>, then raise an  
 <a href="#xml-misc-recommentation" id=xmr-emptyelemtag-not-empty><code>xml-misc-recommendation</code></a>.</li>  
 <li>If an empty-element tag is <em>not</em> used for an element which is  
 declared <code>EMPTY</code>, then raise an  
 <a href="#xml-misc-recommentation" id=xmr-empty-not-emptyelemtag><code>xml-misc-recommendation</code></a>.</li>  
 <!--  
   
 #vc-PEinMarkupDecl Validity constraint: Proper Declaration/PE Nesting  
 #wfc-PEinInternalSubset Well-formedness constraint: PEs in Internal Subset  
 #ExtSubset Well-formedness constraint: External Subset  
 #PE-between-Decls Well-formedness constraint: PE Between Declarations  
 #GIMatch Well-formedness constraint: Element Type Match  
 #uniqattspec Well-formedness constraint: Unique Att Spec  
 #NoExternalRefs Well-formedness constraint: No External Entity References  
 #CleanAttrVals Well-formedness constraint: No < in Attribute Values  
 #vc-PEinGroup Validity constraint: Proper Group/PE Nesting  
 "For interoperability, if a parameter-entity reference appears in a choice, seq, or Mixed construct, its replacement text SHOULD contain at least one non-blank character, and neither the first nor last non-blank character of the replacement text SHOULD be a connector (| or ,)."  
 "For interoperability, an XML processor MAY at user option issue a warning when more than one attribute-list declaration is provided for a given element type, or more than one attribute definition is provided for a given attribute, but this is not an error."  
 #condsec-nesting Validity constraint: Proper Conditional Section/PE Nesting  
 #wf-Legalchar Well-formedness constraint: Legal Character  
 #textent Well-formedness constraint: Parsed Entity  
 #norecursion Well-formedness constraint: No Recursion  
 #indtd Well-formedness constraint: In DTD  
 "External parsed entities SHOULD each begin with a text declaration."  
 "It is an error for a reference to an unparsed entity to appear in the EntityValue in an entity declaration."  
 #UniqueNotationName Validity constraint: Unique Notation Name  
   
 @@ Need detailed review, but maybe should be in parsing phase  
   
 #vc-check-rmd Validity constraint: Standalone Document Declaration  
   
 @@ Need dtailed review  
   
 #wf-entdeclared Well-formedness constraint: Entity Declared  
 #vc-entdeclared Validity constraint: Entity Declared  
 "For interoperability, valid documents SHOULD declare the entities amp, lt, gt, apos, quot, in the form specified in 4.6 Predefined Entities."  
 "If the entities lt or amp are declared, they MUST be declared as internal entities whose replacement text is a character reference to the respective character (less-than sign or ampersand) being escaped; the double escaping is REQUIRED for these entities so that references to them produce a well-formed result. If the entities gt, apos, or quot are declared, they MUST be declared as internal entities whose replacement text is the single character being escaped (or a character reference to that character; the double escaping here is OPTIONAL but harmless)."  
   
 @@ flaged and then reported in DOM check phase  
   
 "Entities encoded in UTF-16 MUST and entities encoded in UTF-8 MAY begin with the Byte Order Mark"  
 "In the absence of external character encoding information (such as MIME headers), parsed entities which are stored in an encoding other than UTF-8 or UTF-16 MUST begin with a text declaration"  
 "In an encoding declaration, the values "UTF-8", "UTF-16", "ISO-10646-UCS-2", and "ISO-10646-UCS-4" SHOULD be used for the various encodings and transformations of Unicode / ISO/IEC 10646, the values "ISO-8859-1", "ISO-8859-2", ... "ISO-8859-n" (where n is the part number) SHOULD be used for the parts of ISO 8859, and the values "ISO-2022-JP", "Shift_JIS", and "EUC-JP" SHOULD be used for the various encoded forms of JIS X-0208-1997. It is RECOMMENDED that character encodings registered (as charsets) with the Internet Assigned Numbers Authority [IANA-CHARSETS], other than those just listed, be referred to using their registered names; other encodings SHOULD use names starting with an "x-" prefix."  
   
 @@ in parsing phase  
   
 "It is a fatal error when an XML processor encounters an entity with an encoding that it is unable to process. It is a fatal error if an XML entity is determined (via default, encoding declaration, or higher-level protocol) to be in a certain encoding but contains byte sequences that are not legal in that encoding."  
486    
487    <!--
488    <p>If an attempt is made to adopt an
489    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> or
490    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node,
491    the <code id=adoptNode>adoptNode</code> method <em class=rfc2119>MUST</em>
492    raise a <code>NOT_SUPPORTED_ERR</code> exception <span class=ed>@@
493    ref</span>.</p>
494  -->  -->
 </ul>  
 </div>  
495    
496  <div class="section" id=checking-dom>  <div class=ed>
497  <h2>Checking <abbr>DOM</abbr></h2>  <p>Future version of the specification is expected to define what should
498    be done if <code>adoptNode</code> or <code>importNode</code> method have to
499  <p>The following algorithms and definitions are applied to  adopt or import an
500  <abbr>XML</abbr> documents; especially, they are not applied  <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> or
501  to <abbr>HTML</abbr> documents.<!-- TODO: ref to HTML5 --></p>  <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node.
502    In addition it might revise behavior of those methods for
503  <div class=section id=definitions>  <a href="#Entity"><code>Entity</code></a>,
504  <h3>Definitions</h3>  <a href="#Notation"><code>Notation</code></a>, and/or
505    <a href="#DocumentType"><code>DocumentType</code></a> nodes.
506  <p>The <dfn id=xml-version><abbr>XML</abbr> version</dfn> of a node is  Behavior of <code>normalizeDocument</code> method for these kinds of
507  the <abbr>XML</abbr> version of the document to which the node belongs.  nodes might also be defined in some day.</p>
508  For a <code>Documemt</code> node, the <abbr>XML</abbr> version  </div>
 of the document is the value of the <code>xmlVersion</code>  
 attribute of the node.  For a <code>DocumentType</code> node whose  
 <code>ownerDocument</code> attribute is set to <code>null</code>,  
 the <abbr>XML</abbr> version of the document is <code>1.0</code><!--  
 since createDocumentType [DOM3CORE] assumes XML 1.0 [XML10TE] -->.  
 For any other node, the <abbr>XML</abbr> version of the document  
 is that of the <code>Document</code> node contained in the  
 <code>ownerDocument</code> attribute of the node.</p>  
   
 </div>  
   
   
 <div class=section id=checking-components>  
 <h3>Conformance Checking Algorithms for Components</h3>  
   
 <p>To  
 <dfn id=algorithm-to-validate-an-xml-character-data title="validate an XML string">to  
 validate an <abbr>XML</abbr> string (<dfn id=var-s><var>s</var></dfn>)</dfn>,  
 the following algorithm <em class=rfc2119>MUST</em> be used:</p>  
 <ol>  
 <li>If <var>s</var> contains a character that is <em>not</em> in  
 the character class <a href="#class-Char10"><code>Char10</code></a>,  
 then raise an  
 <a href="#xml-well-formedness-error" id=wfe-illegal-char><code>xml-well-formedness-error</code></a>.</li>  
 <li>If <var>s</var> contains a character that is in the character  
 class <a href="#class-CompatChar10"><code>CompatChar10</code></a>,  
 then raise an  
 <a href="#xml-misc-warning" id=xmw-compat-char><code>xml-misc-warning</code></a>.</li>  
 <li>If <var>s</var> contains a character that is in the character  
 class <a href="#class-ControlChar10"><code>ControlChar10</code></a>,  
 then raise an  
 <a href="#xml-misc-warning" id=xmw-control-char><code>xml-misc-warning</code></a>.</li>  
 <li class=ed>@@ XML 1.1 support</li>  
 <li>If <var>s</var> contains a <code class=char>U+000D</code>  
 <code class=charname>CARRIAGE RETURN</code> character, then  
 raise a  
 <a href="#round-trip-error" id=rte-cr><code>round-trip-error</code></a>.  
 <span class=ed>@@ We should not raise duplicate errors for U+000D  
 in attribute values.  In addition, we should support a mode where  
 U+000D will be serialized as &#x000D; (so that no round-trip-error  
 will be raised).</span></li>  
 </ol>  
   
 <p>To  
 <dfn id=algorithm-to-validate-a-name title="validate a Name">validate a  
 <code>Name</code> (<dfn id=var-name-s><var>s</var></dfn>)</dfn>, the following  
 algorithm <em class=rfc2119>MUST</em> be used:</p>  
 <ol>  
 <li>If <var>s</var> is an empty string, then raise an  
 <a href="#xml-well-formedness-error" id=wfe-name-empty><code>xml-well-formedness-error</code></a>.  
 Abort these steps.</li>  
 <li><a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML string">Validate  
 <var>s</var> as an <abbr>XML</abbr> string</a>.</li>  
 <li>If the first character in <var>s</var> is a character that is  
 <em>not</em> in the character class  
 <a href="#class-NameStartChar10"><code>NameStartChar10</code></a>, then raise  
 an  
 <a href="#xml-well-formedness-error" id=wfe-name-startchar><code>xml-well-formedness-error</code></a>.</li>  
 <li>If a character other than the first character in <var>s</var> is a  
 character that is <em>not</em> in the character class  
 <a href="#class-NameChar10"><code>NameChar10</code></a>, then raise an  
 <a href="#xml-well-formedness-error" id=wfe-name-char><code>xml-well-formedness-error</code></a>.</li>  
 <li>If <var>s</var> begins with the string <code>xml</code> (in any  
 case combination), then raise an  
 <a href="#xml-misc-warning" id=xmw-reserved-name><code>xml-misc-warning</code></a>.  
 <span class=ed>@@ except for attribute names <code>xml:lang</code>,  
 <code>xml:space</code>, <code>xml:base</code>, <code>xml:id</code>,  
 <code>xmlns</code>, <code>xmlns:<var>*</var></code>,  
 pi name <code>xml-stylesheet</code>.</span><!--  
 "names beginning with a match to (('X'|'x')('M'|'m')('L'|'l')) are reserved for standardization in this or future versions of this specification.":  
 xmlns, xml-stylesheet, xml:base and xml:id specifications violate to this sentense!  
 --></li>  
 <!-- COLON in Name is a lowercase "should not" in a Note of [XML10],  
 [XML11]. -->  
 <li class=ed>@@ XML 1.1 support</li>  
 </ol>  
   
 <p>To  
 <dfn id=algorithm-to-validate-an-ncname title="validate an NCName">validate  
 an <code>NCName</code> (<dfn id=var-ncname-s><var>s</var></dfn>)</dfn>, the  
 following algorithm <em class=rfc2119>MUST</em> be used:</p>  
 <ol>  
 <li><a href="#algorithm-to-validate-a-name" title="validate a Name">Validate  
 <var>s</var> as a <code>Name</code></a>.</li>  
 <li class=ed>@@</li>  
 </ol>  
   
 <p>To  
 <dfn id=algorithm-to-validate-a-public-identifier title="validate a public identifier">validate  
 a public identifier (<dfn id=var-pid><var>pid</var></dfn>)</dfn>, the  
 following algorithm <em class=rfc2119>MUST</em> be used:</p>  
 <ol>  
 <li>If <var>pid</var> is <code>null</code>, abort these steps.</li>  
 <li>If <var>pid</var> contains a character that is <em>not</em> in the  
 character class <a href="#class-PubidChar"><code>PubidChar</code></a>, then  
 raise an  
 <a href="#xml-well-formedness-error" id=wfe-pubid-char><code>xml-well-formedness-error</code></a>.</li>  
   <li>If <var>pid</var> contains one of <code class=char>U+0009</code>  
   <code class=charname>CHARACTER TABULATION</code>,  
   <code class=char>U+000A</code> <code class=charname>CARRIAGE RETURN</code>,  
   and <code class=char>U+000D</code> <code class=charname>LINE FEED</code>  
   characters, if the first character of <var>pid</var> is  
   <code class=char>U+0020</code> <code class=charname>SPACE</code> character,  
   if the last character of <var>pid</var> is <code class=char>U+0020</code>  
   <code class=charname>SPACE</code> character, or if there is a  
   <code class=char>U+0020</code> <code class=charname>SPACE</code> character  
   immediately followed by another <code class=char>U+0020</code>  
   <code class=charname>SPACE</code> character in <var>pid</var>, then it is a  
   <a href="#round-trip-error" id=rte-pubid-space><code>round-trip-error</code></a>.  
   <span class=ed>Is this really a roundtripness problem?  XML spec  
   does only define the way to match public identifiers in fact, no  
   canonical form.</span></li>  
 </ol>  
   
 <p>To  
 <dfn id=algorithm-to-validate-a-system-identifier title="validate a system identifier">validate  
 a system identifier (<dfn id=var-sid><var>sid</var></dfn>)</dfn>, the  
 following algorithm <em class=rfc2119>MUST</em> be used:</p>  
 <ol>  
   <li>If <var>sid</var> is <code>null</code>, abort these steps.</li>  
 <li><a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML string">Validate  
 <var>sid</var> as an <abbr>XML</abbr> string</a>.</li>  
   <li>If <var>sid</var> contains both <code class=char>U+0022</code>  
   <code class=charname>QUOTATION MARK</code> (<code class=char>"</code>) and  
   <code class=char>U+0027</code> <code class=charname>APOSTROPHE</code>  
   (<code class=char>'</code>) characters, raise an  
   <a href="#xml-well-formedness-error" id=wfe-sid-lit><code>xml-well-formedness-error</code></a>.</li>  
   <li>If <var>sid</var> contains at least one <code class=char>U+0023</code>  
   <code class=charname>NUMBER SIGN</code> (<code class=char>#</code>)  
   character, then raise an  
   <a href="#xml-misc-error" id=xme-sid-fragment><code>xml-misc-error</code></a>.</li>  
   <li class=ed>@@ If <var>sid</var> cannot be converted to a URI  
   reference, then raise a fact-level error (xml-misc-warning?).<!--  
   XML 1.0 has no conformance language for system identifier being  
   a URI reference. --></li>  
 </ol>  
509    
510  </div>  </div>
511    
512  <div class=section id=checking-node>  <div class=section id=section-documentxdoctype>
513  <h3>Checking <code>Node</code></h3>  <h3>The <code>DocumentXDoctype</code> Interface</h3>
514    
515  <p>The algorithm <dfn title="to check a node" id=algorithm-to-check-a-node>to  <p>The <a href="#Document"><code>Document</code></a> nodes
516  check a node (<dfn id=var-n><var>n</var></dfn>)</dfn> is defined as  <em class=rfc2119>MUST</em> also implement the
517  following:</p>  <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a> interface.</p>
518  <dl class=switch>  
519  <dt>If <var>n</var> is an <code>Attr</code> node</dt>  <p>An instance of the
520    <dd>  <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a>
521      <ol>  interface <em class=rfc2119>MUST</em> be able to be obtained by using
522      <li><a href="#algorithm-to-validate-an-ncname">Validate the  binding$B!>(Bspecific casting methods on an instance of the
523      <code>localName</code> attribute value as an <code>NCName</code></a>.</li>  <a href="#Document"><code>Document</code></a> interface (if such
524      <li>If the <code>prefix</code> attribute value is different from  casting methods are available) or by using the method <code>getFeature</code>
525      <code>null</code>, then <a href="#algorithm-to-validate-an-ncname">validate  with parameter values
526      the <code>prefix</code> attribute value as an <code>NCName</code></a>.</li>  <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
527      <li>For each node <dfn id=var-attr-nc><var>n<sub><var>c</var></sub></var></dfn> in the  and <a href="#feature-XDoctype-3.0"><code>3.0</code></a> respectively (if the
528      <code>childNodes</code> list of <var>n</var>,  <a href="#Document"><code>Document</code></a> node supports the
529        <ol>  feature <code>Core</code> version <code>3.0</code>
530        <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> a  <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>).</p>
531        <code>Text</code> or <code>EntityReference</code> node, then it is an  
532        <a href="#xml-well-formedness-error" id=wfe-attr-child><code>xml-well-formedness-error</code></a>.</li>  <p>The <a href="#DocumentXDoctype"><code>DocumentXDoctype</code></a> interface
533        <li>Otherwise, if <var>n<sub><var>c</var></sub></var> is an  <em class=rfc2119>MUST</em> be implemented as the following
534        <code>EntityReference</code> node, then it is an  <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
535        <a href="#entity-error" id=ee-attr-er><code>entity-error</code></a>.</li>  <pre class=idl><code>interface <dfn id=DocumentXDoctype><code>DocumentXDoctype</code></dfn> {
536        <li>Otherwise,    DocumentType <a href="#createDocumentTypeDefinition">createDocumentTypeDefinition</a>
537        <a href="#algorithm-to-check-a-node" title="check a node">check      (in DOMString <a href="#createDocumentTypeDefinition-name"><var>name</var></a>)
538        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>      raises (DOMException);
539        </ol></li>    <a href="#ElementTypeDefinition">ElementTypeDefinition</a> <a href="#createElementTypeDefinition">createElementTypeDefinition</a>
540      <li>If <code>nodeName</code> attribute of <var>n</var> is      (in DOMString <a href="#createElementTypeDefinition-name"><var>name</var></a>)
541      <code>xml:space</code> <span class=ed>@@ or {xml namespace}:space ?</span>      raises (DOMException);
542      and <code>value</code> attribute of <var>n</var> is neither    <a href="#AttributeDefinition">AttributeDefinition</a> <a href="#createAttributeDefinition">createAttributeDefinition</a>
543      <code>default</code> nor <code>preserve</code>, then it is an      (in DOMString <a href="#createAttributeDefinition-name"><var>name</var></a>)
544      <a href="#xml-misc-error" id=xme-attr-xml-space><code>xml-misc-error</code></a>.<!--      raises (DOMException);
545      Note that <!ATTLIST e xml:space (default|preserve) "a">...    <a href="#Entity">Entity</a> <a href="#createGeneralEntity">createGeneralEntityDefinition</a>
546      <e xml:space="default"/> is conforming and valid. --></li>      (in DOMString <a href="#createGeneralEntity-name"><var>name</var></a>)
547      <li class=ed>@@ xml:lang value is not a language tag [RFC 3066 or its      raises (DOMException);
548      successor] or an empty string, then xml-misc-warning    <a href="#Notation">Notation</a> <a href="#createNotation">createNotation</a>
549      (a "fact"-level error; not an XML error).</li>      (in DOMString <a href="#createNotation-name"><var>name</var></a>)
550      <li class=ed>@@ <code>specified</code>,      raises (DOMException);
551      <code>manakaiAttributeType</code> (#ValueType Validity constraint: Attribute Value Type)</li>  }</code></pre>
552      <!-- xml:space MUST be declared to be valid. -->  
553      <li>Let <dfn id=var-v><var>v</var></dfn> be the value of the  <dl>
554      attribute <code>value</code> of <var>n</var>.</li>  <dt><dfn id=createDocumentTypeDefinition class=dom-method><code>createDocumentTypeDefinition</code></dfn>,
555      <li>Validate the <var>n</var> against the <span class=ed>declared  method</dt>
     type</span> as following:  
       <dl class=switch>  
       <dt class=ed><code>ID_ATTR</code></dt>  
         <dd>  
           <ol>  
           <li><span class=ed>Validate <var>v</var> as an  
           <code>Name</code>.</span>  If it fails, then raise an  
           <a href="#xml-validity-error" id=vc-id-name><code>xml-validity-error</code></a>.</li>  
           <li><span class=ed>If <code>ID</code> <var>v</var> is defined,</span>  
           then raise an    
           <a href="#xml-validity-error" id=vc-id-duplication><code>xml-validity-error</code></a>.</li>  
           </ol>  
         </dd>  
       <dt class=ed>IDREF_ATTR</dt>  
         <dd>  
           <ol>  
           <li><span class=ed>Validate <var>v</var> as an  
           <code>Name</code>.</span>  If it fails, then raise an  
           <a href="#xml-validity-error" id=vc-idref-name><code>xml-validity-error</code></a>.</li>  
           <li><span class=ed>If <code>ID</code> <var>v</var> is NOT  
           defined,</span> then raise an    
           <a href="#xml-validity-error" id=vc-idref-match><code>xml-validity-error</code></a>.</li>  
           </ol>  
         </dd>  
       <dt class=ed>IDREFS_ATTR</dt>  
         <dd class=ed>@@</dd>  
       <dt class=ed>ENTITY_ATTR</dt>  
         <dd>  
           <ol>  
           <li><span class=ed>Validate <var>v</var> as an  
           <code>Name</code>.</span>  If it fails, then raise an  
           <a href="#xml-validity-error" id=vc-entname-name><code>xml-validity-error</code></a>.</li>  
           <li><span class=ed>If <code>Entity</code> <var>v</var> is NOT  
           defined,</span> then raise an    
           <a href="#xml-validity-error" id=vc-entname-match><code>xml-validity-error</code></a>.</li>  
           </ol>  
         </dd>  
       <dt class=ed>ENTITIES_ATTR</dt>  
         <dd class=ed>@@</dd>  
       <dt class=ed>NMTOKEN_ATTR</dt>  
         <dd>  
           <ol>  
           <li><span class=ed>Validate <var>v</var> as an  
           <code>Nmtoken</code>.</span>  If it fails, then raise an  
           <a href="#xml-validity-error" id=vc-nmtok-name><code>xml-validity-error</code></a>.</li>  
           </ol>  
         </dd>  
       <dt class=ed>NMTOKENS_ATTR</dt>  
         <dd class=ed>@@</dd>  
       <dt class=ed>NOTATION_ATTR</dt>  
         <dd class=ed><var>v</var> must be one of enumerated values.  
         If not, then raise an  
         <a href="#xml-validity-error" id=vc-notatn-match><code>xml-validity-error</code></a>.</dd>  
       <dt class=ed>ENUMERATED_ATTR</dt>  
         <dd class=ed><var>v</var> must be one of enumerated values.  
         If not, then raise an  
         <a href="#xml-validity-error" id=vc-enum><code>xml-validity-error</code></a>.</dd>  
       <dt class=ed>@@</dt>  
       </dl>  
     </li>  
     <li>If <span class=ed>type ID and default is NOT #IMPLIED or #REQUIRED</span>, then  
     raise an  
     <a href="#xml-validity-error" id=vc-id-default><code>xml-validity-error</code></a>.</li>  
     <li class=ed>@@ #FixedAttr Validity constraint: Fixed Attribute Default</li>  
     <li class=ed>@@ strict serialization error for U+000D, U+000A, and  
     U+0009 characters, leading/trailing U+0020, and U+0020{2,} string?</li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is an <code>AttributeDefinition</code> node</dt>  
   <dd>  
     <ol>  
     <li class=ed></li>  
     <li>If <code>nodeName</code> attribute of <var>n</var> is  
     <code>xml:space</code> <span class=ed>@@ or {xml namespace}:space ?</span>  
     and <span class=ed>its declared type is different from (default|preserve),  
     (default), or (preserve)</span>, then raise an  
     <a href="#xml-misc-error" id=xme-at-xml-space><code>xml-misc-error</code></a>.</li>  
     <li>For each node <dfn id=var-ad-nc><var>n<sub><var>c</var></sub></var></dfn> in the  
     <code>childNodes</code> list of <var>n</var>,  
       <ol>  
       <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> a  
       <code>Text</code> or <code>EntityReference</code> node, then it is an  
       <a href="#xml-well-formedness-error" id=wfe-at-child><code>xml-well-formedness-error</code></a>.</li>  
       <li>Otherwise, if <var>n<sub><var>c</var></sub></var> is an  
       <code>EntityReference</code> node, then it is an  
       <a href="#entity-error" id=ee-at-er><code>entity-error</code></a>.</li>  
       <li>Otherwise,  
       <a href="#algorithm-to-check-a-node" title="check a node">check  
       <var>n<sub><var>c</var></sub></var></a> recusrively.</li>  
       </ol></li>  
     <li class=ed>If <code>NOTATION_ATTR</code>, enumerated values MUST  
     be declared.  If not, then raise an  
     <a href="#xml-validity-error" id=vc-notatn-declared><code>xml-validity-error</code></a>.</li>  
     <li class=ed>If <code>NOTATION_ATTR</code> or <code>ENUMERATED_ATTR</code>,  
     values MUST all be distinct.  If not, then raise an  
     <a href="#xml-validity-error" id=vc-no-duplicate-tokens><code>xml-validity-error</code></a>.</li>  
     <li class=ed>If <code>NOTATION_ATTR</code> on an <code>EMPTY</code>  
     element, then raise an  
     <a href="#xml-validity-error" id=vc-no-notation-empty><code>xml-validity-error</code></a>.</li>  
     <li class=ed>@@ #defattrvalid Validity constraint: Attribute Default Value Syntactically Correct</li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is a <code>CDATASection</code> node</dt>  
   <dd>  
     <ol>  
     <li><a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML string">Validate the  
     <code>data</code> attribute value as an <abbr>XML</abbr> character  
     data</a>.</li>  
     <li>If the <code>data</code> attribute value contains  
     a string <code>]]></code>, then raise an  
     <a href="#xml-well-formedness-error" id=wfe-cs-mse><code>xml-well-formedness-error</code></a>.<!-- "for compatibility" --></li>  
     <li>If the <code>childNodes</code> list of <var>n</var> contains  
     any nodes, they are in  
     <a href="#xml-well-formedness-error" id=wfe-cs-child><code>xml-well-formedness-error</code></a>.</li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is a <code>Comment</code> node</dt>  
   <dd>  
     <ol>  
     <li>Raise an  
     <a href="#round-trip-warning" id=rtw-comment><code>round-trip-warning</code></a>.</li>  
     <li><a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML string">Validate the  
     <code>data</code> attribute value as an <abbr>XML</abbr> character  
     data</a>.</li>  
     <li>If the <code>data</code> attribute value contains  
     a string <code>--</code>, or if it ends with a character  
     <code>-</code>, then raise an  
     <a href="#xml-well-formedness-error" id=wfe-comment-com><code>xml-well-formedness-error</code></a>.<!--  
     "for compatibility" --></li>  
     <li>If the <code>childNodes</code> list of <var>n</var> contains  
     any nodes, they are in  
     <a href="#xml-well-formedness-error" id=wfe-comment-child><code>xml-well-formedness-error</code></a>.</li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is a <code>Document</code> node</dt>  
   <dd>  
     <ol>  
     <li>If <a href="#xml-version"><abbr>XML</abbr> version</a> of <var>n</var>  
     is different from <code>1.0</code> or <code>1.1</code>,  
     then it is an <code class=ed>unknown-error?</code>.</li>  
     <li>If the <code>xmlEncoding</code> attribute value does <em>not</em>  
     match to <code>[A-Za-z] ([A-Za-z0-9._] | '-')*</code>  
     <span class=ed>@@ formal def</span>, then it is an  
     <a href="#xml-well-formedness-error" id=wfe-encoding><code>xml-well-formedness-error</code></a>.</li>  
     <li>The <code>childNodes</code> list of <var>n</var> have to  
     consist of zero or more <code>Comment</code> and/or  
     <code>ProcessingInstruction</code> nodes, followed by  
     an optional <code>DocumentType</code> node, followed  
     by zero or more <code>Comment</code> and/or  
     <code>ProcessingInstruction</code> nodes, followed by  
     an <code>Element</code> node, followed  
     by zero or more <code>Comment</code> and/or  
     <code>ProcessingInstruction</code> nodes.  Any violation to this is an  
     <a href="#xml-well-formedness-error" id=wfe-document-child><code>xml-well-formedness-error</code></a>.</li>  
     <li>For each node <dfn id=var-document-nc><var>n<sub><var>c</var></sub></var></dfn>  
     in the <code>childNodes</code> list of <var>n</var>,  
       <ol>  
       <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> an  
       <code>EntityReference</code> node, then  
       <a href="#algorithm-to-check-a-node" title="check a node">check  
       <var>n<sub><var>c</var></sub></var></a> recursively.</li>  
       </ol></li>  
     <li class=ed>@@ <code>allDeclarationsProcessed</code></li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is a <code>DocumentFragment</code> node</dt>  
   <dd>  
     <ol>  
     <li>For each node <dfn id=var-df-nc><var>n<sub><var>c</var></sub></var></dfn>  
     in the <code>childNodes</code> list of <var>n</var>,  
       <ol>  
       <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> an  
       <code>Element</code>, <code>Text</code>, <code>CDATASection</code>,  
       <code>Comment</code>, <code>ProcessingInstruction</code>, or  
       <code>EntityReference</code> node, then it is an  
       <a href="#xml-well-formedness-error" id=wfe-df-child><code>xml-well-formedness-error</code></a>.</li>  
       <li>Otherwise, if <var>n<sub><var>c</var></sub></var> is an  
       <code>EntityReference</code> node, then it is an  
       <a href="#entity-error" id=ee-df-er><code>entity-error</code></a>.</li>  
       <li>Otherwise,  
       <a href="#algorithm-to-check-a-node" title="check a node">check  
       <var>n<sub><var>c</var></sub></var></a> recursively.</li>  
       </ol></li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is a <code>DocumentType</code> node</dt>  
   <dd>  
     <ol>  
     <li><a href="#algorithm-to-validate-an-ncname">Validate the  
     <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>  
     <li>Follow the following substeps:  
       <ol>  
       <li>If <code>ownerDocument</code> attribute of <var>n</var> is  
       <code>null</code>, then abort these substeps.</li>  
       <li>If <code>documentElement</code> attribute of the node  
       set to <code>ownerDocument</code> attribute of <var>n</var> is  
       <code>null</code>, then abort these substeps.</li>  
       <li>If <code>nodeName</code> attribute of the node set to  
       <code>documentElement</code> attribute of the node set to  
       <code>ownerDocument</code> attribute of <var>n</var> is  
       different from <code>nodeName</code> of <var>n</var>,  
       then raise an  
       <a href="#xml-validity-error" id=vc-roottype><code>xml-validity-error</code></a>.</li></li>  
       </ol>  
     </li>  
     <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate  
     the <code>publicId</code> attribute value as a public identifier</a>.</li>  
     <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate  
     the <code>systemId</code> attribute value as a system identifier</a>.</li>  
     <li>If the <code>publicId</code> attribute value of <var>n</var> is  
     <em>not</em> <code>null</code> and the <code>systemId</code> attribute  
     value of <var>n</var> is <code>null</code>, then raise an  
     <a href="#xml-well-formedness-error" id=wfe-dt-sid><code>xml-well-formedness-error</code></a>.  
     <span class=ed>@@ publicId == null?  Or, publicId == ""</span></li>  
     <li>For each node <dfn id=var-dt-nc><var>n<sub><var>c</var></sub></var></dfn>  
     in the <code>childNodes</code> list of <var>n</var>,  
       <ol>  
       <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> a  
       <code>ProcessingInstruction</code> node, then it is an  
       <a href="#xml-well-formedness-error" id=wfe-dt-child><code>xml-well-formedness-error</code></a>.  
       <span class=ed>@@ ref to manakai's extensions</span></li>  
       <li>Otherwise, <!-- if n_c is not an EntityReference node, -->  
       <a href="#algorithm-to-check-a-node" title="check a node">check  
       <var>n<sub><var>c</var></sub></var></a> recusrively.</li>  
       </ol></li>  
     <li>For each node in the <code>entities</code>, <code>notations</code>,  
     and <code>elementTypes</code> lists of <var>n</var>,  
     <a href="#algorithm-to-check-a-node" title="check a node">check the  
     node</a> recursively.</li>  
     <li class=ed>@@ externally declared?</li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is an <code>Element</code> node</dt>  
   <dd>  
     <ol>  
     <li><a href="#algorithm-to-validate-an-ncname">Validate the  
     <code>localName</code> attribute value as an <code>NCName</code></a>.</li>  
     <li>If the <code>prefix</code> attribute value is different from  
     <code>null</code>, then <a href="#algorithm-to-validate-an-ncname">validate  
     the <code>prefix</code> attribute value as an <code>NCName</code></a>.</li>  
     <li>For each node <dfn id=var-element-nc><var>n<sub><var>c</var></sub></var></dfn>  
     in the <code>childNodes</code> list of <var>n</var>,  
       <ol>  
       <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> an  
       <code>Element</code>,  
       <code>Text</code>, <code>CDATASection</code>, <code>Comment</code>,  
       <code>ProcessingInstruction</code>, or  
       <code>EntityReference</code> node, then it is an  
       <a href="#xml-well-formedness-error" id=wfe-element-child><code>xml-well-formedness-error</code></a>.</li>  
       <li>Otherwise, if <var>n<sub><var>c</var></sub></var> is an  
       <code>EntityReference</code> node, then it is an  
       <a href="#entity-error" id=ee-element-er><code>entity-error</code></a>.</li>  
       <li>Otherwise,  
       <a href="#algorithm-to-check-a-node" title="check a node">check  
       <var>n<sub><var>c</var></sub></var></a> recursively.</li>  
       </ol></li>  
     <li class=ed>@@ #elementvalid Validity constraint: Element Valid</li>  
     <li>Let <var>attrs</var> be the value of the <code>attribute</code>  
     attribute of <var>n</var>.  Check conformance of <var>attrs</var>  
     as following:  
       <ol>  
       <li>If <var>attrs</var> contains an <code>Attr</code> node whose  
       <code>nodeName</code> attribute value is equal to that of another  
       <code>Attr</code> node in <var>attrs</var>, then raise an  
       <a href="#xml-well-formedness-error" id=wfe-uniqattspec><code>xml-well-formedness-error</code></a>.<!--  
       #uniqattspec Well-formedness constraint: Unique Att Spec --></li>  
       <li class=ed>@@ #RequiredAttr Validity constraint: Required Attribute</li>  
       </ol>  
     </li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is an <code>ElementTypeDefinition</code> node</dt>  
   <dd>  
     <ol>  
     <li class=ed></li>  
     <li>If the <code>childNodes</code> list of <var>n</var> contains  
     any nodes, they are in  
     <a href="#xml-well-formedness-error" id=wfe-et-child><code>xml-well-formedness-error</code></a>.</li>  
     <li class=ed>@@ <q cite="http://www.w3.org/TR/2006/REC-xml-20060816/#elemdecls">At user option, an XML processor MAY issue a warning when a declaration mentions an element type for which no declaration is provided, but this is not an error.</q></li>  
     <li class=ed>@@ <q cite="http://www.w3.org/TR/2006/REC-xml-20060816/#sec-element-content">For compatibility, it is an error if the content model allows an element to match more than one occurrence of an element type in the content model. </q></li>  
     <li class=ed>@@ #vc-MixedChildrenUnique  
     Validity constraint: No Duplicate Types</li>  
     <li class=ed>@@ <q cite="http://www.w3.org/TR/2006/REC-xml-20060816/#attdecls">At user option, an XML processor MAY issue a warning if attributes are declared for an element type not itself declared, but this is not an error.</q></li>  
     <li>If there is more than one <code>AttributeDefinition</code> node  
     with <span class=ed>attribute type <code>ID</code></span> in the  
     <code>NamedNodeMap</code> list contained in the  
     <code>attributeDefinitions</code> attribute of <var>n</var>, then raise an  
     <a href="#xml-validity-error" id=vc-one-id-per-el><code>xml-validity-error</code></a>.</li>  
     <li>If there is more than one <code>AttributeDefinition</code> node  
     with <span class=ed>attribute type <code>NOTATION</code></span> in the  
     <code>NamedNodeMap</code> list contained in the  
     <code>attributeDefinitions</code> attribute of <var>n</var>, then raise an  
     <a href="#xml-validity-error" id=vc-one-notation-per><code>xml-validity-error</code></a>.</li>  
     <li class=ed>"For interoperability, the same Nmtoken  SHOULD NOT occur more than once in the enumerated attribute types of a single element type."</li>  
     </ol>  
   </dd>  
 <dt>If <var>n</var> is an <code>Entity</code> node whose  
 <code>notationName</code> attribute value is <code>null</code> (i.e. a  
 parsed entity)</dt>  
556    <dd>    <dd>
557      <ol>      <p>This method creates a <code>DocumentType</code> node with the specified
558      <li>Raise an      name, belonging to the document.</p>
559      <a href="#entity-error" id=ee-entity-node><code>entity-error</code></a>.</li>      <p>The
560      <li><a href="#algorithm-to-validate-an-ncname">Validate the      <dfn id=createDocumentTypeDefinition-name class=dom-param><var>name</var></dfn>
561      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      parameter is the name of the document type.</p>
562      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate  
563      the <code>publicId</code> attribute value as a public identifier</a>.</li>      <p>When invoked, the method <em class=rfc2119>MUST</em> create and
564      <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate      return a <a href="#DocumentType"><code>DocumentType</code></a> node with
565      the <code>systemId</code> attribute value as a system identifier</a>.</li>      the following attributes:</p>
566      <li>If the <code>publicId</code> attribute value of <var>n</var> is      <dl>
567      <em>not</em> <code>null</code> and the <code>systemId</code> attribute      <dt><code>attributes</code>, <code>parentNode</code></dt>
568      value of <var>n</var> is <code>null</code>, then raise an        <dd><code>null</code>.</dd>
569      <a href="#xml-well-formedness-error" id=wfe-entity-sid><code>xml-well-formedness-error</code></a>.</li>      <dt><a href="#elementTypes"><code>elementTypes</code></a>,
570      <li>For each node <dfn id=var-entity-nc><var>n<sub><var>c</var></sub></var></dfn>      <a href="#entities"><code>entities</code></a>, and
571      in the <code>childNodes</code> list of <var>n</var>,      <a href="#notations"><code>notations</code></a></dt>
572        <ol>        <dd>Empty <code>NamedNodeMap</code> objects respectively.</dd>
573        <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> an      <dt><code>childNodes</code></dt>
574        <code>Element</code>,        <dd>An empty <code>NodeList</code> object.</dd>
575        <code>Text</code>, <code>CDATASection</code>, <code>Comment</code>,      <dt><a href="#internalSubset"><code>internalSubset</code></a>,
576        <code>ProcessingInstruction</code>, or <code>EntityReference</code>      <a href="#publicId"><code>publicId</code></a>, and
577        node, then it is an      <a href="#systemId"><code>systemId</code></a></dt>
578        <a href="#xml-well-formedness-error" id=wfe-entity-child><code>xml-well-formedness-error</code></a>.</li>        <dd>Empty strings.</dd>
579        <li>Otherwise, if <var>n<sub><var>c</var></sub></var> is an      <dt><code>nodeName</code></dt>
580        <code>EntityReference</code> node, then it is an        <dd><a href="#createDocumentTypeDefinition-name"><var>name</var></a>.</dd>
581        <a href="#entity-error" id=ee-er-er><code>entity-error</code></a>.</li>      <dt><code>ownerDocument</code></dt>
582        <li>Otherwise,        <dd>The <a href="#Document"><code>Document</code></a> node over which the
583        <a href="#algorithm-to-check-a-node" title="check a node">check        method is invoked.</dd>
584        <var>n<sub><var>c</var></sub></var></a> recursively.</li>      </dl>
585        </ol></li>      <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
586      </ol>      <a href="#read-only">read$B!>(Bonly</a>.</p>
587        <p>In addition, the method <em class=rfc2119>MUST</em> be marked as
588        containing five general entity declarations: <code>amp</code>,
589        <code>lt</code>, <code>gt</code>, <code>quot</code>, and
590        <code>apos</code>.</p>
591    </dd>    </dd>
592  <dt>If <var>n</var> is an <code>Entity</code> node whose  <dt><dfn id=createElementTypeDefinition class=dom-method><code>createElementTypeDefinition</code></dfn>,
593  <code>notationName</code> attribute value is <em>not</em> <code>null</code>  method</dt>
 (i.e. an unparsed entity)</dt>  
594    <dd>    <dd>
595      <ol>      <p>This method creates a <code>ElementTypeDefinition</code> node with the
596      <li><a href="#algorithm-to-validate-an-ncname">Validate the      specified name, belonging to the document.</p>
597      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      <p>The <dfn id=createElementTypeDefinition-name class=dom-param><var>name</var></dfn>
598      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate      parameter is the name of the element type defined by the element
599      the <code>publicId</code> attribute value as a public identifier</a>.</li>      type definition.</p>
600      <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate  
601      the <code>systemId</code> attribute value as a system identifier</a>.</li>      <p>When invoked, the method <em class=rfc2119>MUST</em> create and
602      <li>If the <code>systemId</code> attribute value of <var>n</var> is      return an
603      <code>null</code>, then raise an      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
604      <a href="#xml-well-formedness-error" id=wfe-uentity-sid><code>xml-well-formedness-error</code></a>.</li>      node with the following attributes:</p>
605      <li><a href="#algorithm-to-validate-an-ncname">Validate the      <dl>
606      <code>notationName</code> attribute value of <var>n</var> as an      <dt><a href="#attributeDefinitions"><code>attributeDefinitions</code></a></dt>
607      <code>NCName</code></a>.</li>        <dd>An empty <code>NamedNodeMap</code> object.</dd>
608      <li class=ed>@@ #not-declared Validity constraint: Notation Declared</li>      <dt><code>childNodes</code></dt>
609      <li>If the <code>childNodes</code> list of <var>n</var> contains        <dd>An empty <code>NodeList</code> object.</dd>
610      any nodes, they are in      <dt><a href="#nodeName"><code>nodeName</code></a></dt>
611      <a href="#xml-well-formedness-error" id=wfe-uentity-child><code>xml-well-formedness-error</code></a>.</li>        <dd><a href="#createElementTypeDefinition-name"><var>name</var></a>.</dd>
612      </ol>      <dt><code>ownerDocument</code></dt>
613          <dd>The <code>Document</code> node over which the method is invoked.</dd>
614        <dt><a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
615        and <code>parentNode</code></dt>
616          <dd><code>null</code>.</dd>
617        </dl>
618        <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
619        <a href="#read-only">read$B!>(Bonly</a>.</p>
620    </dd>    </dd>
621  <dt>If <var>n</var> is an <code>EntityReference</code> node</dt>  <dt><dfn id=createAttributeDefinition class=dom-method><code>createAttributeDefinition</code></dfn>,
622    method</dt>
623    <dd>    <dd>
624      <ol>      <p>This method creates a <code>AttributeDefinition</code> node with the
625      <li>An <a href="#entity-error" id=ee-er-node><code>entity-error</code></a>.</li>      specified name, belonging to the document.</p>
626      <li><a href="#algorithm-to-validate-an-ncname">Validate the      <p>The <dfn id=createAttributeDefinition-name class=dom-param><var>name</var></dfn>
627      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      parameter is the name of the attribute defined by the attribute
628      <li>For each node <dfn id=var-er-nc><var>n<sub><var>c</var></sub></var></dfn>      definition.</p>
629      in the <code>childNodes</code> list of <var>n</var>,  
630        <ol>      <p>When invoked, the method <em class=rfc2119>MUST</em> create and
631        <li>If <var>n<sub><var>c</var></sub></var> is <em>not</em> an      return an
632        <code>Element</code>,      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
633        <code>Text</code>, <code>CDATASection</code>, <code>Comment</code>,      node with the following attributes:</p>
634        <code>ProcessingInstruction</code>, or <code>EntityReference</code>      <dl>
635        node, then it is an      <dt><a href="#allowedTokens"><code>allowedTokens</code></a></dt>
636        <a href="#xml-well-formedness-error" id=wfe-er-child><code>xml-well-formedness-error</code></a>.</li>        <dd>An empty <code>DOMStringList</code> object.</dd>
637        <li>Otherwise, if <var>n<sub><var>c</var></sub></var> is <em>not</em> an      <dt><code>childNodes</code></dt>
638        <code>EntityReference</code> node, then it is an        <dd>An empty <code>NodeList</code> object.</dd>
639        <a href="#entity-error" id=ee-entity-er><code>entity-error</code></a>.</li>      <dt><a href="#declaredType"><code>declaredType</code></a></dt>
640        <li>Otherwise,        <dd><a href="#NO_TYPE_ATTR"><code>NO_TYPE_ATTR</code></a>.</dd>
641        <a href="#algorithm-to-check-a-node" title="check a node">check      <dt><a href="#defaultType"><code>defaultType</code></a></dt>
642        <var>n<sub><var>c</var></sub></var></a> recursively.</li>        <dd><a href="#UNKNOWN_DEFAULT"><code>UNKNOWN_DEFAULT</code></a>.</dd>
643        </ol></li>      <dt><a href="#nodeName"><code>nodeName</code></a></dt>
644      </ol>        <dd><a href="#createAttributeDefinition-name"><var>name</var></a>.</dd>
645        <dt><code>ownerDocument</code></dt>
646          <dd>The <code>Document</code> node over which the method is invoked.</dd>
647        <dt><a href="#ownerElementTypeDefinition"><code>ownerElementTypeDefinition</code></a>
648        and <code>parentNode</code></dt>
649          <dd><code>null</code>.</dd>
650        </dl>
651        <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
652        <a href="#read-only">read$B!>(Bonly</a>.</p>
653    
654        <!-- This requirement, if not droped, should be part of xml-id spec.
655        <div class=ed>
656        <p>@@ Should we keep these statements?:
657    However, if the &lt;cfg::cfg|xml-id> configuration
658    parameter is set to <code>true</code> and the <var>name</var>
659    is <code>xml:id</code>, then the [CODE(DOMa)@en[[[declaredType]]]]
660    attribute is set to <code>ID_ATTR</code>.
661    [CODE(DOMa)@en[[[defaultType]]]]?</p>
662        </div>-->
663    </dd>    </dd>
664  <dt>If <var>n</var> is a <code>Notation</code> node</dt>  <dt><dfn id=createGeneralEntity class=dom-method><code>createGeneralEntity</code></dfn>,
665    method</dt>
666    <dd>    <dd>
667      <ol>      <p>This method creates a <a href="#Entity"><code>Entity</code></a> node
668      <li><a href="#algorithm-to-validate-an-ncname">Validate the      with the specified name, which represents a general entity, belonging to
669      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      the document.</p>
670      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate      <p>The <dfn id=createGeneralEntity-name class=dom-param><var>name</var></dfn>
671      the <code>publicId</code> attribute value as a public identifier</a>.</li>      parameter is the name of the general entity.</p>
672      <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate  
673      the <code>systemId</code> attribute value as a system identifier</a>.</li>      <p>When invoked, the method <em class=rfc2119>MUST</em> create and return
674      <li>If the <code>childNodes</code> list of <var>n</var> contains      an <a href="#Entity"><code>Entity</code></a> node with the following
675      any nodes, they are in      attributes:</p>
676      <a href="#xml-well-formedness-error" id=wfe-notation-child><code>xml-well-formedness-error</code></a>.</li>      <dl>
677      </ol>      <dt><code>childNodes</code></dt>
678    </dd>        <dd>An empty <code>NodeList</code> object.</dd>
679  <dt>If <var>n</var> is a <code>ProcessingInstruction</code> node</dt>      <dt><code>manakaiDeclarationBaseURI</code>,
680        <code>manakaiEntityBaseURI</code>, and <code>manakaiEntityURI</code>
681        <cite class="bibref normative">[<a href="#ref-MANAKAI">MANAKAI</a>]</cite></dt>
682          <dd><p class=section-info>This entry is applied only to implementations
683          that support these attributes.</p>
684    
685          <p>No explicit value is set.</p></dd>
686        <dt><a href="#hasReplacementTree"><code>hasReplacementTree</code></a> and
687        <a href="#isExternallyDeclared"><code>isExternallyDeclared</code></a></dt>
688          <dd><p><code>false</code>.</p></dd>
689        <dt><code>nodeName</code></dt>
690          <dd><a href="#createGeneralEntity-name"><var>name</var></a>.</dd>
691          <dd>
692            <div class="note memo">
693              <p>It is not an error for
694              <a href="#createGeneralEntity-name"><var>name</var></a> matching
695              to the name of one of predefined general parsed entities in
696              <abbr>XML</abbr> or <abbr>HTML</abbr>.  For example,
697              <a href="#createGeneralEntity-name"><var>name</var></a> might be
698              <code>amp</code>, resulting in an
699              <a href="#Entity"><code>Entity</code></a> node
700              with its <code>nodeName</code> attribute set to <code>amp</code>.</p>
701            </div>
702          </dd>
703        <dt><a href="#notationName"><code>notationName</code></a>,
704        <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>,
705        and <code>parentNode</code></dt>
706          <dd><code>null</code>.</dd>
707        <dt><code>ownerDocument</code></dt>
708          <dd>The <code>Document</code> node over which the method is invoked.</dd>
709        <dt><a href="#publicId"><code>publicId</code></a> and
710        <a href="#systemId"><code>systemId</code></a></dt>
711          <dd><code>null</code>.</dd>
712          <dd class=ed>@@ publicId and systemId should be empty string?</dd>
713        </dl>
714      <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
715      <a href="#read-only">read$B!>(Bonly</a>.</p></dd>
716    <dt><dfn id=createNotation class=dom-method><code>createNotation</code></dfn>,
717    method</dt>
718    <dd>    <dd>
719      <ol>      <p>This method creates a <code>Notation</code> node with the
720      <li>If the <code>target</code> attribute value matches to the string      specified name, belonging to the document.</p>
721      <code>xml</code> in any case combination, then raise a      <p>The <dfn id=createNotation-name class=dom-param><var>name</var></dfn>
722      <a href="#xml-well-formedness-error" id=wfe-pi-xml><code>xml-well-formedness-error</code></a>.</li>      parameter is the name of the notation.</p>
723      <li>Otherwise, <a href="#algorithm-to-validate-an-ncname">validate the  
724      <code>target</code> attribute value as an <code>NCName</code></a>.</li>      <p>When invoked, the method <em class=rfc2119>MUST</em> create and return
725      <li>Then,      a <code>Notation</code> node with the following attributes:</p>
726      <a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML string">validate      <dl>
727      the <code>data</code> attribute value as an <abbr>XML</abbr> character      <dt><code>childNodes</code></dt>
728      data</a>.</li>        <dd>An empty <code>NodeList</code> object.</dd>
729      <li>If the <code>data</code> attribute value contains a string      <dt><code>manakaiDeclarationBaseURI</code>
730      <code>?></code>, then raise a      <cite class="bibref normative">[<a href="#ref-MANAKAI">MANAKAI</a>]</cite></dt>
731      <a href="#xml-well-formedness-error" id=wfe-pi-pic><code>xml-well-formedness-error</code></a>.</li>        <dd><p class=section-info>This entry is applied only to implementations
732      <li>If the <code>data</code> attribute value starts with either        that support these attributes.</p>
733      <code class=char>U+0009</code> <code class=charname>CHARACTER  
734      TABULATION</code>, <code class=char>U+000A</code> <code class=charname>LINE        <p>No explicit value is set.</p></dd>
735      FEED</code>, <code class=char>U+000D</code> <code class=charname>CARRIAGE      <dt><code>nodeName</code></dt>
736      RETURN</code>, or <code class=char>U+0020</code>        <dd><a href="#createNotation-name"><var>name</var></a>.</dd>
737      <code class=charname>SPACE</code> character, then raise a      <dt><code>ownerDocument</code></dt>
738      <a href="#round-trip-error" id=rte-pi-s><code>round-trip-error</code></a>.</li>        <dd><p>The <a href="#Document"><code>Document</code></a> node over which
739      <li>If the <code>childNodes</code> list of <var>n</var> contains        the method is invoked.</p></dd>
740      any nodes, then raise an      <dt><a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
741      <a href="#xml-well-formedness-error" id=wfe-pi-child><code>xml-well-formedness-error</code></a>.</li>      and <code>parentNode</code></dt>
742      </ol>        <dd><code>null</code>.</dd>
743    </dd>      <dt><a href="#publicId"><code>publicId</code></a> and
744  <dt>If <var>n</var> is a <code>Text</code> node</dt>      <a href="#systemId"><code>systemId</code></a></dt>
745    <dd>        <dd><code>null</code>.</dd>
746      <ol>        <dd class=ed>@@ publicId and systemId should be empty string?</dd>
747      <li><a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML string">Validate the      </dl>
748      <code>data</code> attribute value as an <abbr>XML</abbr> character    <p>The returned node <em class=rfc2119>MUST NOT</em> be marked as
749      data</a>.</li>    <a href="#read-only">read$B!>(Bonly</a>.</p></dd>
     <li>If the <code>childNodes</code> list of <var>n</var> contains  
     any nodes, they are in  
     <a href="#xml-well-formedness-error" id=wfe-text-child><code>xml-well-formedness-error</code></a>.</li>  
     </ol>  
   </dd>  
 <dt>Otherwise</dt>  
   <dd><span class=ed>xml-well-formedness-error?  unknown-error?</span></dd>  
750  </dl>  </dl>
751    
752    <p>These methods <em class=rfc2119>MUST</em> raise an
753    <code>INVALID_CHARACTER_ERR</code> if <var>name</var> is <em>not</em> a legal
754    <code>Name</code>
755    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
756    <a href="#ref-XML11">XML11</a>]</cite> according to the <abbr>XML</abbr>
757    version specified in the <code>xmlVersion</code> attribute of the
758    <a href="#Document"><code>Document</code></a> node.</p>
759    
760    <div class="note memo">
761    <p>Non$B!>(B<abbr>XML</abbr> case is intentionally left unspecified for now,
762    since <abbr>DOM</abbr> Level 3 Core specification
763    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>
764    does not define it for <a href="#Document"><code>Document</code></a>
765    methods.</p>
766    
767    <p><var>name</var> does not have to be a namespace qualified name.</p>
768  </div>  </div>
769    
770  </div>  </div>
771    
 <div id=classes class=section>  
 <h2>Character Classes</h2>  
772    
773  <p>This section defines a couple of character classes.  <div class=section id=section-documenttype>
774  These classes are referred to by algorithms specified above.</p>  <h3>Modifications to the <code id=DocumentType>DocumentType</code>
775    Interface</h3>
776    
777    <p>A <a href="#DocumentType"><code>DocumentType</code></a> interface
778    <em class=rfc2119>MAY</em> contain zero or more
779    <code>ProcessingInstruction</code> nodes in the <code>NodeList</code> object
780    contained in the <code>childNodes</code> attribute of the
781    <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
782    
783    <p>If the <a href="#DocumentType"><code>DocumentType</code></a> node is created
784    during the process to create a <abbr>DOM</abbr> from an <abbr>XML</abbr>
785    document, the <code>NodeList</code> object in the <code>childNodes</code>
786    object <em class=rfc2119>MUST</em> contains the
787    <code>ProcessingInstruction</code> nodes representing the processing
788    instructions in the document type definition of the document processed
789    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
790    <a href="#ref-XML11">XML11</a>]</cite> by the <abbr>XML</abbr> processor.  If
791    the <a href="#DocumentType"><code>DocumentType</code></a> node is marked as
792    <a href="#read-only">read$B!>(Bonly</a>, then all the child nodes
793    <em class=rfc2119>MUST</em> also be marked as
794    <a href="#read-only">read$B!>(Bonly</a>.</p>
795    
796    <p>If a <a href="#DocumentType"><code>DocumentType</code></a> node is created
797    from a
798    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.doctype">document
799    type declaration information item</a>
800    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>,
801    the <code>NodeList</code> object in the <code>childNodes</code> attribute
802    of the node <em class=rfc2119>MUST</em> contain the
803    <code>ProcessingInstruction</code> nodes created from any
804    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.pi">processing
805    instruction information items</a> in the list in the [children] property of the
806    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.doctype">document
807    type declaration item</a> in the same order.</p>
808    
809    <p>If a <a href="#DocumentType"><code>DocumentType</code></a> node is mapped to
810    a document type declaration information item, the list in the [children]
811    property <em class=rfc2119>MUST</em> contain the processng instruction
812    information items created from the <code>ProcessingInstruction</code> nodes
813    in the <code>NodeList</code> object in the <code>childNodes</code> attribute
814    of the <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
815    
816    <p>The implementation of the
817    <a href="#DocumentType"><code>DocumentType</code></a> interface
818    <em class=rfc2119>MUST</em> be modified as the following
819    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
820    <pre class=idl><code>// Modifications to the DocumentType interface
821      attribute DOMString <a href="#publicId">publicId</a>;
822      attribute DOMString <a href="#systemId">systemId</a>;
823    
824      attribute DOMString <a href="#internalSubset">internalSubset</a>;
825    </code></pre>
826    
827    <p>The <code id=publicId>publicId</code> attribute and the
828    <code id=systemId>systemId</code> attribute of
829    <a href="#DocumentType"><code>DocumentType</code></a>,
830    <a href="#Entity"><code>Entity</code></a>, and
831    <a href="#Notation"><code>Notation</code></a> interfaces are no longer
832    read$B!>(Bonly.</p>
833    
834    <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
835    <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
836    <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it <em class=rfc2119>MUST</em>
837    set the specified value as the value associated to the attribute.  No
838    normalization, relative reference resolution, or lexical validation is
839    performed. <span class=ed>@@ If the new value is <code>null</code>, should an
840    empty string be set?</span></p>
841    
 <p>Character class <dfn id=class-Char10><code>Char10</code></dfn>  
 contains the following characters:</p>  
 <ul>  
 <li><code class=char>U+0009</code> <code class=charname>CHARACTER  
 TABULATION</code></li>  
 <li><code class=char>U+000A</code> <code class=charname>LINE FEED</code></li>  
 <li><code class=char>U+000D</code> <code class=charname>CARRIAGE  
 RETURN</code></li>  
 <li><code class=char>U+0020</code> <code class=charname>SPACE</code>  
 .. <code class=char>U+D7FF</code></li>  
 <li><code class=char>U+E000</code> .. <code class=char>U+FFFD</code>  
 <code class=charname>REPLACEMENT CHARACTER</code></li>  
 <li><code class=char>U+10000</code> .. <code class=char>U+10FFFF</code></li>  
 </ul>  
842  <div class="note memo">  <div class="note memo">
843  <p>This character class contains all characters allowed in the production rule  <p>Setting an invalid identifier might make the node unserializable.
844  <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#NT-Char"><code>Char</code></a>  Setting a public identifier while leaving system identifier unspecified
845  of <abbr>XML</abbr> 1.0  would also make the <a href="#DocumentType"><code>DocumentType</code></a>
846  <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>.</p>  or <a href="#Entity"><code>Entity</code></a> node unserializable.</p>
 </div>  
   
 <p>Character class <dfn id=class-CompatChar10><code>CompatChar10</code></dfn>  
 contains the following characters:</p>  
 <ul>  
 <li class=ed>@@ <q>Document authors are encouraged to avoid "compatibility characters", as defined in section 6.8 of [Unicode @@ Unicode 2.0 @@] (see also D21 in section 3.6 of [Unicode3]).</q></li>  
 </ul>  
   
 <p>Character class <dfn id=class-ControlChar10><code>ControlChar10</code></dfn>  
 contains the following characters:</p>  
 <ul>  
 <li><code class=char>U+007F</code> <code class=charname>DELETE</code> ..  
 <code class=char>U+0084</code> <code class=charname>INDEX</code></li>  
 <li><code class=char>U+0086</code> <code class=charname>START OF SELECTED  
 AREA</code> .. <code class=char>U+009F</code> <code class=charname>APPLICATION  
 PROGRAM COMMAND</code></li>  
 <li><code class=char>U+FDD0</code> .. <code class=char>U+FDEF</code></li>  
 <li><code class=char>U+1FFFE</code> .. <code class=char>U+1FFFF</code></li>  
 <li><code class=char>U+2FFFE</code> .. <code class=char>U+2FFFF</code></li>  
 <li><code class=char>U+3FFFE</code> .. <code class=char>U+3FFFF</code></li>  
 <li><code class=char>U+4FFFE</code> .. <code class=char>U+4FFFF</code></li>  
 <li><code class=char>U+5FFFE</code> .. <code class=char>U+5FFFF</code></li>  
 <li><code class=char>U+6FFFE</code> .. <code class=char>U+6FFFF</code></li>  
 <li><code class=char>U+7FFFE</code> .. <code class=char>U+7FFFF</code></li>  
 <li><code class=char>U+8FFFE</code> .. <code class=char>U+8FFFF</code></li>  
 <li><code class=char>U+9FFFE</code> .. <code class=char>U+9FFFF</code></li>  
 <li><code class=char>U+AFFFE</code> .. <code class=char>U+AFFFF</code></li>  
 <li><code class=char>U+BFFFE</code> .. <code class=char>U+BFFFF</code></li>  
 <li><code class=char>U+CFFFE</code> .. <code class=char>U+CFFFF</code></li>  
 <li><code class=char>U+DFFFE</code> .. <code class=char>U+DFFFF</code></li>  
 <li><code class=char>U+EFFFE</code> .. <code class=char>U+EFFFF</code></li>  
 <li><code class=char>U+FFFFE</code> .. <code class=char>U+FFFFF</code></li>  
 <li><code class=char>U+10FFFE</code> .. <code class=char>U+10FFFF</code></li>  
 </ul>  
 <div class="note memo">  
 <p>This character class contains the characters listed in the Note in  
 <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#charsets">Section 2.2</a>  
 of <abbr>XML</abbr> 1.0  
 <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>,  
 as amended by  
 <a href="http://www.w3.org/XML/xml-V10-4e-errata#E02">errata</a>.</p>  
847  </div>  </div>
848    
849  <p>The character class <dfn id=class-NameStartChar10><code>NameStartChar10</code></dfn>  <div class=ed>
850  contains the following characters:</p>  <p>ISSUE: In HTML5, Firefox 1.5, and Opera 9, not specifying public or system identifier results in empty strings.</p>
 <ul class=ed>  
 </ul>  
 <div class="note memo">  
 <p>This character class contains all characters allowed as the first character  
 of a string matching to the production rule  
 <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#NT-Name"><code>Name</code></a>  
 of <abbr>XML</abbr> 1.0  
 <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>.</p>  
851  </div>  </div>
852    
853  <p>The character class <dfn id=class-NameChar10><code>NameChar10</code></dfn>  <p>The <code id=internalSubset>internalSubset</code> attribute of the
854  contains the following characters:</p>  <a href="#DocumentType"><code>DocumentType</code></a> interface is no longer
855  <ul>  read$B!>(Bonly.</p>
856  <li>The characters in the character class  
857  <a href="#class-NameStartChar10">NameStartChar10</a>.</li>  <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
858  <li class=ed></li>  <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
859  </ul>  <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it <em class=rfc2119>MUST</em>
860  <div class="note memo">  set the specified value as the value associated to the attribute.  No
861  <p>This character class contains all characters allowed as the second  normalization, or lexical validation is performed.  <span class=ed>@@ If the
862  character of a string matching to the production rule  new value is <code>null</code>, should an empty string be set?</span></p>
863  <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#NT-Name"><code>Name</code></a>  
864  of <abbr>XML</abbr> 1.0  </div>
865  <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>.</p>  
866  </div>  <div class=section id=section-documenttypedefinition>
867    <h3>The <code>DocumentTypeDefinition</code> Interface</h3>
868  <p>The character class <dfn id=class-PubidChar><code>PubidChar</code></dfn>  
869  contains the following characters:</p>  <p>The <a href="#DocumentType"><code>DocumentType</code></a> nodes
870  <ul>  <em class=rfc2119>MUST</em> also implement the
871  <li><code class=char>U+0009</code> <code class=charname>CHARACTER  <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
872  TABULATION</code></li>  interface.</p>
873  <li><code class=char>U+000A</code> <code class=charname>LINE FEED</code></li>  
874  <li><code class=char>U+000D</code> <code class=charname>CARRIAGE  <p>An instance of the
875  RETURN</code></li>  <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
876  <li><code class=char>U+0020</code> <code class=charname>SPACE</code></li>  interface <em class=rfc2119>MUST</em> be able to be obtained by using
877  <li><code class=char>U+0021</code> <code class=charname>EXCLAMATION MARK</code>  binding$B!>(Bspecific casting methods on an instance of the
878  (<code class=char>!</code>)</li>  <a href="#DocumentType"><code>DocumentType</code></a> interface (if such
879  <li><code class=char>U+0023</code> <code class=charname>DOLLAR SIGN</code>  casting methods are available) or by using the method <code>getFeature</code>
880  (<code class=char>$</code>)</li>  with parameter values
881  <li><code class=char>U+0024</code> <code class=charname>NUMBER SIGN</code>  <a href="#feature-XDoctype"><code>http://suika.fam.cx/www/2006/feature/XDoctype</code></a>
882  (<code class=char>#</code>)</li>  and <a href="#feature-XDoctype-3.0"><code>3.0</code></a> respectively (if the
883  <li><code class=char>U+0025</code> <code class=charname>PERCENT SIGN</code>  <a href="#DocumentType"><code>DocumentType</code></a> node supports the
884  (<code class=char>%</code>)</li>  feature <code>Core</code> version <code>3.0</code>
885  <li><code class=char>U+0027</code> <code class=charname>APOSTROPHE</code>  <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>).</p>
886  (<code class=char>'</code>)</li>  
887  <li><code class=char>U+0028</code> <code class=charname>LEFT PARENTHESIS</code>  <p>The
888  (<code class=char>(</code>)</li>  <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
889  <li><code class=char>U+0029</code> <code class=charname>RIGHT  interface <em class=rfc2119>MUST</em> be implemented as the following
890  PARENTHESIS</code> (<code class=char>)</code>)</li>  <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
891  <li><code class=char>U+002A</code> <code class=charname>ASTERISK</code>  <pre class=idl><code>interface <dfn id=DocumentTypeDefinition><code>DocumentTypeDefinition</code></dfn> {
892  (<code class=char>*</code>)</li>    readonly attribute NamedNodeMap <a href="#elementTypes">elementTypes</a>;
893  <li><code class=char>U+002B</code> <code class=charname>PLUS SIGN</code>    readonly attribute NamedNodeMap <a href="#generalEntities">generalEntities</a>;
894  (<code class=char>+</code>)</li>    readonly attribute NamedNodeMap <a href="#notations">notations</a>;
895  <li><code class=char>U+002C</code> <code class=charname>COMMA</code>  
896  (<code class=char>,</code>)</li>    <a href="#ElementTypeDefinition">ElementTypeDefinition</a> <a href="#getElementTypeDefinitionNode">getElementTypeDefinitionNode</a>
897  <li><code class=char>U+002D</code> <code class=charname>HYPHEN-MINUS</code>      (in DOMString <a href="#getElementTypeDefinitionNode-name"><var>name</var></a>);
898  (<code class=char>-</code>)</li>    <a href="#Entity">Entity</a> <a href="#getGeneralEntityNode">getGeneralEntityNode</a>
899  <li><code class=char>U+002E</code> <code class=charname>FULL STOP</code>      (in DOMString <a href="#getGeneralEntityNode-name"><var>name</var></a>);
900  (<code class=char>.</code>)</li>    <a href="#Notation">Notation</a> <a href="#getNotationNode">getNotationNode</a>
901  <li><code class=char>U+002F</code> <code class=charname>SOLIDUS</code>      (in DOMString <a href="#getNotationNode-name"><var>name</var></a>);
902  (<code class=char>/</code>)</li>  
903  <li><code class=char>U+0030</code> <code class=charname>DIGIT ZERO</code>    void <a href="#setElementTypeDefinitionNode">setElementTypeDefinitionNode</a>
904  (<code class=char>0</code>) .. <code class=char>U+0039</code>      (in DOMString <a href="#setElementTypeDefinitionNode-node"><var>node</var></a>)
905  <code class=charname>DIGIT NINE</code> (<code class=char>9</code>)</li>      raises (DOMException);
906  <li><code class=char>U+003A</code> <code class=charname>COLON</code>    void <a href="#setGeneralEntityNode">setGeneralEntityNode</a>
907  (<code class=char>:</code>)</li>      (in DOMString <a href="#setGeneralEntityNode-node"><var>node</var></a>)
908  <li><code class=char>U+003B</code> <code class=charname>SEMICOLON</code>      raises (DOMException);
909  (<code class=char>;</code>)</li>    void <a href="#setNotationNode">setNotationNode</a>
910  <li><code class=char>U+003D</code> <code class=charname>EQUAL SIGN</code>      (in DOMString <a href="#setNotationNode-node"><var>node</var></a>)
911  (<code class=char>=</code>)</li>      raises (DOMException);
912  <li><code class=char>U+003F</code> <code class=charname>QUESTION MARK</code>  }</code></pre>
913  (<code class=char>?</code>)</li>  
914  <li><code class=char>U+0040</code> <code class=charname>COMMERCIAL AT</code>  <dl>
915  (<code class=char>@</code>)</li>  <dt><dfn id=elementTypes class=dom-attr><code>elementTypes</code></dfn> of
916  <li><code class=char>U+0041</code> <code class=charname>LATIN CAPITAL LETTER  type <code>NamedNodeMap</code>, read$B!>(Bonly</dt>
917  A</code> (<code class=char>A</code>) .. <code class=char>U+005A</code>    <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
918  <code class=charname>LATIN CAPITAL LETTER Z</code>    contains all the element type definitions belonging to the
919  (<code class=char>Z</code>)</li>    <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
920  <li><code class=char>U+005F</code> <code class=charname>LOW LINE</code>  
921  (<code class=char>_</code>)</li>    <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
922  <li><code class=char>U+0061</code> <code class=charname>LATIN CAPITAL LETTER    <code>NamedNodeMap</code> object that contains all the
923  A</code> (<code class=char>A</code>) .. <code class=char>U+007A</code>    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
924  <code class=charname>LATIN CAPITAL LETTER Z</code>    nodes belonging to the <code>DocumentType</code> node.  The
925  (<code class=char>Z</code>)</li>    <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be read$B!>(Bonly
926  </ul>    if and only if the node is <a href="#read-only">read$B!>(Bonly</a>.  The
927      <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be
928      <a href="#live">live</a>.</p>
929    
930      <p>If the <code>DocumentType</code> node is created during the process
931      to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document, the following
932      requirements are applied:  The <code>NamedNodeMap</code> object in the
933      <a href="#elementTypes"><code>elementType</code></a> attribute
934      <em class=rfc2119>MUST</em> be so transformed that the object contains
935      the <code>ElementTypeDefinition</code> nodes for the element types
936      whose name is presented as the <code>Name</code> of the element type or
937      attribute definition list declarations processed
938      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
939      <a href="#ref-XML11">XML11</a>]</cite> by the <abbr>XML</abbr>
940      processor.  If there are more than one element type declarations for an
941      element type, then the declarations other than the first one
942      <em class=rfc2119>MUST</em> be ignored for the purpose of constructing the
943      <code>NamedNodeMap</code> object.</p></dd>
944    <dt><dfn id=generalEntities class=dom-attr><code>generalEntities</code></dfn>
945    of type <code>NamedNodeMap</code>, read$B!>(Bonly</dt>
946      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
947      contains all the general entities belonging to the
948      <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
949      
950      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
951      same value as the <code id=entities>entities</code> attribute (defined in the
952      <a href="#DocumentType"><code>DocumentType</code></a> interface) of the same
953      node.</p>
954    
955      <div class="note memo">
956        <p>This attribute is part of the interface for historical reason.</p>
957      </div></dd>
958    <!--
959    All entities declared in the document type definition
960    contained in or referenced from the document entity
961    might not be exposed through this collection, depending
962    on the information provided by the XML processor for
963    the DOM implementation.  In particular, it might not
964    contain any entity if entity references are expanded
965    at the parse time.  An implementation [['''MUST NOT''']]
966    expose an [CODE(DOMi)@en[[[Entity]]]] node whose [CODE(DOMa)@en[[[nodeName]]]]
967    is equal to the name of one of five predefined general entities in
968    XML through the collection as the result of parsing of an XML
969    document that has no error.  Duplicate entity declarations are also discarded.
970    
971    The attribute [['''MUST''']] return the [CODE(DOMi)@en[[[NamedNodeMap]]]]
972    object that contains all the [CODE(DOMi)@en[[[Entity]]]] nodes
973    representing general entities belong to the node.  The returned
974    [CODE(DOMi)@en[[[NamedNodeMap]]]] object [['''MUST''']] be read-only if and only if
975    the node is read-only. Note that the [CODE(DOMi)@en[[[NamedNodeMap]]]] object is live
976    and therefore any change of read-only flag on the node is immediately
977    reflected by that of the object.
978    -->
979    <dt><dfn id=notations class=dom-attr><code>notations</code></dfn> of type
980    <code>notations</code>, read$B!>(Bonly</code>
981      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
982      contains all the notations belonging to the
983      <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
984      
985      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
986      same value as the <code>notations</code> attribute (defined in the
987      <a href="#DocumentType"><code>DocumentType</code></a> interface) of the same
988      node.</p>
989    
990      <div class="note memo">
991        <p>This attribute is part of the interface for historical reason.</p>
992        <p>Implementations are not required to implement the
993        <code>notations</code> attribute twice (for
994        <a href="#DocumentType"><code>DocumentType</code></a> and
995        <a href="#DocumentTypeDefinition"><code>DocumentTypeDefinition</code></a>
996        interfaces); they share exactly same definition.</p>
997      </div></dd>
998    <!--
999    If the [CODE(DOMi)@en[[[DocumentTypeDefinition]]]] node is
1000    created from an XML document, duplicate notation declarations, if any, in DTD
1001    [['''MUST NOT''']] result in a node in the [CODE(DOMi)@en[[[NamedNodeMap]]]]
1002    object and only the first declaration [['''MUST''']] be
1003    made available as a [CODE(DOMi)@en[[[Notation]]]] node.
1004    
1005    ;; This definition is based on one for the
1006    [CODE(DOMa)@en[[[notations]]]] attribute of the
1007    [CODE(DOMi)@en[[[DocumentType]]]] interface in DOM XML module.
1008    Since duplication is violation to the Validity Constraint,
1009    XML parsers might vary on how notations are notified to
1010    the application.  In particular, [CODE(InfoProp)@en[[[notations]]]]
1011    property of the document information item in XML Information Set
1012    is so defined that in case ''any'' notation is declared for
1013    multiple times then the property has no value.
1014    
1015    The attribute [['''MUST''']] return the [CODE(DOMi)@en[[[NamedNodeMap]]]]
1016    object that contains all the [CODE(DOMi)@en[[[Notation]]]] nodes
1017    representing notations belong to the node.  The returned
1018    [CODE(DOMi)@en[[[NamedNodeMap]]]] object [['''MUST''']] be read-only if and only if
1019    the node is read-only. Note that the [CODE(DOMi)@en[[[NamedNodeMap]]]] object is live
1020    and therefore any change of read-only flag on the node is immediately
1021    reflected by that of the object.
1022    -->
1023    <dt><dfn id=getElementTypeDefinitionNode class=dom-method><code>getElementTypeDefinitionNode</code></dfn>,
1024    method</dt>
1025      <dd><p>Returns the
1026      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1027      with the specified name.</p>
1028    
1029      <p>The
1030      <dfn id=getElementTypeDefinitionNode-name class=dom-param><var>name</var></dfn>
1031      parameter is the name of the element type.</p>
1032    
1033      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1034      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node,
1035      whose <a href="#nodeName"><code>nodeName</code></a> is equal to
1036      <a href="#getElementTypeDefinitionNode-name"><var>name</var></a>, in the
1037      <code>NamedNodeMap</code> object in the
1038      <a href="#elementTypes"><code>elementTypes</code></a> attribute of the
1039      node.  If there is no such node, it <em class=rfc2119>MUST</em> return
1040      <code>null</code>.</p></dd>
1041    <dt><dfn id=getGeneralEntityNode class=dom-method><code>getGeneralEntityNode</code></dfn>,
1042    method</dt>
1043      <dd><p>Returns the <a href="#Entity"><code>Entity</code></a> node
1044      with the specified name.</p>
1045    
1046      <p>The
1047      <dfn id=getGeneralEntityNode-name class=dom-param><var>name</var></dfn>
1048      parameter is the name of the general entity.</p>
1049    
1050      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1051      <a href="#Entity"><code>Entity</code></a> node,
1052      whose <a href="#nodeName"><code>nodeName</code></a> is equal to
1053      <a href="#getGeneralEntityNode-name"><var>name</var></a>, in the
1054      <code>NamedNodeMap</code> object in the
1055      <a href="#entities"><code>entities</code></a> attribute of the
1056      node.  If there is no such node, it <em class=rfc2119>MUST</em> return
1057      <code>null</code>.</p></dd>
1058    <dt><dfn id=getNotationNode class=dom-method><code>getNotationNode</code></dfn>,
1059    method</dt>
1060      <dd><p>Returns the <a href="#Notation"><code>Notation</code></a> node
1061      with the specified name.</p>
1062    
1063      <p>The
1064      <dfn id=getNotationNode-name class=dom-param><var>name</var></dfn>
1065      parameter is the name of the notation.</p>
1066    
1067      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1068      <a href="#Notation"><code>Notation</code></a> node,
1069      whose <a href="#nodeName"><code>nodeName</code></a> is equal to
1070      <a href="#getNotationNode-name"><var>name</var></a>, in the
1071      <code>NamedNodeMap</code> object in the
1072      <a href="#notations"><code>notations</code></a> attribute of the
1073      node.  If there is no such node, it <em class=rfc2119>MUST</em> return
1074      <code>null</code>.</p></dd>
1075    <dt><dfn id=setElementTypeDefinitionNode class=dom-method><code>setElementTypeDefinitionNode</code></dfn>,
1076    method</dt>
1077      <dd><p>Associate an
1078      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1079      node with the <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
1080    
1081      <p>The
1082      <dfn id=setElementTypeDefinitionNode-node class=dom-param><var>node</var></dfn>
1083      parameter is the node to associate.</p>
1084    
1085      <p>When invoked, the method <em class=rfc2119>MUST</em> follow the rules
1086      to <a href="#algorithm-attach-node">attach a node</a>, where
1087      <a href="#attach-node-n"><var>n</var></a> is the
1088      <a href="#DocumentType"><code>DocumentType</code></a> node,
1089      <a href="#attach-node-l"><var>l</var></a> is the
1090      <a href="#elementTypes"><code>elementTypes</code></a> attribute value of the
1091      <a href="#DocumentType"><code>DocumentType</code></a> node,
1092      <a href="#attach-node-node"><var>node</var></a> is the
1093      <a href="#setElementTypeDefinitionNode-node"><var>node</var></a>, and
1094      <a href="#attach-node-owner-attr"><var>owner-attr</var></a> is the
1095      <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
1096      attribute.</p></dd>
1097    <dt><dfn id=setGeneralEntityNode class=dom-method><code>setGeneralEntityNode</code></dfn>,
1098    method</dt>
1099      <dd><p>Associate an <a href="#Entity"><code>Entity</code></a>
1100      node with the <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
1101    
1102      <p>The
1103      <dfn id=setGeneralEntityNode-node class=dom-param><var>node</var></dfn>
1104      parameter is the node to associate.</p>
1105    
1106      <p>When invoked, the method <em class=rfc2119>MUST</em> follow the rules
1107      to <a href="#algorithm-attach-node">attach a node</a>, where
1108      <a href="#attach-node-n"><var>n</var></a> is the
1109      <a href="#DocumentType"><code>DocumentType</code></a> node,
1110      <a href="#attach-node-l"><var>l</var></a> is the
1111      <a href="#entities"><code>entities</code></a> attribute value of the
1112      <a href="#DocumentType"><code>DocumentType</code></a> node,
1113      <a href="#attach-node-node"><var>node</var></a> is the
1114      <a href="#setGeneralEntityNode-node"><var>node</var></a>, and
1115      <a href="#attach-node-owner-attr"><var>owner-attr</var></a> is the
1116      <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
1117      attribute.</p></dd>
1118    <dt><dfn id=setNotationNode class=dom-method><code>setNotationNode</code></dfn>,
1119    method</dt>
1120      <dd><p>Associate an <a href="#Notation"><code>Notation</code></a>
1121      node with the <a href="#DocumentType"><code>DocumentType</code></a> node.</p>
1122    
1123      <p>The <dfn id=setNotationNode-node class=dom-param><var>node</var></dfn>
1124      parameter is the node to associate.</p>
1125    
1126      <p>When invoked, the method <em class=rfc2119>MUST</em> follow the rules
1127      to <a href="#algorithm-attach-node">attach a node</a>, where
1128      <a href="#attach-node-n"><var>n</var></a> is the
1129      <a href="#DocumentType"><code>DocumentType</code></a> node,
1130      <a href="#attach-node-l"><var>l</var></a> is the
1131      <a href="#notations"><code>notations</code></a> attribute value of the
1132      <a href="#DocumentType"><code>DocumentType</code></a> node,
1133      <a href="#attach-node-node"><var>node</var></a> is the
1134      <a href="#setNotationNode-node"><var>node</var></a>, and
1135      <a href="#attach-node-owner-attr"><var>owner-attr</var></a> is the
1136      <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
1137      attribute.</p></dd>
1138    </dl>
1139    
1140    <p>When a <dfn id=algorithm-attach-node title="attach a node">node is
1141    attached</dfn>, the rules below, with parameters
1142    <dfn id=attach-node-n><var>n</var></dfn>,
1143    <dfn id=attach-node-l><var>l</var></dfn>,
1144    <dfn id=attach-node-node><var>node</var></dfn>, and
1145    <dfn id=attach-node-owner-attr><var>owner-attr</var></dfn>,
1146    <em class=rfc2119>MUST</em> be followed:</p>
1147      <ol>
1148      <li><p>Let
1149      <dfn id=attach-node-r><var>r</var></dfn> be the node in
1150      <var>l</var> whose <code>nodeName</code> attribute value is equal to the
1151      <code>nodeName</code> attribute value of <var>node</var>, if any.</p></li>
1152      <li><p>If <var>r</var> is different from <code>null</code> and <var>r</var>
1153      is same node as <var>node</var>, then abort these steps.</p></li>
1154      <li><p>If <var>n</var> is <a href="#read-only">read$B!>(Bonly</a>, then raise a
1155      <code>NO_MODIFICATION_ALLOWED_ERR</code> and abort these steps.</p></li>
1156      <li><p>If the <code>ownerDocument</code> attribute value of <var>node</var>
1157      is different from that of <var>n</var>, then raise a
1158      <code>WRONG_DOCUMENT_ERR</code> and abort these steps.</p></li>
1159      <li><p>If the value of the attribute <var>owner-attr</var> of <var>node</var>
1160      is different from <code>null</code>, then raise a
1161      <code>HIERARCHY_REQUEST_ERR</code> and abort these steps.</p></li>
1162      <li><p>If <var>r</var> is a node, then remove it from <var>r</var>.</p>
1163    
1164      <div class="note memo">
1165      <p>By the removal of <var>r</var>, the attribute <var>owner-attr</var> of
1166      <var>r</var> is set to <code>null</code>.</p>
1167      </div></li>
1168      <li><p>Add <var>node</var> to <var>l</var>.</p>
1169    
1170      <div class="note memo">
1171      <p>By the addition of <var>node</var>, the attribute <var>owner-attr</var> of
1172      <var>node</var> is set to <var>n</var>.</p>
1173      </div></li>
1174      </ol>
1175    
1176    <div class=ed>
1177    <p>A future version of this interface might define the
1178    <code>parameterEntities</code> and getter/setter for parameter entities.
1179    </div>
1180    
1181    </div>
1182    
1183    <div class=section id=section-elementtypedefinition>
1184    <h3>The <code>ElementTypeDefinition</code> Interface</h3>
1185    
1186    <p>The nodes of type
1187    <a href="#ELEMENT_TYPE_DEFINITION_NODE"><code>ELEMENT_TYPE_DEFINITION_NODE</code></a>
1188    represents an element type definition.  Such a node
1189    <em class=rfc2119>MUST</em> implement the
1190    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1191    interface, which extends the <a href="#Node"><code>Node</code></a>
1192    interface.</p>
1193    
1194    <p>An element type definition represents a definition of the element type.
1195    It is corresponding to the element type declaration in <abbr>DTD</abbr>.
1196    However, an
1197    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1198    does not represent the element type definition in <abbr>DTD</abbr> itself.  
1199    Even if there are more than one element type declarations for an element type
1200    in <abbr>DTD</abbr>, the result <abbr>DOM</abbr> will contain only an
1201    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1202    node for that element type.  In addition, if there are attribute definition
1203    declarations for an element type, even when there is no element type
1204    declaration for that element type, the <abbr>DOM</abbr> will contain an
1205    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1206    node for that element type.</p>
1207    
1208    <p>An <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1209    node cannot be a child of any node.  An
1210    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1211    cannot have any child node.</p>
1212    
1213    <p>The <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1214    interface <em class=rfc2119>MUST</em> be implemented as the following
1215    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1216    <pre class=idl><code>interface <dfn id=ElementTypeDefinition><code>ElementTypeDefinition</code></dfn> : <a href="#Node">Node</a> {
1217      readonly attribute <a href="#DocumentType">DocumentType</a> <a href="#ownerDocumentTypeDefinition">ownerDocumentTypeDefinition</a>;
1218    
1219      readonly attribute NamedNodeMap <a href="#attributeDefinitions">attributeDefinitions</a>;
1220      <a href="#AttributeDefinition">AttributeDefinition</a> <a href="#getAttributeDefinitionNode">getAttributeDefinitionNode</a>
1221        (in DOMString <a href="#getAttributeDefinitionNode-name"><var>name</var></a>);
1222      void <a href="#setAttributeDefinitionNode">setAttributeDefinitionNode</a>
1223        (in <a href="#AttributeDefinition">AttributeDefinition</a> <a href="#setAttributeDefinitionNode-node"><var>node</var></a>)
1224        raises (DOMException);
1225    }</code></pre>
1226    
1227    <dl>
1228    <dt><dfn id=ownerDocumentTypeDefinition class=dom-attr><code>ownerDocumentTypeDefinition</code></dfn>
1229    of type <a href="#DocumentType"><code>DocumentType</code></a>, read$B!>(Bonly</dt>
1230      <dd><p>The
1231      <a href="#ownerDocumentTypeDefinition"><code>ownerDocumentTypeDefinition</code></a>
1232      attribute of
1233      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
1234      <a href="#Entity"><code>Entity</code></a>, and
1235      <a href="#Notation"><code>Notation</code></a> interfaces contain the
1236      <a href="#DocumentType"><code>DocumentType</code></a> node to which the node
1237      is attached.</p>
1238    
1239      <p>On getting, the attribute <em class=rfc2119>MUST</em> return a
1240      <a href="#DocumentType"><code>DocumentType</code></a> node.  It
1241      <em class=rfc2119>MUST</em> be such a node that whose
1242      <a href="#elementTypes"><code>elementTypes</code></a> (for an
1243      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1244      node), <a href="#entities"><code>entities</code></a> (for an
1245      <a href="#Entity"><code>Entity</code></a> node), or
1246      <a href="#notations"><code>notations</code></a> (for a
1247      <a href="#Notation"><code>Notation</code></a> node) attribute contains the
1248      <code>NamedNodeMap</code> object that contains the node.  If there is no such
1249      a <a href="#DocumentType"><code>DocumentType</code></a> node,
1250      then <code>null</code> <em class=rfc2119>MUST</em> be returned.</p></dd>
1251    <dt><dfn id=attributeDefinitions class=dom-attr><code>attributeDefinitions</code></dfn>
1252    of type NamedNodeMap, read$B!>(Bonly</dt>
1253      <dd><p>A <a href="#live">live</a> <code>NamedNodeMap</code> object that
1254      contains all the attribute definitions belonging to the
1255      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1256      node.</p>
1257    
1258      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
1259      <code>NamedNodeMap</code> object that contains all the
1260      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1261      belonging to the
1262      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node.
1263      The <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be
1264      read$B!>(Bonly if and only if the node is <a href="#read-only">read$B!>(Bonly</a>.  
1265      The <code>NamedNodeMap</code> object <em class=rfc2119>MUST</em> be
1266      <a href="#live">live</a>.</p>
1267      
1268      <p>If the
1269      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node
1270      is created during the process to create a <abbr>DOM</abbr> from an
1271      <abbr>XML</abbr> document, the following requirements are applied:  The
1272      <code>NamedNodeMap</code> object in the
1273      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1274      attribute <em class=rfc2119>MUST</em> be so transformed that the object
1275      contains the
1276      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1277      corresponding to the attribute definitions in the attribute definition
1278      list declarations processed
1279      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1280      <a href="#ref-XML11">XML11</a>]</cite> by the <abbr>XML</abbr> processor and
1281      associated to the element type represented by the node.  If there are more
1282      than one attribute definitions for an attribute, then the definitions other
1283      than the first one <em class=rfc2119>MUST</em> be ignored for the purpose
1284      of constructing the <code>NamedNodeMap</code> object.</p></dd>
1285    <dt><dfn id=getAttributeDefinitionNode class=dom-method><code>getAttributeDefinitionNode</code></dfn>,
1286    method</dt>
1287      <dd><p>Return the
1288      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1289      with the specified name.</p>
1290    
1291      <p>The
1292      <dfn id=getAttributeDefinitionNode-name class=dom-param><var>name</var></dfn>
1293      parameter is the name of the attribute.</p>
1294    
1295      <p>When invoked, the method <em class=rfc2119>MUST</em> return the
1296      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node,
1297      whose <a href="#nodeName"><code>nodeName</code></a> attribute value is
1298      equal to <a href="#getAttributeDefinitionNode-name"><var>name</var></a>,
1299      in the <code>NamedNodeMap</code> in the
1300      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1301      attribute of the node.  If there is no such node, it
1302      <em class=rfc2119>MUST</em> return <code>null</code>.</p></dd>
1303    <dt><dfn id=setAttributeDefinitionNode class=dom-method><code>setAttributeDefinitionNode</code></dfn>,
1304    method</dt>
1305      <dd><p>Associate an
1306      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node with
1307      the
1308      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1309      node.</p>
1310    
1311      <p>The
1312      <dfn id=setAttributeDefinitionNode-node class=dom-param><var>node</var></dfn>
1313      parameter is the node to associate.</p>
1314    
1315      <p>When invoked, the method <em class=rfc2119>MUST</em> follow the rules
1316      to <a href="#algorithm-attach-node">attach a node</a>, where
1317      <a href="#attach-node-n"><var>n</var></a> is the
1318      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>
1319      node, <a href="#attach-node-l"><var>l</var></a> is the
1320      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1321      attribute value of the
1322      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node,
1323      <a href="#attach-node-node"><var>node</var></a> is the
1324      <a href="#setAttributeDefinitionNode-node"><var>node</var></a>, and
1325      <a href="#attach-node-owner-attr"><var>owner-attr</var></a> is the
1326      <a href="#ownerElementTypeDefinition"><code>ownerElementTypeDefinition</code></a>
1327      attribute.</p></dd>
1328    </dl>
1329    
1330    <div class=ed>
1331    <p>A future version of the specification might define a set of attributes
1332    and methods for representing and accessing to the content model of the
1333    element type.</p>
1334    </div>
1335    </div>
1336    
1337    <div class=section id=section-attributedefinition>
1338    <h3>The <code>AttributeDefinition</code> Interface</h3>
1339    
1340    <p>The nodes of type
1341    <a href="#ATTRIBUTE_DEFINITION_NODE"><code>ATTRIBUTE_DEFINITION_NODE</code></a>
1342    represents an attribute definition.  Such a node
1343    <em class=rfc2119>MUST</em> implement the
1344    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> interface,
1345    which extends the <a href="#Node"><code>Node</code></a> interface.</p>
1346    
1347    <p>An attribute definition represents a definition of the attribute
1348    associated to an element type.  It is corresponding to the attribute definition
1349    in the attribute list declaration in <abbr>DTD</abbr>.  However, an
1350    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node does
1351    not represent the attribute definition in <abbr>DTD</abbr> itself.  Even if
1352    there are more than one attribute definitions for an attribute of an element
1353    type in <abbr>DTD</abbr>, the result <abbr>DOM</abbr> will contain only an
1354    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node for
1355    that attribute.</p>
1356    
1357    <p>An <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1358    node cannot be a child of any node.  An
1359    <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1360    can have zero or more child nodes of same kinds as those allowed for
1361    <code>Attr</code> nodes
1362    <cite class="bibref normative">[<a href="#ref-DOM3CORE">DOM3CORE</a>]</cite>.</p>
1363    
1364    <p>The <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1365    interface <em class=rfc2119>MUST</em> be implemented as the following
1366    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1367    <pre class=idl><code>interface <dfn id=AttributeDefinition><code>AttributeDefinition</code></dfn> : <a href="#Node">Node</a> {
1368      <span class=comment>// <a href="#DeclaredValueType">DeclaredValueType</a></span>
1369      const unsigned short <a href="#NO_TYPE_ATTR">NO_TYPE_ATTR</a> = 0;
1370      const unsigned short <a href="#CDATA_ATTR">CDATA_ATTR</a> = 1;
1371      const unsigned short <a href="#ID_ATTR">ID_ATTR</a> = 2;
1372      const unsigned short <a href="#IDREF_ATTR">IDREF_ATTR</a> = 3;
1373      const unsigned short <a href="#IDREFS_ATTR">IDREFS_ATTR</a> = 4;
1374      const unsigned short <a href="#ENTITY_ATTR">ENTITY_ATTR</a> = 5;
1375      const unsigned short <a href="#ENTITIES_ATTR">ENTITIES_ATTR</a> = 6;
1376      const unsigned short <a href="#NMTOKEN_ATTR">NMTOKEN_ATTR</a> = 7;
1377      const unsigned short <a href="#NMTOKENS_ATTR">NMTOKENS_ATTR</a> = 8;
1378      const unsigned short <a href="#NOTATION_ATTR">NOTATION_ATTR</a> = 9;
1379      const unsigned short <a href="#ENUMERATION_ATTR">ENUMERATION_ATTR</a> = 10;
1380      const unsigned short <a href="#UNKNOWN_ATTR">UNKNOWN_ATTR</a> = 11;
1381    
1382      <span class=comment>// <a href="#DefaultValueType">DefaultValueType</a></span>
1383      const unsigned short <a href="#UNKNOWN_DEFAULT">UNKNOWN_DEFAULT</a> = 0;
1384      const unsigned short <a href="#FIXED_DEFAULT">FIXED_DEFAULT</a> = 1;
1385      const unsigned short <a href="#REQUIRED_DEFAULT">REQUIRED_DEFAULT</a> = 2;
1386      const unsigned short <a href="#IMPLIED_DEFAULT">IMPLIED_DEFAULT</a> = 3;
1387      const unsigned short <a href="#EXPLICIT_DEFAULT">EXPLICIT_DEFAULT</a> = 4;
1388      
1389      readonly attribute <a href="#ElementTypeDefinition">ElementTypeDefinition</a> <a href="#ownerElementTypeDefinition">ownerElementTypeDefinition</a>;
1390    
1391      readonly attribute unsigned short <a href="#declaredType">declaredType</a>;
1392      readonly attribute DOMStringList <a href="#allowedTokens">allowedTokens</a>;
1393      readonly attribute unsigned short <a href="#defaultType">defaultType</a>;
1394    }</code></pre>
1395    
1396    <dl>
1397    <dt><dfn id=ownerElementTypeDefinition class=dom-attr><code>ownerElementTypeDefinition</code></dfn>
1398    of type
1399    <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a>,
1400    read$B!>(Bonly</dt>
1401      <dd><p>The
1402      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> to
1403      which the <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1404      node belongs.</p>
1405    
1406      <p>On getting, the attribute <em class=rfc2119>MUST</em> return an
1407      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node.
1408      It <em class=rfc2119>MUST</em> be such a node that whose
1409      <a href="#attributeDefinitions"><code>attributeDefinitions</code></a>
1410      attribute contains the <code>NamedNodeMap</code> object that contains
1411      the <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1412      node.  If there is no such an
1413      <a href="#ElementTypeDefinition"><code>ElementTypeDefinition</code></a> node,
1414      then <code>null</code> <em class=rfc2119>MUST</em> be returned.</p>
1415    <dt><dfn id=declaredType class=dom-attr><code>declaredType</code></dfn> of type
1416    <code>unsigned short</code></dt>
1417      <dd><p>The declared type
1418      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1419      <a href="#ref-XML11">XML11</a>]</cite> of the attribute.  It is expected that
1420      this attribute contains a value from the definition group
1421      <a href="#DeclaredValueType"><code>DeclaredValueType</code></a>.</p>
1422    
1423      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
1424      value associated to this attribute.</p>
1425    
1426      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1427      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the
1428      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1429      is <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1430      <em class=rfc2119>MUST</em> set the specified value as the value
1431      associated to this attribute.</p>
1432    
1433      <p>If the <code>AttributeDefinition</code> node is created during the process
1434      to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document, an
1435      appropriate value from the
1436      <a href="#DeclaredValueType"><code>DeclaredValueType</code></a> constant
1437      group <em class=rfc2119>MUST</em> be set to the attribute.</p>
1438    
1439      <!-- DeclaredValueType -->
1440    <p>The definition group
1441    <dfn id=DeclaredValueType><code>DeclaredValueType</code></dfn> contains
1442    integers indicating the declared type of attributes.  The definition
1443    group contains the following constants:</p>
1444    
1445    <table>
1446    <thead>
1447    <tr><th scope=col>Name<th scope=col>Value<th scope=col>Description</tr>
1448    </thead>
1449    <tbody>
1450    <tr>
1451    <th scope=row><dfn id=NO_TYPE_ATTR class=dom-const><code>NO_TYPE_ATTR</code>
1452    <td><code>0</code><td><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">No
1453    value</a>
1454    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>.</tr>
1455    <tr>
1456    <th scope=row><dfn id=CDATA_ATTR class=dom-const><code>CDATA_ATTR</code>
1457    <td><code>1</code><td><code>CDATA</code>
1458    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1459    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1460    <tr>
1461    <th scope=row><dfn id=ID_ATTR class=dom-const><code>ID_ATTR</code>
1462    <td><code>2</code><td><code>ID</code>
1463    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1464    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1465    <tr>
1466    <th scope=row><dfn id=IDREF_ATTR class=dom-const><code>IDREF_ATTR</code>
1467    <td><code>3</code><td><code>IDREF</code>
1468    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1469    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1470    <tr>
1471    <th scope=row><dfn id=IDREFS_ATTR class=dom-const><code>IDREFS_ATTR</code>
1472    <td><code>4</code><td><code>IDREFS</code>
1473    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1474    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1475    <tr>
1476    <th scope=row><dfn id=ENTITY_ATTR class=dom-const><code>ENTITY_ATTR</code>
1477    <td><code>5</code><td><code>ENTITY</code>
1478    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1479    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1480    <tr>
1481    <th scope=row><dfn id=ENTITIES_ATTR class=dom-const><code>ENTITIES_ATTR</code>
1482    <td><code>6</code><td><code>ENTITIES</code>
1483    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1484    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1485    <tr>
1486    <th scope=row><dfn id=NMTOKEN_ATTR class=dom-const><code>NMTOKEN_ATTR</code>
1487    <td><code>7</code><td><code>NMTOKEN</code>
1488    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1489    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1490    <tr>
1491    <th scope=row><dfn id=NMTOKENS_ATTR class=dom-const><code>NMTOKENS_ATTR</code>
1492    <td><code>8</code><td><code>NMTOKENS</code>
1493    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1494    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1495    <tr>
1496    <th scope=row><dfn id=NOTATION_ATTR class=dom-const><code>NOTATION_ATTR</code>
1497    <td><code>9</code><td><code>NOTATION</code>
1498    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1499    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1500    <tr>
1501    <th scope=row><dfn id=ENUMERATION_ATTR class=dom-const><code>ENUMERATION_ATTR</code>
1502    <td><code>10</code><td>Enumeration
1503    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1504    <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1505    <tr>
1506    <th scope=row><dfn id=UNKNOWN_ATTR class=dom-const><code>UNKNOWN_ATTR</code>
1507    <td><code>11</code><td><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">Unknown</a>,
1508    because no declaration for the attribute has been read but the
1509    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.document">[all declaration processed]</a>
1510    property
1511    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>
1512    would be false.</tr>
1513    </tbody>
1514    </table>
1515    
1516    <p>If no attribute type information is available, or if the source
1517    of the information does not distinguish
1518    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">no
1519    value</a> and
1520    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">unknown</a>
1521    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite>,
1522    then the value
1523    <a href="#NO_TYPE_ATTR"><code>NO_TYPE_ATTR</code></a>
1524    <em class=rfc2119>MUST</em> be used.</p>
1525    
1526  <div class="note memo">  <div class="note memo">
1527  <p>This character class contains all characters allowed in the production rule  <p>An <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1528  <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#NT-PubidChar"><code>PubidChar</code></a>  created by the
1529  of <abbr>XML</abbr> 1.0  <a href="#createAttributeDefinition"><code>createAttributeDefinition</code></a>
1530  <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>]</cite>.</p>  method has its <a href="#declaredType"><code>declaredType</code></a> attribute
1531    set to <a href="#NO_TYPE_ATTR"><code>NO_TYPE_ATTR</code></a>.</p>
1532    </div>
1533    
1534    <p>If the source of the information does not distinguish
1535    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">no
1536    value</a> and/or
1537    <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#intro.null">unknown</a>
1538    <cite class="bibref normative">[<a href="#ref-INFOSET">INFOSET</a>]</cite> and
1539    <code>CDATA</code>
1540    <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1541    <a href="#ref-XML11">XML11</a>]</cite>, then the value
1542    <a href="#CDATA_ATTR"><code>CDATA_ATTR</code></a> <em class=rfc2119>MUST</em>
1543    be used.</p>
1544    
1545    <p>In Perl binding
1546    <cite class="bibref normative">[<a href="#ref-DOMPERL">DOMPERL</a>]</cite>, the
1547    <code>Attr</code> nodes <em class=rfc2119>MUST</em> implement the
1548    <a href="#DeclaredValueType"><code>DeclaredValueType</code></a>
1549    definition group.</p>
1550    
1551      </dd>
1552    <dt><dfn id=allowedTokens class=dom-attr><code>allowedTokens</code></dfn> of
1553    type <code>DOMStringList</code>, read$B!>(Bonly</dt>
1554      <dd><p>The list of allowed attribute values.</p>
1555    
1556      <p>On getting, the attribute <em class=rfc2119>MUST</em> return the
1557      <code>DOMStringList</code> object associated to this attribute.  The object
1558      <em class=rfc2119>MAY</em> contain zero or more ordered strings, consist of
1559      zero or more characters respectively, possibly with duplications.  The
1560      object <em class=rfc2119>MUST</em> be read$B!>(Bonly if and only if the node
1561      is <a href="#read-only">read$B!>(Bonly</a>.</p>
1562    
1563      <p>If the <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1564      node is created during the process to create a <abbr>DOM</abbr> from an
1565      <abbr>XML</abbr> document, the object <em class=rfc2119>MUST</em> contain
1566      the names or name tokens allowed for the attribute defined by the node.
1567      If the document is well$B!>(Bformed, the object will be empty unless
1568      the <a href="#declaredType"><code>declaredType</code></a> is
1569      <a href="#ENUMERATION_ATTR"><code>ENUMERATION_ATTR</code></a> or
1570      <a href="#NOTATION_ATTR"><code>NOTATION_ATTR</code></a>.</p>
1571    
1572      <p>If the <a href="#declaredType"><code>declaredType</code></a> is different
1573      from <a href="#ENUMERATION_ATTR"><code>ENUMERATION_ATTR</code></a> or
1574      <a href="#NOTATION_ATTR"><code>NOTATION_ATTR</code></a>, this attribute
1575      <em class=rfc2119>MUST</em> be ignored for the purpose of serializing
1576      into (part of) <abbr>XML</abbr> document.</p>
1577    
1578      <div class="note memo">
1579        <p>When serializing the node it should be noted that the object might
1580        be empty, might contain duplications, and might contain strings that are
1581        not names or name tokens.</p>
1582      </div></dd>
1583    <dt><dfn id=defaultType class=dom-attr><code>defaultType</code></dfn> of
1584    type <code>unsigned short</code></dt>
1585      <dd><p>The type of the default for the attribute.  It is expected that this
1586      attribute contains a value from the definition group
1587      <a href="#DefaultValueType"><code>DefaultValueType</code></a>.</p>
1588    
1589      <p>On getting, the attribute <em class=rfc2119>MUST</em> return
1590      the value associated to this attribute.</p>
1591    
1592      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1593      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the
1594      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node
1595      is <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1596      <em class=rfc2119>MUST</em> set the specified value as the value
1597      associated to this attribute.</p>
1598    
1599      <p>If the
1600      <a href="#AttributeDefinition"><code>AttributeDefinition</code></a> node is
1601      created during the process to create a <abbr>DOM</abbr> from an
1602      <abbr>XML</abbr> document, an appropriate value from the
1603      <a href="#DefaultValueType"><code>DefaultValueType</code></a> definition
1604      group <em class=rfc2119>MUST</em> be set to the attribute.</p>
1605    
1606      <!-- DefaultValueType -->
1607      <p>The definition group
1608      <dfn id=DefaultValueType><code>DefaultValueType</code></dfn>
1609      contains integers indicating the type of the default for the attribute.
1610      The definition group contains the following constants:</p>
1611    
1612      <table>
1613      <thead>
1614      <tr><th scope=col>Name<th scope=col>Value<th scope=col>Description</tr>
1615      </thead>
1616      <tbody>
1617      <tr>
1618      <th scope=row><dfn id=UNKNOWN_DEFAULT class=dom-const><code>UNKNOWN_DEFAULT</code></dfn>
1619      <td><code>0</code><td>Unknown.</tr>
1620      <tr>
1621      <th scope=row><dfn id=FIXED_DEFAULT class=dom-const><code>FIXED_DEFAULT</code></dfn>
1622      <td><code>1</code><td>Provided explicitly and only the value is allowed.
1623      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1624      <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1625      <tr>
1626      <th scope=row><dfn id=REQUIRED_DEFAULT class=dom-const><code>REQUIRED_DEFAULT</code></dfn>
1627      <td><code>2</code><td>No default value and the attribute have to be
1628      explicitly specified.</tr>
1629      <tr>
1630      <th scope=row><dfn id=IMPLIED_DEFAULT class=dom-const><code>IMPLIED_DEFAULT</code></dfn>
1631      <td><code>3</code><td>Implied
1632      <cite class="bibref normative">[<a href="#ref-XML10">XML10</a>,
1633      <a href="#ref-XML11">XML11</a>]</cite>.</tr>
1634      <tr>
1635      <th scope=row><dfn id=EXPLICIT_DEFAULT class=dom-const><code>EXPLICIT_DEFAULT</code></dfn>
1636      <td><code>4</code><td>Provided explicitly.</tr>
1637      </tbody>
1638      </table>
1639    
1640      <p>If the source of the default type does not distinguish
1641      implied and unknown default types, then the value
1642      <a href="#IMPLIED_DEFAULT"><code>IMPLIED_DEFAULT</code></a>
1643      <em class=rfc2119>MUST</em> be used.</p>
1644    
1645      <div class="note memo">
1646      <p>An <a href="#AttributeDefinition"><code>AttributeDefinition</code></a>
1647      node created by the
1648      <a href="#createAttributeDefinition"><code>createAttributeDefinition</code></a>
1649      method has its <a href="#defaultType"><code>defaultType</code></a>
1650      attribute set to
1651      <a href="#UNKNOWN_DEFAULT"><code>UNKNOWN_DEFAULT</code></a>.</p>
1652      </div></dd>
1653    </dl>
1654    
1655    </div>
1656    
1657    <div class=section id=section-entity>
1658    <h3>Modifications to the <code id=Entity>Entity</code> Interface</h3>
1659    
1660    <p>The implementation of the <a href="#Entity"><code>Entity</code></a>
1661    interface <em class=rfc2119>MUST</em> be modified as the following
1662    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1663    <pre class=idl><code>// Modifications to the Entity interface
1664      attribute DOMString <a href="#publicId">publicId</a>;
1665      attribute DOMString <a href="#systemId">systemId</a>;
1666      attribute DOMString <a href="#notationName">notationName</a>;
1667    
1668      // Additions to the Entity interface
1669      attribute DOMString <a href="#hasReplacementTree">hasReplacementTree</a>;
1670      readonly attribute <a href="#DocumentType">DocumentType</a> <a href="#ownerDocumentTypeDefinition">ownerDocumentTypeDefinition</a>;
1671    
1672      attribute boolean <a href="#isExternallyDeclared">isExternallyDeclared</a>;
1673    </code></pre>
1674    
1675    <p>The <code id=notationName>notationName</code> attribute of the
1676    <a href="#Entity"><code>Entity</code></a> interface is no longer
1677    read$B!>(Bonly.</p>
1678    
1679    <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1680    <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
1681    <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it <em class=rfc2119>MUST</em>
1682    set the specified value as the value associated to the attribute.  No lexical
1683    validation is performed.  The new value <em class=rfc2119>MAY</em> be
1684    <code>null</code>.</p>
1685    
1686    <dl>
1687    <dt><dfn id=hasReplacementTree class=dom-attr><code>hasReplacementTree</code></dfn>
1688    of type boolean</dt>
1689      <dd><p>Whether the structure of the replacement text of the entity
1690      is available via the <code>NodeList</code> object in the
1691      <code>childNodes</code> attribute of the entity.</p>
1692    
1693      <p>On getting, the attribute <em class=rfc2119>MUST</em> return
1694      the value associated to this attribute.</p>
1695    
1696      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1697      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
1698      <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1699      <em class=rfc2119>MUST</em> set the specified value as the
1700      value associated to this attribute.</p>
1701    
1702      <div class="note memo">
1703      <p>The attribute can be set to <code>false</code> even if the
1704      <a href="#Entity"><code>Entity</code></a> node has any child node.
1705      If the attribute is set to <code>false</code>, then any child node of
1706      the <a href="#Entity"><code>Entity</code></a> node ought to be ignored,
1707      say, for the purpose of serialization.</p>
1708      </div>
1709    
1710      <p>When an <code>EntityReference</code> node is created by cloning
1711      the replacement subtree of the <a href="#Entity"><code>Entity</code></a>
1712      node, if the attribute is set to <code>false</code>, then any descendant
1713      of the node <em class=rfc2119>MUST</em> be ignored.</p>
1714    
1715      <p>If the <a href="#Entity"><code>Entity</code></a> node is created during
1716      the process to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document,
1717      the following requirements are applied:  If the entity is an unparsed
1718      entity, then the attribute <em class=rfc2119>MUST</em> be set to
1719      <code>false</code>.  Otherwise, if the entity is an external entity whose
1720      replacement text is not available, or whose replacement text is not converted
1721      to a replacement tree, then the attribute <em class=rfc2119>MUST</em> be set
1722      to <code>false</code>.  Otherwise, the attribute
1723      <em class=rfc2119>MUST</em> be set to <code>true</code>.</p>
1724    
1725      <div class="note memo">
1726      <p>An <a href="#Entity"><code>Entity</code></a> node created by the
1727      <a href="#createGeneralEntity"><code>createGeneralEntity</code></a> method
1728      has its <a href="#hasReplacementTree"><code>hasReplacementTree</code></a>
1729      attribute set to <code>false</code>.</p>
1730      </div></dd>
1731    <dt><dfn id=isExternallyDeclared class=dom-attr><code>isExternallyDeclared</code></dfn>
1732    of type boolean</dt>
1733      <dd><p>Whether the entity is declared by an external entity declaration or
1734      not.  If the value is <code>true</code>, the entity is declared in an entity
1735      declaration in the external subset entity or in an external parameter entity.
1736      If the value is <code>false</code>, the entity is declared in an entity
1737      declaration in the internal subset, or the node is created in memory.</p>
1738    
1739      <p>On getting, the attribute <em class=rfc2119>MUST</em> return
1740      the value associated to this attribute.</p>
1741    
1742      <p>On setting, the attribute <em class=rfc2119>MUST</em> raise a
1743      <code>NO_MODIFICATION_ALLOWED_ERR</code> if the node is
1744      <a href="#read-only">read$B!>(Bonly</a>.  Otherwise, it
1745      <em class=rfc2119>MUST</em> set the specified value as the value associated
1746      to this attribute.</p>
1747    
1748      <p>If the <a href="#Entity"><code>Entity</code></a> node is created during
1749      the process to create a <abbr>DOM</abbr> from an <abbr>XML</abbr> document,
1750      the following requirements are applied:  If the entity is an unparsed
1751      entity, then the attribute <em class=rfc2119>MUST</em> be set to
1752      <code>false</code>.  Otherwise, i.e. the entity is a parsed entity, then the
1753      attribute <em class=rfc2119>MUST</em> be set to the value of whether the
1754      entity is declared by an external markup declaration or not.</p></dd>
1755    </dl>
1756    </div>
1757    
1758    <div class=section id=section-notation>
1759    <h3>Modifications to the <code id=Notation>Notation</code> Interface</h3>
1760    
1761    <p>The implementation of the <a href="#Notation"><code>Notation</code></a>
1762    interface <em class=rfc2119>MUST</em> be modified as the following
1763    <a href="#idl-fragment"><abbr>IDL</abbr> fragment</a>:</p>
1764    <pre class=idl><code>// Modifications to the Notation interface
1765      attribute DOMString <a href="#publicId">publicId</a>;
1766      attribute DOMString <a href="#systemId">systemId</a>;
1767    
1768      // Addition to the Notation interface
1769      readonly attribute <a href="#DocumentType">DocumentType</a> <a href="#ownerDocumentTypeDefinition">ownerDocumentTypeDefinition</a>;
1770    </code></pre>
1771  </div>  </div>
1772    
1773  </div>  </div>
# Line 1093  of <abbr>XML</abbr> 1.0 Line 1780  of <abbr>XML</abbr> 1.0
1780    
1781  <dl>  <dl>
1782  <dt id=ref-DOM3CORE>DOM3CORE</dt>  <dt id=ref-DOM3CORE>DOM3CORE</dt>
1783    <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
1784  <dt id=ref-DOMDTDEF>DOMDTDEF</dt>    Object Model (<abbr>DOM</abbr>) Level 3 Core Specification, Version
1785    <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
1786      April 2004</time>.  <em>This</em> version of the specification is referenced.
1787      The latest version of the specification is available at
1788      <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>
1789    <dt id=ref-DOMBIND>DOMBIND</dt>
1790      <dd><cite><a href="http://www.w3.org/TR/2007/WD-DOM-Bindings-20071017/">Language
1791      Bindings for <abbr>DOM</abbr> Specifications</a></cite>, <abbr>W3C</abbr>
1792      Working Draft, <time datetime=2007-10-17>17 October 2007</time>.  
1793      <em>This</em> version of the specification is referenced.  The latest version
1794      of the specification is available at
1795      <code class=uri>&lt;<a href="http://www.w3.org/TR/DOM-Bindings/">http://www.w3.org/TR/DOM-Bindings/</a>></code>.</dd>
1796    <dt id=ref-DOMPERL>DOMPERL</dt>
1797      <dd><cite><a href="http://suika.fam.cx/gate/2005/sw/manakai/DOM%20Perl%20Binding">manakai's
1798      <abbr>DOM</abbr> Perl Binding</a></cite>, editor's draft.  Work in
1799      progress.</dd>
1800    <dt id=ref-HTML5>HTML5</dt>
1801      <dd><cite><a href="http://whatwg.org/html5"><abbr>HTML</abbr> 5</a></cite>,
1802      <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr>
1803      Working Draft.  Work in progress.</dd>
1804    <dt id=ref-INFOSET>INFOSET</dt>
1805      <dd><cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204"><abbr>XML</abbr>
1806      Information Set (Second Edition)</a></cite>, <abbr>W3C</abbr> Recommendation,
1807      <time datetime=2004-02-04>4 February 2004</time>.  <em>This</em> version of
1808      the specification is referenced.  The latest version of the specification is
1809      available at
1810      <code class=uri>&lt;<a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>></code>.</dd>
1811  <dt id="ref-KEYWORDS">KEYWORDS</dt>  <dt id="ref-KEYWORDS">KEYWORDS</dt>
1812    <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
1813    <abbr>RFCs</abbr> to Indicate Requirement Levels</a></cite>,    <abbr>RFCs</abbr> to Indicate Requirement Levels</a></cite>,
# Line 1104  of <abbr>XML</abbr> 1.0 Line 1816  of <abbr>XML</abbr> 1.0
1816    14</a>, <abbr title="Request for Comments">RFC</abbr> 2119,    14</a>, <abbr title="Request for Comments">RFC</abbr> 2119,
1817    <time datetime=1997-03>March 1997</time>.    <time datetime=1997-03>March 1997</time>.
1818    <em>This</em> version of the specification is referenced.</dd>    <em>This</em> version of the specification is referenced.</dd>
1819  <dt id=ref-INFOSET>INFOSET</dt>  <dt id=ref-MANAKAI>MANAKAI</dt>
1820    <dd class=ed>@@</dd>    <dd><cite><a href="http://suika.fam.cx/gate/2005/sw/manakai/DOM%20Extensions">
1821  <dt id=ref-XML10">XML10</dt>    manakai's <abbr>DOM</abbr> Extensions</a></cite>, editor's draft.  Work in
1822      progress.</dd>
1823    <dt id=ref-XML10>XML10</dt>
1824    <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
1825    Markup Language (<abbr>XML</abbr>) 1.0 (Fourth Edition)</a></cite>,    Markup Language (<abbr>XML</abbr>) 1.0 (Fourth Edition)</a></cite>,
1826    <abbr>W3C</abbr> Recommendation, <time datetime=2006-08-16>16 August    <abbr>W3C</abbr> Recommendation, <time datetime=2006-08-16>16 August
1827    2006</time>, edited in place <time datetime=2006-09-29>29 September    2006</time>, edited in place <time datetime=2006-09-29>29 September
1828    2006</time>.  Tje latest version of the specification is available at    2006</time>.  <em>This</em> version of the specification is referenced.  The
1829    <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
1830    <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>
1831  <dt id=ref-XML11>XML11</dt>  <dt id=ref-XML11>XML11</dt>
1832    <dd class=ed>@@</dd>    <dd><cite><a href="http://www.w3.org/TR/2006/REC-xml11-20060816/">Extensible
1833      Markup Language (<abbr>XML</abbr>) 1.1 (Second Edition)</a></cite>,
1834      <abbr>W3C</abbr> Recommendation, <time datetime=2006-08-16>16 August
1835      2006</time>, edited in place <time datetime=2006-09-29>29 September
1836      2006</time>.  <em>This</em> version of the specification is referenced.  The
1837      latest version of the specification is available at
1838      <code class=uri>&lt;<a href="http://www.w3.org/TR/xml11">http://www.w3.org/TR/xml11</a>></code>.</dd>
1839  </dl>  </dl>
1840  </div>  </div>
1841    
1842  <div id="informative-references" class="section informative reference">  <div id="informative-references" class="section informative reference">
1843  <h3>Non$B!>(Bnormative References</h3>  <h3>Non$B!>(Bnormative References</h3>
1844    
1845  <dl class=ed>  <dl>
1846  <dt id=ref-CSS>CSS</dt>  <dt id=ref-DOM1WD>DOM1WD</dt>
1847    <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
1848    Style Sheets Level 2 Revision 1 (<abbr>CSS</abbr> 2.1)    Model Specification</a></cite>, <abbr>W3C</abbr> Working Draft,
1849    Specification</a></cite>,    <time datetime=1997-12-09>9 December 1998</time>.</dd>
1850    <abbr title="World Wide Web Consortium">W3C</abbr> Candidate    <dd><cite><a href="http://www.w3.org/TR/WD-DOM-19980318/">Document Object
1851    Recommendation, <time datetime=2007-07-19>19 July 2007</time>.    Model Specification</a></cite>, <abbr>W3C</abbr> Working Draft,
1852    Work in progress.  The latest version of the specification is    <time datetime=1998-03-18>18 March 1998</time>.</dd>
1853    available at    <dd><cite><a href="http://www.w3.org/TR/1998/WD-DOM-19980416/">Document
1854    <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
1855  <dt id=ref-CSSOM>CSSOM</dt>    Draft, <time datetime=1998-04-16>16 April 1998</time>.</dd>
1856    <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>
1857    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
1858    <abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft,    Object Model (<abbr>DOM</abbr>) Level 3 Abstract Schemas Specification,
1859    <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
1860    The latest Editor's Draft of the specification is available at    July 2002</time>.  The latest version of the specification is available at
1861    <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>
1862  <dt id=ref-HTML5>HTML5</dt>  <dt id=ref-XSAPI>XSAPI</dt>
1863    <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>
1864    <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr>    Schema <abbr>API</abbr></a></cite>, <abbr>W3C</abbr> Member Submission,
1865    Working Draft.  Work in progress.</dd>    <time datetime=2004-03-09>9 March 2004</time>.  The latest version of the
1866  <dt id=ref-SAPI>SAPI</dt>    specification is available at
1867    <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>  
1868  </dl>  </dl>
1869  </div>  </div>
1870    

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.28

admin@suikawiki.org
ViewVC Help
Powered by ViewVC 1.1.24