- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Sep 2017 08:32:13 +0000
- To: public-poe-archives@w3.org
A first review of spreading the content of section 2.6.8 to corresponding sections: I like the basic approach: the definition of the class covers * the impact of values of properties on the evaluation of a class * a final result from evaluating this class A wide wording issue: the IM must make a strict distinction between a class and a property - in particular if their name uses the same characters and the only difference is the casing, e.g. Duty vs duty. And: values of the evaluation of a class are returned into a class referencing them by properties, therefore the lowercase property name should be used: * in 2.6.1: A Permission allows an **action** to be exercised on an Asset if all **constraints** are satisfied and if all **duties** are fulfilled * in 2.6.2: A Prohibition disallows an **action** to be exercised on an Asset if all **constraints** are satisfied. If the Prohibition has been infringed by the **action** being exercised, then all of the **remedies** must be fulfilled. * in 2.6.3: A Duty is the obligation to exercise **an action.** A Duty is fulfilled if all **constraints** are satisfied and if its action has been exercised. * in 2.6.4: A Policy MAY include an obligation to fulfil a Duty. The **obligation is** fulfilled if all **constraints** are satisfied and if its action has been exercised. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/226#issuecomment-328781985 using your GitHub account
Received on Tuesday, 12 September 2017 08:32:06 UTC