- From: David Wood <david@3roundstones.com>
- Date: Tue, 3 Jan 2012 14:30:04 -0500
- To: Pat Hayes <phayes@ihmc.us>
- Cc: Jeremy Carroll <jeremy@topquadrant.com>, public-rdf-wg@w3.org
Hi Pat, On Dec 19, 2011, at 22:58, Pat Hayes wrote: > Sorry. I know it is *possible*. I wondered if anyone seriously contemplated an actual case where this might happen, other than to prove an academic point. Put another way, are there any 'natural' examples of something that people might reasonably do where this would happen. Yes, Callimachus does this. Requesting the same URL with different ACCEPT headers gives you either a human- or machine-readable representation. In Callimachus' case, one could *almost* parse the same RDF from the RDFa buried in an HTML representation, but they are different since the RDFa is intended to form a SPARQL query and not the query's results. I think this is similar to Dan's answer. Regards, Dave > > Pat > > On Dec 19, 2011, at 7:46 PM, Jeremy Carroll wrote: > >> On 12/19/2011 4:46 PM, Pat Hayes wrote: >>> On Dec 19, 2011, at 4:32 PM, Richard Cyganiak wrote: >>> >>>> >>>> I don't think so. log:semantics depends on retrieval of a representation, and the result of that action may be different for different clients with different configuration, different network location, or different access credentials. >>>> >>>> Content negotiation by language is a nice example where the same client in the same network location and same access credentials would receive different representations, and hence different log:semantics, based on user configuration. >>> ? IS it obvious that it would be different? The object of log:semantics is the RDF graph that the retrieved representation parses into, not the representation itself. Are there cases where content negotiation would give a different RDF graph from the same resource? (Genuine question, not rhetoric.) >>> >>> >> >> Yes. >> >> e.g. put a foo.rdf and a foo.ttl in a directory on an appropriately configured apache web server >> ensure the two files contain non-isomorphic graphs, one in RDF/XML and one in Turtle >> >> retrieve using two different user agents (browser etc) one configured to prefer RDF/XML the other to prefer Turtle >> >> >> Jeremy >> >> >> > > ------------------------------------------------------------ > IHMC (850)434 8903 or (650)494 3973 > 40 South Alcaniz St. (850)202 4416 office > Pensacola (850)202 4440 fax > FL 32502 (850)291 0667 mobile > phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes > > > > > >
Received on Tuesday, 3 January 2012 19:30:36 UTC