- From: Renato Iannella <renato@knowledgeflux.com>
- Date: Sun, 29 Nov 2015 13:09:42 +0000
- To: Enrico.Daga <Enrico.Daga@open.ac.uk>
- CC: "public-odrl@w3.org" <public-odrl@w3.org>
- Message-ID: <65ED361E-02A2-408C-ABC6-1580696FD62A@knowledgeflux.com>
On 27 Nov 2015, at 4:25 AM, Enrico.Daga <Enrico.Daga@open.ac.uk<mailto:Enrico.Daga@open.ac.uk>> wrote: I am attempting to model an agreement in ODRL and I need to formally describe that the assigner grants a non-exclusive set of permissions to the assignee. I noticed the “ensureExclusivity” action in the specification, and the possibility to use constraints. However I could not come to a good solution so far. Hi Enrico…welcome… The model assumes (ie is silent) that granting of permissions is non-exclusive, unless otherwise specified with the “ensureExclusivity” duty. That is, if you are assigned the “distribute” permission, you can assume others may have the same unless you have the “ensureExclusivity” duty as well. Since ODRL does not have a concept for non-exclusive (only the opposite), then the easiest option is to define your own: <o:permission> <o:asset uid="http://ex.com/music:45" relation="o:target"/> <o:action name="o:distribute"/> <o:party uid="http://ex.com/sony" function="o:assigner"/> <o:party uid="http://ex.com/billie" function="o:assignee"/> <o:duty> <o:party uid="http://ex.com/sony" function="o:assignee"/> <o:action name="yourNamespace:nonExclusive"/> </o:duty> </o:permission> Our constraint mechanism does not support a “negate” feature (ie to turn ensureExclusivity into doNotEnsureExclusivity). Renato
Received on Sunday, 29 November 2015 13:10:27 UTC