- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Feb 2017 08:45:42 +0000
- To: public-poe-archives@w3.org
Re POE-UC-19 ...: - C1 Left Operand [Event](http://w3c.github.io/poe/vocab/#term-event): does not fit by its definition "_An identified **event at which** the Action may be exercised._" By that definition the right operand must be an identifier for an event - e.g. for the 2014 FIFA World Cup https://www.wikidata.org/entity/Q79859 - C2 Left Operand [Action Date Time or Period](http://w3c.github.io/poe/vocab/#term-dateTime) is defined as "_The date (and optional time and timezone) to be compared to the time when the Action is exercised or **a period to be compared with the duration of exercising the Action**._" This definition sets as option a period **in which and not after wich** the Action may be exercised - e.g. odrl:lteq and P30M defines: for max 30 minutes. That's why I proposed the new Action Delay Period Left Operand to cover that use case. - re "has to happen first": right, by a formal view that means that only after the event has closed C1 will deliver a "satisfied" result. And that's why I propose to have a relationship: "wait until the constraint of the left operand delivers a satisfied, only after that evaluate the right operand constraint and the point in time of receiving a "satisfied" result is a reference point in time for a temporal Left Operand of the right operand constraint" ... - ... and I share your view that this Constraint Relation operator works only with time driven/related constraints. - (another round of musing about its name: c1 odrl:isSatisfiedBefore c2 ?) Could we take a step in this direction? -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/98#issuecomment-277194430 using your GitHub account
Received on Friday, 3 February 2017 08:46:31 UTC