I checked the profile crates with rocrate-validator and found the following issue (there are others but this is the only one I don't know how to resolve/explain away):
[profile: RO-Crate Metadata Specification 1.1]
[ ro-crate-1.1_14 ]: Data Entity: REQUIRED properties
A DataEntity MUST be linked, either directly or inderectly, from the Root Data Entity
Failed checks
[ ro-crate-1.1_14.1 ] Data Entity MUST be directly referenced:
Check if the Data Entity is linked, either directly of inderectly, to the Root Data Entity using the hasPart
(as defined in schema.org) property"
Detected issues
- [Violation on <https://w3id.org/ro/doi/10.5281/zenodo.10368989>]: Less than 1 values on
<https://w3id.org/ro/doi/10.5281/zenodo.10368989>->[ sh:inversePath <http://schema.org/hasPart> ]
I checked the profile crates with rocrate-validator and found the following issue (there are others but this is the only one I don't know how to resolve/explain away):
https://w3id.org/ro/doi/10.5281/zenodo.10368989 is an RO-Crate with data for the WRROC paper, so it includes older versions of all three profiles plus a mapping. It's currently connected to the root data entities via other relationships:
Should https://w3id.org/ro/doi/10.5281/zenodo.10368989 also be included in
hasPartfor each of them? It's a bit circular.