[OASIS Issue Tracker] Updated: (CMIS-325) getAclCapabilities shouldjust be properties on getRepositoryInfo, not a new service

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

     [ http://tools.oasis-open.org/issues/browse/CMIS-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Al Brown updated CMIS-325:
--------------------------

    Fix Version/s: Draft 0.62

> getAclCapabilities should just be properties on getRepositoryInfo, not a new service
> ------------------------------------------------------------------------------------
>
>                 Key: CMIS-325
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-325
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.62
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>             Fix For: Draft 0.62
>
>
> Current ACL proposal as accepted by TC includes a new method, "getACLCapabilities" that is basically just a way to figure out what ACLs the repository supports.
> This isn't consistent with how we do discover other capabilities like Query.

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