This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 16949 as part of operation convergence. Originally filed: 2012-05-07 04:07:00 +0000 Original reporter: Roger Olsson <master_pumpkin_@hotmail.com> ================================================================================ #0 Roger Olsson 2012-05-07 04:07:27 +0000 -------------------------------------------------------------------------------- 13.1 Writing XHTML documents 'The syntax for using HTML with XML, whether in XHTML documents or embedded in other XML documents, is defined in the XML and Namespaces in XML specifications.' I assume that instead of the HTML syntax, "HTML" refers to the "abstract language" (also called HTML?) here. I guess the reader has to figure out how the abstract language maps to XML. The XML specifications don't give that information, contrary to what this sentence suggests. At least XHTML documents are not valid XML since there is no DTD. 'This specification does not define any syntax-level requirements beyond those defined for XML proper.' What does "defined for" mean here? The abstract language clearly sets syntax-level requirements (part of the syntax), since any well-formed XML document could otherwise be called XHTML. ================================================================================
I suggest resolving this by adding the following text to the introduction for the "The XHTML syntax" section: "The syntax-level contraints for content written in the HTML language and served with an XML MIME type -- whether in XHTML documents or embedded in other XML documents -- are defined in the XML and Namespaces in XML specifications." See related discussion at bug 16949.
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: none Rationale: I believe that the description is clear and consistent with common practice. Discussion in the related bug 16949 confirms that opinion.