Parent Directory
| 
Revision Log
| 
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> | Line 92 normative version.</p> |
| 92 | ||
| 93 | <p class=section-info>This section is <em>non$B!>(Bnormative</em>.</p> | <p class=section-info>This section is <em>non$B!>(Bnormative</em>.</p> |
| 94 | ||
| 95 | <div class="issue ed">...</div> | <div class="issue ed">... |
| 96 | ||
| 97 | <p>Much of invalid (well-formed or not) XML document parsing and XML document | |
| 98 | / XML DOM conformance is left undefined so that this document provides a | |
| 99 | guideline for conformance checkers. | |
| 100 | </div> | |
| 101 | ||
| 102 | ||
| 103 | </div> | </div> |
| # | Line 222 can be easily serialized into a valid XM | Line 227 can be easily serialized into a valid XM |
| 227 | #dt-interop for interoperability</p> | #dt-interop for interoperability</p> |
| 228 | ||
| 229 | <p>TODO: XML 1.1, XML Namespace 1.0/1.1, xml:base, xml:id | <p>TODO: XML 1.1, XML Namespace 1.0/1.1, xml:base, xml:id |
| 230 | ||
| 231 | <p>TODO: XML "error"/"fatal error" is not always non-conforming (only | |
| 232 | when MUST or SHOULD). | |
| 233 | </div> | </div> |
| 234 | ||
| 235 | <p>The parser <em class=rfc2119>MAY</em> continue the parsing of the document | |
| 236 | even after a fatal error (as defined by the relavant specification) is | |
| 237 | encountered. How the parsing ought to be continued is not defined by this | |
| 238 | specification. | |
| 239 | ||
| 240 | <div class="note memo informative"> | |
| 241 | <p>It is expected that the XML5 specification <span class=ed>@@ ref</span> | |
| 242 | will define how the parser has to convert any string into DOM tree | |
| 243 | completely. | |
| 244 | </div> | |
| 245 | ||
| 246 | </div> | </div> |
| 247 | ||
| 248 | <div class=section id=parsing-xml> | <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 |
| 251 | <p>When an <abbr>XML</abbr> document is parsed, the following clauses | <p>When an <abbr>XML</abbr> document is parsed, the following clauses |
| 252 | are applied:</p> | are applied:</p> |
| 253 | <dl class=switch> | <dl class=switch> |
| 254 | <dt>For each external entity (including the document entity and the external | |
| 255 | subset entity, if any) | |
| 256 | <dd>If there is a byte sequence that are not legal in the encoding in use, | |
| 257 | then the parser <em class=rfc2119>MUST</em> raise an | |
| 258 | <a href="#xml-misc-error" id=xme-illegal-bytes><code>xml-misc-error</code></a>. | |
| 259 | <!-- | |
| 260 | <q>It is a fatal error when an XML processor encounters an entity with an | |
| 261 | encoding that it is unable to process. It is a fatal error if an XML | |
| 262 | entity is determined (via default, encoding declaration, or higher-level | |
| 263 | protocol) to be in a certain encoding but contains byte sequences that are | |
| 264 | not legal in that encoding.</q> | |
| 265 | --> | |
| 266 | ||
| 267 | <dd>If it is the document entity or a general entity, then: | |
| 268 | <ul> | |
| 269 | <li>If the input byte sequence for the entity begins with the | |
| 270 | <abbr title="BYTE ORDER MARK" class=charname>BOM</abbr>, then the parser | |
| 271 | <em class=rfc2119>MUST</em> set the <span class=ed>BOM flag</span> of | |
| 272 | the node corresponding to the entity (the <code>Document</code> node | |
| 273 | for the document entity or an <code>Entity</code> node for a general | |
| 274 | entity) to <code>true</code>. | |
| 275 | <!-- | |
| 276 | <q>Entities encoded in UTF-16 MUST and entities encoded in UTF-8 MAY | |
| 277 | begin with the Byte Order Mark</q> | |
| 278 | --> | |
| 279 | <span class=ed>@@ flag must be checked later</span> | |
| 280 | <!-- <?xml encoding=""?> must be reflected to xmlEncoding; this should be | |
| 281 | enforced by DOM Core spec. --> | |
| 282 | </ul> | |
| 283 | <dd>If it is a parameter entity or the external subset entity, then: | |
| 284 | <ul> | |
| 285 | <li>If the character encoding of the entity is <code>UTF-16</code> but | |
| 286 | the input byte stream for the entity does not begin with the | |
| 287 | <abbr title="BYTE ORDER MARK" class=charname>BOM</abbr>, then the parser | |
| 288 | <em class=rfc2119>MUST</em> raise an | |
| 289 | <a href="#xml-misc-error" id=xme-pe-bom><code>xml-misc-error</code></a>. | |
| 290 | <li class=ed>@@ encoding="" preferred name? | |
| 291 | <!-- | |
| 292 | "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." | |
| 293 | ||
| 294 | In addition, this should be checked later for Document and Entity nodes. | |
| 295 | --> | |
| 296 | </ul> | |
| 297 | ||
| 298 | <dt>For the document | <dt>For the document |
| 299 | <dd>If the <abbr>XML</abbr> document does not begin with an | <dd>If the <abbr>XML</abbr> document does not begin with an |
| 300 | <abbr>XML</abbr> declaration, then the parser <em class=rfc2119>MUST</em> | <abbr>XML</abbr> declaration, then the parser <em class=rfc2119>MUST</em> |
| 301 | raise an | raise an |
| 302 | <a href="#xml-misc-recommentation" id=xmr-xml-decl><code>xml-misc-recommendation</code></a>. | <a href="#xml-misc-recommentation" id=xmr-xml-decl><code>xml-misc-recommendation</code></a>. |
| 303 | <dd>If the document does not contain the document type declaration, or | |
| 304 | if it does but the document type definition does not contain entity | |
| 305 | declaration for any of <code>amp</code>, <code>lt</code>, <code>gt</code>, | |
| 306 | <code>apos</code>, or <code>quot</code>, then the parser | |
| 307 | <em class=rfc2119>MUST</em> raise | |
| 308 | <a href="#xml-misc-recommentation" id=xmr-predefined-decl><code>xml-misc-recommendation</code></a>(s). | |
| 309 | <!-- | |
| 310 | <q>For interoperability, valid documents SHOULD declare the entities | |
| 311 | amp, lt, gt, apos, quot, in the form specified in 4.6 Predefined | |
| 312 | Entities.</q> | |
| 313 | --> | |
| 314 | <dt>For the document type declaration | <dt>For the document type declaration |
| 315 | <dd class=ed>@@ read external entity | <dd class=ed>@@ read external entity |
| 316 | <dd>The <code>entities</code> attribute of the <code>DocumentType</code> | <dd>The <code>entities</code> attribute of the <code>DocumentType</code> |
| # | Line 401 parser | Line 475 parser |
| 475 | type declaration as <code>EMPTY</code> content, then the parser | type declaration as <code>EMPTY</code> content, then the parser |
| 476 | <em class=rfc2119>MUST</em> raise an | <em class=rfc2119>MUST</em> raise an |
| 477 | <a href="#xml-misc-recommentation" id=xmr-empty-not-emptyelemtag><code>xml-misc-recommendation</code></a>. | <a href="#xml-misc-recommentation" id=xmr-empty-not-emptyelemtag><code>xml-misc-recommendation</code></a>. |
| 478 | <dt>For each attribute | |
| 479 | <dd><p>The parser <em class=rfc2119>MUST</em> set the normalized value of | |
| 480 | the attribute to the <code>value</code> attribute of the <code>Attr</code> | |
| 481 | node created for the attribute. | |
| 482 | ||
| 483 | <div class="note memo informative"> | |
| 484 | <p>That is, any entity reference has to be expanded. Unexpanded entity | |
| 485 | references in attribute values are discarded. | |
| 486 | </div> | |
| 487 | <dt>For each <code>xml:space</code> attribute | |
| 488 | <dd>The parser <em class=rfc2119>MUST</em> set the normalized value of | |
| 489 | the <code>xml:space</code> attribute to the <code>value</code> attribute | |
| 490 | of the <code>Attr</code> node created for the attribute even if the | |
| 491 | normalized value is different from <code>default</code> or | |
| 492 | <code&g |