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

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

Parent Directory | Revision Log | View Patch Patch

-revision 1.11 by wakaba,
Tue Nov 13 13:00:14 2007 UTC
+revision 1.25 by wakaba,
Sat Mar 29 02:22:57 2008 UTC
 Line 17
  <body class="has-abstract">
  <div class="header">
- <h1>manakai's XML Conformance Checking</h1>
+ <h1>manakai's <abbr>XML</abbr> Conformance Checking</h1>
- <h2>Working Draft <time datetime=2007-11-13>13 November 2007</time></h2>
+ <h2>Working Draft <time datetime=2008-03-29>29 March 2008</time></h2>
  <dl class="versions-uri">
  <dt>This Version</dt>
 Line 42
        >[email protected]</a>&gt;</code></dd>
  </dl>
- <p class="copyright" lang="en">&#xA9; <time>2007</time> <a
+ <p class="copyright" lang="en">&#xA9; <time>2007</time>$B!>(B<time>2008</time> <a
      href="http://suika.fam.cx/~wakaba/who?" rel="author">Wakaba</a>.
  Permission is granted to copy, distribute and/or modify this document
  under the terms of the <a rel="license"
 Line 118 
 else in this specification is normative.
  <p><span class=ed>Algorithm is normative but non-normative</span>.
  In addition, the order in which <a href="#errors">errors</a> are
  raised is undefined.</p>
- </div>
- <div class="section" id=checking-dom>
+ <p>This document sometimes cites parts of <abbr>XML</abbr> 1.0 specification
- <h2>Checking <abbr>DOM</abbr></h2>
+ by hyperlinks.  When the document being processed is an <abbr>XML</abbr> 1.1
+ document, however, corresponding parts of the <abbr>XML</abbr> 1.1
+ specification should be consulted instead.</p>
+ </div>
- <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>
  <div class=section id=error-categories>
- <h3>Error Classification</h3>
+ <h2>Error Classification</h2>
  <p class=ed>If a <code>Document</code> node has no
  xml-well-formedness-error, entity-error, and unknown-error,
