- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Nov 2018 23:06:37 +0000
- To: public-dxwg-wg@w3.org
Responses, 7 - 10: 7. Profile negotiation is on a per-resource basis with resource being an HTTP resource - a thing indicated by a URI. The Profile series of documents are on a not a whole-of-dataset basis, unlike DCAT. So, the question needs to be rephrased: *"is the ‘internet resource’ here the resource that conforms to the profile?"* and then the answer is yes. Negotiation by profile is, as per HTTP negotiation generally, about a single resource and forms of it that conform to the conneg dimension requested. So for the resource identified by `http://example.com/a/resource`, `Content Type` conneg may allow you to get it as an HTML doc (`Accept: text/html`) or other Media Types, conneg by profile will look like `Accept-Profile: http://example.com/profile/x` for /a/resource `dct:conformsTo` the profile `http://example.com/profile/x`, if the server supports it. -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/572#issuecomment-439222961 using your GitHub account
Received on Thursday, 15 November 2018 23:06:39 UTC