Join GitHub today
Use case: modeling permissions, obligations, prohibitions #224
Modeling permissions, obligations, prohibitions
Status: Draft / proposed
Creator: Mathias De Schrijver, Lieven Raes, Thomas D’Haenens, Stijn Goedertier - Agentschap Informatie Vlaanderen
data publisher, data consumer
For a data consumer, it is convenient to be able to search for data on the basis of (categories of) permissions, obligations, or prohibitions associated with it. These could include (but are not limited to):
In addition, a data consumer may wish to automatically meet or enforce obligations such as attribution by extracting relevant information (e.g. attribution text) from the metadata.
Provide a way for expressing permissions, obligations, prohibitions.
Related use cases
added this to In progress
in Use Cases and Requirements for dataset exchange
Apr 26, 2018
This use case is related to (#160) that was addressed in #607 (related to requirement https://w3c.github.io/dxwg/ucr/#RDSA at #59). Indeed, #676 will provide examples related to this use case. But, shouldn't the use case be included in the UCR or mentioned in relation to existing ones (e.g. https://w3c.github.io/dxwg/ucr/#ID17)?
We discussed this issue in today's DCAT meeting. While this belongs to the UCR document and should be considered by the UCR sub-group (if not already addressed), we discussed that it would be good to add examples on how to deal with licenses and rights following the guidance given in the corresponding section.
From a DCAT perspective, this work is done (at least, its complete within the time available for DCAT 2 CR, though furtehr examples would be good). As per https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.04.02, I was going to close it. However, it should be considered for inclusion in the ucr, and may stimulate some work. Its already in the 'Future Priority" milestone, so I have removed the due for closing label and it can be processed in due time.