- From: simon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jul 2017 08:51:51 +0000
- To: public-poe-archives@w3.org
@riannella
> The concept of "activated" would need to be supported. That is, upon the "action" being activated, then you must do Duty X.
duties on permission level are exactly that, e.g.:
```turtle
<http://example.com/policy:01>
a odrl:Policy;
odrl:permission [
a odrl:Permission ;
odrl:target <http://example.com/asset:9898> ;
odrl:action odrl:reproduce ;
odrl:assigner ex:Bob ;
odrl:assignee ex:Alice ;
odrl:duty [
a odrl:Duty ;
odrl:action odrl:play ;
odrl:target <http://example.com/asset:1> ;
]
] ;
odrl:permission [
a odrl:Permission ;
odrl:target <http://example.com/asset:9898> ;
odrl:action odrl:print ;
odrl:assigner ex:Bob ;
odrl:assignee ex:Alice ;
] .
```
only if `ex:Alice` wants the permission to `odrl:reproduce` the target asset `<http://example.com/asset:9898>` is she obliged to `odrl:play` the asset `<http://example.com/asset:1>`. If she only wants to `odrl:print` the asset (or simply doesn't care about the asset at all), she isn't obliged to do anything at all.
--
GitHub Notification of comment by simonstey
Please view or discuss this issue at https://github.com/w3c/poe/issues/191#issuecomment-313336249 using your GitHub account
Received on Thursday, 6 July 2017 08:51:57 UTC