W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > April 2018

[dxwg] Use Case: interoperability between metadata standards describing resources of various types

From: Stijn Goedertier via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Apr 2018 18:53:50 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-317352272-1524596029-sysbot+gh@w3.org>
stijngoedertier has just created a new issue for https://github.com/w3c/dxwg:

== Use Case: interoperability between metadata standards describing resources of various types ==
### Use case name
Status: draft / proposed


Creator: Mathias De Schrijver, Lieven Raes, Thomas D’Haenens, Stijn Goedertier

Deliverable(s): DCAT1.1

## Tags
 dcat meta service

## Stakeholders
data producer, data publisher, data consumer

## Problem statement
 At present, data providers in the public sector are using a wide variety of metadata standards to describe various resource types. For example:
- Geospatial datasets, dataset series, and services are encoded using metadata standards based on ISO19115:2003, ISO19119, ISO19139, or [ISO-19115-1];
- Archival Information on documents, file groups, and record series are described with Encoded Archival Description [EAD3](http://www.loc.gov/ead/)
- Open data datasets and APIs (encoded using DCAT).

Data publishers would like to continue to manage and describe resources of these types using the most appropriate metadata standards, while at the same time reaching the widest possible audience by converting metadata into a frequently used, cross-domain metadata vocabulary like DCAT for inclusion in DCAT-conform catalogs. The currently recommended version of DCAT defines dcat:Dataset as ‘_A collection of data, published or curated by a single agent, and available for access or download in one or more formats_'. If we want to support describing resource types that arguably do not meet this definition (e.g. services, documents, …), we may need to revise the DCAT class structure. One approach could be to provide a more general class than dcat:Dataset like 'Work' or ‘Expression’, taking for example inspiration from definitions in FRBR. In addition, it may be possible to define various sub-classes, like 'Document', 'Data Service', or perhaps even 'Software'. 

## Existing approaches 
- The [GeoDCAT-AP](https://www.w3.org/TR/dcat-ucr/#bib-GeoDCAT-AP) specification provides a mapping for converting ISO19115:2003/ISO19139-based metadata records into DCAT-AP. It also provides an extended vocabulary for encoding other resource types such as services and dataset series.
- The DCAT Application Profile for European Data Portals [DCAT-AP](https://www.w3.org/TR/dcat-ucr/#bib-DCAT-AP) provides an optional dcterms:type property on dcat:Dataset for indicating the resource type (soft typing). A controlled vocabulary for the resource types has not been established.

## Links
- Interoperability between metadata standards: a reference implementation for metadata catalogues. Geraldine Nolf. SDSVoc. 1 December 2016. URL: https://www.w3.org/2016/11/sdsvoc/agenda#p117
- [FRBR] Functional Requirements for Bibliographic Records. 2008. International Federation of Library Associations and Institutions URL: https://www.ifla.org/files/assets/cataloguing/frbr/frbr_2008.pdf#page=18

## Requirements
- [Dataset type \[RDST\]](https://www.w3.org/TR/dcat-ucr/#RDST): Consider creating a generic resource type like 'Work' or a limited set of sub-classes like 'Dataset, 'Data Service', 'Document', 'Series' , etc.

## Related use cases
[Scope or type of dataset with a DCAT description \[ID8\]](https://www.w3.org/TR/dcat-ucr/#ID8), [Modelling resources different from datasets \[ID20\]](https://www.w3.org/TR/dcat-ucr/#ID20), [Cross-vocabulary relationships \[ID36\]](https://www.w3.org/TR/dcat-ucr/#ID36)

## Comments
This relates to #180, #181, #182 and in particular #56 .


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/223 using your GitHub account
Received on Tuesday, 24 April 2018 18:53:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:02 UTC