leftOperand in the catalog is handled as value and not as id

[matgnt]

Test input for the policy (tractusx-edc 0.7.1)

{
    "@type": "LogicalConstraint",
    "odrl:and": [
        {
            "@type": "Constraint",
            "odrl:leftOperand": "UsagePurpose",
            "odrl:operator": {
                "@id": "odrl:eq"
            },
            "odrl:rightOperand": "cx.core.industrycore:1"
        },
        {
            "@type": "Constraint",
            "odrl:leftOperand": "https://w3id.org/catenax/policy/UsagePurpose",
            "odrl:operator": {
                "@id": "odrl:eq"
            },
            "odrl:rightOperand": "cx.core.industrycore:1"
        },
        {
            "@type": "Constraint",
            "odrl:leftOperand": "cx-policy:UsagePurpose",
            "odrl:operator": {
                "@id": "odrl:eq"
            },
            "odrl:rightOperand": "cx.core.industrycore:1"
        },
        {
            "@type": "Constraint",
            "odrl:leftOperand": {
                "@id": "https://w3id.org/catenax/policy/UsagePurpose"
            },
            "odrl:operator": {
                "@id": "odrl:eq"
            },
            "odrl:rightOperand": "cx.core.industrycore:1"
        },

    ]
}

Result in the catalog is:

   "odrl:hasPolicy": {
    "@id": "ODIyNjgyZGItOWE1Ni00ZTM4LWIzZjAtODJiYTMyYTYwMmZm:YzU5ZmU1YzMtZTRiYi00NmFiLTkxZjItOTAwYWQ4MDY2OTAx:NDFhM2VhYjUtYmI2NC00OWM5LWJlMDgtZTBhM2UxMjMyZTQw",
    "@type": "odrl:Offer",
    "odrl:permission": {
     "odrl:action": {
      "odrl:type": "use"
     },
     "odrl:constraint": {
      "odrl:and": [
       {
        "odrl:leftOperand": "UsagePurpose",
        "odrl:operator": {
         "@id": "odrl:eq"
        },
        "odrl:rightOperand": "cx.core.industrycore:1"
       },
       {
        "odrl:leftOperand": "https://w3id.org/catenax/policy/UsagePurpose",
        "odrl:operator": {
         "@id": "odrl:eq"
        },
        "odrl:rightOperand": "cx.core.industrycore:1"
       },
       {
        "odrl:leftOperand": "cx-policy:UsagePurpose",
        "odrl:operator": {
         "@id": "odrl:eq"
        },
        "odrl:rightOperand": "cx.core.industrycore:1"
       },
       {
        "odrl:leftOperand": "https://w3id.org/catenax/policy/UsagePurpose",
        "odrl:operator": {
         "@id": "odrl:eq"
        },
        "odrl:rightOperand": "cx.core.industrycore:1"
       }
      ]
     }
    },

with the catalog's context:

 "@context": {
  "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
  "edc": "https://w3id.org/edc/v0.0.1/ns/",
  "tx": "https://w3id.org/tractusx/v0.0.1/ns/",
  "tx-auth": "https://w3id.org/tractusx/auth/",
  "cx-policy": "https://w3id.org/catenax/policy/",
  "dcat": "http://www.w3.org/ns/dcat#",
  "dct": "http://purl.org/dc/terms/",
  "odrl": "http://www.w3.org/ns/odrl/2/",
  "dspace": "https://w3id.org/dspace/v0.8/"
 }

this doesn't produce the expected structure in the expanded version.
The leftOperand is always treated as value instead as an id.

Even the last example, explicitly using @id doesn't result and the expected @id in the catalog output.

One option as a quick fix would be to add the ODRL remote context to the catalog @context, that defines this for the leftOperand.

"http://www.w3.org/ns/odrl.jsonld"

Any thoughts on this?

---

Matthias Binzer

[wolf4ood]

Hi @matgnt

thanks for the issue, this has already been notified in upstream EDC here, and fixed.

It will be incorporated in the next EDC version and Tractusx EDC 0.7.2

Thanks

[matgnt]

Thanks @wolf4ood , good to hear! Where do we track the required changes for the next tx-edc release?

[wolf4ood]

All the relevant changes will be in the migration document here and in changelogs EDC and TX-EDC

[matgnt]

ah, maybe this was a misunderstanding. The question was how to track issues that need to go into the next tx-edc release.
Not documentation / migration guide for the user.

[jimmarino]

@matgnt We have been through this before. It's fine to open an issue against this repo, but if it turns out to be an upstream issue (as this one is), please do not continue to use the issue in question for "tracking" or other purposes. As we explained, this burdens committers and duplicates information where it may not be found upstream.

Use the sig-release repository (there's even an EDC label) or another mechanism for your tracking, but please do not continue creating duplicate issues in this repository for those purposes.

Given the above, I'm closing this issue.