Re: ODRL Semantics

“ODRL doesn’t really requires you to _follow_ a specific lifecycle.”

 

I think that’s the issue I am highlighting, there are 3 use situations:

 
There’s no lifecycle (it all ‘ends’ with a single agreement).
The lifecycle is left to the implementer (a standard will eventually – possibly – converge).
As cases are highlighted, there is a guideline to the implementer of what is best practice.
 

I’m more inclined to working with the last one.

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: "Steyskal, Simon" <simon.steyskal@siemens.com>
Date: Friday 10 May 2024 at 07:38
To: Joshua Cornejo <josh@marketdata.md>, Nicoletta Fornara <nicoletta.fornara@usi.ch>, "r@iannel.la" <r@iannel.la>, Víctor Rodríguez Doncel <vrodriguez@fi.upm.es>, Gabriel Huecas <gabriel.huecas@upm.es>, Benedict Whittam Smith <ben@deonticdata.com>, "Beatriz Gonçalves Crisóstomo Esteves (UGent-imec)" <Beatriz.Esteves@UGent.be>, Sridhar Krishnamurthy <ksridhar@amagi.com>, "sabrina.kirrane@wu.ac.at" <sabrina.kirrane@wu.ac.at>
Cc: "public-odrl@w3.org Group" <public-odrl@w3.org>
Subject: RE: ODRL Semantics
Resent-From: <public-odrl@w3.org>
Resent-Date: Fri, 10 May 2024 06:37:47 +0000

 

Hi Joshua!

 

FWIW, the lifecycle you described reminds me of a paper @sabrina.kirrane@wu.ac.at and I wrote many years ago:

 

Steyskal, S., & Kirrane, S. (2015). If you can't enforce it, contract it: Enforceability in Policy-Driven(Linked) Data Markets. 

In Agata Filipowska, Ruben Verborgh, Axel Polleres (Ed.), Proceedings of the Posters and Demos Track of the 11th International Conference on Semantic Systems (pp. 63 - 66). 

CEUR Workshop Proceedings. http://ceur-ws.org/Vol-1481/paper21.pdf 

With:


ODRL Offer Policies contain rules that propose terms of

usage to data consumers. The policy defined in Listing 3

offers ex:consumer1 read access to ex:dataset1 if they agree

to a contract that prohibits them from aggregating the data.

 

Listing 3: Offer a contract for ex:dataset1

ex:offer a odrl:Offer ;

odrl:prohibition [ 

a odrl:Prohibition ;

odrl:assigner ex:provider1 ;

odrl:assignee ex:consumer1 ;

odrl:target ex:dataset1 ;

odrl:action odrl:aggregate 

] .

 

ODRL Agreement Policies represent contracts between

data producers and consumers that stipulate all terms of us-

age. The policy defined in Listing 4 states that ex:consumer1

has agreed to a contract that prohibits them from aggregat-

ing the data from ex:dataset1.

 

Listing 4: Construct an agreement for ex:dataset1

ex:agreement a odrl:Agreement ;

odrl:prohibition [ 

a odrl:Prohibition ;

odrl:assigner ex:provider1 ;

odrl:assignee ex:consumer1 ;

odrl:target ex:dataset1 ;

odrl:action odrl:aggregrate 

] ;

odrl:permission [ 

a odrl:Permission ;

odrl:assigner ex:provider1 ;

odrl:assignee ex:consumer1 ;

odrl:target ex:dataset1 ;

odrl:action odrl:read 

] .

 

@ your question

> what is the correct lifecycle (especially in the ‘loop’ which I’ve named ‘RecombineEvent’ back from an Agreement to future Set).

 

ODRL doesn’t really requires you to _follow_ a specific lifecycle. The only thing it does require wrt. the use of odrl:Offer and odrl:Agreement is that the former must contain an odrl:assigner for each of its rules and the latter must have both odrl:assigner as well as odrl:assignee.

 

1.                   An ODRL Policy of subclass Offer:
MUST have one assigner property value (of type Party) to indicate the functional role in the same Rules.
2.                   An ODRL Policy of subclass Agreement:
MUST have one assigner property value (of type Party) to indicate the functional role in the same Rules.
MUST have one assignee property value (of type Party) to indicate the functional role in the same Rules.
 

Hth, simon

 

 

From: Joshua Cornejo <josh@marketdata.md> 
Sent: Tuesday, 7 May 2024 11:12
To: Nicoletta Fornara <nicoletta.fornara@usi.ch>; r@iannel.la; Víctor Rodríguez Doncel <vrodriguez@fi.upm.es>; Gabriel Huecas <gabriel.huecas@upm.es>; Benedict Whittam Smith <ben@deonticdata.com>; Steyskal, Simon (T DAI CON-AT) <simon.steyskal@siemens.com>; Beatriz Gonçalves Crisóstomo Esteves (UGent-imec) <Beatriz.Esteves@UGent.be>; Sridhar Krishnamurthy <ksridhar@amagi.com>
Cc: public-odrl@w3.org Group <public-odrl@w3.org>
Subject: ODRL Semantics

 

Regarding semantics, I want to see if it is possible to address the level above the rules and have the policies within the scope of the conversation.

 

In my understanding, I see a gap in the description of the differences between the subclasses of odrl:Policy, mostly: what is the correct lifecycle (especially in the ‘loop’ which I’ve named ‘RecombineEvent’ back from an Agreement to future Set).

 

I’ve attempted to describe my interpretation as follows:

 
A Set is at its simplest a collection of rules.
An Offer is a list of rules that an odrl:Assigner is preparing or already ‘offering’ to a potential market of odrl:Assignee.
An Agreement is the start of a commercial event between (at least) an odrl:Assigner and odrl:Assignee.
 

Further:
For simplicity, odrl:Agreement renewals are not considered.
Where allowed, an odrl:Assignee can take an agreement and base future supply chain odrl:Offering, becoming an odrl:Assigner on such offerings.
 

 

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain