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
"A Constraint MAY have none or one dataType property value for the data type of the rightOperand/Reference. A Constraint MAY have none or one unit property value (of type IRI [rfc3987]) to set the unit used for the value of the rightOperand/Reference." (source https://www.w3.org/TR/odrl-model/#constraint-class) .
Moreover, odrl:rightOperand again from the ODRL model page
"one rightOperand property value of type: literal, or IRI [rfc3987], or RightOperand; or for set-based operators; list of literals, or list of IRIs [rfc3987], or list of RightOperands; "
Expected Behavior_
Problem 1: Given a policy with odrl:datatype and/or odrl:unit properties on the constraint, EDC should parse them and store them in the SQL database.
Problem 2: EDC should handle odrl:rightOperand with typed literals values.
Observed Behavior
Problem 1: EDC ignores odrl:datatype and/or odrl:unit properties when creating the policy, and does not store them in the db
Problem 2: EDC ignores typed literal as odrl:rightOperand, and keeps only the @value , and stores it as a simple string.
Steps to Reproduce
During policy creation, the following input is provided to EDC that contains both odrl:datatype and odrl:unit properties
and a typed literal for the odrl:rightOperand property for the constraint:
The policy was created successfully, but the returned policy from EDC is missing these two properties and only the value of the rightOperand is returned.
Bug Report
Describe the Bug
Following the ODRL model,
Moreover,
odrl:rightOperand
again from the ODRL model pageExpected Behavior_
odrl:datatype
and/orodrl:unit
properties on the constraint, EDC should parse them and store them in the SQL database.odrl:rightOperand
with typed literals values.Observed Behavior
odrl:datatype
and/orodrl:unit
properties when creating the policy, and does not store them in the dbodrl:rightOperand
, and keeps only the @value , and stores it as a simple string.Steps to Reproduce
During policy creation, the following input is provided to EDC that contains both
odrl:datatype
andodrl:unit
propertiesand a typed literal for the
odrl:rightOperand
property for the constraint:The policy was created successfully, but the returned policy from EDC is missing these two properties and only the value of the rightOperand is returned.
Context Information
Used version EDC v0.8.0
The text was updated successfully, but these errors were encountered: