--- test/html-webhacc/error-description-source.xml 2007/07/16 13:56:26 1.4 +++ test/html-webhacc/error-description-source.xml 2007/09/03 14:30:46 1.9 @@ -28,6 +28,21 @@ + + Tag <$0> + is not allowed after the end tag </body>. + +

The start or end tag of an element appears after the + body element has been closed. The document is + non-conforming.

+ +

Any content of the document other than head + contents and comments must be put into the body + element.

+ + + The & character must @@ -38,6 +53,9 @@ is not part of any reference appears in the input stream. The document is non-conforming.

+

Any & character in URI (or IRI) + must be escaped as &amp;.

+

The & character must be the first character of a reference:

@@ -63,18 +81,41 @@ + + A </ string is not followed + by a tag name. + +

There is a < (U+003C + LESS-THAN SIGN) character + immediately followed by a / (U+005F + SOLIDUS) character, which is not part + of any end tag, in the input stream. The document + is non-conforming.

+ +

The </ sequence immediately followed + by an EOF is + interpreted as a string data of </.

+ +

The </ sequence as string data must + be escaped as: + 

&lt;/
+

+ + + A < character is not followed by tag name or by a ! character. -

A < (U+003C LESS-THAN - SIGN) character which is not part of any markup appears - in the input stream.

+

A < (U+003C + LESS-THAN SIGN) character which is not part + of any markup appears in the input stream.

The < character as a data character must be escaped as: - 

<lt;
+ 
&lt;

 @@ -92,7 +133,6 @@ The document is non-conforming.

The string &# must be the first two characters - NUMBER SIGN) character must be the first two characters of a reference:

Numeric character reference
@@ -107,7 +147,7 @@

To represent &# as data characters, use - named entity reference: + a named entity reference for the & character: 

&amp;#

@@ -129,12 +169,66 @@ of the code point of the character to be referenced.

To represent &#x as data characters, use - named entity reference: + a named entity reference for the & character: 

&amp;#x

+ + String <! is not followed + by --. + +

There is a < (U+003C + LESS-THAN SIGN) character + followed by a ! (U+0021 + EXCLAMATION MARK) character, + which is not followed by a -- or + !DOCTYPE. The document is non-conforming.

+ +
+
Comments
+
In HTML documents, comments must be introduced by + <!-- (<! immediately followed + by two -s) and must be terminated by + -->. Strings <! not followed + by -- and <!- not followed by + - are not valid open delimiters for comments.
+
Marked sections, including CDATA sections
+
Marked sections are not allowed in HTML documents.
+
Markup declarations
+
Markup declarations, except DOCTYPE + and comment declarations, are not allowed in HTML documents.
+
String <!
+
String <! must be escaped as + &lt;!.
+
+ + + + + String </ is not followed + by tag name. + +

There is a < (U+003C + LESS-THAN SIGN) character + immediately followed by a / (U+005F + SOLIDUS) character, which is not part + of any end tag, in the input stream. The document + is non-conforming.

+ +

The </ sequence not followed by a + tag name is parsed as an opening of bogus comment.

+ +

The </ sequence as string data must + be escaped as: + 

&lt;/
+

+ + + There is a -- sequence @@ -154,7 +248,8 @@ - There are two attributes with same name. + There are two attributes with name + $0.

There are more than one attributes with the same name in a tag. The document is non-conforming.

@@ -178,11 +273,72 @@ embed, param, area, col, and input elements.

+
+
<script/>
+

The void element syntax cannot be used for script + element. Even for an empty script element, + there must be an explicit end tag </script>.

+ +

NOTE: Though some user agents interpret + void element syntax for script element as the + closing of the element, such usage is not allowed under + the current standard.

+
<basefont/>, <bgsound/>, + <frame/>, <keygen/>, + <spacer/>, <wbr/>
+
These elements are themselves non-conforming.
+ +
<command/>, <event-source/>, + <source/>
+
Future revision of HTML5 parsing algorithm is expected + to allow void element syntax for these elements.
+
<a/>, <p/>
+
These elements are not always empty and therefore + void element syntax is not allowed.
+
+

Note that, unlike in XML, the void element syntax has no effect in HTML.

 + + + Processing instruction + (<?...>) cannot be used. + +

Processing instructions (<?...?>), + including XML declaration (<?xml ...?>) + and XML style sheet PI + (<?xml-stylesheet ...?>), are not allowed + in the HTML syntax. The document is non-conforming.

+ +
+
<?xml?> (XML declaration)
+
XML declaration is unnecessary for HTML documents.
+
<?xml-stylesheet?> (XML style sheet + PI
+
Use HTML link element with rel + attribute set to stylesheet (or, + alternate stylesheet for an alternate style + sheet).
+
<?php?> (PHP code)
+
The conformance checker does not support + checking for PHP source documents.
+
Other processing instructions
+
Processing instructions cannot be inserted in an HTML + document. Use XML document or insert + ProcessingInstruction node by scripting.
+
+ +

Web browsers will parse processing instructions as bogus + comments. Some legacy Web browsers, such as IE:mac and + some mobile Web browsers, will display processing instructions + as string.

+ + +
@@ -213,10 +369,22 @@ + + Anchor cannot be nested. + +

HTML a elements cannot be nested. + The document is non-conforming.

+ +

In the HTML syntax, a start tag of the a + implies the end tag of any opening a element.

+ + + Tag <$0> - is not allowed in body. + is not allowed in the body element.

The start or end tag of an element, which cannot be a descendant of body element, appears @@ -225,10 +393,24 @@ + + Start tag <head> + is not allowed in the head element. + +

There is a start tag <head> in the + <head> element. The document is non-conforming.

+ +

In an HTML document there must not be more than + one head element, therefore no more than one + start tag <head> can appear in the input stream.

+ + + Tag <$0> - is not allowed in table. + is not allowed in a table element.

The start or end tag of an element, which cannot be a child of table element, appears @@ -277,7 +459,7 @@ - This document does not start with the + This document does not start with a DOCTYPE.

The document does not start with a DOCTYPE. @@ -303,14 +485,32 @@ + + This <html> tag is not + the first start tag. + +

There is a start tag of the html element + that it not the first start tag in the input stream. + The document is non-conforming.

+ +

In an HTML document, there cannot be more than one + html element and therefore there cannot be + more than one <html> tag. In addition, + nothing can be placed before the <html> tag + except a DOCTYPE, white space characters, + and comments.

+ + + This document is written in an old version of HTML.

The document contains a DOCTYPE declaration - that is different from HTML5 DOCTYPE (i.e. <!DOCTYPE - HTML>). The document is non-conforming.

+ that is different from HTML5 DOCTYPE (i.e. + <!DOCTYPE HTML>). The document is non-conforming.

The document might or might not be conformant to some version of HTML. However, conformance to any HTML @@ -347,24 +547,20 @@ context. The document is non-conforming.

Possible causes: -

-
If the erred element is an inline-level element (such - as a or span)
-

A data character cannot be a child - of certain sectioning elements such as body, - section, and blockquote.

- -

Any inline-level content must be put - in e.g. paragraph element such as p.

-
If the erred element is a block-level element (such as - div or hn)
-

Though some elements such as div, - li, and td allow - either one of block-level or inline-level content - is allowed. If there is a block-level content, - any inline-level content must be put - in e.g. paragraph element such as p.

-
+
    +

  • A data character cannot be a child + of certain sectioning elements such as body, + section, and blockquote.

    + +

    Any inline-level content must be put + in e.g. paragraph element such as p.

    • +

  • Though some elements such as div, + li, and td allow + either one of block-level or inline-level content + is allowed. If there is a block-level content, + any inline-level content must be put + in e.g. paragraph element such as p.

    • +

@@ -409,37 +605,84 @@

An element appears where it is not allowed. The document is non-conforming.

-

Note: The conformance checker does - not support form elements yet.

-

Possible causes: -

-
If the erred element is an inline-level element (such - as a or span)
+
+
If the element with the error is an inline-level element, + such as a, progress, or img

An inline-level element cannot be a child of certain sectioning elements such as body, section, and blockquote.

Any inline-level content must be put in e.g. paragraph element such as p.

-
If the erred element is a block-level element (such as - div or hn)
-

Though some elements such as div, - li, and td allow - either one of block-level or inline-level content - is allowed. If there is a block-level content, - any inline-level content must be put - in e.g. paragraph element such as p.

-
If the erred element is the root html element
+
If it is a block-level elements, such as aside, + div, hn, + p, or section
+
+
If the parent element is div, + li, td, or th
+ + +

The parent element allows either + block-level or inline-level content. If there is a + block-level content, any inline-level content must be + put in e.g. paragraph element such as p.

+

For example, an HTML document fragment + <div><p>Hello!</p> World!</div> + is non-conforming, since a word World! does not belong + to any paragraph. (If not part of any paragraph, what is + it!?) A conforming example would be: + 

<div><p>Hello!</p> <p>World!</p></div>
+

+
If the parent element does not allow + block-level elements as content
+
The element is not allowed to be inserted here. + For example, a div element cannot be + a child of an h1 element.
+
+
If the element with the error is a noscript element
+
The noscript element is allowed only in the context + where a block-level or inline-level content is expected + and in the head element. + It cannot be used in e.g. ul, table, + or select.
+
If the element with the error is the html element + that is the root element of an XHTML document

In an XHTML document, the root html element must have an xmlns attribute whose value is set to http://www.w3.org/1999/xhtml.

+
If the element with the error is blink, + center, or marquee element
+
These elements are not part of the HTML standard. + Use CSS for styling control.
+ +
button, datalist, form, + input, label, + optgroup, option, output, + rb, rp, rt, ruby, + textarea, or textarea element
+ +
These elements are intentionally not supported by the conformance + checker yet.

+ + There is no $0 + element before this element. + +

There must be an element before another element, but there + is not. The document is non-conforming.

+ +

For example, there must be a dt element + before any dd element.

+ + +
@@ -454,11 +697,35 @@ is non-conforming.

Some attribute is defined as required. - For example, any img element must have - alt and src attributes specified. Without required attributes specified, user agents - cannot provide the full functionality of the element - to the user.

+ cannot provide full functionality of the element to the user.

+ +
+
HTML img element
+
The src attribute must be specified. + Additionally, the alt attribute must be specified + in many cases.
+
HTML link element
+
The rel attribute must be specified. + Note that the rev attribute is obsolete.
+
+ + + + + Attribute + {local-name} is not allowed for + {element-local-name} element. + +

An attribute is specified where it is not allowed. + The document is non-conforming.

+ +
+
HTML meta element
+
For HTML meta element, only one of + name, http-equiv, or charset + attribute is allowed.
+
@@ -466,16 +733,22 @@ class="attribute-error"> The xml:lang attribute is not allowed in HTML document. - +

The xml:lang attribute is not allowed in HTML document. The document is non-conforming.

-

The lang attribute in the null - namespace for HTML elements is defined as conforming only for - XML document.

+

Use of the xml:lang attribute is conforming + only in XML documents.

To specify natural language information in HTML document, use lang attribute instead.

+ +

XHTML 1.0 Appendix C was encouraged to specify both + lang and xml:lang attributes with + the same value. Such a duplication has no effect in practice. + Use only one of lang (in HTML) or xml:lang (in + XML).

+ @@ -506,8 +779,8 @@ XML document. The document is non-conforming.

The lang attribute in null - namespace for HTML elements is defined as conforming only for - HTML document.

+ namespace for HTML elements is conforming only in + HTML documents.

To specify natural language information in XML document, use xml:lang attribute instead.

@@ -523,7 +796,7 @@

The xmlns attribute in the null namespace is not allowed in XHTML document.

-

This error should not occur in conformance-checking +

This error should not occur in conformance-checking of static documents.

 @@ -536,7 +809,32 @@ This attribute only allow a limited set of - values and the specified value is not one of them. + values and the specified value {@} is not one + of them. + +

For this attribute only several values are allowed and the + value of the attribute is not one of them. The document + is non-conforming.

+ +
+
HTML meta element, http-equiv attribute
+

Only Default-Style and Refresh + is allowed.

+

Value Content-Type is obsolete; for charset + declaration, the charset attribute can be used as: + 

<meta charset="charset-name">
+ ... where charset-name is a name of the character encoding + of the document, such as utf-8.

+

Values Content-Style-Type and + Content-Script-Type are currently not allowed.

+

Value Keywords is not allowed. Use + name attribute instead of http-equiv + attribute.

+

Values Expires, Pragma, + and Cache-Control are not allowed; + use real HTTP header fields for cache control.

+
+ ? --> - The link type $0 cannot be specified for this element. @@ -568,18 +866,29 @@ The link type $0 is non-conforming. -

The specified link type is non-conforming. The entire document - is non-conforming.

+

The specified link type is non-conforming, and therefore + the document is non-conforming.

-

For example, in place of non-conforming link type copyright - you must use link type license.

+
+
Link type contents
+
Use link type index.
+
Link type copyright
+
Use link type license.
+
Link type home
+
Use link type index.
+
Link type start
+
Use link type first.
+
Link type toc
+
Use link type index.
+
- This browsing context name is reserved. - + Browsing context name + {@} is reserved. +

The specified browsing context name is reserved. The document is non-conforming.

@@ -592,7 +901,7 @@ browsing context names _blank, _main, and _replace. However, they are not conforming attribute values.

- +
@@ -636,6 +945,28 @@ th) in the last row. + + This rowspan attribute + results in creating a table row that does not contain + any cell anchored to it. + +

The rowspan attribute value of the cell + is so specified that it extends a table in the row axis. + However, the extended row does not contain any cell by itself. + The document is non-conforming.

+ +

For example, the table below is non-conforming: + 

<table>
+<tbody>
+<tr><td rowspan=2></td></tr>
+</tbody>
+</table>
+ ... since the second row contains only + a cell that spans between first and second rows.

+ + +
@@ -643,18 +974,20 @@ - An obsolete subtype is used. + {@}: An obsolete + subtype is used. - A private (x- or x.) - subtype is used. + {@}: A private + (x- or x.) subtype is used. - The subtype is not registered to IANA. + {@}: The subtype is + not registered to IANA. @@ -665,18 +998,32 @@ - This string is not an IRI syntactically. + The specified value is syntactically not an IRI + reference. + +

The specified value does not satisfy the syntactical requirements + for IRI references. The document is non-conforming.

+ +

Possible causes: +

    +
  • The string might contain one or more white space characters. + Especially, the (U+0020 + SPACE) character cannot be + used in IRI references.
    • +
+

+
-
-

URI (or IRI) Warnings

+
+

URI (or IRI) Should-level Errors

- Dot-segment (. or - ..) should not occur in an absolute reference. + A dot-segment (. or + ..) occurs in an absolute reference.

Dot-segment (. or ..) should not occur in an absolute reference.

@@ -691,14 +1038,14 @@ - This IRI should explicitly end with - /. + This IRI does not end with + a /. - Hexadecimal digit in percent-encoding - should be in lowercase. + A lowercase hexadecimal digit is used + in percent-encoding.

The hexadecimal digit in percent-encoding string in the IRI is in lowercase. Though the IRI is conforming, @@ -717,36 +1064,59 @@ + + URI scheme name is in uppercase. + +

The scheme part of the IRI is written in uppercase letter.

+ +

Uppercase scheme names are not required to be processed + correctly.

+ + + +

Unsupported Messages

- - This attribute is not supported by the - conformance checker; it might or might not be conforming. + Conformance checking for element + {local-name} is not supported; it might or + might not be conforming. -

The conformant checker does not support the attribute. +

The conformant checker does not support the element. It cannot determine whether the document is conforming or not.

 - - This element is not supported by the - conformance checker; it might or might not be conforming. + Conformance checking for attribute + {local-name} of element + {element-local-name} is not supported; + it might or might not be conforming. -

The conformant checker does not support the element. +

The conformant checker does not support the attribute. It cannot determine whether the document is conforming or not.

 - The link type $0 is not + Link type $0 is not standardized or registered at the time of the release of the conformance - checker; it is non-conforming unless it has now been + checker; it is non-conforming unless it now has been registered.

The rel attribute is defined as a list of link types. @@ -759,6 +1129,12 @@ The link type might have been added to the registry since then. In such case it might be conforming. Otherwise, the document is non-conforming.

+ +
+
Link types shortcut icon
+
Link type shortcut is not registered. + Use only icon for linking to so-called favicon.
+
@@ -808,11 +1184,11 @@

License of This Document

-

Copyright 2007 Wakaba

-

This library is free software; you can redistribute it +

Copyright 2007

+

This document is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

- + \ No newline at end of file