- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Mar 2021 16:51:39 +0000
- To: public-dxwg-wg@w3.org
@aisaac said: > 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? You're right, @aisaac . The revision you refer to stems from discussion in https://github.com/w3c/dxwg/issues/1225 - in particular, https://github.com/w3c/dxwg/issues/1225#issuecomment-719374471 -, and I'm afraid I forgot about what discussed in this thread. > 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. (maybe @andrea-perego or @makxdekkers know?) Following the discussion in https://github.com/w3c/dxwg/issues/1225 , we have updated the draft by providing some guidelinles - see the last part of [ยง13.2.1 (Conformance to a standard)](https://w3c.github.io/dxwg/dcat/#quality-conformance-statement). But those guidelines are not discussing specifically whether you should point to the protocol or the query language specification. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1211#issuecomment-808368325 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 16:55:16 UTC