Align with the work of DPVCG
In this issue, we will track the work being done on aligning ODRL with the outputs of the Data Privacy Vocabulary (DPV) (being developed by the DPVCG) towards the publication of a joint report.
@besteves4 any news here? Should we close this issue?
Definitely not, I am actively working on it :)
We will publish the joint DPV-ODRL mapping under the https://w3id.org/dpv/mappings/odrl# namespace and a guide document on how to use DPV and ODRL under the https://w3id.org/dpv/guides/dpv-odrl namespace.
If anyone is interested in this work or wants to provide feedback, please get in touch with me!
Currently, we have an under-development version of the DPV-ODRL mapping at https://dev.dpvcg.org/mappings/odrl/ and a guide document on how to use this mapping at https://dev.dpvcg.org/guides/dpv-odrl. Feel free to leave comments here or email them to me. Feedback is very welcome!
In the Guide, Example 1:
- can you use odrl:use instead of dpv-odrl:Use
- can you use odrl:purpose instead of dpv-odrl:Purpose
In Example 2:
- this "odrl:assigner [ a dpv:DataController ] ;" does not tell me who the assigner is, only their type
In Example 3:
- can you use odrl:PartyCollection instead of dpv:PartyCollection
- can you use odrl:Party instead of dpv-odrl:Entity
- to be clear on the semantics of this policy, the assigner is every AcademicScientificOrganisation in the ex:entities datasource ?
In Example 4:
- should the Belgium refinement be a constraint?
In Example 5:
- can you use odrl:Asset instead of dpv-odrl:PersonalData
In Example 6:
- should odrl:justifications be odrl:rightOperand
- I think the refinement should be a constraint
Examples 1 - 4:
-
odrl:target pd:BankAccount ;// pd:BankAccount isn't an odrl:Asset "A Rule MAY have none or one relation sub-property values of type Asset".