- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Feb 2017 08:04:07 +0000
- To: public-poe-archives@w3.org
1) *All* constraints need to be checked at the time of exercising the action. So why are the Constraint Relations any different? 2) We define what happens if there is no result of a constraint in the Perm/Pro/Duty sections: "Constraint: the Permission may refer to one or more Constraints which affect the validity of the Permission - it only becomes effective if all of the referred Constraints are true " 3) We define "satisfied" in the first para of the section: "If the logical expression evaluates to true, the result of the Constraint is satisfied." 4) "C1 odrl:isNeccessaryFor C2": first: why "both MUST be satisfied" The both needs to be satisfied (since its also an "and" relationship)...then it goes on and says that C1 is "done" before C2 is processed. 5) If a result cannot be generated, then a result cannot be generated. If the constraint is "event = end-of-the-world" then it won't be satisfied...ever ;-) This is something we cannot address. 6) Syntax errors are not our problem. -- GitHub Notification of comment by riannella Please view or discuss this issue at https://github.com/w3c/poe/issues/98#issuecomment-276892133 using your GitHub account
Received on Thursday, 2 February 2017 08:04:15 UTC