- From: Víctor Rodríguez-Doncel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Sep 2017 16:42:10 +0000
- To: public-poe-archives@w3.org
The meaning of example 24 makes me feel uneasy.
`{
"@context": "http://www.w3.org/ns/odrl.jsonld",
"@type": "Agreement",
"uid": "http://example.com/policy:33CC",
"profile": "http://example.com/odrl:profile:09",
"prohibition": [{
"target": "http://example.com/data:77",
"assigner": "http://example.com/person:88",
"assignee": "http://example.com/org:99",
"action": "modify",
"remedy": [{
"action": "delete",
"target": "http://example.com/data:77"
}]
}]
}`
As it means: "you cannot modify data77. But if you happen to modify data77, then delete data77".
Instead of: "you cannot modify data77. But if you happen to modify data77, then delete THE DATA DERIVED FROM data77".
We hint about using other subproperty of odrl:relation, but this case will be very frequent and I would give further examples. In particular, I would propose:
#valid. (example 24 in the IM)
<http://odrlapi.appspot.com/samples/sample072>
dct:source <http://w3c.github.io/poe/model/> ;
a odrl:Agreement ;
odrl:profile <http://example.com/odrl:profile:09> ;
odrl:prohibition [
odrl:target <http://example.com/data:77> ;
XXX:resultingAsset <http://example.com/data:77DERIVED> ;
odrl:assigner <http://example.com/person:88> ;
odrl:assignee <http://example.com/person:99> ;
odrl:action odrl:modify ;
odrl:remedy [
odrl:action "delete" ;
odrl:target <http://example.com/data:77DERIVED>
]
] .
--
GitHub Notification of comment by vroddon
Please view or discuss this issue at https://github.com/w3c/poe/issues/252#issuecomment-328587369 using your GitHub account
Received on Monday, 11 September 2017 16:42:06 UTC