- From: Renato Iannella <r@iannel.la>
- Date: Sun, 21 Feb 2016 21:57:13 +1000
- To: Antoine Isaac <aisaac@few.vu.nl>
- Cc: public-odrl@w3.org
> On 21 Feb 2016, at 03:33, Antoine Isaac <aisaac@few.vu.nl> wrote: > > ODRL defines "A Duty indicates requirements which must be fulfilled in order to receive the permission.” Technically it says "The Duty entity indicates a requirement that MUST be fulfilled in return for being entitled to the referring Permission entity” The intent is that any party can be the subject of a Duty, but it is always within the context of a Permission (which then implies an target resource) In the “first-order” example you gave: > _:ex1 a odrl:Offer > odrl:permission [ > odrl:target _:myDatasetDistribution ; > odrl:action odrl:access; > odrl:assigner _:serviceProvider; > ] > odrl:duty [ > odrl:assignee _:serviceProvider; > odrl:action xxx:serve; > odrl:constraint [ > # the constraint of serving data with 99% uptime > ] > ] There is no scope for the "99%uptime” - it does not refer to myDatasetDistribution or the action the user wants to perform (access). I hope that makes sense? Renato
Received on Sunday, 21 February 2016 11:57:46 UTC