- From: simon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Dec 2016 06:29:24 +0000
- To: public-poe-archives@w3.org
> From the implementors survey, it seems no-one has used these Scope
classes, so there should be minimal impact.
Which (imo) is primarily due to ODRL's definition/interpretation of
scopes rather than limited interest/missing use cases for them.
To start things of, I would begin with removing the collection aspect
of "scopes". E.g., I think it would be way more useful to be able to
write something like this:
```Turtle
<http://example.com/policy:5109>
a odrl:Agreement ;
odrl:permission [
a odrl:Permission ;
odrl:action odrl:display ;
odrl:target
<http://example.com/myPlace:billie:photos:football2010> ;
odrl:assigner <http://example.com/myPlace:billie> ;
odrl:assignee ex:football_network
] .
ex:football_network
a odrl:Group ;
odrl:member (ex:Alice ex:Bob) .
<http://example.com/myPlace:billie> a odrl:Individual.
ex:Alice a odrl:Individual.
ex:Bob a odrl:Individual.
```
--
GitHub Notification of comment by simonstey
Please view or discuss this issue at
https://github.com/w3c/poe/issues/59#issuecomment-265943706 using your
GitHub account
Received on Friday, 9 December 2016 06:29:30 UTC