- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Mar 2020 23:19:56 +0000
- To: public-dxwg-wg@w3.org
Thanks for this comparison with related specifications, @heidivanparys . I can assure you they have all been taken into account by the DXWG while working on DCAT2. However, the point is that the notion of `dcat:Dataset` was indeed very broad since DCAT was first published, and it may well correspond to the one of "information resource". This is how it has been implemented since 2014, which is one of the reasons why the decision of the DXWG was not to narrow down its scope. However, the general issue is - as @makxdekkers said earlier in this thread - that there is no agreed definition of "dataset" across communities and domains. Since DCAT is meant to be domain-independent in order to support metadata interoperability, the notion of "dataset" should necessarily be broad. Note that this does not mean that you MUST use `dcat:Dataset` for anything. If for your purposes, community, catalogue, etc. it is important (or you just prefer) to use a different class for software, images, etc., there's nothing preventing you doing that. This is also what was done in the work I mentioned earlier about the mappings of ISO 19115 and DataCite to DCAT-AP - see https://github.com/w3c/dxwg/issues/1221#issuecomment-596153171 . In that cases, however, resources were specified ALSO as `dcat:Dataset`s (when possible), in view of the sharing and re-use of metadata records across catalogues and domains. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1221#issuecomment-597366685 using your GitHub account
Received on Tuesday, 10 March 2020 23:19:57 UTC