Standard / DCAT (and profiles) export #7600

fxprunayre · 2024-01-09T11:57:56Z

Based on the recent publication of various profiles of DCAT (at least in Europe), GeoNetwork needs to improve its capacity to export metadata records in DCAT. GeoNetwork export to DCAT format initially done in 2012 was targeting interaction with semantic service and semantic sitemap support. Later was added some changes related to GeoDCAT-AP to improve the mapping but the mapping was not fully consistent with SEMICeu work (eg. ISO19139 to GeoDCAT-AP XSL conversion). Actually, new DCAT profiles are defined and some datasets and services managed in catalogue are in the scope of those profiles (eg. HVD, mobility).

DCAT mappings and formatters

This proposal adds:

a default DCAT export following W3C standard https://www.w3.org/TR/vocab-dcat-3/
an extension for the European DCAT-AP https://semiceu.github.io/DCAT-AP/releases/3.0.0/
- an extension for the European GeoDCAT-AP https://semiceu.github.io/GeoDCAT-AP/releases/
- an extension for the European DCAT-AP-Mobility https://mobilitydcat-ap.github.io/mobilityDCAT-AP/releases/1.0.0/index.html
- an extension for the European DCAT-AP-HVD https://semiceu.github.io/DCAT-AP/releases/2.2.0-hvd/

The mapping is done from ISO19115-3 to DCAT*. An ISO19139 to ISO19115-3 conversion can be applied before if needed.

