opendata-swiss / dcat_ap_ch

Examples for geocat and DCAT data-catalogs are given here
6 stars 3 forks source link

dct:accrualPeriodicty MUST use the EU vocabulary #52

Open sabinem opened 3 years ago

sabinem commented 3 years ago

Property: dct:accrualPeriodicty Class: dcat:Dataset Conformance Problem: DCAT-AP demands the use of the EU vocabulary as a MUST Details: EU vocabulary: http://publications.europa.eu/resource/authority/frequency Proposal: restrict the range to the usage of the EU vocabulary and change the implementation on opendata.swiss

metaodi commented 3 years ago

Does this lead to incompatbilities, e.g. terms used now that will no longer be available?

andreasamsler commented 3 years ago

Inputs ZH

Juan-Juan-1 commented 3 years ago

@andreasamsler thank you for your input!! Could you please highlight for us which codes or label are duplicates? Maybe this view helps? https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/frequency

Thank you!

metaodi commented 3 years ago

Bi-monthly here most likely refers to "every two months" and not "twice a month", even tough it could be used as both, see this dictionary entry.

andreasamsler commented 3 years ago

.cc @stadlaur

Juan-Juan-1 commented 3 years ago

Does this lead to incompatbilities, e.g. terms used now that will no longer be available?

I think the eu vocabulary simply has more possible attributes than https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/, but we will check it, thx!

l00mi commented 3 years ago

Sorry for being late to this thread. We are using in an ongoing project (https://test.visualize.admin.ch/en/browse not yet officially public) exactly https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/ as it is proposed by https://www.w3.org/TR/vocab-dcat-2/#Property:dataset_frequency.

What is the reasoning behind using a non standard range?

Juan-Juan-1 commented 3 years ago

Dear @l00mi , thank you for your input! We derive DCAT-AP-CH mainly from DCAT-AP (https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/201-0 ). There the use of https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/frequency seems to be declared mandatory.

But we are still evaluating this subject, I'm not sure either :) We'll provide more infos in the next days.

sabinem commented 3 years ago

@l00mi No worries. I am super glad you finally have found your way here and your comments and suggestions are of high value to us.

Regarding this property: the usage of the EU vocabulary: https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/frequency is indeed mandatory on DCAT-AP. Since DCAT-AP CH strives to remain a subprofile of DCAT-AP, I don't think that there is any choice on this.

The EU vocabulary has more values than the DCAT one. That might have been the reason, why DCAT-AP came up with their own vocabulary for this property rather than using vocabulary, specified in DCAT..

l00mi commented 3 years ago

There is always a choice (-: I can't really see any reason why they needed to overwrite the international standard for such a basic field.

I would at least consider allowing both?

sabinem commented 3 years ago

@l00mi Please checkout the answer to your question, that we received on this question from DCAT-AP.

l00mi commented 3 years ago

Based on my answer in the other Issue above, I think it would be possible to allow both lists, as there is a clear mapping from the EU list pointing to the DC list.

And thank you for asking!