• Sun. Jun 26th, 2022

shoosh infosite

s….s INFO

Content Management Interoperability Services

Byarticle

Dec 11, 2021

Content Management Interoperability Services (CMIS) is an open standard that allows different content management systems to inter-operate over the Internet.[1] Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories using webprotocols.

“CMIS” redirects here. For the computer networking standard for a service that may be employed by network elements for network management, see Common management information service.
CMIS
Type of format Enterprise content management
Extended from SOAP

. . . Content Management Interoperability Services . . .

CMIS defines a domain model plus bindings that can be used by applications to manipulate content stored in a repository.

CMIS provides a common data model covering typed files and folders with generic properties that can be set or read. There is a set of services for adding and retrieving documents (‘objects’). There may be an access control system, a checkout and version control facility, and the ability to define generic relations. Three protocol bindings are defined, one using WSDL and SOAP, another using AtomPub,[2] and a last browser-friendly one using JSON. The model is based on common architectures of document management systems.

The CMIS specification provides an API that is programming language-agnostic, as REST and SOAP are implemented in many languages.

Many of the original contributors to the specification believed [3] a 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 initial work of developing the momentum and use cases that led to the CMIS proposal was conducted by the iECM Initiative[4] sponsored by AIIM. This ongoing project[5] to foster interoperability[6] among ECM systems is supported by the collaborative efforts of governmental, commercial, vendor, and consulting organizations.

Although initiated by AIIM, CMIS is now administered by OASIS, a web standards consortium. 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. The standard is available for public comment at OASIS.[7]

OASIS approved CMIS as an OASIS Specification on May 1, 2010.[8] CMIS 1.1 has been approved as an OASIS specification on December 12, 2012.[9]

The specification is currently approved as OASIS CMIS v1.1 standard.[9]

There are public discussion lists.[10]

The Technical Committee (TC) includes the following organizations: Adobe Systems Incorporated, AIIM, Alfresco Software, ASG Software Solutions, Booz Allen Hamilton, Content Technologies, dotCMS, Ektron, EMC Corporation, Entropysoft, Exalead, Inc., FatWire, Fidelity Investments, GX Software, HP, IBM, ISIS Papyrus, Microsoft Corporation, Nuxeo, Open Text Corporation, Oracle Corporation, Quark, Pearson PLC, SAP AG, Sun Microsystems, Wells Fargo, WeWebU Software AG and Zia Consulting.

The TC was closed on May 9, 2017 and is no longer active.[11]

. . . Content Management Interoperability Services . . .

This article is issued from web site Wikipedia. The original article may be a bit shortened or modified. Some links may have been modified. The text is licensed under “Creative Commons – Attribution – Sharealike” [1] and some of the text can also be licensed under the terms of the “GNU Free Documentation License” [2]. Additional terms may apply for the media files. By using this site, you agree to our Legal pages . Web links: [1] [2]

. . . Content Management Interoperability Services . . .