Re: ODRL enforcement implementation

Hi Andrea,

 

Checking and picking one example out of several from your github:

 

       "constraint": [{

           "leftOperand": { "@value": "06:55:00", "@type": "xsd:time" },

           "operator": "otime:between",

           "rightOperand":  { "@value": "23:55:00", "@type": "xsd:time" }

       }]

 

I don’t understand the purpose of this odrl:LeftOperand instance that looks like a value for the definition of a “range constraint” ( I assume that’s the purpose based on the definition of the operator otime:between)?

 

If you are representing a range:

…

       "and": { 

           "@list": [ 

             { "@id": "http://example.com/p:odre/Codre1" },

             { "@id": "http://example.com/p:odre/Codre2" } 

            ]

       }

…

  {

     "@type": "Constraint",

     "uid": "http://example.com/p:odre/Codre1",

           "leftOperand": "dateTime",

           "operator": "odrl:gteq",

           "rightOperand":  { "@value": "06:55:00", "@type": "xsd:time" }

       }

…

  {

     "@type": "Constraint",

     "uid": "http://example.com/p:odre/Codre2",

           "leftOperand": "dateTime",

           "operator": "odrl:lteq",

           "rightOperand":  { "@value": “23:55:00", "@type": "xsd:time" }

       }

 

You could also define a new operator odre:inRange and have your constraint be:

 

       "constraint": [{

           "leftOperand": “dateTime”,

           "operator": "odre:inRange",

           "rightOperand":  { < here define your range object, descendant from odrl:RightOperand > }

       }]

 

This simplifies the policy, but it has the extra step of creating a model that defines how odre:inRange is evaluated by others who want to implement it.

 

The examples also seem to be implementing only odrl:eq, odrl:lt, odrl:gt, odrl:lteq, odrl:gteq & odrl:neq (none of the other 6 operators?)

 

From the document, it seems to be mixing the “context” with policy definition, IMHO – that isn’t necessary and has the potential to introduce significant security risks downstream (authorisation models clear-cut separate definition from state).

 

Regards,

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: Andrea Cimmino <andreajesus.cimmino@upm.es>
Date: Monday 30 September 2024 at 09:41
To: <public-odrl@w3.org>
Subject: ODRL enforcement implementation
Resent-From: <public-odrl@w3.org>
Resent-Date: Mon, 30 Sep 2024 08:41:15 +0000

 

Dear Community,From Universidad Politécnica de Madrid (UPM) we are pleased to present our ODRL enforcement proposal, we would like to share with you the GitHub organization where you will find our python and java implementations for enforcing ODRL policies. These implementations are the proof-of-concept of the recently submitted research to the Computers & Security journal, in the case you might be interested you can have a look at our pre-print of this article.Any feedback or comment or new idea is more than welcome, also any collaboration.
Many thanks in advance.
Best regards,
Andrea C.

Dr. Andrea Cimmino Arriaga

Profesor Permanente Laboral

Departamento de Sistemas Informáticos,
Ontology Engineering Group

Campus Sur de la UPM.

C. de Alan Turing, s/n. 28031, Madrid, Madrid SPAIN

✉ andreajesus.cimmino@upm.es

✆ +34 671 09 06 24

Aviso / Disclaimer 🌳 🌳 Piensa antes de imprimir.