v3 schema-revision: protocolExecution.schema.json

[lzehl]

The protocolExecution.schema.json will be used to provide information on the individually executed protocol. Note: should be implemented in folder "experiment".

According to the current documentation, this schema will have the following properties:

• @type [expects: constant ("https://openminds.ebrains.eu/core/protocolExecution"), count: 1]
• @id [expects: free text, count: 1]
• hasGenerated [expects: subjectState.schema.json | tissueSampleState.schema.json | fileBundle.schema.json | fileInstance.schema.json, count: 1 - N]
• hasUsed [expects: subjectState.schema.json | tissueSampleState.schema.json | fileBundle.schema.json | fileInstance.schema.json, count: 1 - N]
• protocol [expects: protocol.schema.json, count: 1]
• parameterSettings [expects: parameterSetting.schema.json, count: 0 - N]
• semanticallyAnchoredTo [expects: anatomicalEntity.schema.json (SANDS schema), count: 0 - N]

[lzehl]

Based on discussions for SANDS an additional property semanticallyAnchoredTo added to the protocolExecution.schema.json (see updated docu above).

This property has a dependency for the protocol.schema.json: if a value (anatomicalEntity) is given in this property the protocol linked to this protocolExecution has to have the technique "semantic anatomical anchoring" attached.

@olinux we can make this a documented rule for the curators if the dependency check would be too cumbersome.