[OASIS Issue Tracker] Created: (CMIS-404) ACLs: AllowableActionsMapping should be able to map >1 permission to an action

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

ACLs: AllowableActions Mapping should be able to map >1 permission to an action
-------------------------------------------------------------------------------

                 Key: CMIS-404
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-404
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: Bug
          Components: Domain Model, Schema
    Affects Versions: Draft 0.62
            Reporter: Ethan Gur-esh
            Assignee: Ethan Gur-esh


The PermissionMapping defined in section 2.8.5.2 (line 641) currently specifies that each AllowableAction is mapped to exactly one permission. 

This works OK in the case where a repository is only supporting the basic CMIS permissions (where there's clearly no interaction between read & delete), but not as well for scenarios where the repository has exposed custom permissions (e.g. compound permissions like "contribute" and "manage" -- which may map to "role definitions" in the underlying repository implementation). In those cases, there's no way to express that to perform action Foo, the user needs one or more of the following permissions (contribute, manage). 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira