- From: Renato Iannella <renato@knowledgeflux.com>
- Date: Mon, 30 Nov 2015 12:27:19 +0000
- To: Enrico.Daga <Enrico.Daga@open.ac.uk>
- CC: "public-odrl@w3.org" <public-odrl@w3.org>
Received on Monday, 30 November 2015 12:27:56 UTC
On 30 Nov 2015, at 9:27 PM, Enrico.Daga <Enrico.Daga@open.ac.uk<mailto:Enrico.Daga@open.ac.uk>> wrote: thank you both for your feedback, that also helped to clarify that we can use duties to put constraints on specific parties. Now I guess this is possible also for specific assets, for example: :aPermission a odrl:Permission ; odrl:action odrl:display ; odrl:target :thisApiData ; odrl:duty [ odrl:output :thisWebSiteOnly ] . Makes sense? Hi Enrico, a Duty is "requirement that must be fulfilled in return for being entitled to the referring Permission”. A Duty does not constrain the permission action. It tells you what you must do to get the permission. So, in the above example, you would need a constraint on the display action to state where it can be displayed (eg with deliveryChannel=web or virtualLocation=“url”) (odrl:output is only used as the id of the asset created from an action, such as derive, extract, translate etc) Renato Iannella Head of Innovation and Emerging Technologies, KnowledgeFlux Level 7, 100 Edward St, Brisbane 4000 AUSTRALIA +61 4 1313 2206
Received on Monday, 30 November 2015 12:27:56 UTC