-
Notifications
You must be signed in to change notification settings - Fork 0
Small SHACL fixes; test RECOMMENDED checks on valid crates #58
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
base: develop
Are you sure you want to change the base?
Conversation
| sh:name "object" ; | ||
| sh:path schema:object ; | ||
| sh:minCount 1 ; | ||
| sh:hasValue ro-crate:RootDataEntity ; |
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.
This snuck through the tests as it only fails the valid crate at RECOMMENDED level - which we don't test for (same for the Validation Phase check below). It turns out to be hard to test - see crs4#135, I'm trying to put together another PR to get those tests in never mind, it's included here now
| # There SHOULD be a Sign-Off Phase | ||
| five-safes-crate:SignOffPhase | ||
| a sh:NodeShape ; | ||
| sh:targetNode <./> ; |
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.
This is just a style change really as in 5SROC the RDE should always be <./> - but the change makes it a bit more robust and aligned with the rest of our checks
| @pytest.mark.xfail( | ||
| reason=""" | ||
| Checks that ensure certain Five Safes actions are present currently fail for this crate, | ||
| as this crate represents an early stage of a process before those actions have happened. | ||
| """ | ||
| ) | ||
| def test_valid_five_safes_crate_request_recommended(): |
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.
we don't strictly need to include this test since it fails right now. But if/when we manage to implement dynamic enabling of phase-specific checks, this will eventually pass
objectpointing to the RDEdo_entity_testto accept arbitrary validation settings so the tests above can work (will also PR this upstream)