Note on Duty

[larsgsvensson]

The note on Duty says

While implying different semantics, the Duty entity is similar to Permission in that it is an Action that must be undertaken.

To me that feels incorrect. If I have the permission to do something I am still not obliged to do it (i. e. the performing of a Persmission is optional). In other words: A Duty is a Rule that must be performed by the Assignee. A Permission is a Rule that may be performed by the Assignee.

[riannella]

Updated in this commit e055b79

[simonstey]

To me that feels incorrect. If I have the permission to do something I am still not obliged to do it (i. e. the performing of a Permission is optional). In other words: A Duty is a Rule that must be performed by the Assignee. A Permission is a Rule that may be performed by the Assignee.

I would even argue that the same holds for Duties too:

A Duty class is a specific type of Rule that specifies agreed Actions that are obligatory and MUST be fulfilled. A Duty is only associated with a Permission.

Since Duties can only be associated with Permissions, I only have to fulfill a Duty if I want to be eligible for its respective Permission. (I don't have to pay you 100000€ if I don't want to use your data ;)

[riannella]

Proposal: Update first para of Duty section to read:

A Duty class is a specific type of Rule that specifies agreed Actions that are obligatory and MUST be fulfilled in order to be granted the associated Permission. A Duty MUST only associated with a Permission. The Permission is valid (including the Permission's constraints all being satisfied) if and only if the Duty has been fulfilled. The Duty class inherits all the properties from the Rule class.

[riannella]

Change made

commit 5405479

[larsgsvensson]

Yes, that answers my issue.

Thanks,

Lars