Re: constraining parties and leftOperands

I may have missed some complexity, but would this work:

ex:policy001 a odrl:Agreement ;
    odrl:assigner <http://example.com/party:owner> ;
    odrl:target <http://example.com/asset:1> ;
    odrl:permission [
        odrl:assignee <http://example.com/party:user> ;
        odrl:action odrl:play
    ] ;
    odrl:permission [
        odrl:assignee <http://example.com/party:administrator> ;
        odrl:action odrl:transform
    ] .

Cheers - R



> On 12 Jun 2024, at 18:30, Joshua Cornejo <josh@marketdata.md> wrote:
> 
> Thanks,
>  
> Discarding that operand, the original question remains unanswered.
>  
> How can I model these common restrictions with the current LeftOperand taxonomy:
>  
> ex:User (Renato) can odrl:play an Asset (read) , but ex:Administrator (Victor) can odrl:transform (read/write)?
>  
>  
> <image001.png>
>  
>  
> If odrl:industry wasn’t so narrowly defined, it could fit the purpose.
>  
>  
> Regards,