/[suikacvs]/test/html-webhacc/error-description-source.xml
Suika

Diff of /test/html-webhacc/error-description-source.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.13 by wakaba, Mon Nov 5 09:33:52 2007 UTC revision 1.20 by wakaba, Tue Mar 11 14:10:11 2008 UTC
# Line 11  Web Document Conformance Checker (BETA)< Line 11  Web Document Conformance Checker (BETA)<
11  <body>  <body>
12  <h1>Description of Errors</h1>  <h1>Description of Errors</h1>
13    
14    <section id="html5-character-encoding">
15    <h2>HTML5 Character Encoding Errors</h2>
16    
17    <d:item name="character encoding" class="format-charset must" level="m">
18      <d:message xml:lang="en">Character encoding <code><var>$0</var></code>
19      is not allowed for <abbr>HTML</abbr> document.</d:message>
20      <d:desc xml:lang="en">
21        <p>The character encoding used for the document is not allowed
22        for <abbr>HTML</abbr> document.  The document is non‐conforming.</p>
23      </d:desc>
24    </d:item>
25    
26    <d:item name="character encoding" class="format-charset should"
27        level="s">
28      <d:message xml:lang="en">Character encoding <code><var>$0</var></code>
29      should not be used for <abbr>HTML</abbr> document.</d:message>
30      <d:desc xml:lang="en">
31        <p>The character encoding used for the document is not recommended
32        for <abbr>HTML</abbr> document.  The document is non‐conforming
33        unless there is any good reason to use that encoding.</p>
34      </d:desc>
35    </d:item>
36    
37    <d:item name="character encoding" class="format-charset warning"
38        level="w">
39      <d:message xml:lang="en">Use of UTF-8 is encouraged.</d:message>
40      <d:desc xml:lang="en">
41        <p>Use of UTF-8 as the character encoding of the document is encouraged,
42        though the use of another character encoding is conforming.</p>
43      </d:desc>
44    </d:item>
45    
46    <d:item name="character encoding" class="format-charset unsupported"
47        level="unsupported">
48      <d:message xml:lang="en">Conformance for character encoding requirements
49      cannot be checked.</d:message>
50      <d:desc xml:lang="en">
51        <p>The conformance checker cannot detect whether the input document
52        met the requirements on character encoding, since the document
53        is not inputed as a serialized byte sequence.  The document is
54        not conforming if it is not encoded in an appropriate character
55        encoding with appropriate labeling.</p>
56      </d:desc>
57    </d:item>
58    
59    <d:item name="no character encoding declaration" class="format-charset error"
60        level="m">
61      <d:message xml:lang="en">There is no character encoding
62      declaration.</d:message>
63      <d:desc xml:lang="en">
64        <p>The document does not contain a character encoding
65        declaration.  Unless the character encoding is explicitly
66        specified in lower‐level protocol, e.g. in <abbr>HTTP</abbr>,
67        or is implied by <abbr>BOM</abbr>, there must be a character
68        encoding declaration.  The document is non‐conforming.</p>
69    
70        <p>The long character encoding declaration syntax
71        <code class="html bad example">&lt;meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code>
72        is obsolete.  The new syntax is:</p>
73        <pre class="html example"><code>&lt;meta charset="<var>charset-name</var>"></code></pre>
74    
75        <p>Note that the <code>encoding</code> declaration in <abbr>XML</abbr>
76        declaration has no effect for <abbr>HTML</abbr> document.</p>
77      </d:desc>
78    </d:item>
79    
80    <d:item name="non ascii superset" class="format-charset error"
81        level="m">
82      <d:message xml:lang="en">No character encoding metadata is found
83      in lower‐level protocol nor is there <abbr>BOM</abbr>, while
84      character encoding <code><var>$0</var></code>
85      is not a superset of <abbr>ASCII</abbr>.</d:message>
86      <d:desc xml:lang="en">
87        <p>The document is not labeled with character encoding name
88        in lower‐level protocol, e.g. in <abbr>HTTP</abbr>, and
89        the document is not begin with <abbr>BOM</abbr>.  In addition,
90        the character encoding of the document is not a superset of
91        <abbr>ASCII</abbr>.  The document is non‐conforming.</p>
92    
93        <p>Unless there is a <abbr>BOM</abbr>, the character encoding
94        for the document must be specified in e.g. <abbr>HTTP</abbr>‐level,
95        as:</p>
96        <pre class="http example"><code>Content-Type: text/html; charset=<var>charset-name</var></code></pre>
97    
98        <p>Existence of <abbr>HTML</abbr> character encoding declaration, i.e.
99        <code class="html example">&lt;meta charset="<var>charset-name</var>"></code>,
100        does not allow to omit <code>charset</code> parameter
101        for <abbr>HTML</abbr> document encoded in non‐<abbr>ASCII</abbr>
102        compatible encoding.</p>
103    
104        <p>Character encodings <code>Shift_JIS</code>, <code>Windows-31J</code>,
105        and <code>ISO-2022-JP</code> are <em>not</em> a superset of
106        <abbr>ASCII</abbr> for the purpose of <abbr>HTML</abbr> conformance.</p>
107      </d:desc>
108    </d:item>
109    
110    <d:item name="charset label detected" class="format-charset warning"
111        level="w">
112      <d:message xml:lang="en">While parsing the document as
113      <code><var>$0</var></code>, a character encoding declaration specifying
114      character encoding as <code><var>$1</var></code> is found.  The document
115      is reparsed.</d:message>
116      <d:desc xml:lang="en">
117        <p>While parsing a document in a character encoding,
118        a character encoding declaration which declares the character
119        encoding of the document as another character encoding is found.
120        The occurence of this warning itself does not make the document
121        non‐conforming.  However, the failure of the first attempt to
122        to detect the character encoding might be the result of non‐conformance
123        of the document.</p>
124    
125        <p>The document will be reparsed from the beginning.  Some error
126        or warning might be reported again.</p>
127    
128        <p>These are suggestions to avoid this warning:</p>
129        <ul>
130        <li>Specify <code>charset</code> parameter in the <code>Content-Type</code>
131        field in the <abbr>HTTP</abbr> header, as:
132        <pre class="HTTP example"><code>Content-Type: text/html; charset="<var>charset-name</var>"</code></pre></li>
133        <li>Put the character encoding declaration
134        (<code class="html example">&lt;meta charset="<var>charset-name</var>"></code>)
135        just after <code class="html example">&lt;head></code> start tag.</li>
136        <li>Use <code>UTF-8</code>.</li>
137        </ul>
138      </d:desc>
139    </d:item>
140    </section>
141    
142  <section id="html5-tokenize-error">  <section id="html5-tokenize-error">
143  <h2>HTML5 Parse Errors in Tokenization Stage</h2>  <h2>HTML5 Parse Errors in Tokenization Stage</h2>
144    
# Line 48  Web Document Conformance Checker (BETA)< Line 176  Web Document Conformance Checker (BETA)<
176    <d:message xml:lang="en">The <code>&amp;</code> character must    <d:message xml:lang="en">The <code>&amp;</code> character must
177    introduce a reference.</d:message>    introduce a reference.</d:message>
178    <d:desc xml:lang="en">    <d:desc xml:lang="en">
179      <p>An <code>&amp;</code> (<code>U+0026</code>      <p>An <code>&amp;</code> character which
     <code class="charname">AMPERSAND</code>) character which  
