ro-crate
ro-crate copied to clipboard
ResearchObject
Align with CodeMeta
We should have a CodeMeta dual Resarch Object example, specially as CodeMeta is now being picked up by GitHub, Zenodo, etc and it heavily uses http://schema.org/
It might be that the Workflow example can be adapted for that as arguably a workflow is also software.
Q: Should codemeta.json file be a valid manifest.jsonld alternative by adding some extra RO terms, or would both manifests live side by side? (generating one from another)
codemeta is more oriented towards software. If a workflow has different steps, shouldn't there be a codemeta.json per step? Or do you think the whole RO should have a codemeta? What if the RO does not have software?
Exactly, so I think the codemeta files would better be linked up by annotations and conformsTo. They might be external.
However a workflow-RO could very much be seen as software, and so a codemeta.json for the workflow could very well be in scope for licensing, runtime requirements etc.