- From: <bugzilla@jessica.w3.org>
- Date: Tue, 01 Feb 2011 06:13:47 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11909 --- Comment #9 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-02-01 06:13:40 UTC --- Follwoing off-list discussion with David, I would suggest the HTML-conformance requirement to go like this: ]] Polyglot mark-up conforms to a polyglot (as understood by the rest of these principles [DOM-compatible, no-quirks etc]) subset of one of the following: 1) the text/html syntax of the HTML5 spec; 2) the text/html syntax of the HTML5 spec + applicable spec(s);[1] 3) XML schema-based subsets of HTML5 (example: XHTML1.0); [2] NOTE [2]: XML schema-based supersets or additions the text/html syntax or to subsets of the text/html HTML5 syntax falls in under 2). NOTE [1]: the polyglot requirements must be met: "/>" must be limited to void elements per the HTML5 text/html syntax and all polyglot requirements are followed; [[ Those principles would, for 1), place all non-conforming HTML5 features in the cold; Goodbye to <xmp>, <plaintext>, on conformance grounds; Goodbye to <noscript> on polyglotness grounds (lack of DOM-compatibility); for 2), same as as 1) but would allow whatever the applicable spec permits, as long as it is "polyglot" - e.g. DOM-compatible); for 3), same as 1) except that some features forbidden by HTML5 would be permitted - e.g. the @compact attribute (and other attributes that HTML5 forbids but which XHTML1 may permit) while some features that HTML5 permits would be forbidden, such as the video element. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 1 February 2011 06:13:49 UTC