You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the leftOperand holds a string unwrapped from the object from step 1. Since the returned @context object doesn't include the odrl-context but just the odrl-term/prefix, this expands to a different payload in json-ld, holding a literal (@value) instead a resource (@id).
Context Information
Given the context from call 1, titanium coerces the payload into an object holding @id. It also allows to use
Bug Report
Describe the Bug
The
/v2/policydefinitions
API does not persist resources/objects with@id
in theleftOperand
property.Steps to Reproduce
1. Create policy
POST /v2/policydefinitions
withreturns HTTP 200.
2. Retrieve resource
GET /v2/policydefinitions/left-op-scen-0
Expected Behavior
Though the compacted notation may differ, the content in the
constraint
property should be equal in expanded form.Observed Behavior
Step 2 returns:
Note that the
leftOperand
holds a string unwrapped from the object from step 1. Since the returned@context
object doesn't include the odrl-context but just the odrl-term/prefix, this expands to a different payload in json-ld, holding a literal (@value
) instead a resource (@id
).Context Information
Given the context from call 1, titanium coerces the payload into an object holding
@id
. It also allows to use"leftOperand": "cx-policy:FrameworkAgreement"
,"leftOperand": "https://w3id.org/catenax/policy/FrameworkAgreement"
,"leftOperand": {"@id":"cx-policy:FrameworkAgreement"}
,"leftOperand": {"@id":"https://w3id.org/catenax/policy/FrameworkAgreement"}
,however NOT (yielding an object with
@value
):"odrl:leftOperand": "cx-policy:FrameworkAgreement"
,"odrl:leftOperand": "https://w3id.org/catenax/policy/FrameworkAgreement"
,That makes me guess the issue may lie somewhere in the persistence.
Setup: eclipse-edc 0.6.2 (as part of tractusx-edc 0.7.0).
The text was updated successfully, but these errors were encountered: