New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reporting Duties #7
Comments
The big difference between the notification duty we modeled earlier and standard reporting duties is their periodicity: while notification only need happen once, reporting must be repeated monthly. We can express that by adding a time interval after which the duty "resets" and needs to be fulfilled again:
You only need to report once within this time interval, so we can set the "count" attribute in the action to one. Our duty now looks so:
|
Often, reporting (like payments) can be done one month in arrears. We can model this by adding a deadline delta that provides a grace period for the duty to be fulfilled before it is set to the violated state. The final duty looks so:
|
For those interested in reading further about the possible states of rules, this paper is very useful: https://people.lu.usi.ch/fornaran/AIComm2019/AIComm32(2019)_Fornara.pdf |
Reporting duties share the same structure as Notification duties, except the action is to report rather than notify. So:
We can usually add some useful detail on what needs reporting. Often it's a list, or count, of devices or applications. We can add that by constraining the Report action by the unit of count:
The text was updated successfully, but these errors were encountered: