Best practices or implementations for ODRL enforcement/validation?

Dear ODRL Community,

 

in the scope of dataspaces, ODRL is often used to support data sovereignty
by expressing data access/usage policies.

However, validating/enforcing these policies requires a well-defined
definition of “the current state/context”. Like validate(state, policies) ->
validation result.

 

We are wondering if there are (1) best practices to define such a
state/context and (2) implementations to do so.

 

I found the 2024 “ODRE” paper by Cimmino et al. [1] and an accompanying
GitHub repository [2] with Python and Java implementation. Only supporting
“dateTime” by now, but appears to be a promising base for extensions.

I also found a GitHub repository “SHARCS ODRL enforcement examples” [3],
based on some use cases by Inès, which I however do not really understand.

 

Any suggestions? Thank you and best wishes,

Johannes

 

 

[1]  <https://doi.org/10.48550/arXiv.2409.17602>
https://doi.org/10.48550/arXiv.2409.17602

[2] https://github.com/ODRE-Framework/

[3] https://github.com/KNowledgeOnWebScale/SHARCS

[4] https://github.com/Ines-Akaichi/SHARCS-Use-Case

 

-- 

Dr. rer. nat. Johannes Theissen-Lipp (he/him)

 

RWTH Aachen University: Information Systems & Databases

Ahornstraße 55, Building E2, 52074 Aachen

 <http://dbis.rwth-aachen.de/> http://dbis.rwth-aachen.de

 

Fraunhofer Institute for Applied Information Technology FIT

Data Science and Artificial Intelligence – Data Management and Engineering

Schloss Birlinghoven 1, 53757 Sankt Augustin

 <https://www.fit.fraunhofer.de/> https://www.fit.fraunhofer.de