Re: resolving ISSUE-47: Can SPARQL-based constraints access the shape graph, and how?

Hash: SHA256

I don't think that having a flag indicating that access to the shape graph
is required throughout validation is going to be helpful.  SHACL shape
graphs with this flag on would be unusable in certain situations, which
would fragment the language and also make reuse of libraries of SHACL shapes
more difficult.

If access to the shape graph throughout validation was the only way to get a
reasonable SHACL specification and implementation, then I would have no
problem with requiring it, but access to the shape graph throughout
validation is not so required.


On 06/11/2015 06:37 AM, Dimitris Kontokostas wrote:
> There was a lot of discussion on the related closed issue and I don't
> think that the new formulation changes the core of the question. So I
> would still say access to access between the constraints and the data 
> graph should not be required. If for some people this is helpful we could
> define a "flag" in the SPARQL-based constraints / templates that they
> need access to the constraints graph and we can define ways access can be
> achieved. In cases where access is not supported by a validation setup
> the engine would raise an error.
> Best, Dimitris
> On Wed, Jun 10, 2015 at 11:24 PM, Peter F. Patel-Schneider 
> < <>> wrote:
> ISSUE-47: Can SPARQL-based constraints access the shape graph, and how?
> is still open, but in many place 
> depends on being able to access the shapes graph during constraint
> validation.
> I think that this issue needs attention soon, as the resultant changes
> may be quite extensive.
> peter
> -- Dimitris Kontokostas Department of Computer Science, University of
> Leipzig & DBpedia Association Projects:,
> http://, 
> Homepage: Research Group:
Version: GnuPG v2


Received on Thursday, 11 June 2015 16:14:00 UTC