[OASIS Issue Tracker] Commented: (CMIS-460) supportincludePolicyIDs wherever includeACL is used

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

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

Al Brown commented on CMIS-460:
-------------------------------

JIRA Cleanup

> support includePolicyIDs wherever includeACL is used
> ----------------------------------------------------
>
>                 Key: CMIS-460
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-460
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model, Schema
>    Affects Versions: Draft 0.62
>            Reporter: Steve Roth
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>             Fix For: Draft 0.63
>
>
> For change logs, and other services, there are places in which includeACL can be specified, but there is no peer for policies.   We should make this security information available, especially when retrieving collections of objects.
> This is especially helpful for the changelog case.   For example, if one has a repository which shares policies across multiple objects, it would be very helpful if the (repo-specific) search crawler can retrieve the associated policies along with the change event object.  This will allow for a more efficient crawler, and avoid the one-call-per-object issue.

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