- From: Holger Knublauch <holger@topquadrant.com>
- Date: Fri, 05 Jun 2015 10:37:30 +1000
- To: public-data-shapes-wg@w3.org
Arthur and I had this action, which somehow fell through the cracks although I had included my proposal below already into the draft: My proposal (not coordinated with Arthur yet) would be: 1) SHACL cannot consistently rely on any graph-level inferencing to be available for the given graphs (for various technical reasons). 2) SHACL should rely on engine-level inferencing that walks the rdfs:subClassOf triples where needed, e.g. by generating appropriate SPARQL queries: a) sh:valueType must also accept subclasses of the given class (e.g. via rdfs:subClassOf*) [1] b) sh:scopeClass also applies to subclasses (i.e. constraints defined for a superclass also apply to instances of the subclass) [2] 3) SPARQL queries can be annotated with sh:sparqlEntailment to assert the presence of a given SPARQL entailment regime [3] Given that my task here was just to write down a proposal, I consider the ACTION-26 done unless Arthur disagrees. Thanks, Holger [1] http://w3c.github.io/data-shapes/shacl/#sparql-AbstractValueTypePropertyConstraint [2] http://w3c.github.io/data-shapes/shacl/#operation-validateNode [3] http://w3c.github.io/data-shapes/shacl/#sparql-entailment On 5/21/2015 4:12, RDF Data Shapes Working Group Issue Tracker wrote: > shapes-ACTION-26: Draft a proposal for issue-1 (with holger) > > http://www.w3.org/2014/data-shapes/track/actions/26 > > Assigned to: Arthur Ryman > > > > > > > >
Received on Friday, 5 June 2015 00:39:38 UTC