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

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

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

revision 1.11 by wakaba, Tue Nov 13 13:00:14 2007 UTC revision 1.18 by wakaba, Sat Dec 1 14:32:30 2007 UTC
# Line 17  Line 17 
17  <body class="has-abstract">  <body class="has-abstract">
18    
19  <div class="header">  <div class="header">
20  <h1>manakai's XML Conformance Checking</h1>  <h1>manakai's <abbr>XML</abbr> Conformance Checking</h1>
21  <h2>Working Draft <time datetime=2007-11-13>13 November 2007</time></h2>  <h2>Working Draft <time datetime=2007-12-01>1 December 2007</time></h2>
22    
23  <dl class="versions-uri">  <dl class="versions-uri">
24  <dt>This Version</dt>  <dt>This Version</dt>
# Line 120  In addition, the order in which <a href= Line 120  In addition, the order in which <a href=
120  raised is undefined.</p>  raised is undefined.</p>
121  </div>  </div>
122    
 <div class="section" id=checking-dom>  
 <h2>Checking <abbr>DOM</abbr></h2>  
   
 <p>The following algorithms and definitions are applied to  
 <abbr>XML</abbr> documents; especially, they are not applied  
 to <abbr>HTML</abbr> documents.<!-- TODO: ref to HTML5 --></p>  
123    
124  <div class=section id=error-categories>  <div class=section id=error-categories>
125  <h3>Error Classification</h3>  <h2>Error Classification</h2>
126    
127  <p class=ed>If a <code>Document</code> node has no  <p class=ed>If a <code>Document</code> node has no
128  xml-well-formedness-error, entity-error, and unknown-error,  xml-well-formedness-error, entity-error, and unknown-error,
# Line 141  into a well$B!>(Bformed XML document. Line 135  into a well$B!>(Bformed XML document.
135  can be easily serialized into a valid XML document.</p>  can be easily serialized into a valid XML document.</p>
136  </div>  </div>
137    
138    <p class=ed>To be a conforming <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-validating">validating XML processor</a>,
139    ...</p>
140    
141  <p>Errors are classified into these  <p>Errors are classified into these
142  <dfn id=error-category title="error category">error categories</dfn>:</p>  <dfn id=error-category title="error category">error categories</dfn>:</p>
143    
# Line 159  can be easily serialized into a valid XM Line 156  can be easily serialized into a valid XM
156    </dd>    </dd>
157  <dt><dfn id=round-trip-error><code>round-trip-error</code></dfn></dt>  <dt><dfn id=round-trip-error><code>round-trip-error</code></dfn></dt>
158    <dd class=ed>@@</dd>    <dd class=ed>@@</dd>
159    <dt><dfn id=round-trip-warning><code>round-trip-warning</code></dfn></dt>
160      <dd>
161        <p>A <a href="#round-trip-warning"><code>round-trip-warning</code></a>
162        will be raised when a construct, which might not be restored to the same
163        construct when it is serialized and then re-parsed by a conforming
164        processor, is encountered.</p>
165        <div class="example memo">
166          <p>For a <code>Comment</code> node a
167          <a href="#round-trip-warning"><code>round-trip-warning</code></a> will
168          be raised, since <abbr>XML</abbr> processors are not required to
169          report texts of comments for applications.</p>
170        </div>
171      </dd>
172  <dt class=ed><dfn id=unknown-error><code>unknown-error</code></dfn>?</dt>  <dt class=ed><dfn id=unknown-error><code>unknown-error</code></dfn>?</dt>
173    <dd class=ed>@@</dd>    <dd class=ed>@@</dd>
174  <dt><dfn id=xml-misc-error><code>xml-misc-error</code></dt>  <dt><dfn id=xml-misc-error><code>xml-misc-error</code></dt>
# Line 179  can be easily serialized into a valid XM Line 189  can be easily serialized into a valid XM
189    <a href="@@/#dt-fatal">fatal error</a>)    <a href="@@/#dt-fatal">fatal error</a>)
190    that is not classified to any other <a href="#error-category">error    that is not classified to any other <a href="#error-category">error
191    category</a>. <span class=ed>@@ What errors fall into this category?</span></dd>    category</a>. <span class=ed>@@ What errors fall into this category?</span></dd>
192    <dt><dfn id=xml-misc-recommendation><code>xml-misc-recommendation</code></dfn></dt>
193      <dd>
194        <p>An
195        <a href="#xml-misc-recommendation"><code>xml-misc-recommendation</code></a>
196        will be raised if a <em class=rfc2119>SHOULD</em>$B!>(Blevel requirement
197        in <abbr>XML</abbr> specification is not met.</p>
198      </dd>
199  <dt><dfn id=xml-validity-error><code>xml-validity-error</code></dfn></dt>  <dt><dfn id=xml-validity-error><code>xml-validity-error</code></dfn></dt>
200    <dd>A violation of validity constraint in XML document.</dd>    <dd>A violation of validity constraint in XML document.</dd>
201  <dt><dfn id=xml-well-formedness-error><code>xml-well-formedness-error</code></dfn></dt>  <dt><dfn id=xml-well-formedness-error><code>xml-well-formedness-error</code></dfn></dt>
# Line 196  can be easily serialized into a valid XM Line 213  can be easily serialized into a valid XM
213    
214  </div>  </div>
215    
216    <div class=section id=parsing-xml>
217    <h2>Parsing <abbr>XML</abbr> Document</h2>
218    
219    <ul>
220    <li>If the <abbr>XML</abbr> document does not begin with an
221    <abbr>XML</abbr> declaration, then raise an
222    <a href="#xml-misc-recommentation" id=xmr-xml-decl><code>xml-misc-recommendation</code></a>.</li>
223    <li>If the replacement text of an entity declaration is
224    <code>&lt;</code>, then raise an
225    <a href="#xml-misc-warning" id=xmw-entity-value-lt><code>xml-misc-warning</code></a>.<!--
226    "strongly advised to avoid" in a Note in Section 2.3 of [XML10], [XML11].
227    --></li>
228    <li>If there is an element type declaration whose <code>Name</code>
229    value is already declared, then raise an
230    <a href="#xml-validity-error" id=vc-edunique><code>xml-validity-error</code></a>.</li>
231    <li>If attribute definition whose <code>Name</code> is
232    <code>xml:space</code> has <span class=ed>declared type different from
233    (default|preserve), (default), or (preserve)</span>, then raise an
234    <a href="#xml-misc-error" id=xme-ad-xml-space><code>xml-misc-error</code></a>.
235    <span class=ed>@@ duplication with
236    <a href="#xml-at-xml-space">#xml-at-xml-space</a>.<!--
237    <!ATTLIST e xml:space CDATA #IMPLIED xml:space CDATA #IMPLIED> --></span></li>
238    <li>If an empty-element tag is used for an element which is <em>not</em>
239    declared <code>EMPTY</code>, then raise an
240    <a href="#xml-misc-recommentation" id=xmr-emptyelemtag-not-empty><code>xml-misc-recommendation</code></a>.</li>
241    <li>If an empty-element tag is <em>not</em> used for an element which is
242    declared <code>EMPTY</code>, then raise an
243    <a href="#xml-misc-recommentation" id=xmr-empty-not-emptyelemtag><code>xml-misc-recommendation</code></a>.</li>
244    <!--
245    
246    #vc-PEinMarkupDecl Validity constraint: Proper Declaration/PE Nesting
247    #wfc-PEinInternalSubset Well-formedness constraint: PEs in Internal Subset
248    #ExtSubset Well-formedness constraint: External Subset
249    #PE-between-Decls Well-formedness constraint: PE Between Declarations
250    #GIMatch Well-formedness constraint: Element Type Match
251    #uniqattspec Well-formedness constraint: Unique Att Spec
252    #NoExternalRefs Well-formedness constraint: No External Entity References
253    #CleanAttrVals Well-formedness constraint: No < in Attribute Values
254    #vc-PEinGroup Validity constraint: Proper Group/PE Nesting
255    "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 ,)."
256    "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."
257    #condsec-nesting Validity constraint: Proper Conditional Section/PE Nesting
258    #wf-Legalchar Well-formedness constraint: Legal Character
259    #textent Well-formedness constraint: Parsed Entity
260    #norecursion Well-formedness constraint: No Recursion
261    #indtd Well-formedness constraint: In DTD
262    "External parsed entities SHOULD each begin with a text declaration."
263    "It is an error for a reference to an unparsed entity to appear in the EntityValue in an entity declaration."
264    #UniqueNotationName Validity constraint: Unique Notation Name
265    
266    @@ Need detailed review, but maybe should be in parsing phase
267    
268    #vc-check-rmd Validity constraint: Standalone Document Declaration
269    
270    @@ Need dtailed review
271    
272    #wf-entdeclared Well-formedness constraint: Entity Declared
273    #vc-entdeclared Validity constraint: Entity Declared
274    "For interoperability, valid documents SHOULD declare the entities amp, lt, gt, apos, quot, in the form specified in 4.6 Predefined Entities."
275    "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)."
276    
277    @@ flaged and then reported in DOM check phase
278    
279    "Entities encoded in UTF-16 MUST and entities encoded in UTF-8 MAY begin with the Byte Order Mark"
280    "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"
281    "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."
282    
283    @@ in parsing phase
284    
285    "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."
286    
287    -->
288    </ul>
289    </div>
290    
291    <div class="section" id=checking-dom>
292    <h2>Checking <abbr>DOM</abbr></h2>
293    
294    <p>The following algorithms and definitions are applied to
295    <abbr>XML</abbr> documents; especially, they are not applied
296    to <abbr>HTML</abbr> documents.<!-- TODO: ref to HTML5 --></p>
297    
298  <div class=section id=definitions>  <div class=section id=definitions>
299  <h3>Definitions</h3>  <h3>Definitions</h3>
300    
# Line 235  class <a href="#class-ControlChar10"><co Line 334  class <a href="#class-ControlChar10"><co
334  then raise an  then raise an
335  <a href="#xml-misc-warning" id=xmw-control-char><code>xml-misc-warning</code></a>.</li>  <a href="#xml-misc-warning" id=xmw-control-char><code>xml-misc-warning</code></a>.</li>
336  <li class=ed>@@ XML 1.1 support</li>  <li class=ed>@@ XML 1.1 support</li>
337  <li class=ed>@@ If U+000D, round-trip-error</li>  <li>If <var>s</var> contains a <code class=char>U+000D</code>
338    <code class=charname>CARRIAGE RETURN</code> character, then
339    raise a
340    <a href="#round-trip-error" id=rte-cr><code>round-trip-error</code></a>.
341    <span class=ed>@@ We should not raise duplicate errors for U+000D
342    in attribute values.  In addition, we should support a mode where
343    U+000D will be serialized as &#x000D; (so that no round-trip-error
344    will be raised).</span></li>
345  </ol>  </ol>
346    
347  <p>The algorithm  <p>The algorithm
348  <dfn id=algorithm-to-validate-a-name title="to validate a Name">to validate a  <dfn id=algorithm-to-validate-a-name title="to validate a Name">to validate a
349  <code>Name</code> (<dfn id=var-name><var>name</var></dfn>)</dfn> is defined  <code>Name</code> (<dfn id=var-name-s><var>s</var></dfn>)</dfn> is defined
350  as following:</p>  as following:</p>
351  <ol>  <ol>
352    <li>If <var>s</var> begins with the string <code>xml</code> (in any
353    case combination), then raise an
354    <a href="#xml-misc-warning" id=xmw-reserved-name><code>xml-misc-warning</code></a>.
355    <span class=ed>@@ except for attribute names <code>xml:lang</code>,
356    <code>xml:space</code>, <code>xml:base</code>, <code>xml:id</code>,
357    <code>xmlns</code>, <code>xmlns:<var>*</var></code>,
358    pi name <code>xml-stylesheet</code>.</span><!--
359    "names beginning with a match to (('X'|'x')('M'|'m')('L'|'l')) are reserved for standardization in this or future versions of this specification.":
360    xml:base and xml:id specifications violate to this sentense!
361    --></li>
362    <!-- COLON in Name is a lowercase "should not" in a Note of [XML10],
363    [XML11]. -->
364  <li class=ed>@@</li>  <li class=ed>@@</li>
365  </ol>  </ol>
366    
367  <p>The algorithm  <p>The algorithm
368  <dfn id=algorithm-to-validate-a-ncname title="to validate an NCName">to  <dfn id=algorithm-to-validate-an-ncname title="to validate an NCName">to
369  validate an <code>NCName</code> (<dfn id=var-name><var>name</var></dfn>)</dfn>  validate an <code>NCName</code> (<dfn id=var-name><var>name</var></dfn>)</dfn>
370  is defined as following:</p>  is defined as following:</p>
371  <ol>  <ol>
372  <li class=ed>@@</li>  <li class=ed>@@</li>
373  </ol>  </ol>
374    
375  <p>To <dfn id=algorithm-to-validate-a-public-identifier title="validate a public identifier">validate  <p>To
376    <dfn id=algorithm-to-validate-a-public-identifier title="validate a public identifier">validate
377  a public identifier (<dfn id=var-pid><var>pid</var></dfn>)</dfn>, the  a public identifier (<dfn id=var-pid><var>pid</var></dfn>)</dfn>, the
378  algorithm below <em class=rfc2119>MUST</em> be used:</p>  following algorithm <em class=rfc2119>MUST</em> be used:</p>
379  <ol>  <ol>
380      <li>If <var>pid</var> is <code>null</code>, abort these steps.</li>
381    <li>If <var>pid</var> contains any character    <li>If <var>pid</var> contains any character
382    that is outside of the range of <code>#x20 | #xD | #xA |    that is outside of the range of <code>#x20 | #xD | #xA |
383    [a-zA-Z0-9] | [-'()+,./:=?;!*#@$_%]</code><!-- @@ TODO: formal def -->,    [a-zA-Z0-9] | [-'()+,./:=?;!*#@$_%]</code><!-- @@ TODO: formal def -->,
# Line 274  algorithm below <em class=rfc2119>MUST</ Line 394  algorithm below <em class=rfc2119>MUST</
394    <code class=char>U+0020</code> <code class=charname>SPACE</code> character    <code class=char>U+0020</code> <code class=charname>SPACE</code> character
395    immediately followed by another <code class=char>U+0020</code>    immediately followed by another <code class=char>U+0020</code>
396    <code class=charname>SPACE</code> character in <var>pid</var>, then it is a    <code class=charname>SPACE</code> character in <var>pid</var>, then it is a
397    <a href="#round-trip-error" id=rte-pubid-space><code>round-trip-error</code></a>.</li>    <a href="#round-trip-error" id=rte-pubid-space><code>round-trip-error</code></a>.
398      <span class=ed>Is this really a roundtripness problem?  XML spec
399      does only define the way to match public identifiers in fact, no
400      canonical form.</span></li>
401    <li class=ed>@@ Should we check formal-public-identifierness?</li>    <li class=ed>@@ Should we check formal-public-identifierness?</li>
402  </ol>  </ol>
403    
404    <p>To
405    <dfn id=algorithm-to-validate-a-system-identifier title="validate a system identifier">validate
406    a system identifier (<dfn id=var-sid><var>sid</var></dfn>)</dfn>, the
407    following algorithm <em class=rfc2119>MUST</em> be used:</p>
408    <ol>
409      <li>If <var>sid</var> is <code>null</code>, abort these steps.</li>
410      <li>If <var>sid</var> contains both <code class=char>U+0022</code>
411      <code class=charname>QUOTATION MARK</code> (<code class=char>"</code>) and
412      <code class=char>U+0027</code> <code class=charname>APOSTROPHE</code>
413      (<code class=char>'</code>) characters, raise an
414      <a href="#xml-well-formedness-error" id=wfe-sid-lit><code>xml-well-formedness-error</code></a>.</li>
415      <li>If <var>sid</var> contains at least one <code class=char>U+0023</code>
416      <code class=charname>NUMBER SIGN</code> (<code class=char>#</code>)
417      character, then raise an
418      <a href="#xml-misc-error" id=xme-sid-fragment><code>xml-misc-error</code></a>.</li>
419      <li class=ed>@@ If <var>sid</var> cannot be converted to a URI
420      reference, then raise a fact-level error (xml-misc-warning?).<!--
421      XML 1.0 has no conformance language for system identifier being
422      a URI reference. --></li>
423    </ol>
424    
425  </div>  </div>
426    
427  <div class=section id=checking-node>  <div class=section id=checking-node>
# Line 290  following:</p> Line 434  following:</p>
434  <dt>If <var>n</var> is an <code>Attr</code> node</dt>  <dt>If <var>n</var> is an <code>Attr</code> node</dt>
435    <dd>    <dd>
436      <ol>      <ol>
437      <li><a href="#algorithm-to-validate-a-ncname">Validate the      <li><a href="#algorithm-to-validate-an-ncname">Validate the
438      <code>localName</code> attribute value as an <code>NCName</code></a>.</li>      <code>localName</code> attribute value as an <code>NCName</code></a>.</li>
439      <li>If the <code>prefix</code> attribute value is different from      <li>If the <code>prefix</code> attribute value is different from
440      <code>null</code>, then <a href="#algorithm-to-validate-a-ncname">validate      <code>null</code>, then <a href="#algorithm-to-validate-an-ncname">validate
441      the <code>prefix</code> attribute value as an <code>NCName</code></a>.</li>      the <code>prefix</code> attribute value as an <code>NCName</code></a>.</li>
442      <li>For each node <dfn id=var-attr-nc><var>n<sub><var>c</var></sub></var></dfn> in the      <li>For each node <dfn id=var-attr-nc><var>n<sub><var>c</var></sub></var></dfn> in the
443      <code>childNodes</code> list of <var>n</var>,      <code>childNodes</code> list of <var>n</var>,
# Line 308  following:</p> Line 452  following:</p>
452        <a href="#algorithm-to-check-a-node" title="check a node">check        <a href="#algorithm-to-check-a-node" title="check a node">check
453        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>
454        </ol></li>        </ol></li>
455        <li>If <code>nodeName</code> attribute of <var>n</var> is
456        <code>xml:space</code> <span class=ed>@@ or {xml namespace}:space ?</span>
457        and <code>value</code> attribute of <var>n</var> is neither
458        <code>default</code> nor <code>preserve</code>, then it is an
459        <a href="#xml-misc-error" id=xme-attr-xml-space><code>xml-misc-error</code></a>.<!--
460        Note that <!ATTLIST e xml:space (default|preserve) "a">...
461        <e xml:space="default"/> is conforming and valid. --></li>
462        <li class=ed>@@ xml:lang value is not a language tag [RFC 3066 or its
463        successor] or an empty string, then xml-misc-warning
464        (a "fact"-level error; not an XML error).</li>
465      <li class=ed>@@ <code>specified</code>,      <li class=ed>@@ <code>specified</code>,
466      <code>manakaiAttributeType</code></li>      <code>manakaiAttributeType</code> (#ValueType Validity constraint: Attribute Value Type)</li>
467        <!-- xml:space MUST be declared to be valid. -->
468        <li>Let <dfn id=var-v><var>v</var></dfn> be the value of the
469        attribute <code>value</code> of <var>n</var>.</li>
470        <li>Validate the <var>n</var> against the <span class=ed>declared
471        type</span> as following:
472          <dl class=switch>
473          <dt class=ed><code>ID_ATTR</code></dt>
474            <dd>
475              <ol>
476              <li><span class=ed>Validate <var>v</var> as an
477              <code>Name</code>.</span>  If it fails, then raise an
478              <a href="#xml-validity-error" id=vc-id-name><code>xml-validity-error</code></a>.</li>
479              <li><span class=ed>If <code>ID</code> <var>v</var> is defined,</span>
480              then raise an  
481              <a href="#xml-validity-error" id=vc-id-duplication><code>xml-validity-error</code></a>.</li>
482              </ol>
483            </dd>
484          <dt class=ed>IDREF_ATTR</dt>
485            <dd>
486              <ol>
487              <li><span class=ed>Validate <var>v</var> as an
488              <code>Name</code>.</span>  If it fails, then raise an
489              <a href="#xml-validity-error" id=vc-idref-name><code>xml-validity-error</code></a>.</li>
490              <li><span class=ed>If <code>ID</code> <var>v</var> is NOT
491              defined,</span> then raise an  
492              <a href="#xml-validity-error" id=vc-idref-match><code>xml-validity-error</code></a>.</li>
493              </ol>
494            </dd>
495          <dt class=ed>IDREFS_ATTR</dt>
496            <dd class=ed>@@</dd>
497          <dt class=ed>ENTITY_ATTR</dt>
498            <dd>
499              <ol>
500              <li><span class=ed>Validate <var>v</var> as an
501              <code>Name</code>.</span>  If it fails, then raise an
502              <a href="#xml-validity-error" id=vc-entname-name><code>xml-validity-error</code></a>.</li>
503              <li><span class=ed>If <code>Entity</code> <var>v</var> is NOT
504              defined,</span> then raise an  
505              <a href="#xml-validity-error" id=vc-entname-match><code>xml-validity-error</code></a>.</li>
506              </ol>
507            </dd>
508          <dt class=ed>ENTITIES_ATTR</dt>
509            <dd class=ed>@@</dd>
510          <dt class=ed>NMTOKEN_ATTR</dt>
511            <dd>
512              <ol>
513              <li><span class=ed>Validate <var>v</var> as an
514              <code>Nmtoken</code>.</span>  If it fails, then raise an
515              <a href="#xml-validity-error" id=vc-nmtok-name><code>xml-validity-error</code></a>.</li>
516              </ol>
517            </dd>
518          <dt class=ed>NMTOKENS_ATTR</dt>
519            <dd class=ed>@@</dd>
520          <dt class=ed>NOTATION_ATTR</dt>
521            <dd class=ed><var>v</var> must be one of enumerated values.
522            If not, then raise an
523            <a href="#xml-validity-error" id=vc-notatn-match><code>xml-validity-error</code></a>.</dd>
524          <dt class=ed>ENUMERATED_ATTR</dt>
525            <dd class=ed><var>v</var> must be one of enumerated values.
526            If not, then raise an
527            <a href="#xml-validity-error" id=vc-enum><code>xml-validity-error</code></a>.</dd>
528          <dt class=ed>@@</dt>
529          </dl>
530        </li>
531        <li>If <span class=ed>type ID and default is NOT #IMPLIED or #REQUIRED</span>, then
532        raise an
533        <a href="#xml-validity-error" id=vc-id-default><code>xml-validity-error</code></a>.</li>
534        <li class=ed>@@ #FixedAttr Validity constraint: Fixed Attribute Default</li>
535        <li class=ed>@@ strict serialization error for U+000D, U+000A, and
536        U+0009 characters, leading/trailing U+0020, and U+0020{2,} string?</li>
537      </ol>      </ol>
538    </dd>    </dd>
539  <dt>If <var>n</var> is an <code>AttributeDefinition</code> node</dt>  <dt>If <var>n</var> is an <code>AttributeDefinition</code> node</dt>
540    <dd>    <dd>
541      <ol>      <ol>
542      <li class=ed></li>      <li class=ed></li>
543        <li>If <code>nodeName</code> attribute of <var>n</var> is
544        <code>xml:space</code> <span class=ed>@@ or {xml namespace}:space ?</span>
545        and <span class=ed>its declared type is different from (default|preserve),
546        (default), or (preserve)</span>, then raise an
547        <a href="#xml-misc-error" id=xme-at-xml-space><code>xml-misc-error</code></a>.</li>
548      <li>For each node <dfn id=var-ad-nc><var>n<sub><var>c</var></sub></var></dfn> in the      <li>For each node <dfn id=var-ad-nc><var>n<sub><var>c</var></sub></var></dfn> in the
549      <code>childNodes</code> list of <var>n</var>,      <code>childNodes</code> list of <var>n</var>,
550        <ol>        <ol>
# Line 329  following:</p> Line 558  following:</p>
558        <a href="#algorithm-to-check-a-node" title="check a node">check        <a href="#algorithm-to-check-a-node" title="check a node">check
559        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>
560        </ol></li>        </ol></li>
561        <li class=ed>If <code>NOTATION_ATTR</code>, enumerated values MUST
562        be declared.  If not, then raise an
563        <a href="#xml-validity-error" id=vc-notatn-declared><code>xml-validity-error</code></a>.</li>
564        <li class=ed>If <code>NOTATION_ATTR</code> or <code>ENUMERATED_ATTR</code>,
565        values MUST all be distinct.  If not, then raise an
566        <a href="#xml-validity-error" id=vc-no-duplicate-tokens><code>xml-validity-error</code></a>.</li>
567        <li class=ed>If <code>NOTATION_ATTR</code> on an <code>EMPTY</code>
568        element, then raise an
569        <a href="#xml-validity-error" id=vc-no-notation-empty><code>xml-validity-error</code></a>.</li>
570        <li class=ed>@@ #defattrvalid Validity constraint: Attribute Default Value Syntactically Correct</li>
571      </ol>      </ol>
572    </dd>    </dd>
573  <dt>If <var>n</var> is a <code>CDATASection</code> node</dt>  <dt>If <var>n</var> is a <code>CDATASection</code> node</dt>
# Line 338  following:</p> Line 577  following:</p>
577      <code>data</code> attribute value as an <abbr>XML</abbr> character      <code>data</code> attribute value as an <abbr>XML</abbr> character
578      data</a>.</li>      data</a>.</li>
579      <li>If the <code>data</code> attribute value contains      <li>If the <code>data</code> attribute value contains
580      a string <code>]]></code>, then it is an      a string <code>]]></code>, then raise an
581      <a href="#xml-well-formedness-error" id=wfe-cs-mse><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-cs-mse><code>xml-well-formedness-error</code></a>.<!-- "for compatibility" --></li>
582      <li>If the <code>childNodes</code> list of <var>n</var> contains      <li>If the <code>childNodes</code> list of <var>n</var> contains
583      any nodes, they are in      any nodes, they are in
584      <a href="#xml-well-formedness-error" id=wfe-cs-child><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-cs-child><code>xml-well-formedness-error</code></a>.</li>
# Line 348  following:</p> Line 587  following:</p>
587  <dt>If <var>n</var> is a <code>Comment</code> node</dt>  <dt>If <var>n</var> is a <code>Comment</code> node</dt>
588    <dd>    <dd>
589      <ol>      <ol>
590        <li>Raise an
591        <a href="#round-trip-warning" id=rtw-comment><code>round-trip-warning</code></a>.</li>
592      <li><a href="#algorithm-to-validate-an-xml-character-data">Validate the      <li><a href="#algorithm-to-validate-an-xml-character-data">Validate the
593      <code>data</code> attribute value as an <abbr>XML</abbr> character      <code>data</code> attribute value as an <abbr>XML</abbr> character
594      data</a>.</li>      data</a>.</li>
595      <li>If the <code>data</code> attribute value contains      <li>If the <code>data</code> attribute value contains
596      a string <code>--</code>, or if it ends with a character      a string <code>--</code>, or if it ends with a character
597      <code>-</code>, then it is an      <code>-</code>, then raise an
598      <a href="#xml-well-formedness-error" id=wfe-comment-com><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-comment-com><code>xml-well-formedness-error</code></a>.<!--
599        "for compatibility" --></li>
600      <li>If the <code>childNodes</code> list of <var>n</var> contains      <li>If the <code>childNodes</code> list of <var>n</var> contains
601      any nodes, they are in      any nodes, they are in
602      <a href="#xml-well-formedness-error" id=wfe-comment-child><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-comment-child><code>xml-well-formedness-error</code></a>.</li>
# Line 414  following:</p> Line 656  following:</p>
656  <dt>If <var>n</var> is a <code>DocumentType</code> node</dt>  <dt>If <var>n</var> is a <code>DocumentType</code> node</dt>
657    <dd>    <dd>
658      <ol>      <ol>
659      <li><a href="#algorithm-to-validate-a-ncname">Validate the      <li><a href="#algorithm-to-validate-an-ncname">Validate the
660      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>
661        <li>Follow the following substeps:
662          <ol>
663          <li>If <code>ownerDocument</code> attribute of <var>n</var> is
664          <code>null</code>, then abort these substeps.</li>
665          <li>If <code>documentElement</code> attribute of the node
666          set to <code>ownerDocument</code> attribute of <var>n</var> is
667          <code>null</code>, then abort these substeps.</li>
668          <li>If <code>nodeName</code> attribute of the node set to
669          <code>documentElement</code> attribute of the node set to
670          <code>ownerDocument</code> attribute of <var>n</var> is
671          different from <code>nodeName</code> of <var>n</var>,
672          then raise an
673          <a href="#xml-validity-error" id=vc-roottype><code>xml-validity-error</code></a>.</li></li>
674          </ol>
675        </li>
676      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate
677      the <code>publicId</code> attribute value as a public identifier</a>.</li>      the <code>publicId</code> attribute value as a public identifier</a>.</li>
678      <li>If the <code>systemId</code> attribute value contains      <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate
679      both <code>"</code> and <code>'</code> characters, it is a      the <code>systemId</code> attribute value as a system identifier</a>.</li>
680      <a href="#xml-well-formedness-error" id=wfe-dt-system-id><code>xml-well-formedness-error</code></a>.</li>      <li>If the <code>publicId</code> attribute value of <var>n</var> is
681      <!-- publicId = non-null and systemId = null -->      <em>not</em> <code>null</code> and the <code>systemId</code> attribute
682        value of <var>n</var> is <code>null</code>, then raise an
683        <a href="#xml-well-formedness-error" id=wfe-dt-sid><code>xml-well-formedness-error</code></a>.
684        <span class=ed>@@ publicId == null?  Or, publicId == ""</span></li>
685      <li>For each node <dfn id=var-dt-nc><var>n<sub><var>c</var></sub></var></dfn>      <li>For each node <dfn id=var-dt-nc><var>n<sub><var>c</var></sub></var></dfn>
686      in the <code>childNodes</code> list of <var>n</var>,      in the <code>childNodes</code> list of <var>n</var>,
687        <ol>        <ol>
# Line 433  following:</p> Line 693  following:</p>
693        <a href="#algorithm-to-check-a-node" title="check a node">check        <a href="#algorithm-to-check-a-node" title="check a node">check
694        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>        <var>n<sub><var>c</var></sub></var></a> recusrively.</li>
695        </ol></li>        </ol></li>
696      <li class=ed>@@ <code>entities</code>, <code>notations</code>,      <li>For each node in the <code>entities</code>, <code>notations</code>,
697      <code>elementTypes</code>, externally declared?</li>      and <code>elementTypes</code> lists of <var>n</var>,
698        <a href="#algorithm-to-check-a-node" title="check a node">check the
699        node</a> recursively.</li>
700        <li class=ed>@@ externally declared?</li>
701      </ol>      </ol>
702    </dd>    </dd>
703  <dt>If <var>n</var> is an <code>Element</code> node</dt>  <dt>If <var>n</var> is an <code>Element</code> node</dt>
704    <dd>    <dd>
705      <ol>      <ol>
706      <li><a href="#algorithm-to-validate-a-ncname">Validate the      <li><a href="#algorithm-to-validate-an-ncname">Validate the
707      <code>localName</code> attribute value as an <code>NCName</code></a>.</li>      <code>localName</code> attribute value as an <code>NCName</code></a>.</li>
708      <li>If the <code>prefix</code> attribute value is different from      <li>If the <code>prefix</code> attribute value is different from
709      <code>null</code>, then <a href="#algorithm-to-validate-a-ncname">validate      <code>null</code>, then <a href="#algorithm-to-validate-an-ncname">validate
710      the <code>prefix</code> attribute value as an <code>NCName</code></a>.</li>      the <code>prefix</code> attribute value as an <code>NCName</code></a>.</li>
711      <li>For each node <dfn id=var-element-nc><var>n<sub><var>c</var></sub></var></dfn>      <li>For each node <dfn id=var-element-nc><var>n<sub><var>c</var></sub></var></dfn>
712      in the <code>childNodes</code> list of <var>n</var>,      in the <code>childNodes</code> list of <var>n</var>,
# Line 461  following:</p> Line 724  following:</p>
724        <a href="#algorithm-to-check-a-node" title="check a node">check        <a href="#algorithm-to-check-a-node" title="check a node">check
725        <var>n<sub><var>c</var></sub></var></a> recursively.</li>        <var>n<sub><var>c</var></sub></var></a> recursively.</li>
726        </ol></li>        </ol></li>
727        <li class=ed>@@ #elementvalid Validity constraint: Element Valid</li>
728        <li>Let <var>attrs</var> be the value of the <code>attribute</code>
729        attribute of <var>n</var>.  Check conformance of <var>attrs</var>
730        as following:
731          <ol>
732          <li>If <var>attrs</var> contains an <code>Attr</code> node whose
733          <code>nodeName</code> attribute value is equal to that of another
734          <code>Attr</code> node in <var>attrs</var>, then raise an
735          <a href="#xml-well-formedness-error" id=wfe-uniqattspec><code>xml-well-formedness-error</code></a>.<!--
736          #uniqattspec Well-formedness constraint: Unique Att Spec --></li>
737          <li class=ed>@@ #RequiredAttr Validity constraint: Required Attribute</li>
738          </ol>
739        </li>
740      </ol>      </ol>
741    </dd>    </dd>
742  <dt>If <var>n</var> is an <code>ElementTypeDefinition</code> node</dt>  <dt>If <var>n</var> is an <code>ElementTypeDefinition</code> node</dt>
# Line 470  following:</p> Line 746  following:</p>
746      <li>If the <code>childNodes</code> list of <var>n</var> contains      <li>If the <code>childNodes</code> list of <var>n</var> contains
747      any nodes, they are in      any nodes, they are in
748      <a href="#xml-well-formedness-error" id=wfe-et-child><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-et-child><code>xml-well-formedness-error</code></a>.</li>
749      </ol>      <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>
750    </dd>      <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>
751  <dt>If <var>n</var> is an <code>Entity</code> node</dt>      <li class=ed>@@ #vc-MixedChildrenUnique
752    <dd>      Validity constraint: No Duplicate Types</li>
753      <ol>      <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>
754      <li>An <a href="#entity-error" id=ee-entity-node><code>entity-error</code></a> <span class=ed>@@ if !notationName</span>.</li>      <li>If there is more than one <code>AttributeDefinition</code> node
755      <li><a href="#algorithm-to-validate-a-ncname">Validate the      with <span class=ed>attribute type <code>ID</code></span> in the
756        <code>NamedNodeMap</code> list contained in the
757        <code>attributeDefinitions</code> attribute of <var>n</var>, then raise an
758        <a href="#xml-validity-error" id=vc-one-id-per-el><code>xml-validity-error</code></a>.</li>
759        <li>If there is more than one <code>AttributeDefinition</code> node
760        with <span class=ed>attribute type <code>NOTATION</code></span> in the
761        <code>NamedNodeMap</code> list contained in the
762        <code>attributeDefinitions</code> attribute of <var>n</var>, then raise an
763        <a href="#xml-validity-error" id=vc-one-notation-per><code>xml-validity-error</code></a>.</li>
764        <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>
765        </ol>
766      </dd>
767    <dt>If <var>n</var> is an <code>Entity</code> node whose
768    <code>notationName</code> attribute value is <code>null</code> (i.e. a
769    parsed entity)</dt>
770      <dd>
771        <ol>
772        <li>Raise an
773        <a href="#entity-error" id=ee-entity-node><code>entity-error</code></a>.</li>
774        <li><a href="#algorithm-to-validate-an-ncname">Validate the
775      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>
776      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate
777      the <code>publicId</code> attribute value as a public identifier</a>.</li>      the <code>publicId</code> attribute value as a public identifier</a>.</li>
778      <li>If the <code>systemId</code> attribute value contains      <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate
779      both <code>"</code> and <code>'</code> characters, it is a      the <code>systemId</code> attribute value as a system identifier</a>.</li>
780      <a href="#xml-well-formedness-error" id=wfe-dt-system-id><code>xml-well-formedness-error</code></a>.</li>      <li>If the <code>publicId</code> attribute value of <var>n</var> is
781      <!-- publicId = non-null and systemId = null -->      <em>not</em> <code>null</code> and the <code>systemId</code> attribute
782      <li class=ed>@@ <code>notationName</code></li>      value of <var>n</var> is <code>null</code>, then raise an
783        <a href="#xml-well-formedness-error" id=wfe-entity-sid><code>xml-well-formedness-error</code></a>.</li>
784      <li>For each node <dfn id=var-entity-nc><var>n<sub><var>c</var></sub></var></dfn>      <li>For each node <dfn id=var-entity-nc><var>n<sub><var>c</var></sub></var></dfn>
785      in the <code>childNodes</code> list of <var>n</var>,      in the <code>childNodes</code> list of <var>n</var>,
786        <ol>        <ol>
# Line 503  following:</p> Line 799  following:</p>
799        </ol></li>        </ol></li>
800      </ol>      </ol>
801    </dd>    </dd>
802    <dt>If <var>n</var> is an <code>Entity</code> node whose
803    <code>notationName</code> attribute value is <em>not</em> <code>null</code>
804    (i.e. an unparsed entity)</dt>
805      <dd>
806        <ol>
807        <li><a href="#algorithm-to-validate-an-ncname">Validate the
808        <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>
809        <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate
810        the <code>publicId</code> attribute value as a public identifier</a>.</li>
811        <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate
812        the <code>systemId</code> attribute value as a system identifier</a>.</li>
813        <li>If the <code>systemId</code> attribute value of <var>n</var> is
814        <code>null</code>, then raise an
815        <a href="#xml-well-formedness-error" id=wfe-uentity-sid><code>xml-well-formedness-error</code></a>.</li>
816        <li><a href="#algorithm-to-validate-an-ncname">Validate the
817        <code>notationName</code> attribute value of <var>n</var> as an
818        <code>NCName</code></a>.</li>
819        <li class=ed>@@ #not-declared Validity constraint: Notation Declared</li>
820        <li>If the <code>childNodes</code> list of <var>n</var> contains
821        any nodes, they are in
822        <a href="#xml-well-formedness-error" id=wfe-uentity-child><code>xml-well-formedness-error</code></a>.</li>
823        </ol>
824      </dd>
825  <dt>If <var>n</var> is an <code>EntityReference</code> node</dt>  <dt>If <var>n</var> is an <code>EntityReference</code> node</dt>
826    <dd>    <dd>
827      <ol>      <ol>
828      <li>An <a href="#entity-error" id=ee-er-node><code>entity-error</code></a>.</li>      <li>An <a href="#entity-error" id=ee-er-node><code>entity-error</code></a>.</li>
829      <li><a href="#algorithm-to-validate-a-ncname">Validate the      <li><a href="#algorithm-to-validate-an-ncname">Validate the
830      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>
831      <li>For each node <dfn id=var-er-nc><var>n<sub><var>c</var></sub></var></dfn>      <li>For each node <dfn id=var-er-nc><var>n<sub><var>c</var></sub></var></dfn>
832      in the <code>childNodes</code> list of <var>n</var>,      in the <code>childNodes</code> list of <var>n</var>,
# Line 530  following:</p> Line 849  following:</p>
849  <dt>If <var>n</var> is a <code>Notation</code> node</dt>  <dt>If <var>n</var> is a <code>Notation</code> node</dt>
850    <dd>    <dd>
851      <ol>      <ol>
852      <li><a href="#algorithm-to-validate-a-ncname">Validate the      <li><a href="#algorithm-to-validate-an-ncname">Validate the
853      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>      <code>nodeName</code> attribute value as an <code>NCName</code></a>.</li>
854      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate      <li><a href="#algorithm-to-validate-a-public-identifier" title="validate a public identifier">Validate
855      the <code>publicId</code> attribute value as a public identifier</a>.</li>      the <code>publicId</code> attribute value as a public identifier</a>.</li>
856      <li>If the <code>systemId</code> attribute value contains      <li><a href="#algorithm-to-validate-a-system-identifier" title="validate a system identifier">Validate
857      both <code>"</code> and <code>'</code> characters, it is a      the <code>systemId</code> attribute value as a system identifier</a>.</li>
     <a href="#xml-well-formedness-error" id=wfe-dt-system-id><code>xml-well-formedness-error</code></a>.</li>  
858      <li>If the <code>childNodes</code> list of <var>n</var> contains      <li>If the <code>childNodes</code> list of <var>n</var> contains
859      any nodes, they are in      any nodes, they are in
860      <a href="#xml-well-formedness-error" id=wfe-notation-child><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-notation-child><code>xml-well-formedness-error</code></a>.</li>
# Line 545  following:</p> Line 863  following:</p>
863  <dt>If <var>n</var> is a <code>ProcessingInstruction</code> node</dt>  <dt>If <var>n</var> is a <code>ProcessingInstruction</code> node</dt>
864    <dd>    <dd>
865      <ol>      <ol>
866      <li><a href="#algorithm-to-validate-a-ncname">Validate the      <li>If the <code>target</code> attribute value matches to the string
867      <code>target</code> attribute value as an <code>NCName</code></a>.</li>      <code>xml</code> in any case combination, then raise a
     <li>If the <code>target</code> attribute value matches to  
     <code>XML</code> case-insensitively, then it is a  
868      <a href="#xml-well-formedness-error" id=wfe-pi-xml><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-pi-xml><code>xml-well-formedness-error</code></a>.</li>
869      <li><a href="#algorithm-to-validate-an-xml-character-data">Validate the      <li>Otherwise, <a href="#algorithm-to-validate-an-ncname">validate the
870      <code>data</code> attribute value as an <abbr>XML</abbr> character      <code>target</code> attribute value as an <code>NCName</code></a>.</li>
871        <li>Then,
872        <a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML character data">validate
873        the <code>data</code> attribute value as an <abbr>XML</abbr> character
874      data</a>.</li>      data</a>.</li>
875      <li>If the <code>data</code> attribute value contains      <li>If the <code>data</code> attribute value contains a string
876      a string <code>?></code>, or starts with either      <code>?></code>, then raise a
877      <code class=char>U+0009</code>, <code class=char>U+000A</code>,      <a href="#xml-well-formedness-error" id=wfe-pi-pic><code>xml-well-formedness-error</code></a>.</li>
878      <code class=char>U+000D</code>, or <code class=char>U+0020</code>      <li>If the <code>data</code> attribute value starts with either
879      character, then it is a      <code class=char>U+0009</code> <code class=charname>CHARACTER
880      <a href="#round-trip-error" id=rte-pi-data><code>round-trip-error</code></a>.</li>      TABULATION</code>, <code class=char>U+000A</code> <code class=charname>LINE
881        FEED</code>, <code class=char>U+000D</code> <code class=charname>CARRIAGE
882        RETURN</code>, or <code class=char>U+0020</code>
883        <code class=charname>SPACE</code> character, then raise a
884        <a href="#round-trip-error" id=rte-pi-s><code>round-trip-error</code></a>.</li>
885      <li>If the <code>childNodes</code> list of <var>n</var> contains      <li>If the <code>childNodes</code> list of <var>n</var> contains
886      any nodes, they are in      any nodes, then raise an
887      <a href="#xml-well-formedness-error" id=wfe-pi-child><code>xml-well-formedness-error</code></a>.</li>      <a href="#xml-well-formedness-error" id=wfe-pi-child><code>xml-well-formedness-error</code></a>.</li>
888      </ol>      </ol>
889    </dd>    </dd>
Legend:
Removed from v.1.11  
changed lines
  Added in v.1.18
admin@suikawiki.org
 ViewVC Help
Powered by ViewVC 1.1.24