- From: fornaran via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Jun 2017 10:58:37 +0000
- To: public-poe-archives@w3.org
Hi riannella - thanks for your answer. The proposed update allows the semantics of permission with duties to express a wider set of use-cases, but I see a problem. When do I obtain a VALID permission (and therefore I can use it without violating a prohibition)? 1. If I obtain a VALID permission to perform an action (i.e. play stream music) if and only if the Duty has been fulfilled (i.e. pay 1 euro). This means that if I do not fulfill the duty I will not get a VALID permission. That is the fulfillment of the duty is a pre-condition for getting a valid permission. 2. If I obtain a VALID permission to perform an action (i.e. play stream music) if and only if the Duty will be fulfilled (i.e. pay 1 euro). This means that I get the permission when the policy is attached to the asset regardless the fact that the duty/obligation is satisfied or not. If in the future I will not fulfill the duty/obligation I may be sanctioned for the duty/obligation violation, but in the meantime (thanks to the valid permission) the permitted action may have been already performed. In my opinion, the semantics of permission can be used to express policies of type 1 (fulfilled duty->valid permission) or policies of type 2 (valid permission->active duty/obligation) but using one construct for covering both types may create a lot of confusion on the semantics of duty-permission. -- GitHub Notification of comment by fornaran Please view or discuss this issue at https://github.com/w3c/poe/issues/191#issuecomment-308081017 using your GitHub account
Received on Tuesday, 13 June 2017 10:58:44 UTC