Closes #10.
Depends on ResearchObject/ro-terms#21.
See also #60.
I've added the spec to the Provenance Run Crate profile only since we've always seen this as something a workflow manager would implement. The spec is not very strict, in particular:
There is no subset of common properties reserved by the profile itself. On one hand this gives implementers freedom to define the whole set of properties they support; on the other hand, it makes comparison across crates generated by different engines harder.
QUDT is given as an example vocabulary for unit codes, but its use is not made mandatory. Again, this leans towards freedom of implementation at the expense of simpler cross-engine comparisons.
We should decide what to do about the above points: are they OK as they are now, or do we want the stricter approach?
Closes #10. Depends on ResearchObject/ro-terms#21. See also #60.
I've added the spec to the Provenance Run Crate profile only since we've always seen this as something a workflow manager would implement. The spec is not very strict, in particular:
We should decide what to do about the above points: are they OK as they are now, or do we want the stricter approach?