sparna-git / owl2shacl

OWL 2 SHACL conversion rule

owl2shacl

OWL 2 SHACL conversion rules, adapted from TopQuadrant's original post at https://www.topquadrant.com/from-owl-to-shacl-in-an-automated-way/

These rules can be used by SHACL Play at https://shacl-play.sparna.fr/play/convert to convert an OWL file to SHACL.

This comes in 3 flavors :

1. open flavor does not close the Shapes and does not verify the domain of properties
2. semi-closed flavor does verify the domains of the properties in the ontology, but does not close the shapes, leaving open the possibility to have properties of other ontologies in the data.
3. closed closes all shapes, so does not allow the use of properties outside of the ones declared in the ontology, and closing the shapes verifies that each property is asserted on a valid entity according to its domain declaration

owl2shacl's Issues

Provide licence

Please provide a licence for this code. e.g.

https://github.com/RDFLib/profilewiz/blob/master/LICENSE

Document different options

Can you please provide a short explanation of what each version (?) does.

Might be able to guess -open and -closed but -semi-closed will need some explanation.

Factor all rules common to the 3 variants

Ideally using an owl:imports.
This could make things a little more complicated for clients as the owl:imports will need to be resolved prior to rule execution

Unresolved prefixed name: owl2sh-open:getPropertyShape when using owl2sh-open.ttl

This happens because owl2sh-open defines a wrong prefix here https://github.com/sparna-git/owl2shacl/blob/main/owl2sh-open.ttl#L11-L15:

Solution:

replace line 14 with

sh:prefix "owl2sh-open" ;   

owlAllValuesFrom2shClassOrDatatype references non-existent SPARQLFunction

All 3 shapes graphs reference a sh:SPARQLFunction that doesnt exist (only in the original shapes graph )

1. https://github.com/sparna-git/owl2shacl/blob/main/owl2sh-closed.ttl#L841
2. https://github.com/sparna-git/owl2shacl/blob/main/owl2sh-open.ttl#L834
3. https://github.com/sparna-git/owl2shacl/blob/main/owl2sh-semi-closed.ttl#L836

as such, allValuesFrom restrictions aren't correctly transformed..

Solution:

Use the same approach as used for rdfsRange2shClassOrDatatype also for owlAllValuesFrom2shClassOrDatatype.

Provide conformance and testing details

Is there a test or comparison available to assess the conformance of the outputs with the SHACL specification itself and with a test model.