You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an EOSC user I am encouraged by funders to use DCAT-AP 3.0 for publishing datasets. I want to convert the RO-Crate metadata for a published crate to a DCAT description.
A RO-Crate for DCAT must be published in a way that can fit in a DCAT DataCatalogue and have a distribution.
DCAT expects typically format Turtle (although this is never mandated?) not JSON-LD. In addition the URLs must be absolute, so the RO-Crate must be converted to Detached.
The inner details of an RO-Crate e.g. author per file should not be included in the dcat, only the ./ level root descriptions need to be reflected in DCAT.
Some additional DCAT-AP requirements are not required in Schema.org but can be expressed by given mapping. A corresponding "DCAT-compatible RO-Crate" profile may be needed.
As an EOSC user I am encouraged by funders to use DCAT-AP 3.0 for publishing datasets. I want to convert the RO-Crate metadata for a published crate to a DCAT description.
Dataset
but in a different namespace. Mapping https://ec-jrc.github.io/dcat-ap-to-schema-org/ shows how to map, but we need programmatic versionDataCatalogue
and have adistribution
../
level root descriptions need to be reflected in DCAT.Relates to #220
The text was updated successfully, but these errors were encountered: