- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Mar 2018 22:46:14 +0000
- To: public-dxwg-wg@w3.org
@stijngoedertier , @dr-shorthair , I think that one of the motivations behind the idea of supporting resources different from `dcat:Dataset` is related to a general use case, namely, the use of DCAT as a cross-domain and cross-platform metadata interchange format. This is actually the use case behind the domain-specific extensions of DCAT-AP (GeoDCAT-AP and StatDCAT-AP). So, looking at other metadata schemas, as ISO 19115 and DataCite, datasets are not the only resource "types" - as explained in [UC20](https://www.w3.org/TR/dcat-ucr/#ID20). The same use case also argues that most of these "resource types" can match the definition of `dcat:Dataset` (e.g., software, document), but not resources as "services" and "events". For the former (i.e., those resources matching the definition of `dcat:Dataset`) the soft typing approach would ensure backward compatibility, but for the other ones we need to have some specific classes (e.g., `dctype:Service`, `dctype:Event`). Not supporting resources different from `dcat:Dataset`'s would therefore result in preventing such resources from being shared when ISO 19115 / DataCite / etc. records are transformed into DCAT. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/116#issuecomment-375817833 using your GitHub account
Received on Friday, 23 March 2018 22:46:18 UTC