- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2017 14:18:06 +0000
- To: public-poe-archives@w3.org
Re the evaluation of the Not-/Active state of Permissions: The 2.6.8 in the IM of 29 August defines this workflow for evaluating Permissions: 1. all existing constraints must be evaluated (defined for all kinds of Rule) 2. this sets a first Not-/Active state (defined for all kinds of Rule) 3. then all existing duties are evaluated (defined for Permission only) 4. this sets a second, final Not-/Active state (defined for Permission only) 5. this final state is transformed directly - without any further evaluation - to the outcome of the Permission: Permission rule is not-/allowed The step 5 is in fact useless, its a kind of renaming things only. Therefore I suggest: 1. all existing constraints must be evaluated 2. this sets the Not-/Active state - the final one as for any other kind of Rule 3. then all existing duties are evaluated 4. this sets the outcome of the Permission: **Not-/Ready-for-exercising** (the name of the outcome may be discussed) This is in fact the same workflow as for Prohibition:Not-/Violated and Duty:Not-/Fulfilled. I hope we can agree on that tomorrow. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/226#issuecomment-326004684 using your GitHub account
Received on Wednesday, 30 August 2017 14:18:02 UTC