Link: http://trac.tools.ietf.org/wg/httpbis/trac/ticket/69
Origin: http://www.w3.org/mid/4697DC4A.3090602@gmx.de
Component: non-specific
The spec uses the term "requested variant" in several places (10.2.2 201 Created, 10.2.5 204 No Content, 14.19 ETag, 14.25 If-Modified-Since, 14.28 If-Unmodified-Since). It's quite clear what it means in the context of HEAD/GET, somewhat clear for PUT, but not clear at all for other methods.
We really need to clarify this, potentially choosing a different term.
From http://www.w3.org/mid/F2154EEA-1B28-4C8F-BB64-D3AD29D0F9F9@gbiv.com
variant The ultimate target resource of a request after indirections caused by content negotiation (varying by request fields) and method association (e.g., PROPFIND) have been taken into account. Some variant resources may also be identified directly by their own URI, which may be indicated by a Content-Location in the response.
Dependency on #109.
Part of resolving this ticket will involve removing the "requested variant" phrase from parts of the spec where its use isn't required, as part of other rewrites.