-
Notifications
You must be signed in to change notification settings - Fork 7
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
German addition dcat-ap-spec-german-additions.ttl is does not comply to SHACL #19
Comments
I tracked part of the problem down. With some help of the pySHACL community. RDFLib/pySHACL#168 (comment)
Problem is the node shape
According to W3C https://www.w3.org/TR/shacl/#NodeConstraintComponent
SHACL instances of sh:NodeShape cannot have a value for the property sh:path. So Cheers |
@init-dcat-ap-de |
I pushed updates to improve the conformity. Unfortunately I couldn't find a solution for the |
Any news on the original problem of this issue? |
Should be fixed. |
Then I advice to open a new issue for the "OR problem". When you then there elaborate a bit on the OR problem I am probably able to support you. |
Dear Govdata!
At first a lots of thanks to GovData and ]init[ to provide us with a set of SHACL rules to make DCAT-things better.
We in BBG are currently including these SHACLE rules to come up with a replacement for our homebrew DCAT validator.
Our OpenData Portal the "Datenadler" utilizes Python. Python is quite common in OpenData since CKAN is also Python based.
There is just one SHACL Library in Python: pySHACL, which all the CKAN people may be using if CKAN will utilize SHACL.
Our code supplied with (All files from this GH repository):
validates our DCAT data quite well. The validation points out violations and such in the given DCAT-RDF data. Normal behavior.
But when we include additionally the german shape files dcat-ap-spec-german-additions.ttl and dcat-ap-spec-german-messages.ttl then pySHACL informs us with an exception:
"Shacl File does not validate against the Shacl Shapes Shacl file" with a stacktrace a kilometer long.
This exception arouses since pySHACL checks the SHACL shapes before using them.
In this it was not clear for me where the cause of the problem is:
Having filed already one bugreport to pySHACLE today the first blame was to PySHACL.
But at the end of the day I was not wiser. Desperately I just put the shape files into the European shape validator:
https://www.itb.ec.europa.eu/shacl/shacl/upload
and it produces a comparable number and detail problems with the shape files as pySHACL delivers.
The message file is OK, but dcat-ap-spec-german-additions.ttl produces 21 errors.
Now I think that the German shapes are not in shape.
The only code that I have found concerning DCAT and SHACL is JAVA based.
@]init[ You are using JAVA, I bet? Have you ever tried an other programming language with your shapes? I can try and and run the shapes on our RDF4J DB to get more platforms into play.
Let us work together to supply the BRD with a SHACL validation anyone can use.
Cheers Volker
The text was updated successfully, but these errors were encountered: