Resolution 23

At the last teleconference [1], resolution 23 stated:

"That the extended relations (AND, OR, XOR) will only  apply to Duties and Constraints, not Permissions and Prohibitions"

And Simons comment [2]:

"Besides that, I'm actually wondering whether there's any use case that would motivate/require AND-/OR-/XOR-ing Permissions/Prohibitions?”

A similar question can be asked for the (actual) use case for AND/OR/XOR for Duties and Constraints.

That was the outcome from the TPAC meeting - more concrete use cases for all cases of Extended Relations.

(Historical Note: we removed extended relations for ODRL V2.0 as implementors felt they were difficult to engineer, and there were no examples of its use. It was decided that this level of logic was application-specific, that is, once the “relation” decision has been captured by the “system”, the the concrete ODRL expressions could be created for each case.)


Renato Iannella, Monegraph
Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group

[1] https://www.w3.org/2016/10/17-poe-minutes <https://www.w3.org/2016/10/17-poe-minutes>
[2] https://github.com/w3c/poe/issues/45 <https://github.com/w3c/poe/issues/45>