-
Notifications
You must be signed in to change notification settings - Fork 2
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
1 no link to concept scheme #2
Conversation
I just came across this SHACL Test Suite report: https://w3c.github.io/data-shapes/data-shapes-test-suite/ If we would like to dig deeper into testing this shape, this might be an interesting option. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't tests/valid/ConceptShape.ttl and tests/valid/OrphanConcepts.ttl identical? I don't see why we need both.
They are indeed identical. My idea (that I apparently did not write down) was that maybe a test file is added per shape to test that shape. So |
It would probably reduce possible misunderstanding when the "Error" notes in by the test.sh script would include the filename where the error occured insteadof just "Error: This should be invalid, but is valid" referring to the previous line. (I at least was unsure to what this refers in the first try.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally, this looks fine. You may think about adressing my last comment but it is not necessary. I will have to understand this whole better in the future by taking a more thorough look at it.
That's a good point. I added the filename to the error message. |
I removed the shape in question and also added basic test functionality for the shape.
See https://github.com/skohub-io/shapes/tree/1-no-link-to-concept-scheme#tests for my idea of testing the shape.