- From: Joshua Cornejo <josh@marketdata.md>
- Date: Wed, 15 Jan 2025 08:19:35 +0000
- To: "public-odrl@w3.org Group" <public-odrl@w3.org>
From the screenshot, last week it was highlighted that IRI's are still only at the "proposed" stage and have limited adoption. https://chatgpt.com/share/67807443-74f0-800a-8e4d-d5f7bac4d4a3 ___________________________________ Joshua Cornejo marketdata <https://www.marketdata.md/> smart authorisation management for the AI-era On 14/01/2025, 02:45, "Renato Iannella" <r@iannel.la> wrote: 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
Received on Wednesday, 15 January 2025 08:19:41 UTC