Re: Combined Permissions and Restrictions in ODRL 2.0: Is this example correct?

On 23 Feb 2012, at 12:12, Stuart wrote:
>         <o:duty>
>             <!-- The duty action is to make a payment -->
>             <o:action name="o:pay"/>
>             <!-- The duty creates an asset (i.e. it is an output): the printing fee -->
>             <o:asset uid="ns:printingFee" relation="output"/>
> 
The relation should be "target"

>             <!-- The duty is constrained: the date/time of the duty must be before the date/time of action that is being permitted / restricted -->
>             <o:constraint name="o:dateTime" operator="o:lt" rightOperand="a:actionDateTime"/>
> 
The ODRL Common Vocabulary defines a special Event value of "policyUsage" to cover this scenario.
This is more semantically correct as it says that the action can only occur during the time period whilst the policy is being exercised.
So if you had:

      <o:constraint name="o:event" operator="o:lt" rightOperand="o:policyUsage"/>

It means the pay duty must occur before the policy is exercises (e.g. printing)

>             <!-- The duty is constrained: the duty must be performed exactly once -->
>             <o:constraint name="o:count" operator="o:eq" rightOperand="1"/>
> 
With the above, you probably don't need this…(but you could if they are likely to pay multiple times ;-)


Cheers...
Renato Iannella
Semantic Identity
http://semanticidentity.com
Mobile: +61 4 1313 2206