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

Dataset to Catalog association #1288

Closed
riannella opened this issue Jan 15, 2021 · 6 comments
Closed

Dataset to Catalog association #1288

riannella opened this issue Jan 15, 2021 · 6 comments

Comments

@riannella
Copy link

It would also be useful to add a new explicit association from Dataset to Catalog.
(inverse of dcat:dataset)

@dr-shorthair
Copy link
Contributor

Creating purely inverse relationships is often frowned upon, with the argument that the same effect can be gained by including a single triple in the original direction in the dataset, so having the inverse is unnecessary.

@riccardoAlbertoni riccardoAlbertoni added this to To do in DCAT Sprint: Feedback via automation Feb 2, 2021
@andrea-perego andrea-perego added the feedback Issues stemming from external feedback to the WG label Feb 19, 2021
@andrea-perego
Copy link
Contributor

@riannella , is @dr-shorthair 's reply addressing your comment?

If this is not the case, could you please explain the use case behind the proposal of supporting the inverse of dcat:dataset?

@riannella
Copy link
Author

The use case is Aviation datasets.
We are working on a mapping to use DCAT now: https://ext.eurocontrol.int/aixm_confluence/display/ADS/DCAT2+and+ISO+19115+representation

You can see there is a requirement in the Dataset to refer to which Dataset Series (dcat:Catalog) it belongs to.

We currently use the general dct:isPartOf property.

(We prefer not to expose dataset users to owl:inverseOf concepts, when we can make the property more explicit)

@andrea-perego
Copy link
Contributor

Thanks, @riannella . So, basically, this is about how to map to DCAT the ISO 19115 element MD_DataIdentification.citation.CI_Citation.series.

Actually, your approach (dct:isPartOf) is the same used in the dataset series section of the current DCAT3 ED. Do you think a more specific property is needed?

On a different note:

I see that for the mapping between ISO 19115, DCAT, and Schema.org you are referring to:

https://www.w3.org/2015/spatial/wiki/ISO_19115_-_DCAT_-_Schema.org_mapping

Please note that that wiki space has been frozen, and therefore the mappings have not been updated wrt the latest versions of DCAT and Schema.org.

An up-to-date and more fine-grained mapping from ISO 19115 to DCAT is defined in GeoDCAT-AP:

https://semiceu.github.io/GeoDCAT-AP/releases/#rdf-syntax-bindings-for-inspire-and-iso19115-metadata-elements

@riannella
Copy link
Author

Hi @andrea-perego - given what is said in Section 11.1 - does this mean using dcat:Catalog as the "data set series" is not recommended?

@andrea-perego
Copy link
Contributor

@riannella , @dr-shorthair , as the discussion has moved to #1272 , I'm closing this issue.

DCAT Sprint: Dataset Series automation moved this from To do to Done Feb 23, 2021
DCAT Sprint: Feedback automation moved this from To do to Done Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dataset-series dcat:Catalog dcat:Dataset dcat feedback Issues stemming from external feedback to the WG
Development

No branches or pull requests

4 participants