-
How to model and express rights for Datasets?
- Open Data Rights Statement Vocabulary (ODRS) (http://schema.theodi.org/odrs/)
- Open Digital Rights Language (ODRL) (https://www.w3.org/TR/odrl/)
In the DCAT model, rights and licences are assigned to catalogues and to distributions, not to datasets.
In actual implementations, rights and licences may be associated with the dataset, applying to all distributions of the dataset.
Additional explanation of the approach may be helpful.
Component
DocumentationCategory
improvement
Login or create an account to comment.
Comments
DCAT-AP v1.1 includes a property to express access rights for Datasets:
Property access rights (dct:accessRights), optional, non-repeatable property for Dataset, that refers to information that indicates whether the Dataset is open data, has access restrictions or is not public. A controlled vocabulary with three members (:public, :restricted, :non-public) will be created and maintained by the Publications Office of the EU.
Maybe the Publications Office can provide information on the availability of the three-member vocabulary.
Other than that, do existing implementations already maintain this type of information? Are other implementations considering providing similar information? Are there any other rights-related approaches that have been implemented?
Makx,
I could imagine that the licenses may be different depending on the kind of distribution.
An example is that for downloaded data a different license may be provided than e.g. for an online view service of the data...
Uwe, this issue is about the dct:accessRights associated with the Dataset, a property that was added in the last revision.
DCAT and DCAT-AP associate licences with Distributions, exactly for the reason you mention.