This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20197 - Formally define polyglot’s relationship to HTML5 ("applicable spec")
Summary: Formally define polyglot’s relationship to HTML5 ("applicable spec")
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2012-12-03 05:15 UTC by Leif Halvard Silli
Modified: 2013-04-24 16:45 UTC (History)
5 users (show)

See Also:


Description Leif Halvard Silli 2012-12-03 05:15:06 UTC
Please define polyglot markup’s relationship to HTML5. Sam recently described it as an applicable spec in HTML5's meaning of it,

with the nuance that polyglot markup is *also* a subset of HTML5. I think this should be explicitly expressed in the polyglot markup. I guess it is enough if it is an informative statement.
Comment 1 Leif Halvard Silli 2012-12-03 05:42:25 UTC
]] 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").[[
Comment 2 Eliot Graff 2013-04-24 16:45:32 UTC
    EDITOR'S RESPONSE: This is an Editor's Response to your comment. If
    you are satisfied with this response, please change the state of
    this bug to CLOSED. If you have additional information and would
    like the Editor to reconsider, please reopen this bug. If you would
    like to escalate the issue to the full HTML Working Group, please
    add the TrackerRequest keyword to this bug, and suggest title and
    text for the Tracker Issue; or you may create a Tracker Issue
    yourself, if you are able to do so. For more details, see this

    Status: Rejected
    Rationale: After researching the definition and use of "applicable specifications" and speaking with Sam about whether the relationship between polyglot and html5 could, should, or must be defined, I don't find that the compelling relationship exists or that there is benefit to either spec in creating that relationship.