Join GitHub today
Review definitions of LeftOperands in the Common Vocab #284
The IM claims in 2.5.1 “The leftOperand instances MUST clearly be defined to indicate the semantics of the Constraint, and MAY declare how the value for comparison has to be retrieved or generated.”
Some current definitions of LeftOperands of Constraints in the Common Vocab do not this requirement, e.g.
And a few are even wrong:
As the Common Vocabulary cannot be changed after a Proposed Recommendation such wording issues should be solved by the first week of December, following the WG's current timeline.
Ok, as Editor of the Vocab I guess I should suggest required changes.
I went over 4.5 Constraint Left Operands of the Vocab Editor's draft of 18 November, the number below follows the Vocab document.
... and I continue with a review of 4.6 Constraint Right Operands
referenced this issue
Nov 21, 2017
As for "Policy Usage Time"...
This is a rightOperand, so will be the value for a leftOperand Constraint - it is not a Constraint itself.
The use case was to support "paying $X before playing the video" when you don't know what the "before" datetime is and don't want to specify a specific datetime.
Suggest that the Label (only) be updated to "Policy Rule Usage" and the definition "Indicates the actual datetime the action of the Rule was exercised"
@riannella I'm aware of the role of a rightOperand - but we should narrow down the definition to exercising the action. Your modified definition sounds ok.
While editing the odrl22.ttl I noticed a detail of some LeftOperand definitions: the use the language "... of the Asset." An uppercase Asset stands for the Asset class which has no implicit relationship with a Rule and a Rule does not have an asset property, only the target property refers to an Asset. To make it unambiguous what is meant by "Asset" I inserted target -->> "... of the target Asset."