W3C home > Mailing lists > Public > public-poe-archives@w3.org > October 2017

Re: [poe] Harmonise how a Duty with consequences should be evaluated

From: Michael Steidl via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Oct 2017 08:43:48 +0000
To: public-poe-archives@w3.org
Message-ID: <issue_comment.created-333778181-1507020214-sysbot+gh@w3.org>
Sorry, I disagree. In #275 @simonstey demonstrates that if the "original Duty" has a temporal constraint this Duty cannot be fulfilled outside the time set by the temporal constraint, by the logic of constraints this is impossible. 

The paragraph about the consequence property should be changed to (and a typo in the second sentence should be fixed):

> If either of these fails to be fulfilled, then this will result in the consequence Duty/ies becoming a new requirement, meaning that all the consequence Duty must be fulfilled. For example, if an obligation to provide data by a certain date is not fulfilled, the**n** a consequence of a $100 fine is payable as well.

We may add as Note:

> Note: if a not-fulfilled Duty having consequences should be fulfilled too when evaluating the consequences it should be expressed as one of the consequences.

The first paragraph in 2.6.6 Consequence property with a Permission/Obligation Duty should be changed to:

> A duty of a Permission, and obligation of a Policy, may include a consequence Duty of not fulfilling that duty or obligation. In this case, all consequence Duties must be fulfilled to set the final state of the Permission/Obligation Duty to fulfilled.

GitHub Notification of comment by nitmws
Please view or discuss this issue at https://github.com/w3c/poe/issues/267#issuecomment-333778181 using your GitHub account
Received on Tuesday, 3 October 2017 08:43:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:47:03 UTC