Re: [poe] Assigner/Assignee at the policy level

@riannella that raises an issue of consistent specifications:

Option 1: all the "shared properties" of 2.7.1 are NOT defined as properties of the Policy and its sub-classes.
OR
Option 2: they are defined. In this case the IM is missing definitions in the Policy Class: 
* action property (0..unbounded) type: Action
* abstract relation property (0..unbounded) type: Asset
* abstract function property (0..unbounded) type: Party
* (Note on the abstract properties: they must be there else it would not be possible to use sub-properties defined by a Profile!)
* and ALL of them SHOULD have an explanation under which conditions these properties may be used, like "This property may be used only for the Compact Policy format as defined in 2.7.1."
* specific sub-properties of relation or function in sub-classes of Policy: they should also have this explanation.

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

Received on Saturday, 2 September 2017 13:32:17 UTC