- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Sep 2019 02:15:33 +0000
- To: public-dxwg-wg@w3.org
@kcoyle and for all other readers: The "ability to negotiate the data profile via http" of internet resources is the core concern of Content Negotiation by Profile. The approach is "similar to the negotiation of data formats today" in that where a content request by format (Media Type) is implemented with the requester including the HTTP header `Accept` in an HTTP request, a request for content via its profile conformance is implemented with clients supplying an `Accept-Profile` header. The response will try to honour that and indicate any profiles the response's resource representation conform to with a `Content-Profile` header, just as an `Accept` header would receive a `Content-Type` response. This mechanism is detailed in the Content Negotiation by Profile [Editors Draft](https://w3c.github.io/dxwg/conneg-by-ap/) and the [Second Public Working Draft](https://www.w3.org/TR/2019/WD-dx-prof-conneg-20190430/) and is essentially unchanged between the two, although examples and other supporting information have been added. Note that the Content Negotiation by Profile documents also describe another approach to negotiate for resources by data profile other than via HTTP: via Query String Arguments. -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/265#issuecomment-529275394 using your GitHub account
Received on Monday, 9 September 2019 02:15:35 UTC