-
Notifications
You must be signed in to change notification settings - Fork 24
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal to use IRI nodes for properties in SHACL shapes instead of blank nodes #48
Comments
Thank you for the suggestion. Proposal to discuss this in the next major release cycle. |
Proposed resolution: Replace properties restriction written as blank nodes with IRI. |
resolution: will be for the future to see what is the best organisation of the SHACL file. To be considered in the chosen approach is the creation of local variants reusing part of the SHACL templates. Currently reuse at the level of class is possible. And the usage of controlled vocabularies is in a separated file. |
I created a pull request which does the requested change for the |
An additional wish we have would be to split the shapes further into atomar tests, so
becomes:
This would allow us to give more specific error messages an reuse the shapes even moren. |
Add a reference to a complete list of generated shacl rules: https://semiceu.github.io/uri.semic.eu-generated/DCAT-AP/releases/3.0.0/#validation-of-dcat-ap. |
With the purpose to reuse the SHACL shapes, it would nice the properties restrictions are written as IRI instead of blank nodes, so then reusers might disable certain shapes in case they don't fit in their application profile.
E.g.
dcat:Distribution
rdf:type sh:NodeShape ;
sh:property dcat:accessURLShape ;
dcat:accessURLShape
rdf:type sh:PropertyShape ;
sh:path dcat:accessURL ;
sh:class rdfs:Resource ;
sh:minCount 1 ;
sh:severity sh:Violation .
such shape requires that the access url should be explicitly indicated a rdfs:Resource whereas most of the time just a URL would be enough.
Using it as IRI could deactivate the shape for their need:
dcat:accessURLShape
sh:deactivated true .
The text was updated successfully, but these errors were encountered: