- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Mar 2021 10:30:41 +0000
- To: public-dxwg-wg@w3.org
@rob-metalinkage maybe this could be a different github issue? I was much involved in the creation of the issue, and I can't make the link. There is probably one, but it's unclear and it seems it hints to a more general (or specific?) issue whether to pointing to time-stamped standards or more abstract ones. The original issue was one of pointing either to the standard or to the document expressing it. In fact now I may extend myself, but because it's our issue with @nfreire maybe I can do it ;-) My question is about protocol vs query standard, for an access service. The URI that we agreed here for a SPARQL endpoint (and was in the DCAT spec) was that of the query language (`http://www.w3.org/TR/sparql11-query/`). I've just seen that a recent change in the spec uses the URI for the SPARQL protocol instead (`https://www.w3.org/TR/sparql11-protocol/`): `https://github.com/w3c/dxwg/pull/1310/files` Does this represent a change of approach, or some recommendation that should be followed, on what is expected wrt `dct:conformsTo` for data services? As a side question, I'm wondering whether there is anything here that the DCAT spec editors should be pushed to more specific DCAT-related guidelines such as the DCAT-AP ones. -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1211#issuecomment-808104787 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 March 2021 10:35:23 UTC