This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From the current text in the section 2.2.3 Extensibility it is not completely clear if document using features defined in applicable specification is conforming HTML5 document or not. Adding the following note after the note starting with "Note: As a suggested but not required convention..." should resolve any concerns: Note: If the applicable specification defines additional attributes and elements and they are used in a document, then such document is not conforming HTML5 document. But it might be conforming to the applicable specification.
Related: http://lists.w3.org/Archives/Public/public-html/2011Mar/0574.html At the time, we felt that the proposed changes identified in that decision made it clear. But if there are additional changes which can make this clearer, the chairs will not interfere. If it is decided that clarification is needed, I'd suggest that the last sentence of the proposed addition be reworded to indicate that the document may be conforming to the combination of HTML5 and one or more applicable specifications.
(In reply to comment #1) > If it is decided that clarification is needed, I'd suggest that the last > sentence of the proposed addition be reworded to indicate that the document may > be conforming to the combination of HTML5 and one or more applicable > specifications. I'm happy with such change. So the proposal currently is Note: If the applicable specification defines additional attributes and elements and they are used in a document, then such document is not conforming HTML5 document. But it might be conforming to the combination of HTML5 and one or more applicable specifications.
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 document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change. Rationale: I think this is already really clear in the spec: > 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 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.