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

The ETag header requirement (as opposed to SHOULD) comes from LDP, 
e.g. 4.2.1.3 (https://www.w3.org/TR/ldp/#ldpr-resource or thereabouts)

Making If-Match a MUST would be a burden for very high traffic and low
 fidelity systems. It's only significantly useful when multiple users 
have write access to the same resource ... which doesn't seem like a 
primary use case for Annotations.

I appreciate the desire to be consistent (symmetry is beauty, after 
all) ... but I think the uses for ETag are greater than the uses of 
If-Match (e.g. cache control), so it's already in favor of ETag being 
more useful than If-Match.

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

Received on Wednesday, 13 July 2016 16:07:34 UTC