CMIS 1.1 has been approved as an OASIS specification on December 12, 2012. OASIS approved CMIS as an OASIS Specification on May 1, 2010. The standard is available for public comment at OASIS. Participants in the process include Adobe Systems Incorporated, Alfresco, EMC, eXo, FatWire, HP, IBM, ISIS Papyrus, Liferay, Microsoft, Nuxeo, OpenText, Oracle, Newgen OmniDocs and SAP. This ongoing project to foster interoperability among ECM systems is supported by the collaborative efforts of governmental, commercial, vendor, and consulting organizations.Īlthough initiated by AIIM, CMIS is now administered by OASIS, a web standards consortium.
The initial work of developing the momentum and use cases that led to the CMIS proposal was conducted by the iECM Initiative Many of the original contributors to the specification believedĪ simplified and standardized way to access unstructured content across all vendors would increase the adoption of ECM products, but only if the standard could remain compatible with existing deployed systems, much the way that ODBC Open Database Connectivity did for the relational database market in the 1990s. The CMIS specification provides an API that is programming language-agnostic, as REST and SOAP are implemented in many languages. The model is based on common architectures of document management systems. Three protocol bindings are defined, one using WSDL and SOAP, another using AtomPub, and a last browser-friendly one using JSON. There may be an access control system, a checkout and version control facility, and the ability to define generic relations. There is a set of services for adding and retrieving documents ('objects').
#Webdav client with checkout capability plus#
CMIS defines a domain model plus bindings that can be used by applications to manipulate content stored in a repository.ĬMIS provides a common data model covering typed files and folders with generic properties that can be set or read.
0 kommentar(er)
