metadata101 / dcat2

Data Catalog Vocabulary (DCAT) - Version 2
GNU General Public License v2.0
6 stars 3 forks source link

Tasks list #1

Closed fxprunayre closed 3 years ago

fxprunayre commented 4 years ago

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 xmlns:dc="http://purl.org/dc/elements/1.1/">
         <dcat:Distribution>
            <dcat:downloadURL>https://sdi.eea.europa.eu/data/67c0ccae-a6db-433a-9852-fdb09f1b3a8b</dcat:downloadURL>
            <dct:description>DUT#Direct download|ENG#|FRE#|GER#</dct:description>
            <dct:format>
               <skos:Concept>
                  <skos:prefLabel>WWW:LINK</skos:prefLabel>
               </skos:Concept>
            </dct:format>
         </dcat:Distribution>
      </dcat:distribution>

References: https://github.com/metadata101/dcat2/commit/0391e4cde14dce766043306ee4e2c9e38c8353db

Multilingual

Add similar support as ISO records:

image

<dct:language rdf:resource="http://id.loc.gov/vocabulary/iso639-2/eng"/>

or

      <dct:language>
         <skos:Concept>
            <rdf:type rdf:resource="http://purl.org/dc/terms/LinguisticSystem"/>
            <skos:prefLabel xml:lang="nl"/>
            <skos:prefLabel xml:lang="en"/>
            <skos:prefLabel xml:lang="fr"/>
            <skos:prefLabel xml:lang="de"/>
            <skos:inScheme rdf:resource="http://publications.europa.eu/resource/authority/language"/>
         </skos:Concept>
      </dct:language>
      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?)

Thesaurus for fields

element codelist
dct:language http://publications.europa.eu/resource/authority/language / http://id.loc.gov/vocabulary/iso639-1
dct:license https://spdx.org/licenses/
dct:accessRights http://publications.europa.eu/resource/authority/access-right
dct:accrualPeriodicity http://publications.europa.eu/resource/authority/frequency / http://purl.org/linked-data/sdmx/2009/code#freq-W
dct:conformsTo http://www.opengis.net/def/crs / https://eur-lex.europa.eu/eli/reg / http://www.opengis.net/def/serviceType/ogc
dct:format / dcat:mediaType https://www.iana.org/assignments/media-types

A concept value is preferably referenced as:

<dct:conformsTo rdf:resource="http://www.opengis.net/def/serviceType/ogc/wfs/2.0.0"/>

Although we also see implementations where the concept is (re)defined within the element

<dct:conformsTo> 
  <skos:Concept rdf:about="http://www.opengis.net/def/serviceType/ogc/wfs/2.0.0">
  <dct:title>OGC Web Feature Service</dct:title>
  </skos:Concept>
</dct:conformsTo> 

Both situation may occur alongside each other, especially when indexing remote content.

I/O

GeoNetwork tasks

    <for name="dct:language/@rdf:resource" use="data-gn-language-picker">
      <directiveAttributes data-prefix="http://id.loc.gov/vocabulary/iso639-1/"/>
    </for>

Plugin tasks

Plugin

IO

Editor

Record view

Profiles

fxprunayre commented 3 years ago

Replaced by https://github.com/metadata101/dcat2/projects/1