- From: Bert Van Nuffelen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jun 2022 14:13:17 +0000
- To: public-dxwg-wg@w3.org
Maybe I might throw a stone in the water, but is this not because dcat:Catalog is defined as a subclass of dcat:Dataset? Why not simply removing that restriction? I personally find this too restrictive from DCAT and it blocks profile building. (See another issue I raised). Lifting the restriction is not stating that dcat:Catalog cannot be viewed as Dataset, but it is a different notion. E.g. dct:spatial for a catalog in any simple DCAT instance is different from dct:spatial for a dataset in that catalogue. Namely for the dataset is it geographical coverage of the data in that dataset, while for the catalog is its the legal spatial coverage (country/ supranational entity) Those are different spatial notions. E.g. the dataset of all embassies of France has as spatial coverage the world, while the spatial coverage of the France open data catalog will be France (as legal responsible entity). Just consider them as different notions and leave the complex case where a profile wants to enforce that all Catalogs are a subclass of Datasets for them to solve. -- GitHub Notification of comment by bertvannuffelen Please view or discuss this issue at https://github.com/w3c/dxwg/issues/763#issuecomment-1165617472 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 June 2022 14:13:19 UTC