-
Notifications
You must be signed in to change notification settings - Fork 3
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
Extension dct:availability #187
Comments
@l00mi I think some explantion is needed to distinguish this from |
I am open for any suggestion, there should be two aspects encoded from a data consumer:
|
For reference we start using https://publications.europa.eu/resource/authority/planned-availability for now with |
This already exists in DCAT 2.0 on a distribution level (https://dcat-ap.ch/releases/2.0/dcat-ap-ch.html#distribution-availability), is the proposal to add this on a dataset as well? |
That was the main idea. But this can be reflected, the problem is that I see a different statement in, a distributions availability and the overall dataset. But it can also be reasoned, that the datasets availability is at least the one of the "highest" distribution availability. Also there might be another interaction with https://semiceu.github.io/DCAT-AP/releases/3.0.0/#Distribution.status in the future. |
Property:
dct:availability
Class:
dcat:Dataset
Implementation: implemented as a CV with a list tbd, (e.g. Testing, Draft, Published).
Conformance: For real world applications it is important to quickly understand at which maturity level dataset is published to quickly decide if it can be used in a (data-) project. The goal is to provide a data provider statement regard the maturity of the provided dataset. With the goal to also allow to quickly distribute testing and draft dataset for early feedback and to allow an overall agile data modelling process. This is a non-normative extension to the current DCAT.
The text was updated successfully, but these errors were encountered: