Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dcat:CatalogRecord should always have a foaf:primaryTopic #63

Open
NielsHoffmann opened this issue Dec 9, 2024 · 0 comments
Open

dcat:CatalogRecord should always have a foaf:primaryTopic #63

NielsHoffmann opened this issue Dec 9, 2024 · 0 comments
Labels
3.0.0 Pilot Issues coming from the GeoDCAT-AP 3.0.0 Pilot

Comments

@NielsHoffmann
Copy link

This is an issue for the GeoDCAT-AP 3.0.0 pilot.

According to the Application profile a dcat:CatalogRecord should always point to a dcat:Resource.
https://semiceu.github.io/GeoDCAT-AP/releases/3.0.0/#CatalogueRecord
this is also reflected in the shacl profile:

<https://semiceu.github.io/GeoDCAT-AP/releases/3.0.0#dcat:CatalogRecordShape/65eafe0643a998b84fc2d253de401f9ad8355770> rdfs:seeAlso "https://semiceu.github.io/GeoDCAT-AP/releases/3.0.0#CatalogueRecord.primarytopic";
  shacl:description "A link to the Dataset, Data service or Catalog described in the record."@en;
  shacl:minCount 1;
  shacl:name "primary topic"@en;
  shacl:path foaf:primaryTopic .

<https://semiceu.github.io/GeoDCAT-AP/releases/3.0.0#dcat:CatalogRecordShape/c65d45ed7195ead5f643ec8c8afd29c6dd9662bf> rdfs:seeAlso "https://semiceu.github.io/GeoDCAT-AP/releases/3.0.0#CatalogueRecord.primarytopic";
  shacl:class dcat:Resource;
  shacl:description "A link to the Dataset, Data service or Catalog described in the record."@en;
  shacl:name "primary topic"@en;
  shacl:path foaf:primaryTopic .

The XSLT creates a CatalogRecord for the new DCAT record which points (in this example) properly to the Dataset:

<foaf:isPrimaryTopicOf>
         <rdf:Description>
            <rdf:type rdf:resource="http://www.w3.org/ns/dcat#CatalogRecord"/>
            <foaf:primaryTopic rdf:resource="https://services.rce.geovoorziening.nl/www/download/e39bd6e0-7651-11e0-a1f0-0800200c9a62"/>
            <dct:conformsTo>
               <dct:Standard rdf:about="http://data.europa.eu/930/"/>
            </dct:conformsTo>
...

The XSLT also creates a 'dct:source' CatalogRecord stating that the new (converted) record has a iso-19115 source.
However, this source record, being a dcat:CatalogRecord should contain a foaf:primaryTopic according to the profile and the Shacl file

 <dct:source rdf:parseType="Resource">
               <rdf:type rdf:resource="http://www.w3.org/ns/dcat#CatalogRecord"/>
               <dct:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2024-09-27</dct:modified>
               <cnt:characterEncoding rdf:datatype="http://www.w3.org/2001/XMLSchema#string">UTF-8</cnt:characterEncoding>
               <dct:conformsTo rdf:parseType="Resource">
                  <rdf:type rdf:resource="http://purl.org/dc/terms/Standard"/>
                  <dct:title xml:lang="nl">ISO 19115</dct:title>
                  <owl:versionInfo xml:lang="nl">Nederlands metadata profiel op ISO 19115 voor geografie 2.1.0</owl:versionInfo>
               </dct:conformsTo>
            </dct:source>

The shacl file tests for dcat:Resource, so for the XSLT to conform to the shacl profile, the dcat:Dataset should also be typed as dcat:Resource.

@jakubklimek jakubklimek added the 3.0.0 Pilot Issues coming from the GeoDCAT-AP 3.0.0 Pilot label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0.0 Pilot Issues coming from the GeoDCAT-AP 3.0.0 Pilot
Projects
None yet
Development

No branches or pull requests

2 participants