OASIS-CMIS

OASIS CMIS Content Management vendor-neutral API.

Définition

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, premier large adopter), Microsoft SharePoint, EMC Documentum, IBM FileNet, Oracle WebCenter, Nuxeo Platform, OpenText, Liferay DXP. CMIS Working Group OASIS ferme 2018 (apres CMIS 1.2 expired), pas de version successor. Adoption declining 2020+ : REST APIs custom + cloud storage APIs (S3, Azure Blob, Google Cloud Storage) preferred.

Origine

OASIS CMIS Technical Committee fonde 2008 par EMC + IBM + Microsoft + Alfresco contributions ; CMIS 1.0 OASIS Standard 14 mai 2010 ; CMIS 1.1 2013 ; CMIS 1.2 expiry 2017 ; WG ferme 2018.

Exemple en contexte

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

Termes liés

• OASIS WSDL 2.0 — autre OASIS standard.