[data-shapes] should owl:import be enacted for the Data Graph? (#241)

VladimirAlexiev has just created a new issue for https://github.com/w3c/data-shapes:

== should owl:import be enacted for the Data Graph? ==
`owl:import` is enacted in the Shapes Graph, which is a major modularity mechanism:
https://w3c.github.io/data-shapes/shacl/#shapes-graph
> SHACL processors SHOULD extend the originally provided shapes graph by transitively following and importing all referenced shapes graphs through the owl:imports predicate.

However, https://w3c.github.io/data-shapes/shacl/#data-graph is silent on what happens with `owl:import` in the Data Graph.
Why would anyone use `owl:import` in a data graph? At least 2 reasons:
- If the data is SHACL. 
SHACL is treated as data in the SHACL-SHACL validation process.
The ITB validator does that (https://github.com/ISAITB/shacl-validator/issues/15).
- If the data is ontologies. 
The section clearly says: "The data graph is expected to include all the ontology axioms related to the data".
https://github.com/w3c/data-shapes/issues/185 is related

I suggest to add this to https://w3c.github.io/data-shapes/shacl/#data-graph:
> `owl:import` in the data graph is not enacted, to avoid uncontrolled increase of validation work.
If you want to validate several related ontologies, pass all of them to the SHACL processor (together or one by one), do not rely on `owl:import` links.

Such decision/clarification is important for https://github.com/w3c/data-shapes/issues/214

Please view or discuss this issue at https://github.com/w3c/data-shapes/issues/241 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 13 February 2025 09:17:59 UTC