Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wording in Logical Constraints #250

Closed
vroddon opened this issue Sep 6, 2017 · 1 comment
Closed

Wording in Logical Constraints #250

vroddon opened this issue Sep 6, 2017 · 1 comment

Comments

@vroddon
Copy link
Contributor

vroddon commented Sep 6, 2017

FIRST SUGGESTED CHANGE
The spec reads:

The ODRL validation requirements for Logical Constraints includes:

  1. The operand must only be of the sub-properties; or, xone, and, andSequence. Additional sub-properties of operand may be defined by ODRL Profiles exclusively for the use of Logical Constraints.
  2. All of the operand values must be unique Constraint instances.
  3. These Constraint instances must be evaluated and the outcomes used to determine if the logical relationship is satisfied (based on the semantics of the operand sub-property).

I suggest removing the third element from the list (but keeping it out of the list). The reason is that the validation does not need to evaluate anything.

SECOND SUGGESTED CHANGE
The spec reads:

An ODRL validator must support the following sub-properties of operand:

I suggest replacing the word "validator" by "evaluator".

@riannella
Copy link
Contributor

Done

@riannella riannella added this to Under Current Discussion in ODRL Deliverables Review Sep 7, 2017
@riannella riannella moved this from Under Current Discussion to Wide/Horiz Review in ODRL Deliverables Review Sep 7, 2017
@riannella riannella moved this from Wide/Horiz Review to Proposed Solution in ODRL Deliverables Review Sep 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
ODRL Deliverables Review
Proposed Solution
Development

No branches or pull requests

3 participants