- From: fornaran via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jul 2017 07:48:45 +0000
- To: public-poe-archives@w3.org
A Policy that can contain just a Duty is the first step. For being able to model my use cases the notion of Duty/Obligation should enriched. In particular what I miss is the notion of state of the obligation that follows a specific lyfecycle. Like for the notion of permission there is the idea of having a "valid permission" when the duty is satisfied, and I suppose a "conditioned permission" when the duty is not yet satisfied. An Obligation may be conditioned, activated, satisfied or violated. Regards -- GitHub Notification of comment by fornaran Please view or discuss this issue at https://github.com/w3c/poe/issues/191#issuecomment-313028623 using your GitHub account
Received on Wednesday, 5 July 2017 07:48:51 UTC