180      is not part of any reference appears in the input stream.      is not part of any reference appears in the input stream.
181      The document is non-conforming.</p>      The document is non‐conforming.</p>
182    
183      <p><strong>Any <code>&amp;</code> character in URI (or IRI)      <p><em>Any <code>&amp;</code> character in URI (or IRI)
184      must be escaped as <code>&amp;amp;</code>.</strong></p>      must be escaped as <code class="example">&amp;amp;</code>.</em></p>
185    
186      <p>The <code>&amp;</code> character must      <p>The <code>&amp;</code> character must
187      be the first character of a reference:      be the first character of a reference:
188        <dl>        <dl class="switch">
189        <dt>Named entity reference</dt>        <dt>Named entity reference</dt>
190            <dd><pre class="html example"><code>&amp;<var>entity-name</var>;</code></pre>            <dd><pre class="html example"><code>&amp;<var>entity-name</var>;</code></pre>
191            where <var>entity-name</var> is the name of the            where <var>entity-name</var> is the name of the
# Line 134  Web Document Conformance Checker (BETA)< Line 261  Web Document Conformance Checker (BETA)<
261    
262      <p>The string <code>&amp;#</code> must be the first two characters      <p>The string <code>&amp;#</code> must be the first two characters
263      of a reference:      of a reference:
264        <dl>        <dl class="switch">
265        <dt>Numeric character reference</dt>        <dt>Numeric character reference</dt>
266            <dd><pre class="html example"><code>&amp;#<var>d</var>;</code></pre>            <dd><pre class="html example"><code>&amp;#<var>d</var>;</code></pre>
267            where <var>d</var> is the decimal representation of            where <var>d</var> is the decimal representation of
# Line 189  Web Document Conformance Checker (BETA)< Line 316  Web Document Conformance Checker (BETA)<
316    
317      <dl class="switch">      <dl class="switch">
318      <dt>Comments</dt>      <dt>Comments</dt>
319        <dd>In HTML documents, comments must be introduced by        <dd>In HTML document, comments must be introduced by
320        <code>&lt;!--</code> (<code>&lt;!</code> <em>immediately</em> followed        <code class="example">&lt;!--</code> (<code>&lt;!</code>
321          <em>immediately</em> followed
322        by <em>two</em> <code>-</code>s) and must be terminated by        by <em>two</em> <code>-</code>s) and must be terminated by
323        <code>--></code>.  Strings <code>&lt;!</code> not followed        <code class="example">--></code>.
324          Strings <code>&lt;!</code> not followed
325        by <code>--</code> and <code>&lt;!-</code> not followed by        by <code>--</code> and <code>&lt;!-</code> not followed by
326        <code>-</code> are not valid open delimiters for comments.</dd>        <code>-</code> are not valid open delimiters for comments.</dd>
327      <dt>Marked sections, including <code>CDATA</code> sections</dt>      <dt>Marked sections, including <code>CDATA</code> sections</dt>
328        <dd>Marked sections are not allowed in HTML documents.</dd>        <dd>Marked sections are not allowed in HTML document.</dd>
329      <dt>Markup declarations</dt>      <dt>Markup declarations</dt>
330        <dd>Markup declarations, except <code>DOCTYPE</code>        <dd>Markup declarations, except for <code>DOCTYPE</code>
331        and comment declarations, are not allowed in HTML documents.</dd>        and comment declarations, are not allowed in HTML document.</dd>
332      <dt>String <code>&lt;!</code></dt>      <dt>String <code>&lt;!</code></dt>
333        <dd>String <code>&lt;!</code> must be escaped as        <dd>String <code>&lt;!</code> must be escaped as
334        <code>&amp;lt;!</code>.</dd>        <code class="example">&amp;lt;!</code>.</dd>
335      </dl>      </dl>
336    </d:desc>    </d:desc>
337  </d:item>  </d:item>
# Line 277  Web Document Conformance Checker (BETA)< Line 406  Web Document Conformance Checker (BETA)<
406      <dt><code>&lt;script/></code></dt>      <dt><code>&lt;script/></code></dt>
407          <dd><p>The polytheistic slash cannot be used for <code>script</code>          <dd><p>The polytheistic slash cannot be used for <code>script</code>
408          element.  Even for an empty <code>script</code> element,          element.  Even for an empty <code>script</code> element,
409          there must be an explicit end tag <code>&lt;/script></code>.</p>          there must be an explicit end tag
410            <code class="html example">&lt;/script></code>.</p>
411    
412          <p><strong>NOTE</strong>: Though some user agents interpret          <p><strong>NOTE</strong>: Though some user agents interpret
413          polytheistic slash for <code>script</code> element as the          polytheistic slash for <code>script</code> element as the
# Line 294  Web Document Conformance Checker (BETA)< Line 424  Web Document Conformance Checker (BETA)<
424          to allow polytheistic slash for these elements.</dd>          to allow polytheistic slash for these elements.</dd>
425      <dt><code>&lt;a/></code>, <code>&lt;p/></code></dt>      <dt><code>&lt;a/></code>, <code>&lt;p/></code></dt>
426          <dd>These elements are not always empty and therefore          <dd>These elements are not always empty and therefore
427          polytheistic slash is not allowed.</dd>          polytheistic slash is not allowed.  Use explicit end tag
428            to represent empty element as:
429              <pre class="example html"><code>&lt;p>&lt;/p></code></pre>
430            </dd>
431      </dl>      </dl>
432    
433      <p>Note that, unlike in XML, the polytheistic slash has      <p>Note that, unlike in XML, the polytheistic slash has
# Line 319  Web Document Conformance Checker (BETA)< Line 452  Web Document Conformance Checker (BETA)<
452        <dd>An <abbr>XBL</abbr> binding cannot be associated by        <dd>An <abbr>XBL</abbr> binding cannot be associated by
453        <abbr title="processing instruction">PI</abbr> in <abbr>HTML</abbr>        <abbr title="processing instruction">PI</abbr> in <abbr>HTML</abbr>
454        document.  Use <code>binding</code> property in <abbr>CSS</abbr>        document.  Use <code>binding</code> property in <abbr>CSS</abbr>
455        style sheet.</dd>        style sheet as:
456            <pre class="html example"><code>&lt;style>
457    p {
458      binding: url(binding.xbl);
459    }
460    &lt;/style></code></pre>
461          </dd>
462      <dt><code>&lt;?xml?&gt;</code> (XML declaration)</dt>      <dt><code>&lt;?xml?&gt;</code> (XML declaration)</dt>
463          <dd>XML declaration is unnecessary for HTML documents.</dd>          <dd>XML declaration is unnecessary for HTML documents.</dd>
464      <dt><code>&lt;?xml-stylesheet?></code> (XML style sheet      <dt><code>&lt;?xml-stylesheet?></code> (XML style sheet
# Line 327  Web Document Conformance Checker (BETA)< Line 466  Web Document Conformance Checker (BETA)<
466          <dd>Use HTML <code>link</code> element with <code>rel</code>          <dd>Use HTML <code>link</code> element with <code>rel</code>
467          attribute set to <code>stylesheet</code> (or,          attribute set to <code>stylesheet</code> (or,
468          <code>alternate stylesheet</code> for an alternate style          <code>alternate stylesheet</code> for an alternate style
469          sheet).</dd>          sheet).
470              <pre class="example html"><code>&lt;link rel=stylesheet href="path/to/stylesheet.css"></code></pre>
471            </dd>
472      <dt><code>&lt;?php?&gt;</code> or      <dt><code>&lt;?php?&gt;</code> or
473      <code>&lt;? <var>... <abbr>PHP</abbr> code ...</var> ?&gt;</code>      <code>&lt;? <var>... <abbr>PHP</abbr> code ...</var> ?&gt;</code>
474      (<abbr>PHP</abbr> code)</dt>      (<abbr>PHP</abbr> code)</dt>
# Line 506  Web Document Conformance Checker (BETA)< Line 647  Web Document Conformance Checker (BETA)<
647        <dd>Though the element is void in earlier versions of Safari,        <dd>Though the element is void in earlier versions of Safari,
648        the <code>canvas</code> element is <em>no</em> longer        the <code>canvas</code> element is <em>no</em> longer
649        defined as empty.  There must be an end tag        defined as empty.  There must be an end tag
650        <code>&lt;/canvas></code>.</dd>        <code class="html example">&lt;/canvas></code>.</dd>
651      </dl>      </dl>
652    
653      <p>Note that misnesting tags, such as      <p>Note that misnesting tags, such as
# Line 540  Web Document Conformance Checker (BETA)< Line 681  Web Document Conformance Checker (BETA)<
681    <d:desc xml:lang="en">    <d:desc xml:lang="en">
682      <p>The document contains a <code>DOCTYPE</code> declaration      <p>The document contains a <code>DOCTYPE</code> declaration
683      that is different from HTML5 <code>DOCTYPE</code> (i.e.      that is different from HTML5 <code>DOCTYPE</code> (i.e.
684      <code>&lt;!DOCTYPE HTML&gt;</code>).  The document is non-conforming.</p>      <code class="example html">&lt;!DOCTYPE HTML&gt;</code>).
685        The document is non‐conforming.</p>
686    
687      <p>The document might or might not be conformant to      <p>The document might or might not be conformant to
688      some version of HTML.  However, conformance to any HTML      some version of HTML.  However, conformance to any HTML
# Line 672  Web Document Conformance Checker (BETA)< Line 814  Web Document Conformance Checker (BETA)<
814                    block-level content, any inline-level content must be                    block-level content, any inline-level content must be
815                    put in e.g. paragraph element such as <code>p</code>.</p>                    put in e.g. paragraph element such as <code>p</code>.</p>
816                    <p>For example, an HTML document fragment                    <p>For example, an HTML document fragment
817                    <code class="bad example">&lt;div>&lt;p>Hello!&lt;/p> World!&lt;/div></code>                    <code class="html bad example">&lt;div>&lt;p>Hello!&lt;/p> World!&lt;/div></code>
818                    is non-conforming, since a word <q>World!</q> does not belong                    is non-conforming, since a word <q>World!</q> does not belong
819                    to any paragraph.  (If not part of any paragraph, what is                    to any paragraph.  (If not part of any paragraph, what is
820                    it!?)  A conforming example would be:                    it!?)  A conforming example would be:
821                      <pre class="example"><code>&lt;div>&lt;p>Hello!&lt;/p> &lt;p>World!&lt;/p>&lt;/div></code></pre>                      <pre class="html example"><code>&lt;div>&lt;p>Hello!&lt;/p> &lt;p>World!&lt;/p>&lt;/div></code></pre>
822                    </p></dd>                    </p></dd>
823                <dt>If the parent element does <em>not</em> allow                <dt>If the parent element does <em>not</em> allow
824                block-level elements as content</dt>                block-level elements as content</dt>
# Line 720  Web Document Conformance Checker (BETA)< Line 862  Web Document Conformance Checker (BETA)<
862    
863      <dl class="switch">      <dl class="switch">
864      <dt><code>html</code> element in an XHTML document</dt>      <dt><code>html</code> element in an XHTML document</dt>
865          <dd><p>In an XHTML document, the root <code>html</code>          <dd><p>In <abbr>XHTML</abbr> document, the root <code>html</code>
866          element must have an <code>xmlns</code> attribute          element must have an <code>xmlns</code> attribute as:
867          whose value is set to            <pre class="xml example"><code>&lt;html xmlns="http://www.w3.org/1999/xhtml"></code></pre></p></dd>
         <code>http://www.w3.org/1999/xhtml</code>.</p></dd>  
868      <dt><code>rss</code> element</dt>      <dt><code>rss</code> element</dt>
869          <dd><p>The document is written in some version of RSS.</p>          <dd><p>The document is written in some version of RSS.</p>
870          <p>The conformance checker does not support any version          <p>The conformance checker does not support any version
871          of RSS.  Use Atom 1.0 for feed documents.</p></dd>          of RSS.  Use Atom 1.0 for feed documents.</p></dd>
872      <dt><code>feed</code> element</dt>      <dt><code>feed</code> element</dt>
873          <dd><p>The Atom <code>feed</code> element must be          <dd><p>The Atom <code>feed</code> element must be
874          in the <code>http://www.w3.org/2004/Atom</code>          in the <code>http://www.w3.org/2005/Atom</code>
875          namespace.</p>          namespace as:
876              <pre class="xml example"><code>&lt;feed xmlns="http://www.w3.org/2005/Atom"></code></pre>
877            </p>
878          <p>The conformance checker does not support Atom 0.3.          <p>The conformance checker does not support Atom 0.3.
879          Use Atom 1.0 for feed documents.</p></dd>          Use Atom 1.0 for feed documents.</p></dd>
880      </dl>      </dl>
# Line 874  Web Document Conformance Checker (BETA)< Line 1017  Web Document Conformance Checker (BETA)<
1017  <section id="attribute-value-errors">  <section id="attribute-value-errors">
1018  <h2>Attribute Value Errors</h2>  <h2>Attribute Value Errors</h2>
1019    
1020    <d:item name="charset:not registered" class="attribute-value-warning warning"
1021        level="w">
1022      <d:message xml:lang="en">Character encoding name <code><var>$0</var></code>
1023      is not registered.</d:message>
1024      <d:desc xml:lang="en">
1025        <p>The specified character encoding name is not registered to
1026        <abbr>IANA</abbr>.  Use of registered character encoding name
1027        is a good practice to facilitate interoperability.</p>
1028    
1029        <dl class="switch">
1030        <dt><code>EUC-TW</code></dt>
1031          <dd><code>EUC-TW</code> is not registered.  Unfortunately, there
1032          is no registered name for that character encoding.  Use
1033          Big5 encoding with character encoding name <code>Big5</code>
1034          if it is enough to represent the document.</dd>
1035        <dt><code>ISO-2022-JP-1</code></dt>
1036          <dd><code>ISO-2022-JP-1</code> is not registered, nevertheless
1037          this character encoding name is documented in
1038          <a href="urn:ietf:rfc:2237"><abbr>RFC</abbr> 2237</a>.  Use
1039          <code>ISO-2022-JP-2</code> instead, since that character encoding
1040          is a superset of ISO-2022-JP-1.</dd>
1041        <dt><code>ISO-2022-JP-3</code>, <code>ISO-2022-JP-3-plane1</code></dt>
1042          <dd>These names are not registered and obsoleted in favor of
1043          <code>ISO-2022-JP-2004</code> and
1044          <code>ISO-2022-JP-2004-plane1</code>.</dd>
1045        <dt><code>ISO-2022-JP-2003</code>,
1046        <code>ISO-2022-JP-2003-plane1</code></dt>
1047          <dd>These names are not registered and corrected to
1048          <code>ISO-2022-JP-2004</code> and
1049          <code>ISO-2022-JP-2004-plane1</code>.</dd>
1050        <dt><code>ISO-2022-JP-2004</code>,
1051        <code>ISO-2022-JP-2004-plane1</code></dt>
1052          <dd>These names are not registered.  Unfortunately, there is
1053          no registered name for these character encodings.</dd>
1054        <dt><code>UTF-8N</code></dt>
1055          <dd><code>UTF-8N</code> is not registered.  Character encoding
1056          name <code>UTF-8</code> represents UTF-8 encoding with or
1057          without <abbr>BOM</abbr>.</dd>
1058        </dl>
1059    
1060        <p><strong>WARNING</strong>: This error might be raised for
1061        a registered character encoding name, since the character encoding
1062        name database of the conformance checker is not complete yet.</p>
1063      </d:desc>
1064    </d:item>
1065    
1066    <d:item name="charset:private" class="attribute-value-warning warning"
1067        level="w">
1068      <d:message xml:lang="en"><code><var>$0</var></code> is a private
1069      character encoding name.</d:message>
1070      <d:desc xml:lang="en">
1071        <p>The specified character encoding name is a private name and
1072        not registered to <abbr>IANA</abbr>.  Use of registered character
1073        encoding name is a good practice to facilitate interoperability.</p>
1074    
1075        <dl class="switch">
1076        <dt><code>x-euc-jp</code></dt>
1077          <dd>Use <code>EUC-JP</code> for the Japanese <abbr>EUC</abbr>
1078          character encoding.</dd>
1079        <dt><code>x-sjis</code></dt>
1080          <dd>Use <code>Shift_JIS</code> for standard Shift encoding scheme of
1081          <abbr>JIS</abbr> coded character set, or <code>Windows-31J</code>
1082          for Microsoft standard character set as implemented by
1083          Microsoft Windows.</dd>
1084        </dl>
1085      </d:desc>
1086    </d:item>
1087    
1088    <d:item name="charset:syntax error" class="attribute-value-error"
1089        level="m">
1090      <d:message xml:lang="en">The specified value is syntactically not a
1091      character encoding name.</d:message>
1092      <d:desc xml:lang="en">
1093        <p>The attribute value must be a character encoding name.  However,
1094        the specified value is not a character encoding name syntactically.
1095        The document is non‐conforming.</p>
1096        <p>Character encoding name is a string of <abbr>ASCII</abbr>
1097        printable characters, up to 40 characters.</p>
1098      </d:desc>
1099    </d:item>
1100    
1101  <d:item name="enumerated:invalid"  <d:item name="enumerated:invalid"
1102      class="attribute-value-error">      class="attribute-value-error">
1103    <d:message xml:lang="en">This attribute only allow a limited set of    <d:message xml:lang="en">This attribute only allow a limited set of
# Line 886  Web Document Conformance Checker (BETA)< Line 1110  Web Document Conformance Checker (BETA)<
1110    
1111      <dl>      <dl>
1112      <dt>HTML <code>meta</code> element, <code>http-equiv</code> attribute</dt>      <dt>HTML <code>meta</code> element, <code>http-equiv</code> attribute</dt>
1113          <dd><p>Only <code>Default-Style</code> and <code>Refresh</code>          <dd><p>Only values <code>Default-Style</code> and <code>Refresh</code>
1114          is allowed.</p>          are allowed.</p>
1115          <p>Value <code>Content-Type</code> is obsolete; for charset          <p>Value <code>Content-Type</code> is obsolete; for charset
1116          declaration, the <code>charset</code> attribute can be used as:          declaration, the <code>charset</code> attribute can be used as:
1117          <pre class="html example"><code>&lt;meta charset="<var>charset-name</var>"></code></pre>          <pre class="html example"><code>&lt;meta charset="<var>charset-name</var>"></code></pre>
# Line 905  Web Document Conformance Checker (BETA)< Line 1129  Web Document Conformance Checker (BETA)<
1129    </d:desc>    </d:desc>
1130  </d:item>  </d:item>
1131    
1132    <d:item name="enumerated:invalid:http-equiv:content-type"
1133        class="attribute-value-error">
1134      <d:message xml:lang="en">Character encoding declaration syntax
1135      <code class="html bad example">&lt;meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code>
1136      is obsolete.</d:message>
1137      <d:desc xml:lang="en">
1138        <p>Old long character encoding declaration syntax
1139        <code class="html bad example">&lt;meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code>
1140        is in use.  The document is non‐conforming.</p>
1141    
1142        <p>The new character encoding declaration syntax is:
1143          <pre class="html example"><code>&lt;meta charset="<var>charset-name</var>"></code></pre>
1144        </p>
1145      </d:desc>
1146    </d:item>
1147    
1148  <d:item name="duplicate ID"  <d:item name="duplicate ID"
1149      class="attribute-value-error">      class="attribute-value-error">
1150    <d:message xml:lang="en">This identifier has already been    <d:message xml:lang="en">This identifier has already been
# Line 954  Web Document Conformance Checker (BETA)< Line 1194  Web Document Conformance Checker (BETA)<
1194    </d:desc>    </d:desc>
1195  </d:item>  </d:item>
1196    
1197    <d:item name="mismatched charset name" class="attribute-value-error"
1198        level="m">
1199      <d:message xml:lang="en">Character encoding name <code><var>$1</var></code>
1200      is different from document character encoding
1201      <code><var>$0</var></code>.</d:message>
1202      <d:desc xml:lang="en">
1203        <p>The specified character encoding name is different from
1204        the character encoding of the document.  The document
1205        is non‐conforming.</p>
1206      </d:desc>
1207    </d:item>
1208    
1209  <d:item name="reserved browsing context name"  <d:item name="reserved browsing context name"
1210      class="attribute-value-error">      class="attribute-value-error">
1211    <d:message xml:lang="en">Browsing context name    <d:message xml:lang="en">Browsing context name
# Line 1027  Web Document Conformance Checker (BETA)< Line 1279  Web Document Conformance Checker (BETA)<
1279      The document is non-conforming.</p>      The document is non-conforming.</p>
1280    
1281      <p>For example, the table below is non-conforming:      <p>For example, the table below is non-conforming:
1282        <pre class="html non-conforming example"><code>&lt;table>        <pre class="html bad example"><code>&lt;table>
1283  &lt;tbody>  &lt;tbody>
1284  &lt;tr>&lt;td rowspan=2>&lt;/td>&lt;/tr>  &lt;tr>&lt;td rowspan=2>&lt;/td>&lt;/tr>
1285  &lt;/tbody>  &lt;/tbody>
# Line 1194  Web Document Conformance Checker (BETA)< Line 1446  Web Document Conformance Checker (BETA)<
1446      <code>text/cache-manifest</code> must contain a cache manifest.</p>      <code>text/cache-manifest</code> must contain a cache manifest.</p>
1447    
1448      <p>A cache manifest must start with a line whose content is      <p>A cache manifest must start with a line whose content is
1449      <code>CACHE MANIFEST</code> (exactly one space character between      <code class="manifest example">CACHE MANIFEST</code>
1450        (exactly one space character between
1451      <code>CACHE</code> and <code>MANIFEST</code>).</p>      <code>CACHE</code> and <code>MANIFEST</code>).</p>
1452    </d:desc>    </d:desc>
1453  </d:item>  </d:item>
1454  </section>  </section>
1455    
1456    <section id="information">
1457    <h2>Stability Information</h2>
1458    
1459    <d:item name="status:cr:element" class="level-i" level="i">
1460      <d:message xml:lang="en">This element is in the
1461      <strong>call‐for‐implementation</strong> stage.</d:message>
1462      <d:desc xml:lang="en">
1463        <p>The element is in the call‐for‐implementation stage.</p>
1464        
1465        <p>Usually, using the element is safe.  However, it is a new feature
1466        so that it might not be implemented correctly.  If it is found that
1467        the feature is hard or impossible to implement, the feature
1468        might be revised, or in some case it might be dropped.</p>
1469    
1470        <p>Elements defined by Atom 1.0, and XBL 2.0 belong to this
1471        class.</p>
1472      </d:desc>
1473    </d:item>
1474    
1475    <d:item name="status:lc:element" class="level-i" level="i">
1476      <d:message xml:lang="en">This element is in the <strong>last
1477      call for comments</strong> stage.</d:message>
1478      <d:desc xml:lang="en">
1479        <p>The element is in the last call for comments stage.</p>
1480        
1481        <p>The element is relatively mature, though the standardization
1482        is not done yet.  It may be used for experiments.  Since it is a new
1483        feature, it might not be implemented correctly or at all.  If it is
1484        found that the feature is hard or impossible to implement, the feature
1485        might be revised or might be dropped.</p>
1486    
1487        <p>Elements defined by Web Forms 2.0 as well as some elements
1488        defined by HTML5 belong to this class.</p>
1489      </d:desc>
1490    </d:item>
1491    
1492    <d:item name="status:wd:element" class="level-i" level="i">
1493      <d:message xml:lang="en">This element is documented in a <strong>working
1494      draft</strong>.</d:message>
1495      <d:desc xml:lang="en">
1496        <p>The element is documented in a working or editor's draft
1497        and not yet completed.</p>
1498        
1499        <p>The element should not be used for any practical purpose.
1500        The feature might be drastically changed later or might be
1501        entirely removed.</p>
1502    
1503        <p>Most of new elements defined by HTML5 belong to this class.</p>
1504      </d:desc>
1505    </d:item>
1506    
1507    <d:item name="status:non-standard:element" class="level-i" level="i">
1508      <d:message xml:lang="en">This element is <strong>not part of any
1509      standard</strong>.</d:message>
1510      <d:desc xml:lang="en">
1511        <p>The element is not part of any standard or draft.</p>
1512        
1513        <p>The element should not be used for any practical purpose.</p>
1514      </d:desc>
1515    </d:item>
1516    </section>
1517    
1518  <section id="unsupported-messages">  <section id="unsupported-messages">
1519  <h2><i>Unsupported</i> Messages</h2>  <h2><i>Unsupported</i> Messages</h2>
1520    
# Line 1322  to solve a problem in a confusing or pos Line 1637  to solve a problem in a confusing or pos
1637  It does not affect to the conformance of the document, and  It does not affect to the conformance of the document, and
1638  may sometimes be inappropriate.</td>  may sometimes be inappropriate.</td>
1639  </tr>  </tr>
1640  <tr id="level-unsupported" class="level-unsupported">  <tr id="level-i" class="level-i">
1641    <th scope="row">Information</th>
1642    <td>Conforming.</td>
1643    <td>An informational message just provides an additional information
1644    on the feature used in the document or the status of the retrieval
1645    or so on.
1646    It does not affect to the conformance of the document.</td>
1647    </tr>
1648    <tr id="level-u" class="level-u">
1649  <th scope="row">Not supported</th>  <th scope="row">Not supported</th>
1650  <td><em>Unknown</em>.</td>  <td><em>Unknown</em>.</td>
1651  <td>Some feature that is not supported by the conformance checker  <td>Some feature that is not supported by the conformance checker
Legend:
Removed from v.1.13  
changed lines
  Added in v.1.20
admin@suikawiki.org
 ViewVC Help
Powered by ViewVC 1.1.24