/[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.23 by wakaba, Sun Mar 16 12:37:17 2008 UTC revision 1.24 by wakaba, Fri Mar 28 15:37:01 2008 UTC
# Line 18  Line 18 
18    
19  <div class="header">  <div class="header">
20  <h1>manakai's <abbr>XML</abbr> Conformance Checking</h1>  <h1>manakai's <abbr>XML</abbr> Conformance Checking</h1>
21  <h2>Working Draft <time datetime=2008-03-16>16 March 2008</time></h2>  <h2>Working Draft <time datetime=2008-03-29>29 March 2008</time></h2>
22    
23  <dl class="versions-uri">  <dl class="versions-uri">
24  <dt>This Version</dt>  <dt>This Version</dt>
# Line 260  are applied:</p> Line 260  are applied:</p>
260    type declaration as <code>EMPTY</code> content, then the parser    type declaration as <code>EMPTY</code> content, then the parser
261    <em class=rfc2119>MUST</em> raise an    <em class=rfc2119>MUST</em> raise an
262    <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>.
263    </dl>
264    
265    <p>In addition, the parser <em class=rfc2119>MUST</em> check whether the
266    following constraints are met.
267    
268    <p><strong>Well-formedness constraints</strong>.  For each violation to
269    one of constraints below, an
270    <a href="#xml-well-formedness-error"><code>xml-well-formedness-error</code></a>
271    <em class=rfc2119>MUST</em> be raised.  The list of well-formedness
272    constraints is below:
273    <ul>
274    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#wfc-PEinInternalSubset">Well-formedness constraint: PEs in Internal Subset</a>
275    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#ExtSubset">Well-formedness constraint: External Subset</a>
276    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#PE-between-Decls">Well-formedness constraint: PE Between Declarations</a>
277    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#GIMatch">Well-formedness constraint: Element Type Match</a>
278    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#uniqattspec">Well-formedness constraint: Unique Att Spec</a>
279    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#NoExternalRefs">Well-formedness constraint: No External Entity References</a>
280    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#CleanAttrVals">Well-formedness constraint: No &lt; in Attribute Values</a>
281    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#wf-Legalchar">Well-formedness constraint: Legal Character</a>
282    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#textent">Well-formedness constraint: Parsed Entity</a>
283    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#norecursion">Well-formedness constraint: No Recursion</a>
284    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#indtd">Well-formedness constraint: In DTD</a>
285    </ul>
286    
287    <p><strong>Validity constraints</strong>.  For each violation to
288    one of constraints below, an
289    <a href="#xml-validity-error"><code>xml-validity-error</code></a>.
290    <em class=rfc2119>MUST</em> be raised.  The list of validity
291    constraints is below:
292    <ul>
293    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#vc-PEinMarkupDecl">Validity constraint: Proper Declaration/PE Nesting</a>
294    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#vc-PEinGroup">Validity constraint: Proper Group/PE Nesting</a>
295    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#condsec-nesting">Validity constraint: Proper Conditional Section/PE Nesting</a>
296    <li><a href="http://www.w3.org/TR/2006/REC-xml-20060816/#UniqueNotationName">Validity constraint: Unique Notation Name</a>
297    </ul>
298    
299    <p><strong>Other creteria</strong>.  For each violation to
300    one of constraints below, an
301    <a href="#xml-misc-recommendation"><code>xml-misc-recommendation</code></a>
302    <em class=rfc2119>MUST</em> be raised.  The list of constraints is below:
303    <ul>
304    <li><q>For interoperability, if a parameter-entity reference appears in a
305    <code>choice</code>, <code>seq</code>, or <code>Mixed</code> construct, its
306    replacement text <em class=rfc2119>SHOULD</em> contain at least one non-blank
307    character, and neither the first nor last non-blank character of the
308    replacement text <em class=rfc2119>SHOULD</em> be a connector (<code>|</code>
309    or <code>,</code>).</q>
310    <li><q>External parsed entities <em class=rfc2119>SHOULD</em> each begin with a
311    text declaration.</q>
312    </ul>
313    
314    <!--
315    <li><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>
316    
317    <a href="#xml-misc-error" id=xme-attr-xml-space><code>xml-misc-error</code></a>.
318    <li>It is an error for a reference to an unparsed entity to appear in the EntityValue in an entity declaration."
319    -->
320    
321  <!--  <!--
322    
 #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."  
 #condsec-nesting Validity constraint: Proper Conditional Section/PE Nesting  
 #wf-Legalchar Well-formedness constraint: Legal Character  
 #textent Well-formedness constraint: Parsed Entity  
 #norecursion Well-formedness constraint: No Recursion  
 #indtd Well-formedness constraint: In DTD  
 "External parsed entities SHOULD each begin with a text declaration."  
 "It is an error for a reference to an unparsed entity to appear in the EntityValue in an entity declaration."  
 #UniqueNotationName Validity constraint: Unique Notation Name  
323    
324  @@ Need detailed review, but maybe should be in parsing phase  @@ Need detailed review, but maybe should be in parsing phase
325    
# Line 308  left undefined.  For example: Comment mu Line 347  left undefined.  For example: Comment mu
347  illegal xml:space value must be preserved, so on.  illegal xml:space value must be preserved, so on.
348    
349  -->  -->
 </dl>  
350  </div>  </div>
351    
352  <div class="section" id=checking-dom>  <div class="section" id=checking-dom>
Legend:
Removed from v.1.23  
changed lines
  Added in v.1.24
admin@suikawiki.org
 ViewVC Help
Powered by ViewVC 1.1.24