CMIS is Showing Promise

Standards development is slow and standards implementation is slower. Proposed standards are reviewed and revised to make a first generation standard. Even the participants in the standards process make implementation investment cautiously, if at all. Competing standards vie for prominence and succeeding generations of the standard emerge, but implementation investments remain scarce. In rare cases a version of a particular standard wins confidence across a community of stakeholders, the implementation investments begin to flow, and the investment in the standard begins to pay off. While JSR 170 and JSR 238 have failed to gain momentum, the next generation standard, CMIS shows promise of paying off.

The JSR 170 and JSR 283 standards have been in development since 2002 and 2005 respectively. They are designed to make application functionality portable across content repositories from different vendors, protect investment in content management applications, to foster an increase in commercially available content management applications, and encourage increasingly lower prices for content management repositories. JSR 170 and JSR 283 were unduly influenced by smaller players and did not protect significant investments of major stakeholders. The required support did not emerge for these standards, the investment never materialized, and there’s been no impact on the marketplace.

The experiences from JSR 170 and JSR 283 are reflected in a next generation standard, Content Management Interoperability Services Specification (CMIS). CMIS shows promise because:
- CMIS reflects the interests of the EMC, IBM, and Microsoft customer bases, and shows promise of winning support from across the community of stakeholders.
- CMIS is planned to protect existing vendor and user organization investments. CMIS will not require major product changes or significant data model changes.
- Aggressive standard approval timelines have been set with an objective of initial standard approval by OASIS in 2009.
- Even though the standard is not yet approved, expectations for product implementations are already being set. For example, IBM has identified CMIS as its plan for integrating its Lotus and enterprise content management products.

Archiving and electronic legal discovery are applications of increasing importance to Crown customers who are making investments in these areas to reduce operating costs, increase efficiency, and reduce risk. The CMIS standard is particularly suited for enabling further automation of archiving and legal discovery when the standard is leveraged using an Extract Transform and Load (ETL) utility such as Crown’s Buldoser Center. Crown is already adapting the design of Buldoser Center to take advantage of CMIS when EMC, IBM, and Microsoft implementations become available. (Some early CMIS functionality is already available and Crown is using it.) CMIS, in conjunction with Buldoser Center will make it easier to expand the sources that can be addressed with Buldoser Center and expand the advantage that Crown provides to its customers. CMIS is showing promise, and Crown is ready to leverage it.