The SEMICeu XSLT conversion is also included with minor improvements (https://github.com/SEMICeu/iso-19139-to-dcat-ap/pulls). This conversion is from ISO19139 to RDF and if needed a conversion from ISO19115-3 is applied.

The mapping was created with:

BRGM and Wallonia Region (SPW)
Existing GeoNetwork DCAT mapping
SEMICeu ISO to GeoDCAT-AP conversion

Each DCAT formats are available using a formatter eg. http://localhost:8080/geonetwork/srv/api/records/be44fe5a-65ca-4b70-9d29-ac5bf1f0ebc5/formatters/eu-dcat-ap

Validation

Validation in test:

check that RDF graph is valid
check using SHACL rules (disabled)

Online validation tool:

https://www.itb.ec.europa.eu/shacl/dcat-ap/upload

Opendata portal testing

Tested with success with the following data portals:

https://data.gov.be/
https://www.data.gouv.fr/ (with some limitations noticed, udata does not support: temporal range with no end date - now in ISO, multiple resource identifiers, EU vocabularies for licenses, series are not imported)

Mapping discussion

Embedded objects vs. references

ISO rarely contains references to objects but it can be done with various encoding:

using Anchor eg. keywords

 <gmd:keyword>
    <gmx:Anchor xlink:href="http://rod.eionet.europa.eu/obligations/102">Greenhouse gas inventories (UNFCCC)</gmx:Anchor>
 </gmd:keyword>

using @uuid (sometimes used in contact)

<gmd:contact>
  <gmd:CI_ResponsibleParty uuid="https://edmo.seadatanet.org/report/4667">

using a specific field eg. metadataLinkage, identifier party

<cit:partyIdentifier>
  <mcc:MD_Identifier>
     <mcc:code>
        <gco:CharacterString>https://orcid.org/0000-0002-5150-2276</gco:CharacterString>
     </mcc:code>
     <mcc:codeSpace>
        <gco:CharacterString>ORCID</gco:CharacterString>

<mdb:metadataLinkage>
  <cit:CI_OnlineResource>
    <cit:linkage>
      <gco:CharacterString>https://metawal.wallonie.be/geonetwork/srv/api/records/3dc91d81-338f-425d-b27b-f62aa0464e21</gco:CharacterString>
    </cit:linkage>
    <cit:function>
      <cit:CI_OnLineFunctionCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#CI_OnLineFunctionCode" codeListValue="completeMetadata"/>

The DCAT mapping provides an entry point to customize where to pick up object references.

DCAT in CSW service

All DCAT profiles are also accessible using CSW protocol.
A GetRecordById operation can be used: http://localhost:8080/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=da165110-88fd-11da-a88f-000d939bc5d8&outputSchema=https://semiceu.github.io/DCAT-AP/releases/2.2.0-hvd/ and is equivalent to the API http://localhost:8080/geonetwork/srv/api/records/da165110-88fd-11da-a88f-000d939bc5d8/formatters/eu-dcat-ap-hvd . For this, outputSchema configuration is improved to not be mixed with typenames.

If an outputSchema does not provide brief, summary, full variations, only one XSLT can be provided (so it is easier to bridge CSW output to a formatter):

DCAT download from the record view

To add the formatter in the record view download list:

{
  "mods": {
    "search": {
      "downloadFormatter": [
        {
          "label": "exportMEF",
          "url": "/formatters/zip?withRelated=false",
          "class": "fa-file-zip-o"
        },
        {
          "label": "exportPDF",
          "url": "/formatters/xsl-view?output=pdf&language=${lang}",
          "class": "fa-file-pdf-o"
        },
        {
          "label": "exportXML",
          "url": "/formatters/xml",
          "class": "fa-file-code-o"
        },
        {
          "label": "DCAT",
          "url": "/formatters/dcat"
        },
        {
          "label": "EU-DCAT-AP",
          "url": "/formatters/eu-dcat-ap"
        },
        {
          "label": "EU-GEO-DCAT-AP",
          "url": "/formatters/eu-geodcat-ap"
        },
        {
          "label": "EU-DCAT-AP-MOBILITY",
          "url": "/formatters/eu-dcat-ap-mobility"
        },
        {
          "label": "EU-DCAT-AP-HVD",
          "url": "/formatters/eu-dcat-ap-hvd"
        }
      ]

Related item

Future work & known limitation

Improve URI scheme for each resources (eg. organisations, contacts, distributions, keywords)
Mapping improvements eg.
- updates following ongoing GeoDCAT-APv3 revision
- currently not supported property: distribution > spdx:checksum,
- improve associated resources mapping (using API?) eg. service to and from dataset relations ?
Add those formats to OGC API Records in order to have same mapping everywhere.
Add schematron validation in order to ensure user editing on ISO records are populating all fields needed for each DCAT profiles

Supported by

Funded by BRGM
Funded by Wallonia region (SPW)

Checklist

Proposal to better organize various flavor of DCAT. The target is to support: * DCAT * EU DCAT-AP * EU DCAT-AP mobility * EU GeoDCAT-AP.

…codec versions)

…d status.

…1 accrualPeriodicity.

…ccessRights and rights.

… from EU vocabulary as skos:Concept.

…ic is required even if isPrimaryTopic is defined. Only one rights allowed.

…ct:type allowed.

…for now.

…conformity for the CatalogueRecord.

…moved xsl messages)

.../iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-access-and-use.xsl

…lowing GeoDCAT-AP 3 revision working group progress.

…rking group meeting.

… template.

…e robust on CRS.

jeanpommier · 2024-06-20T15:15:25Z

schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-dataset.xsl

+  Range:	dcterms:Frequency (A rate at which something recurs)
+  Usage note:	The value of dcterms:accrualPeriodicity gives the rate at which the dataset-as-a-whole is updated. This may be complemented by dcat:temporalResolution to give the time between collected data points in a time series.
+  -->
+  <xsl:variable name="isoFrequencyToDublinCore"


I am under the impression that this mapping is not applied. On my experiments, annually is kept as-is instead of being replaced by ANNUAL in the dcat output (default DCAT outputSchema=http://www.w3.org/ns/dcat#)

Previous remark applies to csw-dcat output.

But indeed it works when formattin the file through the dcat download formatter /formatters/dcat (download button)

http://www.w3.org/ns/dcat# correspond to current conversion (see dcat-brief.xsl)

Use http://www.w3.org/ns/dcat#core when using CSW
eg.
http://localhost:8080/geonetwork/srv/fre/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=da165110-88fd-11da-a88f-000d939bc5d8&outputschema=http%3A%2F%2Fwww.w3.org%2Fns%2Fdcat%23core

Maybe the current conversion should be renamed to http://www.w3.org/ns/dcat#legacy ? but that will alter current apps using the current DCAT mapping

jeanpommier · 2024-06-20T15:20:13Z

About the licence section, can you provide a licence definition (XML snippet for instance) that would be properly recognized by data.gouv.fr ?

fxprunayre · 2024-06-25T12:16:11Z

About the licence section, can you provide a licence definition (XML snippet for instance) that would be properly recognized by data.gouv.fr ?

eg.
https://apps.titellus.net/geonetwork/srv/eng/catalog.search#/metadata/fa6e13d4-5700-4391-a472-dd29b82ba3dbREMITEST
which correspond to
https://demo.data.gouv.fr/fr/datasets/lieux-dobservation-et-de-surveillance-du-reseau-remitest/

josegar74 · 2024-07-16T09:23:37Z

There are some vocabularies, like data-themes, HVD and licenses that are provided in the formatters folder as seem used in the xslt. HVD seems requiring keywords from that vocabulary in the metadata records. Also Licenses seems require to be used in use constraints elements in the metadata records.

For data-themes, doesn't seem to be associated in the metadata to that vocabulary (https://github.com/geonetwork/core-geonetwork/pull/7600/files#diff-e032efa415655cf3ab6df515d6853952475f431571cbbaf1e2005257761accf2R216-R244), which looks bizarre, but I don't have all the context.

Can be these vocabularies downloaded from the INSPIRE Registry? Otherwise, including them in the formatters folder doesn't seem a good location, if the users need to load them in GeoNetwork.

fxprunayre · 2024-07-16T10:08:22Z

Licenses seems require to be used in use constraints elements in the metadata records.

For license, SHACL validation may expect EU codelist value eg. http://publications.europa.eu/resource/authority/licence/CC0

So we need to map more general values like "http://creativecommons.org/publicdomain/zero/1.0/" or "https://creativecommons.org/publicdomain/zero/1.0/" or the labels "Creative Commons Atribución 4.0 Internacional" to the EU value.

For data-themes, doesn't seem to be associated in the metadata to that vocabulary

SEMICeu conversion is providing a mapping between topic category or INSPIRE theme and data theme so data theme does not need to be encoded in the record.

Can be these vocabularies downloaded from the INSPIRE Registry? Otherwise, including them in the formatters folder doesn't seem a good location, if the users need to load them in GeoNetwork.

It depends, eg. HVD define vocabularies
https://semiceu.github.io/DCAT-AP/releases/2.2.0-hvd/#controlled-vocabularies-to-be-used
and some of them are available in
https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/high-value-dataset-category
so you've to import them from here if you want to encode HVD.

Also for applicable legislation, the vocabularies does not exist yet http://data.europa.eu/r5r/applicableLegislation so indeed a specific thesaurus was created.

So all this type of issue is indeed something hard to track because you need to first setup a proper template with required vocabularies depending on the type of DCAT flavor you want to produce. Not sure how we could improve that? By default, it would require to provide templates + vocabularies.

josegar74 · 2024-07-16T11:18:31Z

schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-resource.xsl

+  <!-- Resource
+   Unsupported:
+   * dcat:first|previous(sameAs replaces, previousVersion?)|next|last|hasVersion (using the Associated API, navigate to series and sort by date?)
+   * dct:isReferencedBy (using the Associated API)


What does it mean (using the Associated API)?

Some of the relations to other records are not stored in the record itself. It also depends on privileges on related records. So another approach could be to use the associated API which resolve relation in both direction and filter records based on privileges.

josegar74 · 2024-07-16T11:29:14Z

schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-variables.xsl

+    <entry key="dcat:keyword">mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/mri:MD_Keywords/mri:keyword</entry>
+    <entry key="dcat:keyword">mdb:MD_Metadata/mdb:identificationInfo/srv:SV_ServiceIdentification/mri:descriptiveKeywords/mri:MD_Keywords/mri:keyword</entry>


Are these entries used? It seems keywords are handled in https://github.com/geonetwork/core-geonetwork/pull/7600/files#diff-466d4f123bce63f74e41e43d0a57f7be6bde3f8e6f59713fbb03670f8337128d instead of https://github.com/geonetwork/core-geonetwork/pull/7600/files#diff-ce8fa96060c124fa54925719f00ade2da31b5a6d2e56073ffd6de504350cffdfR144-R160 where is used isoToDcatCommonNames

Removed. Indeed there is 2 templates handling keyword with CharacterString and Anchor that are more specialized so it should be never used.

josegar74 · 2024-07-16T11:32:39Z

schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-keywords.xsl

+  <xsl:template mode="iso19115-3-to-dcat"
+                match="mdb:identificationInfo/*/mri:descriptiveKeywords/*/mri:keyword[gcx:Anchor/@xlink:href != '']"
+                priority="2">
+    <dcat:theme>
+      <skos:Concept>
+        <xsl:call-template name="rdf-object-ref-attribute"/>
+        <xsl:call-template name="rdf-localised">
+          <xsl:with-param name="nodeName"
+                          select="'skos:prefLabel'"/>
+        </xsl:call-template>
+      </skos:Concept>
+    </dcat:theme>
+  </xsl:template>
+
+  <xsl:template mode="iso19115-3-to-dcat"
+                match="mdb:identificationInfo/*/mri:descriptiveKeywords/*/mri:keyword[gco:CharacterString/text() != '']"
+                priority="2">
+    <xsl:call-template name="rdf-localised">
+      <xsl:with-param name="nodeName"
+                      select="'dcat:keyword'"/>
+    </xsl:call-template>
+  </xsl:template>


dcat:theme should be used when the keyword comes from a thesaurus, but here is checking only for gcx:Anchor.

While dcat:keyword keyword should be used for free text keywords, assuming that uses gco:CharacterString, but it can be that keywords from a thesaurus use gco:CharacterString, no?

Should not be checked if the keyword has a thesarusName element?

It depends a bit on what application are doing with theme and keyword. The main restriction from a DCAT AP point of view is https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/services/src/test/resources/org/fao/geonet/api/records/formatters/shacl/eu-dcat-ap-3.0.0/mdr-vocabularies.shape.ttl#L121-L130

Then it looks like in practice sometime only http://publications.europa.eu/resource/authority/data-theme vocabulary is used to set the dcat:theme and all others keywords are dcat:keyword. Here the conversion should be SHACL valid as far as you have a topic or INSPIRE theme mapped to data-theme. If there is a thesaurus, indeed we could produce a dcat:theme with a skos:Concept instead of a simple keyword.

See https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/services/src/test/resources/org/fao/geonet/api/records/formatters/iso19115-3.2018-eu-dcat-ap-dataset-core.rdf#L245-L380

Most of the time we are configuring the editor to encode ISO keyword using Anchor (as requested for INSPIRE). This is facilitated by #8118

josegar74 · 2024-07-16T12:40:22Z

schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-variables.xsl

+    <entry key="dct:description">mdb:MD_Metadata/mdb:distributionInfo/mrd:MD_Distribution/mrd:transferOptions/mrd:MD_DigitalTransferOptions/mrd:onLine/cit:CI_OnlineResource/cit:description</entry>
+    <entry key="dct:description">mdb:MD_Metadata/mdb:distributionInfo/mrd:MD_Distribution/mrd:distributor/mrd:MD_Distributor/mrd:distributorTransferOptions/mrd:MD_DigitalTransferOptions/mrd:onLine/cit:CI_OnlineResource/cit:description</entry>
+    <entry key="owl:versionInfo">mdb:MD_Metadata/mdb:metadataStandard/cit:CI_Citation/cit:edition</entry>
+    <entry key="adms:versionNotes">mdb:MD_Metadata/mdb:resourceLineage/mrl:LI_Lineage/mrl:statement</entry>


This seems not used.

See https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-lineage.xsl#L40-L48

It comes from lineage eg. https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/services/src/test/resources/org/fao/geonet/api/records/formatters/iso19115-3.2018-dcat-dataset-core.rdf#L370-L390

josegar74 · 2024-07-17T08:11:52Z

...as/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-distribution.xsl

+            Rule:
+            * Use mimetype if any
+            * Use WWW:DOWNLOAD:(.*=format) if any
+            * fallback to ancestor::mrd:MD_DigitalTransferOptions/mrd:distributionFormat/*/mrd:formatSpecificationCitation


This is a bit unclear, apparently for dcat:mediaType, dcat:compressFormat and dcat:packageFormat relies onmrd:MD_DigitalTransferOptions/mrd:distributionFormat/*/mrd:formatSpecificationCitation?

But in https://github.com/geonetwork/core-geonetwork/pull/7600/files#diff-5fa6856eb0e0615450b025fa6ac293be136ee98f4b82b908997ebf6667438ef8R399-R404 it is not set the elementName for any of them.

For dcat:compressFormat there is another template, that is also unclear if used: https://github.com/geonetwork/core-geonetwork/pull/7600/files#diff-5fa6856eb0e0615450b025fa6ac293be136ee98f4b82b908997ebf6667438ef8R407-R413

Not sure if pointing to https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-distribution.xsl#L416-L417 but if yes, the template define a default value for elementName.

schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-associated.xsl

josegar74 · 2024-07-17T08:53:58Z

...as/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-distribution.xsl

+  <xsl:template mode="iso19115-3-to-dcat-distribution"
+                match="mrd:distributionFormat/*/mrd:fileDecompressionTechnique">
+    <xsl:call-template name="rdf-format-as-mediatype">
+      <xsl:with-param name="elementName" select="'dcat:compressFormat'"/>
+      <xsl:with-param name="format" select="*/text()"/>
+    </xsl:call-template>
+  </xsl:template>


Unclear as doesn’t seem to work, also apparently it seems the same value assigned to all the online resources?

Yes this can be challenging as DCAT distribution contains a number of properties that ISO affect to the resource. So it could work fine if we have only one download link in a record or could be encoded using different distribution block but it is not the case usually.

There is a test for example
https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/services/src/test/resources/org/fao/geonet/api/records/formatters/iso19115-3.2018-dcat-dataset.xml#L1254-L1294
is converted to
https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/services/src/test/resources/org/fao/geonet/api/records/formatters/iso19115-3.2018-eu-dcat-ap-dataset-core.rdf#L554-L570

Dedicated template exist in dcat-core-keyword

* Add mapping for referenceSystem * Add test * Disable distribution for now and delegate to DCAT-AP for now.

…intenanceFrequency which can be mapped to mobility DCAT vocabulary https://mobilitydcat-ap.github.io/controlled-vocabularies/update-frequency/latest/index.html#.

Match first resource constraints and then map to access and use elements.

…ividual.

Cardinality: * ISO 0..n * DCAT 0..n * DCAT-AP 0..1 * Mobility DCAT 1..1 (in ISO either use corresponding period eg. P0Y0M0DT1H0M0S or extend the codelist with the proper vocabulary) accrualPeriodicity mapping done using the ISO to Dublin core value mapping but additional checks are done when ISO records extended the codelist and may used the EU Publication Office frequency codes or the Mobility DCAT-AP update frequency codes. Domain specific codelists take priority over the DC or ISO codelists. eg. <mmi:MD_MaintenanceFrequencyCode codeListValue="15min"/> multipleAccrualPeriodicityAllowed is a parameter that can be set to true to allow multiple accrualPeriodicity values. Default to false for EU formatters. true for DCAT.

jahow · 2024-09-23T09:17:35Z

Hi @fxprunayre,

Could you please clarify something for me: why do we need different export profiles (HVD, Mobility etc.)? Why can't we just output one graph that would provide the proper elements to fill the requirements for all of these profiles?

I feel like RDF allows creating graphs that are quite rich and contain many different statements targeting various consumers. Is there a reason, technical or other, for this profile-based approach? Thanks

fxprunayre · 2024-09-23T10:46:05Z

why do we need different export profiles (HVD, Mobility etc.)? Why can't we just output one graph that would provide the proper elements to fill the requirements for all of these profiles?

Some opendata portals expect a particular DCAT profiles but true, we could mix all in one. But if you look to profile's model and SHACL validation, one element can be encoded using different encoding and can be optional in one profile, mandatory in others, or not having the same definition (eg. vocabularies) ... Looking at different versions of a profile, the encoding for an element can also change over time.
So it is important to do testing with other applications ingesting DCAT and see what is expected. We are currently using this PR with Belgium mobility and HVD portals.

https://semiceu.github.io/DCAT-AP/r5r/releases/3.0.0/#applicableLegislation Add the element to DCAT-AP base. Element is 0..n in DCAT-AP and should be present in extensions (mobility, hvd, geodcat). HVD requires at least http://data.europa.eu/eli/reg_impl/2023/138/oj and cardinality is 1..n. Do not restrict to a particular legislation list. A sample vocabulary is provided but it can be extended depending on catalogue domains.

In DCAT and DCAT-AP, `dct:identifier` is 0..n. Mobility DCAT restrict it to 0..1. In DCAT-AP and extensions, only convert the first identifier as `dct:identifier`; others as `adms:identifier`.

Use `:` separator for URN like identifiers.

fxprunayre and others added 30 commits December 6, 2023 11:29

Standard / ISO / DCAT formatters

262422f

Proposal to better organize various flavor of DCAT. The target is to support: * DCAT * EU DCAT-AP * EU DCAT-AP mobility * EU GeoDCAT-AP.

Formatter / DCAT / Improvements.

b1555e9

Formatter / DCAT / Core.

0d06674

Formatter / DCAT / Core / Associated.

94318cb

Formatter / DCAT / Core / Lineage.

10ee379

Formatter / DCAT / Core / Dataset / Temporal.

1944cd4

Formatter / DCAT / Core / Dataset / Distributions.

18fb48c

Formatter / DCAT / Core / Dataset / Services.

18285eb

Formatter / DCAT / Core / Mulitlingual support.

87fcbf2

Formatter / DCAT / RDF valid model.

19b11e5

Formatter / DCAT / Tests.

b59f45d

Formatter / EU-DCAT-AP / CatalogRecord.

354ba25

Formatter / DCAT / Test dep.

2ff0c73

Formatter / EU-DCAT-AP / Draft with test.

cb6e152

Added DCAT-AP validation with SHACL rules in FormatterApiTest.

ebb1104

Library / Update Jena for SHACL validation (issue on various commons-…

26297e2

…codec versions)

Formatter / EU-DCAT-AP / Improve shacl validation status - license an…

0871113

…d status.

Formatter / EU-DCAT-AP / Improve shacl validation status - bytesize.

eccaf59

Formatter / EU-DCAT-AP / Improve shacl validation status - 1 format, …

0fbd299

…1 accrualPeriodicity.

Formatter / EU-DCAT-AP / Improve shacl validation status - license, a…

374682b

…ccessRights and rights.

Formatter / EU-DCAT-AP / Improve shacl validation status - dcat:theme…

f0bf45e

… from EU vocabulary as skos:Concept.

Formatter / EU-DCAT-AP / Improve shacl validation status - primaryTop…

b85e1e5

…ic is required even if isPrimaryTopic is defined. Only one rights allowed.

Formatter / EU-DCAT-AP / Improve shacl validation status - only one d…

d8b4c7a

…ct:type allowed.

Formatter / EU-DCAT-AP / Add 2.1.1 base shacl validation level.

e3d2780

Formatter / EU-DCAT-AP / Validation / Shacl 2.1.1 / Success.

9aae81d

Formatter / EU-DCAT-AP-HVD / Base conversion with HVD category

92638f0

Formatter / EU-DCAT-AP-HVD / Add Shacl validation - which is failing …

bfa921c

…for now.

Formatter / EU-GEODCAT-AP / CatalogRecord.

e914ce0

Formatter / EU-GEODCAT-AP / Shacl validation.

191b5d2

Formatter / DCAT / Declare ISO conformity for the source and DCAT-AP …

52e7b15

…conformity for the CatalogueRecord.

Updated license mapping to map to EU licenses for dcat-ap profile (re…

c35b34d

…moved xsl messages)

fxprunayre commented May 14, 2024

View reviewed changes

.../iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-access-and-use.xsl Outdated Show resolved Hide resolved

fxprunayre added 4 commits May 15, 2024 18:43

Standards / ISO / Formatters / DCAT / Update SEMICeu conversion - fol…

7398ba1

…lowing GeoDCAT-AP 3 revision working group progress.

Standards / ISO / Formatters / DCAT / Updates following GeoDCAT-AP wo…

0bb68c1

…rking group meeting.

Standards / ISO / Formatters / DCAT / Update SEMICeu conversion - fix…

6a3b7dc

… template.

Standards / ISO / Formatters / DCAT / Update SEMICeu conversion - mor…

fe54f4a

…e robust on CRS.

josegar74 self-requested a review June 3, 2024 08:43

fxprunayre modified the milestones: 4.4.5, 4.4.6 Jun 13, 2024

jeanpommier reviewed Jun 20, 2024

View reviewed changes

josegar74 reviewed Jul 17, 2024

View reviewed changes

Formatter / DCAT / ISO common name are unused for keywords

63db0da

Dedicated template exist in dcat-core-keyword

fxprunayre force-pushed the dcat branch from 605e755 to 63db0da Compare July 18, 2024 11:51

fxprunayre added 2 commits July 18, 2024 14:37

Formatter / DCAT / Mobility DCAT improvement.

34cb78b

* Add mapping for referenceSystem * Add test * Disable distribution for now and delegate to DCAT-AP for now.

Formatter / DCAT / accrualPeriodicity / Add support for userDefinedMa…

53aeffc

…intenanceFrequency which can be mapped to mobility DCAT vocabulary https://mobilitydcat-ap.github.io/controlled-vocabularies/update-frequency/latest/index.html#.

josegar74 added the backport 4.2.x label Aug 21, 2024

fxprunayre added 2 commits August 22, 2024 17:13

DCAT / Formatter / Simplify template for constraint

2c29a5a

Match first resource constraints and then map to access and use elements.

Formatter / DCAT / Improve mapping for organization with multiple ind…

0e183c1

…ividual.

fxprunayre mentioned this pull request Sep 17, 2024

Why default Dataset resources to dcat:landingPage instead of foaf:page? SEMICeu/GeoDCAT-AP#135

Open

fxprunayre added 2 commits September 20, 2024 14:07

Missing test file update.

60f6e98

fxprunayre added 3 commits September 30, 2024 19:30

Formatter / DCAT / Identifier(s)

bee5bf4

In DCAT and DCAT-AP, `dct:identifier` is 0..n. Mobility DCAT restrict it to 0..1. In DCAT-AP and extensions, only convert the first identifier as `dct:identifier`; others as `adms:identifier`.

Formatter / DCAT / Identifier / Urn

08a58c8

Use `:` separator for URN like identifiers.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Standard / DCAT (and profiles) export #7600

Standard / DCAT (and profiles) export #7600

fxprunayre commented Jan 9, 2024 •

edited

Loading

jeanpommier Jun 20, 2024

jeanpommier Jun 20, 2024

jeanpommier Jun 20, 2024

fxprunayre Jun 25, 2024

jeanpommier commented Jun 20, 2024

fxprunayre commented Jun 25, 2024

josegar74 commented Jul 16, 2024

fxprunayre commented Jul 16, 2024

josegar74 Jul 16, 2024

fxprunayre Jul 17, 2024

josegar74 Jul 16, 2024

fxprunayre Jul 17, 2024

josegar74 Jul 16, 2024

fxprunayre Jul 17, 2024

josegar74 Jul 16, 2024

fxprunayre Jul 17, 2024

josegar74 Jul 17, 2024

fxprunayre Jul 17, 2024

josegar74 Jul 17, 2024

fxprunayre Jul 17, 2024

jahow commented Sep 23, 2024

fxprunayre commented Sep 23, 2024

		<entry key="dcat:keyword">mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/mri:MD_Keywords/mri:keyword</entry>
		<entry key="dcat:keyword">mdb:MD_Metadata/mdb:identificationInfo/srv:SV_ServiceIdentification/mri:descriptiveKeywords/mri:MD_Keywords/mri:keyword</entry>

Standard / DCAT (and profiles) export #7600

Are you sure you want to change the base?

Standard / DCAT (and profiles) export #7600

Conversation

fxprunayre commented Jan 9, 2024 • edited Loading

DCAT mappings and formatters

Validation

Opendata portal testing

Mapping discussion

Embedded objects vs. references

DCAT in CSW service

DCAT download from the record view

Related item

Future work & known limitation

Supported by

Checklist

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jeanpommier commented Jun 20, 2024

fxprunayre commented Jun 25, 2024

josegar74 commented Jul 16, 2024

fxprunayre commented Jul 16, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jahow commented Sep 23, 2024

fxprunayre commented Sep 23, 2024

fxprunayre commented Jan 9, 2024 •

edited

Loading