[OASIS Issue Tracker] Commented: (CMIS-293) Consistency -ACLControllable - put on all type definitions rather than just documents orfolders

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

    [ http://tools.oasis-open.org/issues/browse/CMIS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653#action_12653 ] 

Alison Macmillan  commented on CMIS-293:
----------------------------------------

By allowing every type to potentially be ACLControllable we need to revisit the proposed Basic Permission Mapping table in 2.6.2.4.3. For example, if a Relationship has an ACL, what permissions are now required for getPermissions? Presumably at least read on the Relationship in addition.

If the main reason for this change is to simplify the XSD, then I think this is outweighed by complicating the Basic Permission Mappings table (which is itself runtime discoverable).

> Consistency - ACLControllable - put on all type definitions rather than just documents or folders
> -------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-293
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-293
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>    Affects Versions: Draft 0.62
>            Reporter: Al Brown
>             Fix For: Draft 0.62
>
>
> put ACLControllable on all type defs not just doc & folder
> - Easier to model in XSD since on base cmisTypeDefinitionType rather than on cmisTypeDocumentDefinitionType and cmisTypeFolderDefinitionType separately.
> - Easy for repositories to set to 'false' for each type if not supported
> - Consistent

-- 
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