/[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.26 by wakaba,
Sat Mar 29 06:35:16 2008 UTC
+revision 1.27 by wakaba,
Sat Mar 29 10:12:46 2008 UTC
 Line 92 
 normative version.</p>
  <p class=section-info>This section is <em>non$B!>(Bnormative</em>.</p>
- <div class="issue ed">...</div>
+ <div class="issue ed">...
+ <p>Much of invalid (well-formed or not) XML document parsing and XML document
+ / XML DOM conformance is left undefined so that this document provides a
+ guideline for conformance checkers.
+ </div>
  </div>
-Line 222 
 can be easily serialized into a valid XM
+Line 227 
 can be easily serialized into a valid XM
  #dt-interop for interoperability</p>
  <p>TODO: XML 1.1, XML Namespace 1.0/1.1, xml:base, xml:id
+ <p>TODO: XML "error"/"fatal error" is not always non-conforming (only
+ when MUST or SHOULD).
  </div>
+ <p>The parser <em class=rfc2119>MAY</em> continue the parsing of the document
+ even after a fatal error (as defined by the relavant specification) is
+ encountered.  How the parsing ought to be continued is not defined by this
+ specification.
+   <div class="note memo informative">
+   <p>It is expected that the XML5 specification <span class=ed>@@ ref</span>
+   will define how the parser has to convert any string into DOM tree
+   completely.
+   </div>
  </div>
  <div class=section id=parsing-xml>
-Line 232 
 can be easily serialized into a valid XM
+Line 251 
 can be easily serialized into a valid XM
  <p>When an <abbr>XML</abbr> document is parsed, the following clauses
  are applied:</p>
  <dl class=switch>
+ <dt>For each external entity (including the document entity and the external
+ subset entity, if any)
+   <dd>If there is a byte sequence that are not legal in the encoding in use,
+   then the parser <em class=rfc2119>MUST</em> raise an
+   <a href="#xml-misc-error" id=xme-illegal-bytes><code>xml-misc-error</code></a>.
+   <!--
+      <q>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.</q>
+   -->
+   <dd>If it is the document entity or a general entity, then:
+     <ul>
+     <li>If the input byte sequence for the entity begins with the
+     <abbr title="BYTE ORDER MARK" class=charname>BOM</abbr>, then the parser
+     <em class=rfc2119>MUST</em> set the <span class=ed>BOM flag</span> of
+     the node corresponding to the entity (the <code>Document</code> node
+     for the document entity or an <code>Entity</code> node for a general
+     entity) to <code>true</code>.
+     <!--
+       <q>Entities encoded in UTF-16 MUST and entities encoded in UTF-8 MAY
+       begin with the Byte Order Mark</q>
+     -->
+     <span class=ed>@@ flag must be checked later</span>
+     <!-- <?xml encoding=""?> must be reflected to xmlEncoding; this should be
+     enforced by DOM Core spec. -->
+     </ul>
+   <dd>If it is a parameter entity or the external subset entity, then:
+     <ul>
+     <li>If the character encoding of the entity is <code>UTF-16</code> but
+     the input byte stream for the entity does not begin with the
+     <abbr title="BYTE ORDER MARK" class=charname>BOM</abbr>, then the parser
+     <em class=rfc2119>MUST</em> raise an
+     <a href="#xml-misc-error" id=xme-pe-bom><code>xml-misc-error</code></a>.
+     <li class=ed>@@ encoding="" preferred name?
+ <!--
+ "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 addition, this should be checked later for Document and Entity nodes.
+ -->
+     </ul>
  <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>.
+   <dd>If the document does not contain the document type declaration, or
+   if it does but the document type definition does not contain entity
+   declaration for any of <code>amp</code>, <code>lt</code>, <code>gt</code>,
+   <code>apos</code>, or <code>quot</code>, then the parser
+   <em class=rfc2119>MUST</em> raise
+   <a href="#xml-misc-recommentation" id=xmr-predefined-decl><code>xml-misc-recommendation</code></a>(s).
+   <!--
+     <q>For interoperability, valid documents SHOULD declare the entities
+     amp, lt, gt, apos, quot, in the form specified in 4.6 Predefined
+     Entities.</q>
+   -->
  <dt>For the document type declaration
    <dd class=ed>@@ read external entity
    <dd>The <code>entities</code> attribute of the <code>DocumentType</code>
-Line 401 
 parser
+Line 475 
 parser
    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 attribute
+   <dd><p>The parser <em class=rfc2119>MUST</em> set the normalized value of
+   the attribute to the <code>value</code> attribute of the <code>Attr</code>
+   node created for the attribute.
+     <div class="note memo informative">
+     <p>That is, any entity reference has to be expanded.  Unexpanded entity
+     references in attribute values are discarded.
+     </div>
+ <dt>For each <code>xml:space</code> attribute
+   <dd>The parser <em class=rfc2119>MUST</em> set the normalized value of
+   the <code>xml:space</code> attribute to the <code>value</code> attribute
+   of the <code>Attr</code> node created for the attribute even if the
+   normalized value is different from <code>default</code> or
+   <code>preserve</code>.
+   <!-- In XML 1.0/1.1 specification, the attribute specification MAY be
+   ignored. -->
  <dt>For each parameter entity reference
    <dd>If the declaration for the entity is not read (i.e. no declaration
-Line 442 
 of an element
+Line 533 
 of an element
      <span class=ed>@@ entity declared WFC?</span>
      <li class=ed>An unexpended entity reference node <em class=rfc2119>MUST</em> be inserted to the current node.
      </ul>
+ <dt>For each comment <em>outside</em> of document type declaration
+   <dd>A <code>Comment</code> node <em class=rfc2119>MUST</em> be created
+   and inserted appropriately.
+   <!-- In XML 1.0/1.1 spec, this is optional. -->
  </dl>
  <p class=ed>@@ MUST try to read external entity
-Line 503 
 text declaration.</q>
+Line 599 
 text declaration.</q>
  #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."
- @@ 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."
- @@ We should phrase out what the parser should do where the XML specification
- left undefined.  For example: Comment must be converted to a Comment node,
- illegal xml:space value must be preserved, so on.
- Warn <!ENTITY % xml... ...>
  -->
+ <p>The parser <em class=rfc2119>MUST</em> act as if it is a
+ <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-validating">validating
+ XML processor</a> for the informing of white space appearing in
+ <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#dt-elemcontent">element
+ content</a> (See
+ <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#sec-white-space">Section
+.10</a> of the XML specification).
+   <div class="note memo informative">
+   <p>In other word, the <code>isElementContentWhitespace</code> attribute
+   of <code>Text</code> nodes has to be set appropriately.  Note that the
+   value of the attribute will be set to <code>false</code> for any
+   <code>Text</code> node in the content of an element whose declaration
+   is not processed.
+   </div>
  <p>The parser <em class=rfc2119>MUST</em> raise an
  <a href="#xml-well-formedness-error" id=wfe-syntax><code>xml-well-formedness-error</code></a>
  for any failure to match to a production rule in the XML specification.
-Line 530 
 for any failure to match to a production
+Line 625 
 for any failure to match to a production
    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#ExtSubset">Well-formedness constraint: External Subset</a>
    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#PE-between-Decls">Well-formedness constraint: PE Between Declarations</a>
  -->
+ <!--
+   Inpossible to test:
+     "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"
+ -->
  </div>
  <div class="section" id=checking-dom>
-Line 1151 
 parsed entity)</dt>
+Line 1253 
 parsed entity)</dt>
      <li>If the <code>childNodes</code> list of <var>n</var> contains
      any nodes, then raise an
      <a href="#xml-well-formedness-error" id=wfe-pi-child><code>xml-well-formedness-error</code></a>.</li>
+     <li class=ed>@@ Warn if not declared
      </ol>
    </dd>
  <dt>If <var>n</var> is a <code>Text</code> node</dt>

 Legend:



Removed from v.1.26
 


changed lines


 
Added in v.1.27
 Legend:



Removed from v.1.26
 


changed lines


 
Added in v.1.27
-Removed from v.1.26
+Added in v.1.27

admin@suikawiki.org	ViewVC Help
Powered by ViewVC 1.1.24