Structure SHACL-SHACL to match profiles

[bergos]

Some SHACL 1.2 features won't cause errors in a 1.0-compatible engine but may lead to different validation results. Since we previously considered defining a profile for SHACL 1.0, we could also think about structuring the SHACL-SHACL shapes to support multiple profiles.

I see two options:

• Using node expressions to disable certain shapes
• Organize shapes in multiple files with imports, where each profile extends the previous one

For example:

• core12 extends core10 by adding additional shapes
• sparql12 includes core12

See this PR where the discussion started.

[nicholascar]

Can the issue of how to formalise the profiling be left to the SHACL 1.2 Profiling deliverable please?

I have some private ideas about this but we should defer conversation until work on that deliverable is underway so that this work aligns with its recommendations.

[bergos]

Yes, as we need the profiles first, the work for this issue must happen in the SHACL 1.2 Profiling deliverable.

But since @ajnelson-nist is already working on the SHACL-SHACL, I thought it was worth mentioning this now as one could structure the basic shapes (without deactivated or imports) a bit differently with this in mind.

[VladimirAlexiev]

@nicholascar Can you please consider and add "to #216 ?

• The way I read "SHACL 1.2 Profiling" it is about using SHACL to create profiles
• Whereas my issue is about splitting of SHACL features into "own" profiles: to control complexity of implementation and execution. This work I think should come earlier

PS: I'm very glad that under #235, SPARQL was removed from Core.

[nicholascar]

Yes, I will add to #216.

I think we are de facto implementing profiles of SHACL with Core & SPARQL etc., so perhaps we just need to formalize these profiles and their feature lists a bit.

[ajnelson-nist]

This Issue appears to be in progress, with the resolution of shacl-resources PR 1.

@nicholascar , were you envisioning the file in this repository, /shacl12-vocabularies/shacl-shacl.ttl, start being split to match the form of the stubs over in shacl-resources? Further, split in this repository, or would shacl-shacl.ttl be moved over to shsh12-core.ttl in the shacl-resources repository?