The content management world got proposal for a new standard, CMIS, backed by the three giants in this domain. The introduction reminded me something of the Java world, that was supposed to take the content management world by storm. It has progressed to the next version, but it has not become exactly popular.
Coming back to CMIS, it will standardize communication with content repositories, giving you freedom to switch to a different content repository or use a third party application that uses it.
CMIS focuses on the basic content capabilities of an ECM system—the create, read, write, delete, and query functions. When deployed, CMIS ensures interoperability by defining how these core content management capabilities function in a uniform manner over a variety of ECM systems.
In reality, I wonder if the switch will be completely seamless. However, this proposal definitely tries to address the issue of locking into repositories. It might turn out to be beneficial if someone has a mixture of legacy repositories and expects a uniform interface to communicate with them.
It will be really interesting to see implementations on the Web. CMIS already boasts of offering both SOAP and REST compliant interfaces. However, Roy Fielding contests and tears apart the REST talk. I have always felt that any effort of building abstractions over HTTP makes it easy to lose the concept of resources and their identity, and REST compliance. This might turn out to be a key factor for acceptance of CMIS.