- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Mar 2018 16:34:35 +0000
- To: public-dxwg-wg@w3.org
Thanks for drafting this proposal, @dr-shorthair . I have a couple of comments: 1. I'm not sure `dcat:Catalog` should be made a subclass of `dctype:Service`. [Its definition in DCAT 1.0](https://www.w3.org/TR/vocab-dcat/#class-catalog) says "A data catalog is a curated collection of metadata about datasets." So, although it _may_ correspond to a catalogue service (as done in GeoDCAT-AP), it can simply be a "static" collection, a mechanism for grouping datasets based on some criteria. I'm aware of examples of this use - e.g., the list of datasets produced by a project/activity. 2. The proposal seems to imply that a `dcat:Catalog` can include records of "data services" only. I agree this is the case for ISO 19115, but I think we should relax such range constraint to allow any type of services to support other use cases. E.g., in DataCite, a service is not necessarily a data service. Moreover, we have examples in Europe of catalogues of online/offline public services (whose metadata follow the [Core Public Service vocabulary](https://ec.europa.eu/isa2/solutions/common-public-service-vocabulary-application-profile-cpsv-ap_en)). 3. It is not clear to me if the proposal supports the possibility for a `dcat:Catalog` to include metadata records of other `dcat:Catalog`'s - I mean, not as sub-catalogues. This is supported in ISO 19115. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/172#issuecomment-376229475 using your GitHub account
Received on Monday, 26 March 2018 16:34:38 UTC