- From: Steve Harris <steve.harris@garlik.com>
- Date: Fri, 14 Oct 2011 11:49:39 +0100
- To: Jeremy Carroll <jeremy@topquadrant.com>
- Cc: public-rdf-wg@w3.org
+1 to Jeremy. - Steve On 2011-10-14, at 02:59, 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 > -- Steve Harris, CTO, Garlik Limited 1-3 Halford Road, Richmond, TW10 6AW, UK +44 20 8439 8203 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Friday, 14 October 2011 10:50:12 UTC