Rights on Distribution, Access rights on Dataset


Why can a Distribution have a general dct:rights, but Dataset can have only an (arguably more specific) dct:accessRights?


This issue has been reported by Antoine Isaac:



Issue is related to:







Fri, 04/09/2015 - 12:59

Thanks for the pointer to the other. But why not having added accessRights to Distribution too?


In relation to the other issue on licenses (https://joinup.ec.europa.eu/asset/dcat_application_profile/issue/licenc…) I really don't understand why Distributions have licenses and Datasets have access rights, and it's not the other way round. (or not either way). To me access rights tend (but of course not always!) to derive from a pre-existing license, not the other way round. Given that Datasets are more 'fundamental' to Distributions, it is surprising to see that we'd force to attach what is derived to the resource from which things derive.

(and again, I know that this 'direction' is not a general rule, but I'm quite sure it will happen)


Fri, 11/09/2015 - 17:03

I agree with Antoine.

The rationale behind associating dct:license with dcat:Distribution is valid also for dct:accessRights, since you may have different distributions with different access rights - e.g., only aggregated (or low resolution) data are public, but the original data are not (e.g., because of privacy / security issues, or marketing purposes). 

Thu, 24/09/2015 - 09:58





Analysis: The addition of dct:accessRights to Dataset was the result of earlier discussion (https://joinup.ec.europa.eu/discussion/pr2-add-new-property-dataset-indicate-whether-dataset-public-restricted-or-non-public). DCAT lists dct:rights on Distribution.

Proposal: No change.

The content of this field is kept private and will not be shown publicly.