Re: ACTION-118 Status of ISSUE-137


indeed, I do not think we have a problem with text/html. If this is what one gets, it is HTML+RDFa.

However... if the media type is application/xhtml+xml then... we do have an issue at the moment, and I believe that this is the problem of Alex.

What I (try to) do in my implementation, in those cases, is to see of a DTD is present in the file, and if it is one of the RDFa defined DTD-s. That, incidentally, also sets the RDFa version (1.0 and 1.1) but, more to the point for this case, whether it is to be processes along the lines of the XHTML1+RDFa host language or the HTML+RDFa (ie, XHTML5+RDFa). Because there are differences (which terms are interpreted, usage of time related attributes, etc), it is important to make that difference.

Ain't pretty, I know.


On Aug 16, 2012, at 15:27 , Shane McCarron wrote:

> 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 in section 12.1 of the HTML5 specification [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]
> [2]
> -- 
> Shane McCarron
> Managing Director, Applied Testing and Technology, Inc.
> +1 763 786 8160 x120

Ivan Herman, W3C Semantic Web Activity Lead
mobile: +31-641044153

Received on Thursday, 16 August 2012 14:09:54 UTC