fix: add binding to tx namespace for credential policy #713

wolf4ood · 2023-08-17T10:07:38Z

WHAT

Add fix for leftOperand when using @context of odrl which get expanded with wrong namespace.

to fix this the functions are registered also in the tx namespace and the final usage will be

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
    "tx" : "https://w3id.org/tractusx/v0.0.1/ns/"
  },
  "@type": "PolicyDefinition",
  "@id": "{{policy-id'}}",
  "policy": {
    "@context": "http://www.w3.org/ns/odrl.jsonld",
    "permission": {
      "action": "use",
      "constraint": {
        "leftOperand": "tx:Dismantler",
        "operator": "eq",
        "rightOperand": "active"
      }
    }
  }
}

WHY

bugfix

FURTHER NOTES

In addition in order to simplify policy expressions 2 context where drafted and added in the cache:

tractusx
edc

This two for the moment are just an exploration, once we decided that they works well we can proceed to upstream the
edc one and fetch the two persistent id in https://w3id.org

Here an example on how it will look like with @context

{
  "@context": [
    "https://w3id.org/edc/v0.0.1",
    "https://w3id.org/tractusx/edc/v0.0.1",
    "http://www.w3.org/ns/odrl.jsonld"
  ],
  "@type": "PolicyDefinitionRequest",
  "@id": "${POLICY_ID}",
  "policy": {
    "@type": "Set",
    "permission": [
      {
        "action": "use",
        "constraint": [
          {
            "leftOperand": "Dismantler",
            "operator": "eq",
            "rightOperand": "active"
          }
        ]
      }
    ]
  }
}