- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Apr 2010 08:18:15 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9530 --- Comment #3 from Julian Reschke <julian.reschke@gmx.de> 2010-04-16 08:18:16 --- (In reply to comment #2) > (In reply to comment #0) > > #1: Validity depends on the current content of the Wiki registry. I'd like to > > see proof that conformance checkers are actually going to implement this. > > validator.nu already implements something similar for the cases of registered > language subtags and registered character encoding names. It reads in and > parses the current contents of the IANA registries for those > (http://www.iana.org/assignments/language-subtag-registry and > http://www.iana.org/assignments/character-sets) and then validates lang and > charset attribute values against those. The same kind of mechanism its using > for those could also be used for validating http-equiv attribute values. Mike, thanks for the feedback. My concern is that we have conformance requirements that nobody is aware of because validator.nu isn't checking them - this essentially applies to all WhatWG-Wiki-based registries. I'd like to find out what's keeping the validator.nu developers from implementing these checks (well, besides workload). Is checking these registries more complex than checking IANA registries? -- 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 Friday, 16 April 2010 08:18:19 UTC