- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 May 2017 03:17:10 +0000
- To: public-poe-archives@w3.org
We tried to make them feel natural with the left/rightOperand+ operator properties. And operators are important. So "gt" and "lt" mean different times for an "event" rightOperand. I think the key point here is that ODRL is aimed at **expressing** a policy - not enforcing it. So I can imagine that an ODRL policy would drive more detailed and enforceable rules at a specific implementation level. Take "compensate" with constraint "payAmount" of $5.00. That ODRL policy expression would be used to inform a "payment system" to make the payment, or verify the payment was made. That "payment system" interface is not in our scope. The same for "purpose = eduction" - we can express this, but we have now way pf providing any further details. If we took out constraint expressions, then we would not meet one of the fundamental needs of ODRL. We also have a legacy XML world (yes, not all the world is into SemWeb ;-) -- GitHub Notification of comment by riannella Please view or discuss this issue at https://github.com/w3c/poe/issues/161#issuecomment-302289291 using your GitHub account
Received on Thursday, 18 May 2017 03:17:17 UTC