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

@azaroth42 related question. Should the `ETag` value change whenever 
`Content-Location` and/or the `id` change?

Currently, all the various representations of the container share the 
same `ETag` value even, though the contents vary widely based on the 
`Prefer` values.

The entity itself, of course, is unchanged, however, so should we add 
`Prefer` to the `Vary` list to make these distinct to caches?

That seems more accurate than having the `ETag` value change when the 
underlying entity has not.

Thoughts?

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

Received on Monday, 1 August 2016 23:25:39 UTC