CMIS

In the spring of 2007, I first heard rumors about IBM and Microsoft working together on a specification that could change the content management landscape. Last week, EMC, IBM and Microsoft (with support from Oracle, SAP, Alfresco and OpenText) announced that they will be collaborating on CMIS, a standard to enable interoperability among content management systems. CMIS stands for Content Management Interoperability Services and promises improved content unification, better content aggregation and mashups, cross-silo federation, and better integration with desktop publishing.

Various people blogged about CMIS, including John Newton (CTO Alfresco), Craig Randall (software architect for EMC), Kas Thomas (analyst for CMSWatch), Brian Huff, Andrew Chapman (Senior Director EMC) and more. If you want to learn more, you can also check https://community.emc.com/community/labs/cmis for video presentations and additional technical materials.

It will probably take years before this becomes an actual standard and before it gets widely adopted, but it is interesting for at least two reasons:

  1. CMIS can use Atom in its REST model. This makes me want to push even harder for adding Atom as one of the default output formats for Drupal nodes (see also refactor node rendering and pluggable renders for JSON, XML, etc). Looks like Drupal was already heading in similar directions, so we might as well keep an eye on CMIS.
  2. The specification solves a real problem and the big boys are backing it. If EMC, IBM and Microsoft put code behind their words, CMIS might become part of Microsoft Office, SharePoint, Documentum, FileNet, etc. I'd love to see Microsoft Office users to be able to save documents into Drupal. Pushing for standards is always a good thing.