Re: [web-annotation] MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE

This is (essentially) the difference between Strong and Weak ETags:  
https://en.wikipedia.org/wiki/HTTP_ETag#Strong_and_weak_validation

LDP simply requires ETags and doesn't make any statement about strong 
vs weak.  My preference is for weak, as changing the ETag for every 
different representation makes it useless.  The _resource_ hasn't 
changed, even if a different _representation_ of the resource has been
 requested.  The Content-Location header should be sufficient for 
caching (but would love to hear practical experience of that), though 
it would be good to put Prefer into Vary.

And the same applies to both container/collection and annotation 
representations.

-- 
GitHub Notification of comment by azaroth42
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/327#issuecomment-236742341
 using your GitHub account

Received on Monday, 1 August 2016 23:37:46 UTC