/[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.16 by wakaba,
Mon Nov 26 12:38:53 2007 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=2007-11-26>26 November 2007</time></h2>
  <dl class="versions-uri">
  <dt>This Version</dt>
 Line 120 
 In addition, the order in which <a href=
  raised is undefined.</p>
  </div>
- <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>
  <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 159 
 can be easily serialized into a valid XM
+Line 153 
 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 186 
 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 196 
 can be easily serialized into a valid XM
+Line 210 
 can be easily serialized into a valid XM
  </div>
+ <div class=section id=parsing-xml>
+ <h2>Parsing <abbr>XML</abbr> Document</h2>
+ <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."
+ @@ Need detailed review, but maybe should be in parsing phase
+ #vc-check-rmd Validity constraint: Standalone Document Declaration
+ -->
+ </ul>
+ </div>
+ <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>
  <div class=section id=definitions>
  <h3>Definitions</h3>
-Line 235 
 class <a href="#class-ControlChar10"><co
+Line 306 
 class <a href="#class-ControlChar10"><co
  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 class=ed>@@ If U+000D, round-trip-error</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>The algorithm
  <dfn id=algorithm-to-validate-a-name title="to validate a Name">to validate a
- <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
  as following:</p>
  <ol>
+ <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.":
+ 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>@@</li>
  </ol>
-Line 308 
 following:</p>
+Line 398 
 following:</p>
        <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>If <code>nodeName</code> attribute of <var>n</var> is
+     <code>xml:space</code> <span class=ed>@@ or {xml namespace}:space ?</span>
+     and <code>value</code> attribute of <var>n</var> is neither
+     <code>default</code> nor <code>preserve</code>, then it is an
+     <a href="#xml-misc-error" id=xme-attr-xml-space><code>xml-misc-error</code></a>.<!--
+     Note that <!ATTLIST e xml:space (default|preserve) "a">...
+     <e xml:space="default"/> is conforming and valid. --></li>
+     <li class=ed>@@ xml:lang value is not a language tag [RFC 3066 or its
+     successor] or an empty string, then xml-misc-warning
+     (a "fact"-level error; not an XML error).</li>
      <li class=ed>@@ <code>specified</code>,
-     <code>manakaiAttributeType</code></li>
+     <code>manakaiAttributeType</code> (#ValueType Validity constraint: Attribute Value Type)</li>
+     <!-- xml:space MUST be declared to be valid. -->
+     <li>Let <dfn id=var-v><var>v</var></dfn> be the value of the
+     attribute <code>value</code> of <var>n</var>.</li>
+     <li>Validate the <var>n</var> against the <span class=ed>declared
+     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>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>
      </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>
-Line 329 
 following:</p>
+Line 501 
 following:</p>
        <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>
      </ol>
    </dd>
  <dt>If <var>n</var> is a <code>CDATASection</code> node</dt>
-Line 338 
 following:</p>
+Line 519 
 following:</p>
      <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 it is an
+     a string <code>]]></code>, then raise an
-     <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>
      <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>
-Line 348 
 following:</p>
+Line 529 
 following:</p>
  <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">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 it is an
+     <code>-</code>, then raise an
-     <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>.<!--
+     "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>
-Line 416 
 following:</p>
+Line 600 
 following:</p>
      <ol>
      <li><a href="#algorithm-to-validate-a-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>If the <code>systemId</code> attribute value contains
-Line 461 
 following:</p>
+Line 660 
 following:</p>
        <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 class=ed>@@ #uniqattspec Well-formedness constraint: Unique Att Spec</li>
      </ol>
    </dd>
  <dt>If <var>n</var> is an <code>ElementTypeDefinition</code> node</dt>
-Line 470 
 following:</p>
+Line 671 
 following:</p>
      <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</dt>
-Line 545 
 following:</p>
+Line 762 
 following:</p>
  <dt>If <var>n</var> is a <code>ProcessingInstruction</code> node</dt>
    <dd>
      <ol>
-     <li><a href="#algorithm-to-validate-a-ncname">Validate the
+     <li>If the <code>target</code> attribute value matches to the string
-     <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
      <a href="#xml-well-formedness-error" id=wfe-pi-xml><code>xml-well-formedness-error</code></a>.</li>
-     <li><a href="#algorithm-to-validate-an-xml-character-data">Validate the
+     <li>Otherwise, <a href="#algorithm-to-validate-a-ncname">validate the
-     <code>data</code> attribute value as an <abbr>XML</abbr> character
+     <code>target</code> attribute value as an <code>NCName</code></a>.</li>
+     <li>Then,
+     <a href="#algorithm-to-validate-an-xml-character-data" title="validate an XML character data">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
+     <li>If the <code>data</code> attribute value contains a string
-     a string <code>?></code>, or starts with either
+     <code>?></code>, then raise a
-     <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>
-     <code class=char>U+000D</code>, or <code class=char>U+0020</code>
+     <li>If the <code>data</code> attribute value starts with either
-     character, then it is a
+     <code class=char>U+0009</code> <code class=charname>CHARACTER
-     <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
+     FEED</code>, <code class=char>U+000D</code> <code class=charname>CARRIAGE
+     RETURN</code>, or <code class=char>U+0020</code>
+     <code class=charname>SPACE</code> character, then raise a
+     <a href="#round-trip-error" id=rte-pi-s><code>round-trip-error</code></a>.</li>
      <li>If the <code>childNodes</code> list of <var>n</var> contains
-     any nodes, they are in
+     any nodes, then raise an
      <a href="#xml-well-formedness-error" id=wfe-pi-child><code>xml-well-formedness-error</code></a>.</li>
      </ol>
    </dd>

 Legend:



Removed from v.1.11
 


changed lines


 
Added in v.1.16
 Legend:



Removed from v.1.11
 


changed lines


 
Added in v.1.16
-Removed from v.1.11
+Added in v.1.16

admin@suikawiki.org	ViewVC Help
Powered by ViewVC 1.1.24