dcat:Distribution can have spatial and temporal resolution, license, accessRights, ... so hard to make all those properties available using the associated resource panel
dct:language "This property refers to a language used in the textual metadata describing titles, descriptions, etc. of the Datasets in the Catalogue. This property can be repeated if the metadata is provided in multiple languages."
The first dct:language is the main language
Do we store language as a @rdf:resource or using skos:Concept (like in dcat-ap1)?
If main language is eng.
Other language fre.
<dcat:keyword xml:lang="eng">Water</dcat:keyword>
<dcat:keyword xml:lang="fre">Eau</dcat:keyword>
<dcat:keyword xml:lang="eng">Management plan</dcat:keyword>
<dcat:keyword xml:lang="fre">Plan de gestion</dcat:keyword>
<dcat:keyword xml:lang="eng">Well</dcat:keyword>
fre is missing. Empty field is available.
<dcat:keyword xml:lang="spa">Cuenca</dcat:keyword>
main language eng is missing and spa not declared has other language. This is not supported.
To retrieve multilingual element by group we assume that an
element in the main language is defined first and then
we collect translations by group.
update-fixed-info cleanup the encoding and create empty elements when needed. (maybe use inflate?)
GeoNetwork target version
This plugin will work on version 4 (is 3.10.x or 3.12.x needed?)
Implementation rules
Associated resources
dcat:Distribution
can have spatial and temporal resolution, license, accessRights, ... so hard to make all those properties available using the associated resource panelReferences: https://github.com/metadata101/dcat2/commit/0391e4cde14dce766043306ee4e2c9e38c8353db
Multilingual
Add similar support as ISO records:
dct:language
"This property refers to a language used in the textual metadata describing titles, descriptions, etc. of the Datasets in the Catalogue. This property can be repeated if the metadata is provided in multiple languages."dct:language
is the main language@rdf:resource
or usingskos:Concept
(like in dcat-ap1)?or
Thesaurus for fields
A concept value is preferably referenced as:
Although we also see implementations where the concept is (re)defined within the element
Both situation may occur alongside each other, especially when indexing remote content.
I/O
GeoNetwork tasks
Plugin tasks
Plugin
[x] DCAT2 XSD
[x] DCAT2 Plugin initial config
[ ] DCAT2 Basic editor
IO
Editor
Record view
Profiles