- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 May 2017 07:32:40 +0000
- To: public-poe-archives@w3.org
I reckon the effort to make them feel natural, but what is natural for a couple of elements is less so when it's put in the perspective of what is natural for other elements. I'm not asking to remove the constraint expression from POE altogether: just trying to isolate it from a much less debatable core. In fact while the current constraint mechanism is for expression not for enforcement, some sub-community may prefer to develop an expression that also works for enforcement (i.e. constraints with sound formal semantics and implemented checkers). It will be a much easier affair if the current mechanism does not stand in the way of such effort. (but again this can be done by just giving a different status to the constraints from the rest of the POE recommendations, not removing them entirely). On 18/05/17 05:17, Renato Iannella wrote: > 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 ;-) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/w3c/poe/issues/161#issuecomment-302289291>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnprYGcrvEzrh3H80Nd6-qPctNcFtr_ks5r67g2gaJpZM4NNr9a>. > -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/poe/issues/161#issuecomment-302324763 using your GitHub account
Received on Thursday, 18 May 2017 07:32:47 UTC