Skip to content

Operator clarification #126

@joshcornejo

Description

@joshcornejo

In the case of the logical constraints it is unclear if the characteristics (on the target/function/action) must be present.

In pseudo code:

party1 [ location eq 'EU' ]

refinement list:

const1 [ location eq 'EU' ]
const2 [ systemDevice eq 'Mac' ]

and, andSequence will only return true when all the conditions are satisfied (and to be satisfied, they must be present).

or and xone have the following behaviour to return true:

  • if only 1 condition is true,
  • if only 1 condition is true and the other conditions are not present

In the example above,party1 would be in the set from the refinement.

If not mandatory for the condition to be present, the possible "sets" of objects to be considered for the different operands are different.

2.5.2Logical Constraint Class

An ODRL evaluator MUST support the following sub-properties of operand:

  • or - at least one of the Constraints MUST be satisfied
  • xone - only one, and not more, of the Constraints MUST be satisfied
  • and - all of the Constraints MUST be satisfied
  • andSequence - all of the Constraints - in sequence - MUST be satisfied

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions