ISSUE-71: SHACL Endpoint Protocol

Protocol

SHACL Endpoint Protocol

State:

CLOSED

Product:

SHACL Spec

Raised by:

Holger Knublauch

Opened on:

2015-06-19

Description:

I believe we should produce a network protocol similar to SPARQL endpoints, but for SHACL. The main operation in this protocol would be to send a SHACL graph (e.g. serialized in Turtle) to the server, possibly with instructions which resources to validate against which shapes. The result of this operation would be a list of constraint violations.

Another operation could be to determine the capabilities of the server, e.g. as an extension of http://www.w3.org/TR/sparql11-service-description/

The operation would do all the right things server side - create a temporary named graph for the shapes, install the required functions and templates from the shapes graph, and thus solve most of the limitations that a remote-control of SPARQL endpoints have. It will also be much faster - no SHACL engine is needed to trigger all the various SPARQL queries; it would just be a single transaction.

The only downside is that it will take a while before vendors implement this, but that's a bit like expecting running SPARQL queries when all you have are SPO queries.

Related Actions Items:

No related actions

Related emails:

1. RDF Data Shapes WG agenda for 8 September 2016 (from eric@w3.org on 2016-09-07)
2. Re: ISSUE-71 (from eric@w3.org on 2016-09-07)
3. Re: ISSUE-71 (from holger@topquadrant.com on 2016-09-07)
4. Re: ISSUE-71 (from kcoyle@kcoyle.net on 2016-09-06)
5. Re: ISSUE-71 (was: ISSUE-176: Rules will not modify the data graph) (from eric@w3.org on 2016-09-06)
6. ISSUE-71 (was: ISSUE-176: Rules will not modify the data graph) (from holger@topquadrant.com on 2016-09-06)
7. Re: ISSUE-176: Rules will not modify the data graph (from kcoyle@kcoyle.net on 2016-09-05)
8. Re: ISSUE-176: Rules will not modify the data graph (from holger@topquadrant.com on 2016-09-05)
9. Re: Please review the SHACL draft (was Re: Editing progress) (from holger@topquadrant.com on 2016-08-31)
10. Re: shapes-ISSUE-130 (rdf dataset assumption): SHACL should not assume that the data graph is in an RDF dataset [SHACL Spec] (from holger@topquadrant.com on 2016-03-24)
11. Re: SHACL: A language for multiple platforms (from johnson.tom@gmail.com on 2015-07-03)
12. SPARQL Endpoint support (from holger@topquadrant.com on 2015-07-03)
13. Re: shapes-ISSUE-71 (Protocol): SHACL Endpoint Protocol [SHACL Spec] (from arthur.ryman@gmail.com on 2015-06-24)
14. Re: SHACL: A language for multiple platforms (from holger@topquadrant.com on 2015-06-23)
15. Re: SHACL: A language for multiple platforms (from kontokostas@informatik.uni-leipzig.de on 2015-06-23)
16. Re: SHACL: A language for multiple platforms (from holger@topquadrant.com on 2015-06-20)
17. shapes-ISSUE-71 (Protocol): SHACL Endpoint Protocol [SHACL Spec] (from sysbot+tracker@w3.org on 2015-06-19)

Related notes:

Display change log