Standards Supported by Web Document Conformance Checker

Summary

Standard	Version	Note
HTML	5 (Editor's Draft)	Partially
Atom	RFC	Partially
XML	1.0 Fourth Edition	Tentative
	1.1 Second Edition	Tentative
XML Namespaces	1.0 Second Edition	Tentative
	1.1 First Edition	Tentative
CSS	2.1	Most part
Selectors	3
HTTP		Tentative (no validation)

DOM

The current implementation assumes that there are following requirements:

• The document element (or root element) MUST be allowed to be a root element. For example, an html element in http://www.w3.org/1999/xhtml namespace is allowed to be a root element by the HTML5 specification.

HTML

HTML5 is partially implemented.

In addition, the current implementation assumes that there are following requirements:

• Any element or attribute in the HTML namespace which is not defined by the HTML5 specification (including Web Forms 2.0 specification) MUST NOT be used.
• For an element in the HTML namespace, any attribute in the null namespace (or per‐element partition) MUST NOT be used unless it is allowed by the HTML5 specification (including Web Forms 2.0 specification).
• @@ Forms elements: ...
• For the attribute not defined in HTML5, the following definitions are applied.

  These definitions are updated version of their original definitions in previous versions of HTML4.

  For each row in the table below, if an attribute (i.e. an Attr node) met the following conditions, then the value attribute value of the node MUST be valid with regard to the constraints shown in the Value cell of the row. The conditions are:

  • There is an owner element (i.e. the Element node pointed by the ownerElement attribute of the Attr node).
  • The namespaceURI attribute value of the owner element is http://www.w3.org/1999/xhtml.
  • The manakaiLocalName attribute value [@@ TODO: ref] of the owner element is equal to the value in the Element cell of the row.
  • The namespaceURI attribute value of the Attr node is null.
  • The manakaiLocalName attribute value of the Attr node is equal to the value in the Attribute cell of the row.

  Element	Attribute	Value
  body	background	Same as img src [HTML5]
  img	longdesc	Same as img src [HTML5]
  object	classid or codebase	Same as img src [HTML5]
  object	archive	Same as a ping [HTML5]
  object	codetype	Same as object type [HTML5]
  param	type	Same as object type [HTML5]
  div, h1, h2, h3, h4, h5, h6, or p	align	Enumerated attribute [HTML5]
  img or object	align	Enumerated attribute [HTML5]
  br	clear	Enumerated attribute [HTML5]
  param	valuetype	Enumerated attribute [HTML5]
  pre	width	Valid non-negative integer [HTML5]
  ul, ol, dir, menu, or dl	compact	Boolean attribute [HTML5]
  table	frame or rules	Enumerated attribute [HTML5]
  td	scope	Same as scope attribute of the th element [HTML5]
  tbody, thead, tfoot, colgroup, col, tr, td, or th	align or valign	Enumerated attribute [HTML5]
  link	target	Valid browsing context name or keyword [HTML5]
  meta	schema	Any string
  a or link	rev	Unordered set of unique space-separated tokens [HTML5] (where any word is allowed)
  table	cellpadding	A non-negative integer [HTML5] or a non-negative integer [HTML5] followed by a % character
  	cellspacing

• Any value MAY be specified to the version attribute of an html element.
• @@ elements ...

  Element	Content Model	Allowed Context
  center	Same as div [HTML5]

Atom

The current implementation assumes that there are following requirements:

• Elements and attributes in the Atom namespace, as well as attributes in the null namespace for an element in the Atom namespace, MUST NOT be used except for contexts where they are allowed by the Atom specification.
• Inter-element whitespace [HTML5], processing instructions, and comments MUST be ignored for the purpose of conformance of the content of an element.

CSS

CSS @namespace and Selectors Level 3 are fully implemented.

CSS 2.1 and CSS Color Level 3 are partially implemented.

Since the CSS 2.1 specification is sometimes ambigious or disagree with browsers, our implementation is tend to copy what browsers do unless there is strong resaon to do different thing.

In addition, the current implementation assumes that there are following requirements:

• The charset parameter of the media type text/css MUST be treated as if it were an unknown parameter for the purpose of determining styling langauge for an HTML style element.
• Content of an HTML style element whose content is interpreted as a CSS style sheet MUST consist of zero or more text nodes. Note that it may also contain zero or more comment and/or processing instruction nodes.