[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=24850#action_24850 ] 

David Pitfield commented on CMIS-714:
-------------------------------------

Thank you for preparing the new draft.  Our Records Management folks had a few comments, which I'd like to pass along.

Section 1 Retention-Policy:  The term "retention policy" is potentially confusing since, among the record management community, "retention policy" usually refers to an approved corporate policy that describes the retention and disposition requirements for various categories of artifacts.  In other words, an organization has a single "retention policy", not one for every document as is the case in the proposal's use of the term.  That said, since CMIS already uses the term "policy" in the per-document sense, it's reasonable to use the term "retention policy" to refer to the policy on a specific document.  But, for clarity, it would be helpful for the proposal to explicitly mention that the CMIS definition of "retention policy" is different that what record managers might expect.

Section 4 Managed Retention Policy:  The Managed Retention Policies (in Section 4) are a more compelling feature than the "unmanaged" Retention Policies (in Section 1).  As Section 4 states, applications (or end users using them) usually aren't in a position to understand what a retention policy requires or restricts, and for how long; the interpretation and enforcement of a policy is the responsibility of the content repository working with the records management system.  At most, the application might specify *which* retention policy a document is subject to.  Often, however, applications can't even do this, and rely on the content repository working with the records management system to select a policy (for example, based on the type of document or the author).  So, the inclusion of Managed Retention Policies (Section 4) might allow the "unmanaged" Retention Policies (Section 1) to be backgrounded or removed altogether.


> 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