- From: <bugzilla@jessica.w3.org>
- Date: Mon, 03 Dec 2012 05:36:31 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20198 Bug ID: 20198 Summary: Formally define that polyglot can be extended Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC URL: http://www.w3.org/TR/html-polyglot/#introduction OS: All Status: NEW Severity: normal Priority: P2 Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) Assignee: eliotgra@microsoft.com Reporter: xn--mlform-iua@xn--mlform-iua.no QA Contact: public-html-bugzilla@w3.org CC: eliotgra@microsoft.com, mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org See: http://www.w3.org/mid/20121130201051140186.fa51de03@xn--mlform-iua.no Issue: the XML/HTML task force came to the, in my view, incorrect conclusion that polyglot markup cannot be extended. On the question "2.4 How can islands of XML be embedded in HTML?", the group concluded that polyglot markup, for pure validation reasons, was no aid: "Note also that polyglot markup is not an aid here as it forbids arbitrary XML content from the document." See: http://www.w3.org/TR/html-xml-tf-report/#uc04 But this conclusion, which sounds like thinking from the era of DTD-based XHTML, seems just as correct and as it is gravely wrong. Because the thing is that HTML5 itself cannot be extended. Or, it can be extended. But then it is not HTML5 anymore. (Though - ah - there is a difference, when I think about it, between being extended via applicable spec and be extended by some extra spec.) So, perhaps say something like this - as an informative note somewhere: Polyglot markup, itself being HTML5, supports extensiblity according to the rules that HTML5 draws up <http://www.w3.org/TR/html5/infrastructure.html#extensibility>, but the extension must pay attention to fullfilling the polyglot principles. Also, it should probably be said that that polyglot markup stops being polyglot markup, in the formal sense, in the moment the markup stops conforming to HTML5. (If there are some extension methods that shoud definitely be ruled out as not polyglot, then of course it would be fine to mention it.) And, also - being XHTML5, it could - on a postive note - be fine to say that polyglot markup can be easily extended when or if it is served as applixation/xhtml+xml. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 3 December 2012 05:37:00 UTC