Extend the structure of how the IRS can handle Policies

[jzbmw]

As IRS Consumer,
I want to add policies the same way as EDC handles those ,
so that there is no structural change within the overall architecture of where the Services acts.

LOP

• @jzbmw should we use json-ld as the EDC uses that. This might increase the complexity. Odrl: Prefix would not be used if we do not use json-ld . Alternative, we could use the term odrl:action as a string attribute and ignoring the namespace :odrl

Hints / Details

• child of PCWM Transfer sig-release#212
• policy store concept https://confluence.catena-x.net/display/IRS/%5BTRI-1320%5D%5BTRI-1512%5D+IRS%3A+PolicyStore

Example:

{
	info: xy,
	ttl: xx,
	policy_use_for_use_case:[xys,ggg,ggg,]
	payload  {
		...policy payload... as it is  
	}
}

Example:

{
  "@context": {
      "odrl": http://www.w3.org/ns/odrl/2/
  },
  "@type": "PolicyDefinitionRequestDto",
  "@id": "ap-bpn-and-up-member-trace-idtrace-up",
  "policy": {
      "@type": "Policy",
      "odrl:permission": [
          {
              "odrl:action": "USE",
              "odrl:constraint": {
                  "@type": "LogicalConstraint",
                  "odrl:and": [
                      {
                          "@type": "Constraint",
                          "odrl:leftOperand": "Membership",
                          "odrl:operator": {
                              "@id": "odrl:eq"
                          },
                          "odrl:rightOperand": "active"
                      },
                      {
                          "@type": "Constraint",
                          "odrl:leftOperand": "FrameworkAgreement.traceability",
                          "odrl:operator": {
                              "@id": "odrl:eq"
                          },
                         "odrl:rightOperand": "active"
                      },
                      {
                          "@type": "Constraint",
                          "odrl:leftOperand": "PURPOSE",
                          "odrl:operator": {
                             "@id": "odrl:eq"
                          },
                          "odrl:rightOperand": "ID 3.1 Trace"
                      }
                  ]
              }
          }
      ]
  }
} 

Outcome / Acceptance Criteria

Outcome

• ...

Acceptance Criteria

• EDC policy schema is used for importing policies into Policy store
• it shall be additionally possible to add a policy in the schema described above

Out of Scope

• ...

[jzbmw]

built uppon json-ld

[ds-psosnowski]

@ds-alexander-bulgakov ready for QA

[ds-alexander-bulgakov]

@ds-psosnowski as already discussed could you please adjust the insomnia-collection with new JSON-body for the POST-Request?
Creation and update of policy with new structure is working as expected. IRS-jobs are can be requested and are working as expected with new created policy. Tested with creation of this policy:
{ "validUntil": "2025-02-06T23:59:59.999Z", "payload": { "@context": { "odrl": "http://www.w3.org/ns/odrl/2/" }, "@id": "policy-test-AB_2", "policy": { "odrl:permission": [ { "odrl:action": "USE", "odrl:constraint": { "odrl:and": [ { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "ID 3.0 Trace" }, { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "ID 3.1 Trace" }, { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "R2_Traceability" }, { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "active" }, { "odrl:leftOperand": "Membership", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "active" } ], "odrl:or": [ { "odrl:leftOperand": "Membership", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "active" }, { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "ID 3.0 Trace" }, { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "R2_Traceability" }, { "odrl:leftOperand": "PURPOSE", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "ID 3.1 Trace" }, { "odrl:leftOperand": "FrameworkAgreement.traceability", "odrl:operator": { "@id": "odrl:eq" }, "odrl:rightOperand": "active" } ] } } ] } } }
The createdOn information for created police is not given however. Could you please check this as well?
Thank you!

[ds-alexander-bulgakov]

Insomnia collection has been extended and previously described issue with missing createdOn has been fixed, see e.g.:

Ticket is done and was accepted in PO-review already.