Closed stain closed 1 year ago
Yeah, I think we can still indicate that inheritance in the Profile Crate for documentation, but that it should keep it explicit in conformsTo
in each conforming Crate - just like we have those lovely @type
arrays rather than some ontology with inferred subclasses. Will add that to the RO-Crate 1.2 page.
Following https://www.researchobject.org/ro-crate/1.2-DRAFT/profiles but with "conformsTo" applied to "./" as suggested in https://github.com/ResearchObject/ro-crate/issues/153#issuecomment-1240446098 rather than
conformsTo
Example for provenance crate.
Process Crate:
https://w3id.org/ro/wfrun/process/0.1
Workflow Crate:
https://w3id.org/ro/wfrun/process/0.1
https://w3id.org/ro/wfrun/workflow/0.1
https://w3id.org/workflowhub/workflow-ro-crate/1.0
Provenance Crate:
https://w3id.org/ro/wfrun/process/0.1
https://w3id.org/ro/wfrun/workflow/0.1
https://w3id.org/ro/wfrun/provenance/0.1
https://w3id.org/workflowhub/workflow-ro-crate/1.0
Notes:
conformsTo
always goes to a profile PID withmajor.minor
versionconformsTo
toro-crate-metadata.json
. To keep conformance with that one (before it can be updated to 1.2 once that is released) I have kept that in the examples here, but also added the Workflow RO-Crate PID to make it consistent with 1.2wfrun/process
andworkflowhub/workflow-ro-crate
aswfrun/workflow
adds a requirement for theCreateAction
to be connected to themainEntity
workflowwfrun/provenance
is again different fromwfrun/workflow
, e.g. it addsOrganizeAction
andControlAction