W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > April 2018

[dxwg] Use case: modeling permissions, obligations, prohibitions

From: Stijn Goedertier via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Apr 2018 20:43:59 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-317387931-1524602638-sysbot+gh@w3.org>
stijngoedertier has just created a new issue for https://github.com/w3c/dxwg:

== Use case: modeling permissions, obligations, prohibitions ==
### Modeling permissions, obligations, prohibitions
Status: Draft / proposed


Creator: Mathias De Schrijver, Lieven Raes, Thomas D’Haenens, Stijn Goedertier - Agentschap Informatie Vlaanderen

Deliverable(s): DCAT1.1
## Tags
dcat rights

## Stakeholders
data publisher, data consumer

## Problem statement
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):
- **royalties**: whether a fee must be paid (perhaps not specifying the amount) for example for a data license or usage of an API.
- **attribution**: whether attribution must be given and which text must be used when attributing.
- **commercial use**: whether commercial use is allowed.
- **derivatives**: whether derived work is allowed.
- **share-alike**: whether derivative works must be shared under the same license conditions.
- **reserved names**: whether there is a prohibition to use the name of the publisher/owner when communicating about derivative works (e.g. as an implied endorsement).
- **restrictions**: restrictions stemming from patents, copyright, trademarks, designs, etc.
- **access restrictions**:  whether there are limitations on public access or not.

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.

## Existing approaches
- The Creative Commons vocabulary ([ccRel](https://creativecommons.org/ns)) provides a vocabulary to describe copyright licenses, it provides properties attributionName, and attributionURL for attribution.
- The Open Data Rights Statement Vocabulary ([ODRS]( http://schema.theodi.org/odrs/)) allows modelling machine-readable rights statements. It provides properties such as attributionURL and attributionText.
- The Open Digital Rights Language ([ODRL](http://w3c.github.io/poe/vocab/)) aims to provide a standard description model and format to express permission, prohibition, and obligation statements to be associated to content in general.
- The Data on the Web Best Practices [DWBP](https://www.w3.org/TR/dwbp/#licenses) includes a best practice on including license information with data on the Web.
- ISO19115:2003 and ISO19115-1:2014 allows representing LegalConstraints in a somewhat structured way. 
- [DCAT-AP](https://www.w3.org/TR/dcat-ucr/#bib-DCAT-AP) proposes the use of a controlled vocabulary for ‘[license type](http://purl.org/adms/licencetype/)’ of license categories that can be convenient to filter resources based on the applicable rights.

## Links
- POE Use Cases and Requirements. URL: https://www.w3.org/TR/poe-ucr/ 

## Requirements
Provide a way for expressing permissions, obligations, prohibitions.
Provide a way to classify a dataset according to applicable (categories of) permissions, obligations, prohibitions.

## Related use cases
[Data access restrictions \[ID17\]](https://www.w3.org/TR/dcat-ucr/#ID17)

## Comments
This is already under discussion in #114, #160

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/224 using your GitHub account
Received on Tuesday, 24 April 2018 20:44:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 March 2019 10:33:22 UTC