This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Since HTML5 does not have a version specification and RDFa does, <html version="HTML+RDFa 1.1" lang="en"> can be confusing with regard to understanding what is actually being versioned here. It seems to be that it's HTML (implied 5) plus RDFa 1.1 but without an explicitly stated HTML version number, it looks like the it is 1.1 of something called HTML+RDFa. My recommendation would be to add a version number to the HTML part of the string: <html version="HTML5+RDFa 1.1" lang="en">
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Fixed Change Description: RDFa Core 1.1 has dropped the @version attribute. As a result, HTML+RDFa specification is now version-less in its design: http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/#sotd Rationale: As it became apparent that HTML5 was not going to include a @version attribute and be largely version-less, RDFa adopted the same approach. This has resulted in simpler implementations for RDFa. RDFa Core 1.1 now assumes that the data being parsed is the latest version of RDFa and does not switch between 1.0 and 1.1. That is, once RDFa 1.1 hits REC, all RDFa 1.0 documents will be parsed as 1.1 by default.
mass-move component to LC1