SHACL: Do not prohibit inverse reasoning

[VladimirAlexiev]

It was decided that Inverse reasoning should not be mandatory, but is desirable for querying.

There were plans to write SHACL shapes to check that cims:AssociationUsed "No" triples are not included.
If shapes that prohibit inverse triples are added,
they will raise a number of errors on repositories that do in fact provide inverse reasoning.
This problem may be overcome by validating only named graphs with explicit instance data
(eg in GraphDB all inferred triples are in the onto:implicit graph).
But it may complicate validation scenarios.