- From: Steve Chavez via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Feb 2020 20:40:30 +0000
- To: public-dxwg-wg@w3.org
steve-chavez has just created a new issue for https://github.com/w3c/dxwg: == Profile negotiaton: profile token in Accept-Profile header == In https://www.w3.org/TR/dx-prof-conneg/#profileid it's mentioned that: > A client requesting the representation of a resource conforming to a data profile MUST identify the resource by a Uniform Resource Identifier (URI) [RFC3986] and MUST identify the profile either by a URI or **a token**. There is an example in https://www.w3.org/TR/dx-prof-conneg/#getresourcebyprofile on how to make a request with a token profile in the UR(with the `_profile` query param): ```http GET http://example.com/path/to/resource/a?_profile=prof-01&_mediatype=text/turtle. ``` But there isn't an example with a profile token in an `Accept-Profile` header. Would a request like the following be valid for profile negotiation? ```http # A request for resource a according to Profile x is made GET /resource/a HTTP/1.1 Accept-Profile: x ``` (Granted that token mappings are provided as specified in https://www.w3.org/TR/dx-prof-conneg/#http-tokens) I'm trying to implement content negotiation by profile on [postgrest.org](http://postgrest.org/en/v6.0/). Would appreciate any clarification/guidance on this. Thank you. Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1219 using your GitHub account
Received on Thursday, 27 February 2020 20:40:31 UTC