Add new option for passing in an ontology specification document about pyshacl HOT 5 CLOSED

Are you interested in just RDFS entailment so the non-RDFS statements in the extra ontology document are ignored, or would you also want entailment from some OWL 2 profile? Maybe run the data file through some external tool(s) that provide these (like cwm or pychinko, or maybe something you can feed in SPIN rules)?

from pyshacl.

pySHACL can already do OWL-RL entailment, RDFS entailment, Both, or None.
I am interested in the use case where there is an external ontology document that uses (a combination of) OWL2 and RDFS to describe a data model, and where a data file given to pySHACL contains snippets which are instances of that data model and rely on those OWL/RDFS axioms in order to be fully described, but the data file itself does not contain the necessary axioms for the pySHACL pre-validation inferencer to correctly build out the graph.

from pyshacl.

Agree this would be great to have as it would basically unify SHACL and custom ontology validation, given that pySHACL already does OWL-RL-level graph expansion as Ashley mentioned above.

Have to be a bit careful you don't implement a recursive loading mechanism where user wants to add in Ontology X that import Y which imports Z etc. so you might have to either provide import options or limit to just import that ontology only.

from pyshacl.

@nicholascar
Absolutely, it will be limited to just one external ontology document, and it will explicitly not follow imports declared in that file.

from pyshacl.

This feature is implemented in da55eab
and released as part of pySHACL v0.9.9

from pyshacl.