Re: [poe] Cardinality of odrl:rightOperand

@riannella I was hoping the odrl:eq example is invalid - but one never knows ;-)

Re suggestion above: I would simply append the lists to the rightOperand definition:

one rightOperand property value of type literal, **or?** IRI [rfc3987], or RightOperand; **or, list of literals, or? list of IRIs [rfc3987], or list of RightOperands (for set-based operators); or,**
(Question: why are no "or"s before the IRIs?)

@vroddon this strategy already exists:

2.5.2 Logical Constraint Class - properties

> A Logical Constraint must have one operand sub-property indicating the logical relationship of the compared existing constraints; its value is a list of the existing Constraint types.

@riannella there is an error: ... its value is a list of the existing Constraint **instances.**

... and operator andSequence:

>  all of the Constraints - in sequence - must be satisfied


-- 
GitHub Notification of comment by nitmws
Please view or discuss this issue at https://github.com/w3c/poe/issues/255#issuecomment-328885402 using your GitHub account

Received on Tuesday, 12 September 2017 15:18:04 UTC