W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > March 2015

Re: Looking at the current proposals for SHACL

From: Holger Knublauch <holger@topquadrant.com>
Date: Fri, 20 Mar 2015 10:16:34 +1000
Message-ID: <550B66E2.4020709@topquadrant.com>
To: public-data-shapes-wg@w3.org
On 3/20/2015 10:03, Peter F. Patel-Schneider wrote:
> 3/ http://w3c.github.io/data-shapes/shacl/
>
> This document contains a formal specification of SHACL based on SPARQL with
> extra functionality.
>
> Significant Features:
> - - It provides a formal specification for SHACL in terms of an extended
>    version of SPARQL.

Hi Peter, this topic (the presence of the sh:hasShape function as a 
SPARQL extension) seems to have become one of your favorite recurring 
points. Yet I have stated multiple times, and will state it again here, 
that this is just one implementation option among others, and that no 
"extension" to SPARQL is needed. The Spec makes this clear at

http://w3c.github.io/data-shapes/shacl/#sparql-AbstractValueShapePropertyConstraint

I would appreciate if you stop using this tiny detail to make our two 
proposals appear more different than they really are.

Thanks
Holger

> - - It presents a full SHACL (modulo some of the non-validation portions).
> - - Its version of SHACL has all the expressive power of SPARQL.
> - - Its version of SHACL permits global constraints and recursive shapes but
>    not closed shapes.
> - - It provides a macro-expansion language.
> - - It provides violation reporting.
> - - The specification of recursive shapes appears to be ill-founded.
> - - It does not define a core, but the high-level constructs can act as such.
> - - The core does not need to be implemented using a SPARQL engine.
> - - It defines several methods for controlling evaluation of shapes.
> - - It defines a limited API.
>
> 4/ https://www.w3.org/2014/data-shapes/wiki/Shacl-sparql
>
> This document contains a formal specification of SHACL directly based on
> SPARQL.
>
> Significant Features:
> - - It provides a formal specification for SHACL in terms of SPARQL.
> - - It presents a full SHACL (modulo some of the minor features and some of
>    the non-validation portions).
> - - Its version of SHACL has all the expressive power of SPARQL.
> - - Its version of SHACL permits global constraints but not recursive shapes
>    or closed shapes.
> - - It provides violation reporting.
> - - It does not define a core, but the high-level constructs can act as such.
> - - The core does not need to be implemented using a SPARQL engine.
> - - It defines several methods for controlling evaluation of shapes.
> - - It defines a flexible API.
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJVC2PAAAoJECjN6+QThfjzeEMIAMfI18HI7JP6vh7GF5gXD1z9
> tq7hRe7GiCpslvxYcKdA8PNkyjOerY+xMMSrUjiMU+zUkqQR36VBJkFfwDLhyBpN
> 7gAHL8fB0HGfcxeBAlHddhKXs07YiRnhKuG4/7p01vMMmY9SEMFJjFogf2BgplDF
> RZ2ZZfMmQDk4/V9Jhy7dhNkQWd/NDTWhRquZgbSIZTXV0TWX7IIYnZ2Jiyz6rtSh
> us6xGK5psFxeWDCkzSVSfM7eGp57I/kGAUWpIpWR8ZiL8zqWr8A3L4M5RRLTukwb
> IIzMK4oFBHau4luXfHu5mJwVsF/fDENXnPTHeQYXJqQJOjqVUVtCNSUBmImKuCg=
> =kUVd
> -----END PGP SIGNATURE-----
>
Received on Friday, 20 March 2015 00:17:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:18 UTC