Merged
Conversation
Author
|
I need to add to the endTime and startTime checks |
EttoreM
reviewed
Nov 29, 2025
douglowe
commented
Dec 1, 2025
Author
|
start and end date checks added. |
Merged
elichad
reviewed
Dec 4, 2025
alexhambley
requested changes
Dec 5, 2025
There was a problem hiding this comment.
I also wanted to add that for the "TRE policy should include an ID referencing the TRE policy document" rule, currently ID is not checked - we could add sh:nodeKind sh:IRI or some SPARQL as a blank node will pass I think
Obviously referencing the TRE policy document is a manual check, but we can specify at least an ID requirement?
EttoreM
approved these changes
Dec 8, 2025
elichad
reviewed
Dec 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rules Implemented (so far)
(*) Implicit in rule 2, so doesn't have a dedicated SHACL rule.
(**) I've only checked for a string here. Human-readable will depend on plugging in an AI / human
(***) This rule is implicitly included in rule 2, so it does not have a dedicated SHACL implementation.