Content Management Interoperability Services

From Wikipedia, the free encyclopedia

Jump to: navigation, search
CMIS
Type of format Enterprise Content Management
Extended from SOAP


Content Management Interoperability Services (CMIS) [1] 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[2] CMIS, the first Web services technical specification for exchanging content with and between Enterprise Content Management (ECM) systems. The standards proposal has been registered for public comment with OASIS. [3] [4]

More specifically, Content Management Interoperability Services (CMIS) is a technical specification domain model (data and services) for interacting with an document centric ECM repository via Web Services. It provides a content management domain-specific data model, a set of generic services that act on that data model and several protocol bindings for these services, including: SOAP and Representational State Transfer (REST)/(Atom).

Contents

[edit] Specification Progress & TC Members

The specification is current in the early stages of being developed at OASIS. The progress of the specification can be tracked by following the respective public discussion lists[5]. Currently the list of Members that are on the TC includes the following organizations: Adullact, AIIM, Alfresco Software, Booz Allen Hamilton, Day Software, EMC Corporation, Ektron, ESoCE-NET, Exalead, Inc., Fidelity Investments, Flatirons Solutions Corporation, IBM, Magnolia International AG, Microsoft Corporation, Nuxeo, Open Text Corporation, Oracle Corporation, Pearson PLC, Quark, SAP AG, Sun Microsystems, Vamosa, Vignette Corporation

[edit] CMIS Benefits

CMIS specification provides a Web services interface that:

  • Is designed to work over existing repositories enabling customers to build and leverage applications against multiple repositories -- unlocking content they already have
  • Decouples Web services and content from the content management repository, enabling customers to manage content independently
  • Provides common Web services and Web 2.0 interfaces to dramatically simplify application development
  • Is development platform and language agnostic
  • Supports composite application development and mash-up “on the glass” by the business or IT analyst
  • Grows the ISV and developer community


[edit] Historical Notes

The initial work of developing the momentum and use cases that led to the CMIS proposal was conducted by the iECM Initiative [6] sponsored by AIIM. This ongoing project [7] to foster interoperability [8] among ECM systems is supported by the collaborative efforts of governmental, commercial, vendor, and consulting organizations.


[edit] References

  1. ^ Cover Pages - Vendors Publish Content Management Interoperability Services (CMIS) Standard
  2. ^ List of Proposers of CMIS
  3. ^ OASIS - Organization for the Advancement of Structured Information Standards
  4. ^ OASIS - Proposed Charter for OASIS Content Management Interoperability Services (CMIS) TC
  5. ^ CMIS specification mailing list
  6. ^ AIIM - The iECM Initiative
  7. ^ AIIM - Interoperable ECM Standards Committee
  8. ^ AIIM - Interoperable ECM - Fact or Fiction?

[edit] External links

Retrieved from "http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services"
Personal tools
Languages