The following is a must read for those in the ECM and RIM space. It is a blog post from Cheryl McKinnon at forrester on the approval of CMIS 1.1
Today OASIS announced official approval of version 1.1 of the CMIS (Content Management Interoperability Services) standard. OASIS is the non-profit, international consortium behind many of the key technology standards in areas related to information management, cloud, privacy and security.
I’ve been keenly watching the development and adoption of CMIS since its early beginnings in 2006 as an idea incubated by the AIIM iECM standards committee, and then moved to the stewardship of OASIS in 2008, once a critical mass of major vendor support had coalesced. Interoperability has always been an important requirement for ECM systems, not only because most large organizations have multiple systems, often from different vendors, but because business content needs to move, flow and be accessible to many other essential line of business applications.
Interoperability is also finding renewed purpose as content management moves to the cloud, and content must be accessible to users, devices and apps regardless of whether it is stored on-premises or in a hosted repository. According to the OASIS press release, “CMIS frees content trapped in traditional ‘content silos’ and facilitates ‘content in the cloud’ and mobile computing”.
Two of the new functions supported in 1.1 are of particular interest to me and my records management/eDiscovery research agenda: support for object “Retention” and support for object “Hold”. CMIS does not itself define records management policies or business rules but is evolving to help support at some of the most basic use cases. An RM application must still define hold and retention rules, but this extension of the interoperability spec now permits these rules to be pushed into the repository layer.
· Retention prevents an object from deletion until the retention is expired or removed
· Hold prevents an object from being modified until the hold is removed
I’ve heard some criticism from ECM experts, questioning whether such records management capabilities really belong in CMIS. I believe that these foundational ones do. This evolution at last brings these fundamental information governance concepts out of the silo of RM systems. What’s happened here is not the creep of RM domain specific functions, but the recognition that these functions are core to ECM.
I would encourage you to read the rest at CMIS 1.1 Approved – OASIS Standard for ECM Interoperability Evolves and Gains Traction for more analysis and links to helpful context.