- From: Julian Matz <julianmatz@netlink.ie>
- Date: Wed, 20 Mar 2013 18:47:51 +0000
- To: "Michael[tm] Smith" <mike@w3.org>
- CC: www-validator@w3.org
Thanks, Mike, for clearing that up. I wasn't aware of the issue with the documentation. It now makes sense. I assumed that incomplete proposals would be moved under "Proposals that don't meet the requirements for a registration" or "Failed proposals". Julian On 20/03/2013 18:32, Michael[tm] Smith wrote: > Julian Matz <julianmatz@netlink.ie>, 2013-03-20 00:25 +0000: > >> The error message is as follows: >> >>> Line 10, Column 109: Bad value google-translate-customization for attribute name on element meta: Keyword google-translate-customization is not registered. >>> >>> …ustomization" content="xxx....xxx"> >> >> However, the metadata name "google-translate-customization" is >> registered at >> http://wiki.whatwg.org/wiki/MetaExtensions#Registered_Extensions > > It's not properly registered. The "Google documentation" hyperlink there > goes to http://googlewebmastercentral.blogspot.co.nz/2012_05_01_archive.html, > which is a blog posting, not a spec. And that blog posting doesn't actually > even mention "google-translate-customization" at all, as far as I can see. > >> My suggestion would be to either stick to the official, original specs, > > The HTML spec is the official, original, spec. And it formally references > the WHATWG wiki page. > >> and remove the message about WHATWG, or stay updated with the WHATWG >> wiki/database. Otherwise, it's confusing. > > In this case, the "google-translate-customization" is intentionally not > supported, because it's not properly registered. If somebody cares to take > the time to properly register it by linking to an actual specification that > defines what it means, that'd be great. > > --Mike >
Received on Wednesday, 20 March 2013 18:54:29 UTC