[OASIS Issue Tracker] Commented: (CMIS-714) Proposal to addRetention & Legal Hold Policies for next version of spec

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

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

David Choy commented on CMIS-714:
---------------------------------

(1) Secondary Type
So far, all CMIS properties contain passive data values. The basic CRUD methods do not alter an object's behavior; change its external state (only its internal property values); or impose a constraint on an object. Unless we change this basic design, secondary type would not be a good fit for representing policy. Another issue, if we use secondary type to support policy, and if we allow multiple policies of the same type applied to an object (see below), then we need to support hierarchical properties.

Currently one can navigate from an object to its applied policies. If necessary, we can add a method to navigate from a policy to the objects it applied to. If there is a real need to navigate within a query, we can, for example, add functions to the query grammar, e.g. AppliedPolicies(NonPolicyObjectId) and ObjectsAppliedTo(PolicyObjectId).

(2) Retention Policy
- I don't have a strong opinion on whether to keep retention policy. On the one hand, it's good to keep things simple. On the other hand, Martin pointed out a use case in which the app does not want to continue to track the object and wants to pass the responsibility to the repository.
- "startOfRetention" needs an explanation.

(3) Legal Hold Policy
- Besides object deletion, should a legal hold also prohibit set/delete content stream, and check-out/check-in?
- Multiple holds may be applied to an object. But each hold is likely to be applied to a different set of objects. If a policy object represents multiple legal cases, then which set of objects it should be applied to? It seemed to me that each policy should represent a single legal case, and multiple legal-hold policies (for different legal cases) may be applied to the same object.

(4) Destruction Policy
Can a destruction policy applied to an object be removed?
Should "managed retention" be added to the list of deletion criteria?

(5) Managed Retention Policy
How does this work? Is the retention to be terminated by a removal of the applied policy? How are "3YearsAutoDelete" and "KeepMin2YearsAfterRelease" to be handled? That is, what method should the retention manager app use?

> Proposal to add Retention & Legal Hold Policies for next version of spec
> ------------------------------------------------------------------------
>
>                 Key: CMIS-714
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-714
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>            Reporter: Martin Hermes
>
> A new Draft Version 0.2 of the proposal to add Retention & Legal Hold Policies has been uploaded. Main differences to the previous version:
> - A "Managed Retention Policy" has been added to support repository-determined retention periods (Thanks to Jens)
> - Previous Retention Policy with expiration date and optional destruction date has been split into two policies: Retention Policy and Destruction Policy
> Feedback appreciated

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