Suggested profile updates from validation development

[elichad]

While developing the validation profile for Five Safes Crate we have found some places where wording could be improved for clarity (and enforceability).

1. In Requesting Agent:

   The individual person who is requesting the run MUST be indicated as an agent from the CreateAction, which SHOULD have an affiliation to the organisation they are representing for access control purposes.

   add:

   • CreateAction agent MUST be a contextual entity
   • Person affiliation MUST be a contextual entity (if present)

2. In Referencing a workflow crate:

   Note: unlike in the Workflow Run profile, the programming language of the workflow and its other metadata are not expressed in this RO-Crate, but within the referenced Workflow RO-Crate. The programmingLanguage inside the Workflow RO-Crate SHOULD be either https://w3id.org/workflowhub/workflow-ro-crate#cwl or https://w3id.org/workflowhub/workflow-ro-crate#nextflow.

   add:

   • "... the programming language of the workflow and its other metadata SHOULD NOT be expressed in this RO-Crate..."
   • the entity representing the referenced crate MUST include conformsTo with the Workflow RO-Crate profile (stricter than base spec where this is optional)

3. In Responsible Project:

   The project MAY indicate the member organisations, in which case one of them SHOULD match the affiliation of the Requesting Agent with a memberOf to this project.

   add:

   • Project member MUST be a contextual entity
   • Project member MUST have type Organization or Person

More suggestions may be added as comments as we continue development.

[elichad]

4. update @context to use "https://w3id.org/ro/crate/1.2/context" (i.e. update references to 1.2-DRAFT)

[elichad]

https://trefx.uk/5s-crate/0.4/#publishing-phase

The mentions MUST be expanded to include all the AssessActions recorded by the TRE.

Interpreted this as (partly) "RDE mentions MUST include all AssessAction entities present in the crate." This isn't quite accurate but it's the most machine-actionable way to phrase this.