Set -> Offer -> Agreement

[joshcornejo]

Set definition: An ODRL Policy of subclass Set represents any combination of Rules. The Set Policy subclass is also the default subclass of Policy (if none is specified).

Offer definition: An ODRL Policy of subclass Offer represents Rules that are being offered from assigner Parties. An Offer is typically used to make available Policies to a wider audience, but does not grant any Rules.

Agreement definition: An ODRL Policy of subclass Agreement represents Rules that have been granted from assigner to assignee Parties. An Agreement is typically used to grant the terms of the Rules between the Parties.

Request definition: A Policy that proposes a Rule over an Asset from an assignee.

According to these definitions, the state diagram would be:

@startuml

[*] --> Set 
Set --> Offer
Offer --> Agreement

@enduml

This is probably one of the "simplest" views for the lifecycle described by the verbs used in the definitions above (including a 'mediator'/marketplace and a system 'Policy Manager' as helpers)

@startuml
'https://plantuml.com/sequence-diagram

@startuml
autonumber
participant Assignee as Ae
control PolicyMediator as Mrk
control PolicyManager as Pm
participant Assigner as Ar

alt creation and publishing
  Ar --> Pm : create an Offer
  Ar --> Mrk : make available Policies to a wider audience
end

alt negotiation
  Ae --> Mrk : proposes changes within a Request
  Mrk --> Ar : publishes Request for review by owner of Offer
  Ar --> Pm : decides to create new Offer (see creation) 
end

alt deal
   Ae --> Mrk : signs as Assignee
   Mrk --> Mrk : creates an agreement 
end 

@enduml
```plantuml

@YassirSellami @vroddon 

[vroddon]

I think this is more of a "protocol" issue. We have now the clear understanding that some features are task-dependant. We hope to list these tasks explicitly, where negotiation will be clearly one of them...

[joshcornejo]

@fornaran - here is the issue