Specify requirements for ODRL policies (templates)

[jdsika]

EVES-005 defines the process for a contract negotiation. We need to specify the requirements for the ODRL policy. e.g. minimum content and how to verify it.

[lenasauermann]

There are three main types of an ODRL policy:

odrl:Set:

Represents a collection of policies (Permissions, Duties, Constraints).
It is the most general type and is often used to define a policy that consists of several elements.
--> We could use it as a policy template

odrl:Offer:

A policy that describes an offer to use a specific target.
Used when an entity (e.g. a licensor) provides an offer to potential users.
--> We could use this in the context of negotiation

odrl:Agreement:

Represents an agreement between parties that shows formal agreement to the terms of the policy.
--> We could use this as part of the agreement.

Here a policy template as an example:

odrl-example.json

[jdsika]

Status check: EVES-005 mandates "ODRL-compatible contract templates" and references the ODRL Information Model 2.2, but does not provide concrete policy templates or minimum content requirements.

@lenasauermann's comment above outlines three ODRL policy types (Set, Offer, Agreement) with an example JSON — this is valuable groundwork.

Questions:

1. Should concrete ODRL template requirements become their own EVES (e.g. EVES-010), or should they be added to EVES-005?
2. Is the current EVES-005 reference to ODRL-compatibility sufficient for the first implementation, with detailed templates deferred?