-Line 141 
 into a well$B!>(Bformed XML document.
+Line 140 
 into a well$B!>(Bformed XML document.
  can be easily serialized into a valid XML document.</p>
  </div>
+ <p class=ed>To be a conforming <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-validating">validating XML processor</a>,
+ ...</p>
  <p>Errors are classified into these
  <dfn id=error-category title="error category">error categories</dfn>:</p>
-Line 159 
 can be easily serialized into a valid XM
+Line 161 
 can be easily serialized into a valid XM
    </dd>
  <dt><dfn id=round-trip-error><code>round-trip-error</code></dfn></dt>
    <dd class=ed>@@</dd>
+ <dt><dfn id=round-trip-warning><code>round-trip-warning</code></dfn></dt>
+   <dd>
+     <p>A <a href="#round-trip-warning"><code>round-trip-warning</code></a>
+     will be raised when a construct, which might not be restored to the same
+     construct when it is serialized and then re-parsed by a conforming
+     processor, is encountered.</p>
+     <div class="example memo">
+       <p>For a <code>Comment</code> node a
+       <a href="#round-trip-warning"><code>round-trip-warning</code></a> will
+       be raised, since <abbr>XML</abbr> processors are not required to
+       report texts of comments for applications.</p>
+     </div>
+   </dd>
  <dt class=ed><dfn id=unknown-error><code>unknown-error</code></dfn>?</dt>
    <dd class=ed>@@</dd>
  <dt><dfn id=xml-misc-error><code>xml-misc-error</code></dt>
-Line 179 
 can be easily serialized into a valid XM
+Line 194 
 can be easily serialized into a valid XM
    <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>
+   <dd>
+     <p>An
+     <a href="#xml-misc-recommendation"><code>xml-misc-recommendation</code></a>
+     will be raised if a <em class=rfc2119>SHOULD</em>$B!>(Blevel requirement
+     in <abbr>XML</abbr> specification is not met.</p>
+   </dd>
  <dt><dfn id=xml-validity-error><code>xml-validity-error</code></dfn></dt>
    <dd>A violation of validity constraint in XML document.</dd>
  <dt><dfn id=xml-well-formedness-error><code>xml-well-formedness-error</code></dfn></dt>
-Line 192 
 can be easily serialized into a valid XM
+Line 214 
 can be easily serialized into a valid XM
  <div class=ed><p>@@ TODO: #dt-atuseroption at user option
  (MAY or MUST), #dt-compat for compatibility,
- #dt-interop for interoperability</p></div>
+ #dt-interop for interoperability</p>
+ <p>TODO: XML 1.1, XML Namespace 1.0/1.1, xml:base, xml:id
  </div>
+ </div>
+ <div class=section id=parsing-xml>
+ <h2>Parsing <abbr>XML</abbr> Document</h2>
+ <p>When an <abbr>XML</abbr> document is parsed, the following clauses
+ are applied:</p>
+ <dl class=switch>
+ <dt>For the document
+   <dd>If the <abbr>XML</abbr> document does not begin with an
+   <abbr>XML</abbr> declaration, then the parser <em class=rfc2119>MUST</em>
+   raise an
+   <a href="#xml-misc-recommentation" id=xmr-xml-decl><code>xml-misc-recommendation</code></a>.
+ <dt>For the document type declaration
+   <dd class=ed>@@ read external entity
+ <dt>For each internal general entity declaration being processed by the parser
+   <dd>If the
+   <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#NT-EntityValue"><code>EntityValue</code></a>
+   part of the general entity declaration contains a bare <code>U+003C</code>
+   <code>LESS-THAN SIGN</code> (<code>&lt;</code>) character, then the parser
+   <em class=rfc2119>MUST</em> 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].
+ -->
+ <dt>For each element type declaration being processed by the parser
+   <dd>If there is another processed element type declaration whose
+   <code>Name</code> is equal to the <code>Name</code> of the element type
+   declaration, then the parser <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-validity-error" id=vc-edunique><code>xml-validity-error</code></a>.
+ <dt>For each attribute definition list declaration being processed by the
+ parser
+   <dd>If there is another processed attribute defintion list declaration whose
+   <code>Name</code> is equal to the <code>Name</code> of the attribute
+   definition list declaration, then the parser <em class=rfc2119>MUST</em>
+   raise an
+   <a href="#xml-misc-warning" id=xme-attlist-unique><code>xml-misc-warning</code></a>.
+   <dd>For each attribute definition in the attribute definition list
+   declaration, if there is another processed attribute definition whose
+   <code>Name</code> is equal to the <code>Name</code> of the attribute
+   definition (whether or not in the same attribute definition list
+   declaration), then the parser <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-misc-warning" id=xme-attrdef-unique><code>xml-misc-warning</code></a>.
+   <!--
+     <q>For interoperability, an XML processor <em class=rfc2119>MAY</em> 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.</q>
+   -->
+ <!--
+   NOTE: <!ATTLIST a xml:space (default) #IMPLIED xml:space CDATA #IMPLIED>
+   will not be warned.
+ -->
+ <dt>For each entity declaration being processed by the parser
+   <dd>If the entity declaration declares a parameter entity and the
+   <code>Name</code> of the entity begins with the string <code>xml</code>
+   (in any combination of upper- and lowercase letters), then the parser
+   <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-misc-warning" id=xmw-reserved-pe-name><code>xml-misc-warning</code></a>.
+   <dd>If the entity declaration contains the <code>EntityValue</code>, then
+   for each occurence of any references to unparsed entities in the
+   <code>EntityValue</code>, the parser <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-misc-error" id=xme-unparsed-in-ev><code>xml-misc-error</code></a>.
+   <!--
+     <q>It is an error for a reference to an unparsed entity to appear in the
+     EntityValue in an entity declaration.</q>
+   -->
+ <dt>For each notation declaration being processed by the parser
+   <dd>If there is another processed notation declaration whose
+   <code>Name</code> is equal to the <code>Name</code> of the notation
+   declaration, then the parser <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-validity-error" id=vc-uniquenotationname><code>xml-validity-error</code></a>.
+   <!-- <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#UniqueNotationName">Validity constraint: Unique Notation Name</a> -->
+ <dt>For each empty-element tag
+   <dd>If the <code>Name</code> of the tag is not declared by a processed
+   element type declaration as <code>EMPTY</code> content, then the parser
+   <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-misc-recommentation" id=xmr-emptyelemtag-not-empty><code>xml-misc-recommendation</code></a>.
+ <dt>For each start-tag
+   <dd>If the <code>Name</code> of the tag is declared by a processed element
+   type declaration as <code>EMPTY</code> content, then the parser
+   <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-misc-recommentation" id=xmr-empty-not-emptyelemtag><code>xml-misc-recommendation</code></a>.
+ <dt>For each parameter entity reference
+   <dd>If the declaration for the entity is not read (i.e. no declaration
+   for the entity is processed or the external entity referenced by the
+   declaration cannot be retrieved), then:
+     <ul>
+     <li>If the parameter entity is contained in a declaration, then the
+     declaration <em class=rfc2119>MUST</em> be ignored <em>except</em> that
+     any error before the parameter entity <em class=rfc2119>MUST</em> be
+     raised as usual.
+     <li>If the parameter entity is contained in the status portion of a
+     conditional section, then the conditional section
+     <em class=rfc2119>MUST</em> be processed as if it were an
+     <code>IGNORE</code>d section.
+     <li>The parser <em class=rfc2119>MUST NOT</em> process any entity or
+     attribute-list declaration after the parameter entity reference in the DTD
+     <em>except</em> when the <code>standalone</code> pseudo-attribute of the
+     XML declaration (if any) is set to <code>yes</code>.
+     <!-- This requirement is enforced for internal DTD subset case in
+     XML 1.0/1.1 specification (section 5.1) but not for any other cases. -->
+     <!-- According to this definition, element type declarations, notation
+     declarations, and PIs ARE processed. -->