NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 887 - Synchronize meta name attribute recognition with the spec
Synchronize meta name attribute recognition with the spec
Status: RESOLVED FIXED
Product: Validator.nu
Classification: Unclassified
Component: General
HEAD
All All
: P2 normal
Assigned To: Nobody
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-18 15:07 CET by Jukka K. Korpela
Modified: 2011-12-20 20:18 CET (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jukka K. Korpela 2011-12-18 15:07:36 CET
For example,

<meta name="og:type" content="website" />

is rejected, with the message
“A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.”

Yet, the WHATWG wiki contains og:type (it seems to have been added there in October).

So apparently validator.nu has not been updated for some time to reflect the WHATWG wiki contents.

Preferably, set up automated synchronization. As this may be rather difficult and would take time, please do a manual update and include a note about the latest update visibly in the validator.nu interface and/or the relevant error message(s) and/or the WHAT wiki page.
Comment 1 Henri Sivonen 2011-12-19 10:03:34 CET
I'll sync the data, but I'm curious: What software consumes name="og:type" (as opposed to bogo-RDFa property="og:type")?
Comment 2 Henri Sivonen 2011-12-19 10:59:28 CET
I have synchronized the data.

However, before synchronizing, I curated the registry and moved non-compliant registrations out of the registration table to the list of incomplete registrations. og:type was among those. The linked spec doesn't specify og:type as a keyword to be used in the name attribute on the meta element.
Comment 3 Vineet Gupta 2011-12-20 20:18:07 CET
(In reply to comment #2)
> I have synchronized the data.
> 
> However, before synchronizing, I curated the registry and moved non-compliant
> registrations out of the registration table to the list of incomplete
> registrations. og:type was among those. The linked spec doesn't specify og:type
> as a keyword to be used in the name attribute on the meta element.

Yes, I had checked you had moved the Facebook.com tags to Proposals that don't meet the requirements for a registration and also done the clean up the page. But as now Facebook, Google, Twitter are becoming the major traffic generators for website and if there meta tags are moved out of valid tag's then how one could validate web page. HTML5 is providing Backwards compatibility and page get validate one with <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/html401-rdfa-1.dtd">. Kindly let me know how to validate the web page with HTML5. Millions of web pages today use Facebook like button and comments and all are invalid, kindly provide some solution to resolve the issue, if it is not already provided....