OWL Property Restrictions vs. SHACL

Question

Given a choice between OWL Property Restrictions and SHACL, is there any reason to choose the OWL approach any more?

Particularly with respect to cardinality constraints

Answer 1

In my experience OWL reasoning is very rarely used, and the complex OWL constructs (including Restriction and unionOf) are not very useful.

Even rdfs:domain/range cause reuse problems because they are monomorphic: use them with several values, and you're calling for trouble.

So we at Ontotext have been using lately example-based models, non-committal schema:domain/rangeIncludes, and shapes to express how classes and props are used together.