SEMICeu / DCAT-AP

This is the issue tracker for the maintenance of DCAT-AP
https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe
76 stars 24 forks source link

Adding dcatap:availability to dcat:Resource #190

Closed init-dcat-ap-de closed 2 years ago

init-dcat-ap-de commented 3 years ago

We had the request to add dcatde:plannedAvailablity also to dcat:Dataset (https://github.com/GovDataOfficial/DCAT-AP.de/issues/16)

With the introduction of dcat:Resource, we are thinking about allowing it there as well. Especially for a DataService we see the usecase for stating whethter it is stable, experimental or deprecated.

Is this something you could consider for DCAT-AP as well?

bertvannuffelen commented 3 years ago

@init-dcat-ap-de we like to address your request in the context of an improvement on the management of the controlled vocabulary. W.r.t. the specific concept: can you have a proposed definition?

To improve the management of the controlled vocabulary we propose to use the expertise and setup of the Publications Office. In this way all EU-based controlled vocabularies mentioned in DCAT-AP are at one spot.

The transfer has impact because it involves URI changes. 2 options have been identified.

The concept local identifier is maintained. For instance for the 'experimental' value http://data.europa.eu/r5r/availability/experimental becomes http://publications.europa.eu/resource/authority/distribution-availability/experimental.

Both options have benefits and drawbacks.

Option 1 has the least impact on the current active users. It requires extra attention to future users when they start to use this codelist as it does not follow the default URI strategy of the Publications Office. It also adds additional complexity in the publication flows.

Option 2 creates the highest level of coherency, both on the expectation of URIs being part of the authority tables disclosed by the Publications Office, but also in the publication flows. But they require a change to current users.

In both cases, but in particular for option 2, deprecation must be supported with forwarding to the new concepts.

To ensure that the management of the controlled vocabulary is done in full transparancy with the DCAT-AP community the SEMIC team and Publications Office has established a collaboration so that requests for changes are being discussed in this community.

init-dcat-ap-de commented 3 years ago

We would vote for Option 2. But we are a special case, since we're currently not yet using dcatap:availability, we still use (until mid 2021) dcatde:plannedAvailabilty. So an URI switch wouldn't affect us at all. At the same time we see a big benefit in using the Publications Office. If necessary, maybe we could use the Publications Office und add a redirect or add an owl:sameAs, but my guess would be that there are not many users of the current URIs.

init-dcat-ap-de commented 3 years ago

W.r.t. the specific concept: can you have a proposed definition?

Do you mean definitions for the different properties? We propose:

temporary - Data can disappear at any time, no planning. experimental - Data is available on a trial basis, the expected availability is roughly a year. available - Data is available for a few years, medium term planning. stable - Data will remain available in the long term.

What about the request for moving this attribute to dcat:Resource?

bertvannuffelen commented 3 years ago

@init-dcat-ap-de , apologises I thought there was need for a new value in the controlled vocabulary. My mistake.

The proposal is thus:

make the range of dcatap:availability apply on all catalogue resources (dataset, services) and distributions

motivation:

Availability information is useful for endusers to plan their usage.

bertvannuffelen commented 3 years ago

Side-effects are of this request:

as currently the notion of distribution is included in those sentences.

jimjyang commented 3 years ago

What is the status of publishing availability as a controlled vocabulary by the Publications Office?

http://data.europa.eu/r5r/availability/ which according to the PDF document this availability vocabular should be available under, is not working.

MPaunescu commented 3 years ago

The table is already in preparation at OP. It is planned for publication in September

MPaunescu commented 3 years ago

The table is already in preparation at OP. It is planned for publication in September

But the team at OP is waiting for some clarifications

jimjyang commented 3 years ago

@MPaunescu Any news about publishing availability vocabulary as a machine-readable resource?

bertvannuffelen commented 3 years ago

After consulting with the PO the plan is to publish and release the new NAL in the next release moment which will take place in 8 december 2021. To be ready by then, the 1st of november 2021 this community should have decided on the last remaining issues related the publication.

The proposal is to follow option 2. But after investigation there has been one remark that the PO team would like to sort out with the DCAT-AP community. Namely the title of the new NAL. Originally there was distribution-availability proposed. But if the intend is to use it on other entities beyond distribution, then this qualification felt to restrictive.

Some suggestions that were made as acceptable alternatives (avoiding unintentional clashes with NALs resulting from other communities) :

Is there a preference that the community has?

init-dcat-ap-de commented 2 years ago

Option2 with the title "planned-availability" is our preferred way.

bertvannuffelen commented 2 years ago

During the webinar of 21 oct 2021, a poll has been hold and the option "planned-availability" has been chosen.

This closes the issue, and thus the new controlled vocabulary will be created with this name.

H-a-g-L commented 2 years ago

As of 08/12/2021 the Planned Availability Named Authority List is published by the Publications Office. The SKOS (rdf/xml) can be downloaded and URIs of terms are redirected (see for example, http://publications.europa.eu/resource/authority/planned-availability/AVAILABLE). The equivalence between DCAT-AP URI and the new Table have been defined:

<rdf:Description rdf:about="http://data.europa.eu/r5r/availability/available">
   <skos:exactMatch rdf:resource="http://publications.europa.eu/resource/authority/planned-availability/AVAILABLE"/>

and redirection will be made for the original URIs to the current ones.

init-dcat-ap-de commented 2 years ago

Hello,

the name of the controlled vocabulary was only a sub-question of the issue. The main objective was to archive the following:

make the range of dcatap:availability apply on all catalogue resources (dataset, services) and distributions

I am afraid we lost track of this request, but we still consider it useful and we will allow it in DCAT-AP.de V 2.0.

EDIT: The description of the list already mentions the use case we describe:

The Planned availability authority table is a controlled vocabulary specifying planned availability of DCAT-AP defined resources, namely distribution, dataset and data service.