Английская Википедия:Content Management Interoperability Services
Шаблон:Short description Шаблон:Redirect Шаблон:Infobox file format 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 web protocols.
Concept
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.
Reasoning
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.
History
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]
Criticism
There is some discussion on the name of CMIS. Some blogs and authors say that it should be named "DMIS",[12][13] with D for Document since it is more targeted on ECM.
From the CMIS Specification 1.1, page:[14] "[...] this data model does not cover all the concepts that a full-function ECM repository [...] transient entities (such as programming interface objects), administrative entities (such as user profiles), and extended concepts (such as compound or virtual document, work flow and business process, event and subscription) are not included."
List of implementations
CMIS Servers
A CMIS server stores content, and offers access via the CMIS protocol. Some servers also allow access via other protocols.
| Software | Open source | Notes |
|---|---|---|
| Alfresco 3.3+ | Шаблон:Yes | |
| Apache Chemistry InMemory Server 0.3 | Шаблон:Yes | Holds all data in memory targeted for testing and development (not for production use) |
| Cincom ECM 2.1+ CMIS Connector | Шаблон:Yes | CMIS interface of Cincom ECM, forked from NemakiWare.[15] |
| Day Software CRX 2.1+ | Шаблон:No | |
| dotCMS 2.2 | Шаблон:No | Early commercial editions of dotCMS had CMIS support, however the open source community edition did not. Note that the latest v4.0 edition of dotCMS has removed support for CMIS entirely. |
| Doxis4 (SER Group) | Шаблон:No | Doxis4 CMIS Connector, also supports the optional CMIS capabilities such as the metadata-based storage of documents, multiple linking of documents in different folder hierarchies and the index and full text search as well as combined index and full text search [16] |
| ELO CMIS Connector (ELO Digital Office GmbH) | Шаблон:No | The interface provides the standard functionalities for accessing and handling documents and archive structures for external programs that want to access the DMS/CMS functionalities of ELO. |
| Fabasoft | Шаблон:No | Provides extensions to the core CMIS specification to support "aspects"[17] |
| HP Autonomy Interwoven Worksite 8.5 | Шаблон:No | |
| IBM Content Manager On Demand 9.0+ | Шаблон:No | |
| IBM Connections Files 3.0 | Шаблон:No | Only documents are accessible via CMIS, other content types are inaccessible. |
| IBM LotusLive Files | Шаблон:No | |
| IBM QuickFile[18] | Шаблон:No | |
| IBM Lotus Quickr 8.5 Lists | Шаблон:No | Only data lists are accessible via CMIS, other content types are inaccessible. |
| KGS tia® for CMIS | Шаблон:No | Implementation based on Apache Chemistry, OpenCMIS. Specification Version 1.1 |
| LogicalDOC 6.5.1+[19] | Шаблон:No | |
| Magnolia (CMS) 4.5[20] | Шаблон:Yes | |
| Microsoft SharePoint Server[21][22] | Шаблон:No | CMIS 1.0 is supported out-of-the-box in SharePoint Server 2013. It requires installation of the Administration Toolkit in SharePoint Server 2010. Not available in Foundation version.[23] |
| Nuxeo Platform 5.5+[24] | Шаблон:Yes | |
| O3Spaces 3.2+ | Шаблон:No | |
| OpenCms 8.5[25] | Шаблон:Yes | |
| OpenKM 6.3+[26] | Шаблон:Yes | |
| OpenText | Шаблон:No | Since ECM Suite 2010. Implemented through a CMIS Connector above Enterprise Library Services 10.2.0. |
| OpenText Documentum[27] 7.x | Шаблон:No | |
| OpenWGA 5.2+ | Шаблон:No | |
| Oracle Webcenter Content | Шаблон:No | Content Management REST Service Developer's Guide. |
| PTC Windchill | Шаблон:No | |
| SAP HANA Cloud Document Service | Шаблон:No | SAP HANA Cloud Platform Documentation. |
| Surround SCM 2011.1 | Шаблон:No | |
| Laserfiche 9.1[28] & 10[29] | Шаблон:No | Laserfiche Servers Workflow & Forms |
Capabilities
Each CMIS server declares a set of capabilities. For instance, servers that allow documents to be filed in different places declare the capability "Multifiling". This mechanism allows clients to interact differently with servers that support or don't support a particular operation.
Some server products allow certain capabilities to be disabled or enabled by configuration. the table below lists maximum capabilities.
Server libraries
A CMIS server library allows developers to create CMIS server applications.
| Software | Technology | Open source |
|---|---|---|
| NCMIS | .NET | Шаблон:Yes |
| OpenCMIS Server Framework (part of Apache Chemistry) | Java | Шаблон:Yes |
| VB.CMIS | .NET | Шаблон:Yes |
Client applications
A CMIS client application typically allows users to browse, read and modify content.
| Software | Technology | Open source | Notes |
|---|---|---|---|
| Atlassian Confluence + Crowd 3.5+/2.2.2+ | Java | Шаблон:No | Access, list, display, edit, upload and delete Enterprise Alfresco files from Confluence. |
| Connect-CMIS[33] (Connector in Pegasystems Inc. Pega 7) | Pega 7 | Шаблон:No | Allows for connectivity to any CMIS compliant server from Pega 7 |
| Drupal 7.x and 8.x[34] | PHP | Шаблон:Yes | Can be configured as a CMIS browser |
| Hippo CMS[35] | Java | Шаблон:Yes | Can be configured as a CMIS browser |
| HP Exstream LAL | Java | Шаблон:No | Framework to connect Live documents with CMIS repositories |
| LibreOffice 4.0[36] | C++ | Шаблон:Yes | |
| Liferay 6.1[37] | Java | Шаблон:Yes | Synchronizes Liferay's document repository with CMIS servers |
| TYPO3[38] | PHP | Шаблон:Yes | |
| WordPress[39] | PHP | Шаблон:Yes | Can be configured as a CMIS browser |
Books and publications
- Alfresco CMIS, by Martin Bergljung, March 2014. Packt Publishing Шаблон:ISBN
- OpenCMIS Server Development Guide 2nd Edition, October 2014, at Github [1]
- CMIS and Apache Chemistry in Action, July 2013, by Florian Müller, Jay Brown, and Jeff Potts. Manning Publications, Шаблон:ISBN
- Implementing a Case Management Modeling and Notation (CMMN) System using a Content Management Interoperability Services (CMIS) compliant repository, by Mike A. Marin and Jay A. Brown, April 27, 2015, at arXiv.org [2]
See also
References
External links
- ↑ Шаблон:Cite web
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite book
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite web
- ↑ 9,0 9,1 Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/CMIS-v1.1-cs01.pdf Шаблон:Bare URL PDF
- ↑ Шаблон:Cite web
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite news
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
