[dxwg] Adding dct:accessRights to DCAT

andrea-perego has just created a new issue for https://github.com/w3c/dxwg:

== Adding dct:accessRights to DCAT ==
> Related use case: [5.17 Data access restrictions](https://www.w3.org/TR/dcat-ucr/#ID17)
> Related requirement: [6.7.1 Dataset access [RDSA]](https://www.w3.org/TR/dcat-ucr/#RDSA)
> Related action: [ACTION-86](https://www.w3.org/2017/dxwg/track/actions/86)

The relevant use case provides the context, and the existing solutions. 

I copy-paste the relevant problem statement for our convenience:

> The types of possible access restrictions of a dataset are one of the key filtering criteria for data consumers. For instance, while searching in a data catalogue, I may not be interested in those data I cannot access (closed data), or in those data requiring I provide personal information (as data that can be accessible by anyone, but only after registration).
> Moreover, it is often the case that different distributions of the same dataset are released with different access restrictions. For instance, a dataset containing sensitive information (as personal data) should not be publicly accessible, although it would be possible to openly release a distribution where these data are aggregated and/or anonymized.
> Finally, whenever data are not publicly available, an explanation of a reason why they are closed should be provided - especially when these data are maintained by public authorities, or are the outcomes of public-funded research activities.

[The existing solutions described in the UC](https://www.w3.org/TR/dcat-ucr/#ID17) address two different aspects of the problem, and by associating property `dct:accessRights` with `dcat:Dataset` and `dcat:Distribution`, respectively. However, both cases highlight that DCAT misses a property to specify access restrictions / conditions - since `dct:license` is about *use* conditions.

About how to express access conditions / restrictions:
- for simple / standardised access restrictions - analogous to the existing solutions mentioned in the use case - URIs can be used
- for access restrictions not fitting in the former ones, ODRL could be an option - so this links to the discussion around #114

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/160 using your GitHub account

Received on Thursday, 8 March 2018 00:22:09 UTC