- From: <bugzilla@jessica.w3.org>
- Date: Mon, 20 Dec 2010 12:15:36 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11064 --- Comment #15 from David Carlisle <davidc@nag.co.uk> 2010-12-20 12:15:36 UTC --- (In reply to comment #14) > (In reply to comment #12) > > I think that a mechanical representation of the rules (perhaps better in > > schematron or relaxng than dtd) would be a lot shorter than the document, so > > actually easier to see at a glance. > > I think this is not a good idea, because polyglotness includes lower-level > constraints that can't be expressed in Schematron or RELAX NG. For example, the > requirement not to have an XML declaration and the requirement to have one of > the few doctypes can't be represented in Schematron or RELAX NG. the posted schematron _only_ tries to check the constraints needed to ensure that a conforming html5 document that is well formed xml is polyglot. If either of the things you mention are wrong, then the document isn't conforming html5, so fails the preconditions for using this. (Basically if the document hasn't already been cleared by validator.nu, it shouldn't be used with this schematron) However there are a couple of things that you can't check as noted in my email to the list, and also checking that entities are not used requires using an xml parser that doesn't read the dtd, so it might yet be better to have some custom code that checks these things. However I think having such a mechanical check helps to distinguish between those requirements that are needed for the document to be valid html5, those that are needed for the document to be well formed XML, and those that are needed for the document to be polyglot. The schematron _only_ tries to check the last of these. The polyglot document currently has requirements of all three types, but doesn't state which category each requirement is in. -- 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 Monday, 20 December 2010 12:15:40 UTC