ODRL 3.0

Hello,

 

Here is my attempt at summarising the ideas that can be represented visually as modifications in the diagram (the numbers at the far right are the associated GitHub tickets, yellow marked from the previous email).

 

As you can see, it is backwards compatible.

 

 

 

I’ve left templates (marked in red below) for later.

 

Regards,

 

___________________________________

Joshua Cornejo

marketdata

smart authorisation management for the AI-era

 

From: Joshua Cornejo <josh@marketdata.md>
Date: Monday, 24 March 2025 at 13:36
To: "public-odrl@w3.org Group" <public-odrl@w3.org>, "public-md-odrl-profile@w3.org" <public-md-odrl-profile@w3.org>
Subject: ODRL 3.0 - proposal to kickstart work
Resent-From: <public-odrl@w3.org>
Resent-Date: Mon, 24 Mar 2025 13:35:54 +0000

 

Hi,

 

Following up on our last ODRL call, I would like to take the first step to kickstart the conversations around ODRL 3.0.

 

Proposal:

As some might know, I created a brainstorm page at the beginning of December building a tentative roadmap based on features that have surfaced through conversations around use cases with different types of parties.

In no particular order:
Some minor improvements to refinements
Create a standard way for supply chain transit of rules as controlled subsets
Allow for the creation of policy templates where neither the assigner nor assignee (or other parties) is known
Enrich some parts of the semantics by:
Creating a baseline/root taxonomy for Assignee refinements
Allow for a way for the assigner to self-reference without being an actual named party
Create a standard approach for referencing attributes in parties or assets for those looking at a transformation to other languages (e.g. REGO)
Allow for hierarchical logical constraints to enable a relationship between policies and attribute-based encryption
Interoperability
I’ve added a tag (Protocol) to some GitHub tickets I’ve created with requirements/ideas for interoperability (e.g. use of DID’s, lifecycle for upgrades/transfers between providers, etc)
Agree on the format/parameters (normative/non-normative) for an evaluation
Format for transference of state/context across providers
Artificial Intelligence use cases:
Training/usage (e.g. reference CAWG)
Ring-fenced delegation to agents (User -> Agent … -> other Agents)
Post-processing (e.g. RAG / CAG) of assets and the impact on policies.
 

Some other participants have established they will add their requirements, which are more than welcome.

 

Brainstorm page:
https://github.com/w3c/odrl/wiki/Roadmap-brainstorm
 

GitHub for issues:
https://github.com/w3c/odrl/issues
 

Proposed meetings:
1st Monday of every month (8 am GMT/BST) – if any stakeholders from the eastern hemisphere (if no interest, 3 pm GMT/BST)
3rd Monday of every month (3 pm GMT/BST) – western hemisphere
Using the current Zoom link (if possible?)
Engaging also via matrix (https://matrix.to/#/!NEHbyXzTIesEzLoePI:matrix.org?via=matrix.org)
 

Regards,

___________________________________

Joshua Cornejo

marketdata

smart authorisation management for the AI-era