Re: [dxwg] A separate class for DatasetSeries (?) (#1272)

We have modelled the dcat:Catalog as representing a "Dataset Series" and dcat:Dataset for all the datasets in that Series.
The main reason for this is that a dcat:Dataset is defined as "A collection of data..." and dcat:Catalog as "A curated collection of metadata about resources". This closely maps the Series/Dataset relationship.

The proposals in section 11.1 do not seem to fit this model.
1) Publishing a dcat:Dataset as a "series" and the "dataset" as a dcat:Distribution breaks the DCAT model.
2) Using dcat:Datatset as both a "series" and a Dataset breaks the DCAT model.

Since a dcat:Catalog can refer to many other dcat:Catalog entities, then it can be used to model the idea that an over-aching Catalog is made of many Catalog "dataset" series (each of which contains the actual Datasets).

We suggest that Section 11 makes this the preferred solution.

To make it even more specific (and inference-able!), we should add a predicate from dcat:Dataset to dcat:Catalog called dcat:series (that is used when the Catalog acts as a Series metadata)




-- 
GitHub Notification of comment by riannella
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1272#issuecomment-783788126 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 23 February 2021 00:54:29 UTC