-
Notifications
You must be signed in to change notification settings - Fork 0
Added checks for rules about Requesting Agent. #13
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
Conversation
rocrate_validator/profiles/five-safes-crate/must/2_agent_entity.ttl
Outdated
Show resolved
Hide resolved
|
Will get to this Weds morning @EttoreM - apologies for the delay, it's the HDR Fed A roadmap Monday + Tues. |
alexhambley
left a comment
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.
Hi @EttoreM - sorry for the delay! I have made some comments in-line :)
rocrate_validator/profiles/five-safes-crate/must/2_requesting_agent.ttl
Outdated
Show resolved
Hide resolved
rocrate_validator/profiles/five-safes-crate/must/2_requesting_agent.ttl
Outdated
Show resolved
Hide resolved
rocrate_validator/profiles/five-safes-crate/must/2_requesting_agent.ttl
Outdated
Show resolved
Hide resolved
rocrate_validator/profiles/five-safes-crate/should/2_requesting_agent.ttl
Show resolved
Hide resolved
rocrate_validator/profiles/five-safes-crate/should/2_requesting_agent.ttl
Show resolved
Hide resolved
rocrate_validator/profiles/five-safes-crate/should/2_requesting_agent.ttl
Outdated
Show resolved
Hide resolved
rocrate_validator/profiles/five-safes-crate/should/2_requesting_agent.ttl
Show resolved
Hide resolved
…ck on @id being a permalink is now restricted to Organizations that are affiliations of agents.
…t (and possibly licence for RooDataEntity...???)
73a78a9 to
d4b9c90
Compare
|
I've rebased this branch from develop. I think I shouldn't have broken any of your code @EttoreM, but please could you check to make sure. I don't know why git has flagged the removal of |
|
@douglowe Alas those files are on develop: https://github.com/eScienceLab/rocrate-validator/tree/develop/rocrate_validator/profiles/five-safes-crate/must (as well as in #15 ) so you might have accidentally removed them when rebasing (this also looks to be why the tests are failing) |
|
yep. I've realised that, and have been checking to see if the tests are covered anywhere else. I think that, as this PR is for the requesting agent, I'll reverse out the removal of these two files. If they do duplicate requirements elsewhere we can tidy up the duplication later. |
|
I have addresses @elichad's comments and added python tests to this set of rules. I think it is ready for review. |
elichad
left a comment
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.
@EttoreM this looks good to me!
My only suggestion is that we use the term "contextual entity" in messages instead of "IRI", as that is the terminology that RO-Crate users are more familiar with.
Please hit the merge button when you're ready as I'm not sure if you want this or #27 to be merged first (don't know if it matters).
| sh:minCount 1 ; | ||
| sh:nodeKind sh:IRI ; | ||
| sh:severity sh:Violation ; | ||
| sh:message "CreateAction MUST have at least one schema:agent that is an IRI." ; |
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 could refer to this as a contextual entity to suit our audience better (though I appreciate this just replaces RDF jargon with RO-Crate jargon...)
| sh:message "CreateAction MUST have at least one schema:agent that is an IRI." ; | |
| sh:message "CreateAction MUST have at least one schema:agent that is a contextual entity." ; |
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.
Done
| sh:nodeKind sh:IRI ; | ||
| sh:class schema:Person ; | ||
| sh:severity sh:Violation ; | ||
| sh:message "Each CreateAction agent MUST be typed as schema:Person and be an IRI." ; |
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.
since the IRI/contextual entity part is covered above
| sh:message "Each CreateAction agent MUST be typed as schema:Person and be an IRI." ; | |
| sh:message "Each CreateAction agent MUST be typed as schema:Person." ; |
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.
Done
| sh:class schema:Organization ; | ||
| sh:nodeKind sh:IRI ; | ||
| sh:severity sh:Violation ; | ||
| sh:message "The affiliation of a CreateAction's agent MUST be a schema:Organization and be an IRI." ; |
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.
| sh:message "The affiliation of a CreateAction's agent MUST be a schema:Organization and be an IRI." ; | |
| sh:message "The affiliation of a CreateAction's agent MUST be a contextual entity with type schema:Organization." ; |
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.
Done
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.
(note for my own benefit as I think you're already aware of this)
GH interprets this as a renamed file ...rate/must/1_root_data_entity_metadata.ttl → ...safes-crate/should/2_requesting_agent.ttl
and this might therefore have conflicts with #27 which also updates the 1_root_data_entity_metadata.ttl file (but #27 also renames the file, so maybe it'll be fine!?).
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.
Yes, it should be fine.
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.
(another note for myself) this file is updated with a different filename in #27
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.
cross-referencing #27 (comment) which confirms that this is fine to remove
Rules implemented
|
Assumption
The checks have been devised under the following assumptions:
@type schema:Personthat are not agents of a CreateAction entity.schema:Personentities that are agents of CreateAction SHOULD have an affiliation (otherschema:Personentities are not checked for affiliation)@type schema:Organization(affiliations of other entities are not checked for@type).schema:Organizations that are not affiliations of any CreateAction's agent.