ODRL in Solid #55

Activity

1. csarven

   added

   proposal

   on Dec 1, 2019
2. jaxoncreed commented on Dec 9, 2019

   

   jaxoncreed

   on Dec 9, 2019

   Contributor

   More actions

   This looks good. We probably would still need to invent some way to denote things like "all resources including this shape". Perhaps that could be an extension of an asset collection.
3. michielbdejong commented on Dec 9, 2019

   

   michielbdejong

   on Dec 9, 2019

   Contributor

   More actions

   CC @Mitzi-Laszlo
4. simonstey commented on Jan 1, 2020

   

   simonstey

   on Jan 1, 2020

   More actions

   This looks good. We probably would still need to invent some way to denote things like "all resources including this shape". Perhaps that could be an extension of an asset collection.

   something along the lines of this?

   <http://alice.pod/policy:88>
       a odrl:Policy ;
       odrl:permission [ 
           odrl:target [
               a odrl:AssetCollection ;
               odrl:source <http://alice.pod/share/photoAnnotations/> ;
               odrl:refinement [
                   a sh:NodeShape ;
                   sh:pattern "public" ;
                   sh:flags   "i" .
               ]
           ]
           odrl:action acl:Read;
       ] .

   ODRL Constraints would be replaced with SHACL shapes where all focus nodes passing the refinement node shape would serve as target to the permission.

   👀React with 👀2Reacted by Sarven Capadisli and Sébastien Rosset
5. coolharsh55 commented on Sep 12, 2021

   

   coolharsh55

   on Sep 12, 2021

   More actions

   Of relevance is work by @besteves4 @vroddon and mysel - where the ODRL policy is used to express preferences for sharing categories of data for specific purposes. Example:

   :policy-1 a odrl:Policy ;
       odrl:profile oac: ;
       odrl:permission [
           a odrl:Permission ;
           odrl:assigner :anne ;
           odrl:target oac:Contact ;
           odrl:action oac:Read ;
           odrl:constraint [
               odrl:leftOperand oac:Purpose ;
               odrl:operator odrl:isA ;
               odrl:rightOperand 
                   dpv:ResearchAndDevelopment ] ] .
                   
   :anne a oac:DataSubject ;
       cert:key <https://anne.databox.me/profile/card#me> .

   • paper: https://hdl.handle.net/2262/96757
   • profile: https://w3id.org/oac/
   • website with interactive demo of policy authorisation: https://protect.oeg.fi.upm.es/solid-consent/#examples

   🚀React with 🚀2Reacted by Sarven Capadisli and Laurens Debackere
6. timbl commented on Sep 13, 2021

   

   timbl

   on Sep 13, 2021

   Contributor

   More actions

   How does ODRL fit with/compete with gConsent? gConsent has a concept of what purpose the information or access is going to be used for, which I think is important.

   ❤️React with ❤️1Reacted by aha hah
7. coolharsh55 commented on Sep 13, 2021

   

   coolharsh55

   on Sep 13, 2021

   More actions

   GConsent (and others like DPV) can complement ODRL to express legal concepts of Purpose and Processing (e.g. EU/GDPR). ODRL's Action concept tells what is the operation, but not why it needs to happen (as you point out). To have ODRL express the purpose of action, possibilities are:

   1. Combine Processing and Purpose together into an Action. e.g. Collect for Service Provision where Collect is processing operation and Service Provision is the purpose (missing item is data i.e. Collect <data> for .... which is an Asset in ODRL)
   2. Consider Processing to be same/similar as Action and express Purpose as part of a restriction on where that action can be applied. This is the approach taken in my earlier comment
   3. Create a new concept to integrate Purpose in an ODRL rule or profile. Example is of this is in ODRL policy modelling and compliance checking by Vos et al. https://doi.org/10.1007/978-3-030-31095-0_3 ODRL example: https://github.com/instsuite/instsuite.github.io/blob/master/gdpr.ial

   <http://example.com/policy:01> a orcp:Set ;
       odrl:profile <http://example.com/odrl:profile:regulatory-compliance> .
       orcp:request [ 
            odrl:action orcp:Processing ;
            orcp:resource orcp:PersonalData ;
            orcp:controller <http://example.com/CompanyA> ;
            orcp:purpose orcp:KYC ;
            orcp:location orcp:EU ;
            orcp:legalBasis orcp:Consent ; 
            odrl:responsibleParty orcp:Controller
   ] ;

   ❤️React with ❤️1Reacted by aha hah
8. csarven

   added this to <https://csarven.ca/#i> foaf:intereston Sep 23, 2022