[Bug 9874] HTML+RDFa 1.1 in @version could be confusing

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9874

Manu Sporny <msporny@digitalbazaar.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Manu Sporny <msporny@digitalbazaar.com> 2010-12-04 19:02:23 UTC ---
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.

-- 
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 Saturday, 4 December 2010 19:02:25 UTC