- From: Arnaud Le Hors <lehors@us.ibm.com>
- Date: Fri, 29 May 2015 06:41:14 -0700
- To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
- Cc: public-data-shapes-wg@w3.org
Received on Friday, 29 May 2015 13:41:48 UTC
"Peter F. Patel-Schneider" <pfpschneider@gmail.com> wrote on 05/29/2015 05:15:37 AM: > ... > There will be SPARQL-based implementations of SHACL, and these > implementations will include the ability to use the raw SPARQL construct of > SHACL. If other implementations of SHACL do not implement this part of > SHACL, then all that that means is that these implementations cannot avail > themselves of this useful feature. Users can always switch to an > implementation that does support this part of SHACL, and thus "SPARQL is > always a fallback" for them. > Except that not all users will be able to switch to such an implementation. I believe you have in mind the common but use case where a generic/vanilla rdf datastore is used. In other cases such as those I know of where RDF is used as a thin layer on top of legacy software SPARQL support isn't an option and switching implementation isn't either. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Software Group
Received on Friday, 29 May 2015 13:41:48 UTC