[Odrl-version2] Duties query

[Francis Cave]

Hi Renato

 

Thanks for this. Both your interpretations are clear to me, but this does
seem to imply that a Duty without some kind of Constraint is ambiguous. If
it is always necessary to include a Constraint to make it clear when the
Duty must be performed, does this need to be made explicit in the definition
of a Duty in the Core Model?

 

Regards,

 

Francis

 

 

 

From: odrl-version2-bounces at odrl.net [mailto:odrl-version2-bounces at odrl.net]
On Behalf Of ri at odrl.net
Sent: 24 March 2011 03:51
To: ODRL-Version2
Subject: Re: [Odrl-version2] Duties query

 

 

Francis - here is how I would interpret your two use cases:

 

a) If the duty must be performed every time (no Constraint needed?)

 

You can put the Constraint on the Action, hence you Pay each time to Play
the asset once:

 

    <o:permission>

        <o:asset uid="urn:music:4545"/>

        <o:action name="o:play"/>

        <o:constraint name="o:count" operator="o:lteq" rightOperand="1"/>

        <o:duty>

            <o:asset uid="urn:ubl:AUD0.50"/>

            <o:action name="o:pay"/>

        </o:duty>

        ...

    </o:permission>

 





b) If the duty must be performed once before the permitted action is
performed for the first time (Constraint needed).

 

We can use the new policyUsage value for the event Constraint:

 

    <o:permission>

        <o:asset uid="urn:music:4545"/>

        <o:action name="o:play"/>

        <o:duty>

             <o:asset uid="urn:ubl:AUD0.50"/>

             <o:action name="o:pay"/>

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

        </o:duty>

        ...

    </o:permission>

 

 

Cheers

 

Renato Iannella

ODRL Initiative

http://odrl.net





 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://odrl.net/pipermail/odrl-version2_odrl.net/attachments/20110324/73c0a195/attachment.html>