- From: Pat Hayes <phayes@ihmc.us>
- Date: Thu, 13 Oct 2011 22:04:59 -0500
- To: Jeremy Carroll <jeremy@topquadrant.com>
- Cc: public-rdf-wg@w3.org
Jeremy, does all this apply to every format for RDF? Pat On Oct 13, 2011, at 8:59 PM, Jeremy Carroll wrote: > On 10/13/2011 4:49 PM, Pat Hayes wrote: >> Factual data that is time-dependent but not given with time information is bad. > This is a non-issue. > > On the WEB it is not possible to publish any information without also giving some time-information. The HTTP headers have it. > > Essentially, we have two graphs of interest - the graph on the server, and the graph on the client. The graph on the client is a cached copy of the graph on the server, and the considerations of: > http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13 > apply > > > > (I do not know if any semantic web implementers have taken this point of view, but whether or not there is implementation experience, this seems to be to have been standardized long ago). > > A Graph that says that Alice is 29, when in fact she is 30, and the updated information is available from the Graph's document URL is a stale cached copy that should be discarded. If a particular implementation does not have the mechanisms to check the HTTP headers to work this out, then that implementation is faulty, and it needn't concern us in this WG, other than we might wish to write a test case. (And we might also wish to fix our code). > > 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 Friday, 14 October 2011 03:05:36 UTC