-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
This is in response to Marek's request to take a look at how CCMM actually stands against DCAT-AP. It is clear that in order to see a CCMM record as DCAT-AP, non-trivial mapping will be required due to different modeling approaches taken. Still, some classes/properties that overlap with DCAT-AP could be profiles of their DCAT-AP counterparts, and they are not. So it could be considered to make them profiles of the DCAT-AP counterparts to make the connection explicit. In other cases, it should at least be clear how the mapping will happen, and if we have everything in place and decided to make this doable in a predictable way.
Here are my notes:
- Dataset.title profiles directly
dcterms:titleinstead of DCAT-AP dataset title and there is no support for language (which is used e.g. for autotranslations, etc.) - Dataset.hasDescription is modelled in a different way than in DCAT-AP, it has a description type. In case of multiple descriptions, which one is the one to be considered in DCAT-AP?
- Dataset.hasIdentifier has no relation to DCAT-AP main/other identifier and the guidelines. In case of mapping to DCAT-AP, all can be connected to Dataset using other identifier, but it is unclear which one should be the main identifier and/or the identifier used for the instance of
dcat:Dataset- Identifier is not a profile of DCAT-AP Identifier
- Identifier value is not profile of Identifier.notation
- has primary/other language is profile of
dcterms:languagedirectly and not of of DCAT-AP dataset language - Why is Language system called Language system, when everywhere else (dcterms, dcat) it is called Linguistic System?
- Dataset.relatedResource is not a profile of DCAT-AP related resource
- Dataset.hasTermsOfUse will have to be mapped to DCAT-AP distributions (so the assumption here is that they will be the same for all distributions), possibly split into rights, licence with a EU Licence NAL attached. access rights are on Dataset level in DCAT-AP, also paired with the Access right NAL.
- Data service label has no connection to the mandatory DCAT-AP Data Service title
- Time reference to Dataset Temporal coverage mapping?
- Metadata record date updated is not mandatory, but it is in DCAT-AP
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels