- From: Brian Suda <brian.suda@gmail.com>
- Date: Thu, 5 Oct 2006 12:52:03 +0000
- To: public-grddl-wg <public-grddl-wg@w3.org>
I'm not sure if this an issue that needs to be addressed, or if this is just part of the architecture of the web, but what about content negotiation based on language preferences? If I de-reference a site, for example apache.org, that serves-up a different version of the HTML based on the language settings sent in the HTTP request, 'es' in this example, I will get back the Spanish version of the index (index.html.es) page. Now if I view source I can see all the data written in Spanish. If I run the transformation locally I would get back RDF with Spanish values. What happens when I use another application that is GRDDL aware on a remote machine, for example one running a SPARQL query and pull in apache.org as one of the FROM values. The SPAQRL app is GRDDL aware so it converts the HTML to RDF, but in this case it would NOT be sending the same HTTP headers as your local application did, and the SPARQL service would probably get back RDF with English values. So the same URI when converted to RDF generates two files with different values. Is this an issue, or is this just par for course? -brian -- brian suda http://suda.co.uk
Received on Thursday, 5 October 2006 12:52:13 UTC