RE: caching HTTP 303 responses

Hello Jacek,

> -----Original Message-----
> From: Jacek Kopecky [mailto:jacek.kopecky@deri.org] 
> Sent: 12 July 2007 12:14
> To: Williams, Stuart (HP Labs, Bristol)
> Cc: Jeremy Carroll; Giovanni Tummarello; semantic-web@w3.org
> Subject: RE: caching HTTP 303 responses
> 
> Stuart, 
> 
> I was thinking along the same lines, but decided to use the 
> caching terminology instead because it's hard to define when 
> an agent knows
> *enough* about something.
> 
> For instance the DC case - they have different URIs, and 
> initially the agent doesn't know anything about them. It 
> dereferences dc:description, let's say, and finds some 
> information about that and other DC properties. It can 
> probably assume now that it need never again (for small 
> values of never) dereference that. But when it encounters 
> dc:title, how can the client know that the stuff it got from 
> the dc:description redirect is all the pertinent information 
> that it can get from dc:title, which it doesn't yet know to 
> redirect anywhere?

Well... does it know *enough* about dc:title not to have to ask the
question? In an open-world semantic web, finding *all* of anything is
presumably hard - and determining pertainancy. Maybe, one should take
the view that if your going to say something about something you should
say all that you consider pertainent about that thing in the one breath.

FWIW, I sympathise and not being able to use a local cache to avoid the
round trip it's hard. I think that you can certainly avoid the round
trip wrt to repeated reference to the *same* thing.

> Best regards,
> Jacek

Stuart
--

Received on Thursday, 12 July 2007 11:26:19 UTC