This means conformsTo on the ro-crate-metadata.json is only for RO-Crate spec itself (considering it from a JSON/JSON-LD perspective) while profiles about the content/shapes of a class of crates are appliec using conformsTo on the root dataset (./)
This also makes it easier to link to other RO-Crates as a Dataset and saying they follow a particular profile -- however you would also need to add a subjectOf to link to their ro-crate-metadata.json in order to indicate it is an RO-Crate - so still not ideal.
To indicate RO-Crate following a particular profile, then move so "conformsTo" applied to "./" as suggested in https://github.com/ResearchObject/ro-crate/issues/153#issuecomment-1240446098 (and agreed in calls 2022-09-08 and 2022-01-27) rather than on
ro-crate-metadata.json
entity.This means
conformsTo
on thero-crate-metadata.json
is only for RO-Crate spec itself (considering it from a JSON/JSON-LD perspective) while profiles about the content/shapes of a class of crates are appliec usingconformsTo
on the root dataset (./
)This also makes it easier to link to other RO-Crates as a
Dataset
and saying they follow a particular profile -- however you would also need to add asubjectOf
to link to theirro-crate-metadata.json
in order to indicate it is an RO-Crate - so still not ideal.(also there is still no way to indicate RO-Crate-ness on a nested
Dataset
which has adistribution
to a Zip/tarDataDownload
according to https://www.researchobject.org/ro-crate/1.1/data-entities.html#directories-on-the-web-dataset-distributions.)See also ResearchObject/workflow-run-crate#40 which applies this on the Workflow Run Crate profiles.
This fixes #126