[dxwg] Consider HTTP 300 as realization for list profiles / list tokens

azaroth42 has just created a new issue for https://github.com/w3c/dxwg:

== Consider HTTP 300 as realization for list profiles / list tokens ==

OPTIONS is not cacheable, and there isn't a profile parameter for the Link header construct ... so ... how about an HTTP 300 Multiple Choices response?

HTTP 300 says:

> For request methods other than HEAD, the server SHOULD generate a
> payload in the 300 response containing a list of representation
> metadata and URI reference(s) from which the user or user agent can
> choose the one most preferred.

This would allow the response to describe the URIs of the representations, and their metadata, thus including both profile URI and token, if any. The disadvantage is that it would be a custom response format, but one that is likely very obvious and could tie back to other DXWG deliverables.



Please view or discuss this issue at https://github.com/w3c/dxwg/issues/549 using your GitHub account

Received on Thursday, 8 November 2018 21:56:02 UTC