W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2012

[Bug 20197] Formally define polyglot’s relationship to HTML5 ("applicable spec")

From: <bugzilla@jessica.w3.org>
Date: Mon, 03 Dec 2012 05:42:25 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-20197-2486-CmALuj9cfP@http.www.w3.org/Bugs/Public/>

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
                 CC|                            |xn--mlform-iua@xn--mlform-i
                   |                            |ua.no

--- Comment #1 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
]] Applicable specifications MAY define new document content (e.g. a foobar
element), MAY prohibit certain otherwise conforming content (e.g. prohibit use
of <table>s), or MAY change the semantics, DOM mappings, or other processing
rules for content defined in this specification. Whether a document is or is
not a conforming HTML5 document does not depend on the use of applicable
specifications: if the syntax and semantics of a given conforming HTML5
document is unchanged by the use of applicable specification(s), then that
document remains a conforming HTML5 document. If the semantics or processing of
a given (otherwise conforming) document is changed by use of applicable
specification(s), then it is not a conforming HTML5 document. For such cases,
the applicable specifications SHOULD define conformance terminology.

As a suggested but not required convention, such specifications might define
conformance terminology such as: "Conforming HTML5+XXX document", where XXX is
a short name for the applicable specification. (Example: "Conforming
HTML5+AutomotiveExtensions document").[[

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 3 December 2012 05:43:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:35 UTC