- From: simon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Jun 2017 05:49:12 +0000
- To: public-poe-archives@w3.org
> Updated the list of Duty requirements to make it clear about the assignee of the Duty
commit: e88abc3
lets see..
> 1.) A Duty must only be associated with a Permission.
that's not in line with what we discussed in https://github.com/w3c/poe/issues/154#issuecomment-301697412 :
> Done: 38b945c
Let Set be free :-)
------------------
> 2.) A Duty may be linked to an Asset via a `target` relation property on which the agreed Action must be performed. This does not restrict the sub-properties of `relation` that are used as properties of the Asset.
+ What's the difference between the term **relation** in _`target` relation property_ and _sub-properties of `relation`_? why are the 2 formatted differently?
+ I don't get the second sentence.. What's the rationale behind it?
------------------
> 3.) The assignee(s) of the Permission are the assignee(s) of the Duty.
4.) A Duty may define different assignee(s) functional roles (than defined in the Permission) that overide the assignee(s) in the Permission for the purposes of the Duty.
+ and what about the assigne**r**(s)?
+ if the ass. of the perm. are the ones of the duty, does that mean a policy like the following one has no assignee at all?:
```turtle
<http://example.com/policy:00>
a odrl:Set;
odrl:assigner ex:Bob ;
odrl:permission [
a odrl:Permission ;
odrl:assignee ex:Alice ;
odrl:target <http://example.com/asset:1> ;
odrl:action odrl:use ;
odrl:duty [
a odrl:Duty ;
odrl:action odrl:play ;
odrl:target <http://example.com/asset:2> ;
]
] .
```
+ who are the assignees of the permissions & duties in following examples:
```turtle
<http://example.com/policy:01>
a odrl:Set;
odrl:assigner ex:Bob ;
odrl:permission [
a odrl:Permission ;
odrl:assignee ex:Alice ;
odrl:target <http://example.com/asset:1> ;
odrl:action odrl:use ;
] ;
odrl:duty [
a odrl:Duty ;
odrl:action odrl:play ;
odrl:target <http://example.com/asset:2> ;
] .
```
```turtle
<http://example.com/policy:02>
a odrl:Set;
odrl:assigner ex:Bob ;
odrl:permission [
a odrl:Permission ;
odrl:target <http://example.com/asset:1> ;
odrl:action odrl:use ;
] ;
odrl:duty [
a odrl:Duty ;
odrl:assignee ex:Alice ;
odrl:action odrl:play ;
odrl:target <http://example.com/asset:2> ;
] .
```
------------------
> 5.) The assignee(s) of the Duty must satisfy the Duty.
+ what does that mean for duties like [ensureExclusivity](http://w3c.github.io/poe/vocab/#term-ensureExclusivity)?
```turtle
<http://example.com/policy:03>
a odrl:Set;
odrl:permission [
a odrl:Permission ;
odrl:assignee ex:Alice ;
odrl:assigner ex:Bob ;
odrl:target <http://example.com/asset:1> ;
odrl:action odrl:use ;
odrl:duty [
a odrl:Duty ;
odrl:action odrl:ensureExclusivity ;
odrl:target <http://example.com/asset:1> ;
]
] .
```
------------------
> 6.) A Duty may define other functional roles (for example, to indicate the compensatedParty or a different assigner).
+ but those can't override?
------------------
> 7.) The assignee must have the Permission to perform the Duty Action.
+ what about assigner(s)?
+ _"must have Permission to perform"_ != _"must not be prohibited to perform"_
--
GitHub Notification of comment by simonstey
Please view or discuss this issue at https://github.com/w3c/poe/issues/162#issuecomment-309344539 using your GitHub account
Received on Monday, 19 June 2017 05:49:19 UTC