- From: Jakub Klímek via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Mar 2021 06:04:43 +0000
- To: public-dxwg-wg@w3.org
Regarding the `hasSeriesMember` and `inSeries`, the way it is defined now it always connects an instance of dataset series to an instance of the dataset. However, the dataset series may have a hierarchical nature, with a different kind of series on each level, e.g. the top-level series is split according to topical facets, the next level according to geographical division, and the lowest level according to temporal division. The bottom line is that I think that the range of `hasSeriesMember` and the domain of `inSeries` should allow the users to use both Datasets and Dataset Series. We can already see this in the Czech catalog: - [Top level dataset series](https://data.gov.cz/zdroj/datové-sady/00006947/833106130/c4ad2c2eb48baea04b67600e907b45aa), grouping datasets coming from a single IT system - [Middle level dataset series](https://data.gov.cz/zdroj/datové-sady/00006947/833106130/a77f25e1dfee2b3ec4be09f02c5fc197) representing a part of the IT system - [Specific dataset at the bottom of the hierarchy](https://data.gov.cz/zdroj/datové-sady/00006947/833106130/a77f25e1dfee2b3ec4be09f02c5fc197) -- GitHub Notification of comment by jakubklimek Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1307#issuecomment-799139402 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 March 2021 06:04:45 UTC