http://w3c.github.io/poe/model/#duty:
If either of these fails to be fulfilled, then this will result in the consequence Duty also becoming a new requirement, meaning that the original obligation or duty, as well as the consequence Duty MUST all be fulfilled
O1: original obligation or duty
O2: consequence Duty
O2 is triggered once O1 is considered to be not fulfilled and as a result both O1 and O2 have to be fulfilled.
For example, if an obligation to provide data by a certain date is not fulfilled, the a consequence of a $100 fine is payable as well.
O1: provide data by a certain date (e.g., 2017-12-31)
O2: pay 100$ fine
O2 is triggered once O1 is considered to be not fulfilled (i.e., date >= 2018-01-01), now O1 and O2 both have to be fulfilled.
However, without updating O1's refinement constraints that's no longer possible, because in 2018 the obligation to provide data by 2017-12-31 can't be fulfilled anymore.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3