Closed aidig closed 2 months ago
This comment applies to the class Catalog Record too.
@aidig said:
This comment applies to the class Catalog Record too.
Actually, it applies also to other class descriptions and properties.
E.g.:
An entity that is associated with Catalogues and/or Datasets.
A subject of a Dataset.
A textual resource intended for human consumption that contains information, e.g. a web page about a Dataset.
A rate at which something recurs, e.g. the publication of a Dataset.
A standard or other specification to which a Dataset or Distribution conforms
proposal:
to align the definitions and usagenotes when a new textual (HTML) representation is being build.
motivation:
Although the definitions and usagenotes are not perfectly aligned with those in W3C DCAT, they are not incorrect either. When building a new master specification (HTML) the distinction between definition/usage note and the reference to W3C DCAT can be included. Because this work is a major editorial effort.
Connected with #150
If I understand the proposal correctly, the upcoming (already findable) web version will have updated descriptions for many properties and classes.
Will you provide an overview/comparison? It will take time (and maybe many github issues) to find & discuss changes.
@init-dcat-ap-de, we provided the following change tracking:
W.r.t. the individual properties and class descriptions. In general, only the following editorial activities are applied:
Added where possible are reference to DCAT 3.0 so that readers can compare to DCAT 3.0 requirements/expectations versus the DCAT-AP ones.
The result of this editorial process is a strong alignment with the previous DCAT-AP version.
The usage note of the class dcat:Catalog is currently:
One of the main changes in DCAT 2.0 is the addition of a dcat:Resource class for representing any asset than can be included in the catalog as well as the addition of dcat:DataService to support catalog service end-points providing access to data assets. The fact that dcat:Dataset and dcat:DataService are both resources that can be catalogued is poorly reflected in the above usage note.
Also, note that definition of catalogue in DCAT 2.0:
Might the usage note in this EU Data Portal context possibly benefit from better alignment with the DCAT definition, if indeed such portal could catalogue both dataset and dataservices.