- From: <bugzilla@jessica.w3.org>
- Date: Mon, 18 Feb 2013 13:51:08 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20993 Robin Berjon <robin@w3.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |robin@w3.org Resolution|--- |WONTFIX --- Comment #1 from Robin Berjon <robin@w3.org> --- 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: Here's what the XML specification has to say about this: """ Validity constraint: Root Element Type The Name in the document type declaration MUST match the element type of the root element. """ This is a *validity constraint*. Which is to say: """ [Definition: A rule which applies to all valid XML documents. Violations of validity constraints are errors; they MUST, at user option, be reported by validating XML processors.] """ That only makes sense if you see what a "valid" XML document is: """ An XML document is valid if it has an associated document type declaration and if the document complies with the constraints expressed in it. """ Since XHTML5 has no DTD to define constraints on it, an XHTML5 can never be made to pass validity constraints. What you are requesting be checked should in fact never be checked (unless you invent an XHTML5 DTD of your own, but then you'd get the behaviour you want as per the XML spec automatically.) An XML processor that enforces the Name constraint while there is no DTD is in violation of the XML specification, as per my reading. It is no business of the HTML specification to modify XML (unless strictly required by Web compatibility). So concerning your justifications: (1) is not supported by the XML specification. (2) I don't think that this is a justification. Authors should be empowered to cry out their love of web technology wherever they see fit. (3) is a problem for polyglot to address. (4) I don't really understand what you're trying to get at there. I don't think that encouraging validation using XML Schema is a good practice in any situation. (5) seems to be a comment about NU. (6) I don't understand, sorry. Concerning your notes: NOTE 1: if your XML editor enforces DTD validation, you are using a broken XML editor. NOTE 2: but that is already covered by the XML specification. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 18 February 2013 13:51:12 UTC