The ODRL Model is open (and “flexible") to allow any form for specifying rightOperands:
But clearly the use of URIs is the (industry wide) preferred option (open linked data etc…)
Cheers - Renato
> On 13 Jan 2025, at 19:03, Harshvardhan J. Pandit <me@harshp.com> wrote:
>
> Thanks Renato. Interesting piece and I'll look at it in more detail.
> Though I think it would be better to not have strings like this: https://profile.mydata-control.de/ods/#example-3
>
> "rightOperand": [{ "@value": "emergency", "@type": "xsd:string" }],
>
> And to have a controlled vocabulary to avoid issues that arise with string-based expressions and multilingual policies. (E.g. in dpv, this might be something like dpv:EmergencyManagement which would be an IRI and which can be further expanded to justify what is the emergency etc.)
>
> Is this type of modelling part of ODRL best practices already?
>
> Regards, Harsh
