As you may aware, CMIS (Content Management Interoperability Services) uses web services to provide greater interoperability across multiple Enterprise Content Management (ECM) repositories. Here is a small introduction about CMIS who doesn’t aware of it: CMIS is a standards proposal consisting of a set of Web services for sharing information among disparate content repositories that seeks to ensure interoperability for people and applications using multiple content repositories. Alfresco, Day Software, Dennis Hamilton, EMC, IBM, Microsoft, Open Text, Oracle and SAP have joined forces to propose CMIS, the first Web services technical specification for exchanging content with and between Enterprise Content Management (ECM) systems. Here is the conceptual CMIS architecture
and here is the Service Oriented Content Management architecture from Optaros
When you think about Interoperable Content Management(CMIS), first thing you could have ask: Is (CMIS) the perfect solution? Maybe. Maybe not. But the fact that something has been developed that ECMs and other application developers can work with to provide an integrated view of an organization’s content is a step in the direction we need to go. We all know the days of a single, in-house ECM system are pretty much over. SharePoint has already taken care of that. We need something to give us hope that our content is manageable — regardless of where it’s located. CMIS does that. Kyle McNabb has answered the lehman question on his prespectives and here is the DRAFT specification which will be submitted to OASIS – and AIIM has shown an excellent CMIS Demo (i.e., “Federator”)
[Update]:
Attached: CMIS Federated Search Code from AIIM iECM Demo – You can download it from here https://community.emc.com/docs/DOC-3771
