Open bertvannuffelen opened 1 year ago
We don't see the need to add adms:status
in other classes.
In JRC it is a recommended property for Datasets used with values from the dataset-status Named Authority List of the Publications Office
@ODP-hil thanks for the pointer, I think INSPIRE has a similar use using the codelist: https://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_ProgressCode. (You have to look for ProgressCode in this file).
The See Also section of adms:status is:
6.4.26 Property: current version, 6.4.25 Property: has version, 6.4.24 Property: previous version, 6.4.7 Property: release date, 6.4.27 Property: replaces, 6.4.28 Property: version, 6.4.29 Property: version notes.
so we should discuss the need in connection with https://github.com/SEMICeu/DCAT-AP/issues/203 This thwarts my former statement a little bit.
Multiple issues with the current planned solution:
1) No NAL für adms:status
in dcat:CatalogueRecord
2) Not in dcat:Dataset
, even though DCAT 3 recommends adms:status
for life-cycle management
See also #203
We will not apply any changes in the new release. The issue 1 will be addressed together with the ADMS skos codelists transfer to the Publications Office.
The further expansion and listing of possible to be used properties we try to avoid, as the DCAT-AP specification is then growing too large.
DCAT 3.0 adopts adms:status as property for dcat:Resource, while in DCAP-AP it has been adopted as property for Catalogue Record and Distribution.
Is there need to adopt adms:status beyond the existing cases?