Re: [poe] Modelling duty/obligation

We will be treating "constraint checking" as a "black-box" for ODRL evaluators (as we are not scoped to address enforcement, only expression).

So when an constraint is evaluated by the external system, it will simply return true or false.
If its true, then the Permission is valid, if false, then not-valid.

So in case 2) above, the implementations may have the assignee's credit card details (which we don't know about)  and then is happy to return "true" (and charge them later at the end of the month).

The only real difference between 1) and 2) is temporal.
Ideally, that would be part of the compensate duty (that you can pay at the end of the month), and still get access to the Permission now.

GitHub Notification of comment by riannella
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 14 June 2017 05:46:12 UTC