- From: Ivan Herman <ivan@w3.org>
- Date: Fri, 31 May 2013 11:58:48 +0200
- To: Peter Occil <poccil14@gmail.com>
- CC: public-rdfa-wg@w3.org
- Message-ID: <51A87458.9070807@w3.org>
It was discussed yesterday on the call and this is certainly the general direction. Manu will check with the HTML5 experts on what happens in the DOM... Thanks Ivan Peter Occil wrote: > Your suggestion would be fine by me if it's accepted by the working group. > > --Peter > > -----Original Message----- From: Ivan Herman > Sent: Thursday, May 30, 2013 9:34 AM > To: Peter Occil > Cc: public-rdfa-wg@w3.org > Subject: Re: Language of a node and HTML+RDFa JavaScript implementations > > Peter, > > I *think* I understand the issue and, coincidentally, we will have a call in a > half an hour where this issue may be discussed. Again as an individual, I > believe that the only way we can handle that in RDFa is that the generated RDF > uses whatever the markup gives us (which indeed means that the current section > 3.3. may not be precise enough). Ie, to use the example below, in the case of > Document 4: > > <html><p>Document 4</p></html> > > the generated RDF literal will _not_ include a language tag. Actually, that > would be the case for > > <html><meta http-equiv="content-language" content="en"><p>Document>3</p></html> > > because RDFa tries to be language neutral. AFAIK, all current RDFa processors > work this way. > > I think the important point is that RDF makes a difference between plain > literals and literals with language tags. Ie, the generated RDF from RDFa has > the freedom to generate a plain literal if no language tag has been assigned. > > Thanks! > > Ivan > -- 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 Friday, 31 May 2013 09:59:16 UTC