Re: [poe] IM: upgrade Short-cut Instances of Classes in Policy Rule Composition to a section

@riannella thanks for your considerations, they provide background.
I'm not sure if the approach "make short-cuts non-normative" will work:
* currently only 1. Introduction and 3. ODRL Profiles of the IM are non-normative - both have no impact on classes and their properties
* the e.g. Rule Class defines in the IM that it may have any sub-property of the relation property, this covers non-normative sub-properties defined in the in the [Common Vocabulary](http://w3c.github.io/poe/vocab/#assetRelationsCommon). This way reading the IM an implementer can infer "using the output asset relationship is ok"
* Currently the definition of the Policy Class in the IM does not say anything about using target, assignee, assigner etc (= the short-cuts) as property. An implementer seeing a policy instance using these properties may get confused, which should be avoided.

**I suggest this solution:**
* In the IM add to the list of [Policy Class](http://w3c.github.io/poe/model/#policy) properties this bullet: "Other properties may occur. They are used to provide Constraints referenced by Compound Constraints  or as non-normative short-cuts of Compact Policies and must not be considered as property of the Policy Class." (Links to Compound Constraint and to Compact Policy may be applied.)
* In the [Compact Policy](http://w3c.github.io/poe/model/#composition-compact) define these rules for "collecting" properties applicable to permissions and prohibitions of this Policy (note: this is using a different approach: check the Permission and Prohibition class for properties and include the short-cuts at the Policy-level):
  * For Permissions: a target or assigner or assigner or action or duty property applying to the Permission is a property of the Permission or a property of the Policy. Any of these properties of  a Policy is the same as a property of the Permission.
  * For Prohibitions: a target or assigner or assigner or action or duty property applying to the Prohibition is a property of the Prohibition or a property of the Policy. Any of these properties of  a Policy is the same as a property of the Prohibition.
* This Compact Policy may be declared as non-normative.
* I see no need to add anything to the[ Compound Constraint](http://w3c.github.io/poe/model/#constraint-compound), it shows already how constraint properties at the policy-level are used.




-- 
GitHub Notification of comment by nitmws
Please view or discuss this issue at https://github.com/w3c/poe/issues/202#issuecomment-311599577 using your GitHub account

Received on Wednesday, 28 June 2017 08:57:55 UTC