- From: Laurent Le Meur <laurent.lemeur@edrlab.org>
- Date: Tue, 30 Nov 2021 16:18:51 +0100
- To: <public-tdmrep@w3.org>
Dear TDMRep participants, I have taken the freedom to apply a small evolution to the specification, in the ODRL Policy section : we were using either a "permission" or an "obligation" property to express a requirement, depending the case: - Expressing the duty to contact the rightsholder before getting a permission -> obligation - Expressing the duty to compensate financially the rightsholder -> permission- Expressing a constraint on the type of usage -> permission Where in fact a permission in all cases makes sense and further simplifies the ODRL profile. You'll see how the three corresponding examples are similar now: https://w3c.github.io/tdm-reservation-protocol/spec/#example-11 https://w3c.github.io/tdm-reservation-protocol/spec/#example-12 https://w3c.github.io/tdm-reservation-protocol/spec/#example-13 The exact commit is: https://github.com/w3c/tdm-reservation-protocol/commit/4cb03348f69dac5adb9690f0dfff0a0b9f090b98 I hope this does not impact the prototypes that have been developed so far. I'm pretty sure it can simplify client processing. Feedback welcome. If you see a real issue there, we can change back to the previous state before making the spec our "final report". Best regards Laurent Le Meur
Received on Tuesday, 30 November 2021 15:19:07 UTC