W3C HTML5 validator no longer accepting RDFa?
Internet
UPDATE: This issue has since been resolved.
As of last night, something is wrong with the W3C’s HTML5 validator and RDFa prefix syntax (maybe). Previously validating pages that employ either the html prefix tag, or Dublin Core schemas no longer validate.
Broken HTML5 prefix
This is how I currently employ RDFa Dublin Core metadata properties on my pages (and will be on Rubenerd.com soon):
<html prefix="dc: http://purl.org/dc/elements/1.1/"> [..] <meta property="dc:date" content="[some timestamp]" />
Doing so now generates this error:
“Element meta is missing required attribute name”
Attributes for element meta: name http-equiv content charset
The “property” attribute is now no longer even listed. Huh.
Broken HTML5 schemas
If you replace RDFa syntax with a schema link (such as to Dublin Core), and replace the meta properties with meta names:
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" /> <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" /> [..] <meta name="DC.date" content="[some timestamp]" />
You get this error:
“Bad value schema.dc for attribute rel on element link: The string schema.dc is not a registered keyword or absolute URL.”
I am unsure how to proceed. If this is an error in the evolving, beta HTML5 validatior, I’ll understand. If instead they’ve decided RDFa-like syntax can’t tango with HTML5 after all, I won’t be a very happy munchkin.
