OASIS-CMIS

OASIS CMIS Content Management vendor-neutral API.

Definition

CMIS object model: 4 object types: (1) Document (file content + properties), (2) Folder (container), (3) Relationship (link between objects), (4) Policy (governance, retention). Bindings: AtomPub binding (REST-style HTTP + AtomPub XML), SOAP binding (legacy SOAP 1.1), Browser binding (added in 1.1 lightweight HTTP+JSON). Operations: CRUD (Create-Read-Update-Delete), Query CMIS SQL-like (SELECT * FROM cmis:document WHERE cmis:name LIKE '%report%'), Discovery (browse hierarchy), Versioning (check-in check-out), ACLs management, Multi-filing. Vendor implementations: Alfresco (Java open-source, first large adopter), Microsoft SharePoint, EMC Documentum, IBM FileNet, Oracle WebCenter, Nuxeo Platform, OpenText, Liferay DXP. CMIS OASIS Working Group closed 2018 (after CMIS 1.2 expired), no successor version. Adoption declining 2020+: custom REST APIs + cloud storage APIs (S3, Azure Blob, Google Cloud Storage) preferred.

Origin

OASIS CMIS Technical Committee founded 2008 by EMC + IBM + Microsoft + Alfresco contributions ; CMIS 1.0 OASIS Standard 14 May 2010 ; CMIS 1.1 2013 ; CMIS 1.2 expiry 2017 ; WG closed 2018.

Example in context

Alfresco Content Services exposes CMIS 1.1 Browser Binding REST API: external applications can CRUD Alfresco repository documents via HTTP+JSON, CMIS SQL queries search content/metadata, legacy enterprise applications integration.

Related terms

• OASIS WSDL 2.0 — other OASIS standard.