- From: Shane McCarron <shane@aptest.com>
- Date: Thu, 16 Aug 2012 08:27:50 -0500
- To: W3C RDFWA WG <public-rdfa-wg@w3.org>
- Message-ID: <502CF556.2030304@aptest.com>
I did a quick review. We resolved at the meeting on 10 May [1] that we should include non-normative text that says what should be done into the HTML5+RDFa spec. However, the spec already says in section 2.1 "Non-XML mode HTML+RDFa 1.1 documents/should/be labeled with the Internet Media Type|text/html|as defined insection 12.1 <http://www.w3.org/TR/html5/iana.html#text-html>of the HTML5 specification [HTML5 <http://dev.w3.org/html5/rdfa/#bib-HTML5>]." - this is normative. We also already include text in section 3.1 that says what to do in the presence of @version: "The|version|attribute is not supported in HTML5 and is non-conforming. However, if an HTML+RDFa document contains the|version|attribute on the|html|element, a conforming RDFa Processor must examine the value of this attribute. If the value matches that of a defined version of RDFa, then the processing rules for that version must be used. If the value does not match a defined version, or there is no|version|attribute, then the processing rules for the most recent version of RDFa 1.1 must be used." A note in section 2.1 would be non-normative, and could serve to clarify: Note: Some processors may not be able to detect the media type of the document being processed because of system limitations. In these cases the default processing rules in [RDFA-CORE] [2] section 4.1 - RDFa Processor Conformance - take precedence. Or something like that. [1] http://www.w3.org/2010/02/rdfa/meetings/2012-05-10 [2] http://www.w3.org/TR/rdfa-syntax/#conformance -- Shane McCarron Managing Director, Applied Testing and Technology, Inc. +1 763 786 8160 x120
Received on Thursday, 16 August 2012 13:28:32 UTC