W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > January 2011

ISSUE-73 (RDFa Profile management): The RDFa WG needs to determine how each RDFa Profile document is managed [LC Comment - RDFa Core 1.1]

From: RDFa Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 06 Jan 2011 17:27:02 +0000
To: public-rdfa-wg@w3.org
Message-Id: <E1Patc6-0007e7-K6@barney.w3.org>

ISSUE-73 (RDFa Profile management): The RDFa WG needs to determine how each RDFa Profile document is managed [LC Comment - RDFa Core 1.1]

http://www.w3.org/2010/02/rdfa/track/issues/73

Raised by: Manu Sporny
On product: LC Comment - RDFa Core 1.1

Based on a discussion in the RDFa WG telecon today:

http://www.w3.org/2010/02/rdfa/meetings/2011-01-06#XHTML_Profile_document_changes__2f_management

The RDFa WG needs to determine how each RDFa Profile document is managed. One management proposal was provided by Toby:

http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Dec/0054.html

Another option is to create the XML+RDFa and XHTML+RDFa Profile documents and freeze them when the first specification that they're associated with goes to REC. Note the XHTML Profile document is associated with XHTML+RDFa 1.1 and HTML+RDFa - it would be frozen when XHTML+RDFa 1.1 goes to REC.

The RDFa WG should be careful to ensure that the management proposal doesn't block RDFa Core and XHTML+RDFa from going to REC.
Received on Thursday, 6 January 2011 17:27:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:08 GMT