- From: Ivan Herman <ivan@w3.org>
- Date: Sun, 26 May 2013 10:39:17 +0200
- To: Peter Occil <poccil14@gmail.com>
- CC: public-rdfa-wg@w3.org
- Message-ID: <51A1CA35.8050901@w3.org>
Dear Peter, (to avoid misunderstanding, commenting here as a technical person, not as an official W3C staff member!) First of all, thanks for the comment. I must admit I do not remember this issue coming up before. However... I believe that the fundamental approach to RDFa has always been that, conceptually, RDFa data extraction operates on the DOM tree, ie, whatever the DOM is supposed to give us. I have not checked the specs yet but I believe the specs that we refer to, and therefore RDFa itself, is in the clear in this sense... Thanks Ivan Peter Occil wrote: > Section 3.3 of HTML+RDFa says: > RDFa processors MUST use the mechanism described in The lang and xml:lang > attributes section of the [HTML5] specification to determine the > language of a node. > But a node's language depends not only on the lang and xml:lang attributes, > but also on the HTTP Content-Language header. > This may be problematic for JavaScript browser implementations since > there is no current > way to get the Content-Language header of a DOM Document object. That > means those > implementations will not be fully conforming, unless the rule is changed > so as to rely > on only the lang and xml:lang attributes, or a new DOM attribute is > added that retrieves > the Content-Language header, or in some other way. > Moreover, I don't believe this requirement is fully reflected in the current > test suite, I'm not sure. > --Peter -- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 http://www.ivan-herman.net/foaf#me
Received on Sunday, 26 May 2013 08:39:47 UTC