OASIS Approves Updated CMIS Standard

2 minute read
Barry Levine avatar

Enterprise content management (ECM) systems now have an updated version of the standard for sharing information.

This week, the OASIS international consortium announced that it had approved version 1.1 of Content Management Interoperability Services (CMIS) as an official OASIS standard, which is intended to facilitate a common interface for managing and exchanging content. The specification itself was actually approved in late December.

Formerly SGML Open

Particularly with today’s emphasis on cloud-based platforms and storage, and with the diversity of mobile devices, interoperability of functions and content assumes a greater importance.

With more than 600 organizational and individual members in over 65 countries, OASIS -- or the Organization for the Advancement of Structured Information Standards -- is a non-profit consortium that supports open standards for the global information society. The organization develops standards for security, cloud computing, SOA, Web services, the Smart Grid, electronic publishing, emergency management and other areas. Participants in its standards process include Adobe, Alfresco, EMC, IBM, Microsoft, Nuxeo, Open Text, Oracle, SAP and others.

The organization was initially organized around standards relating to electronic publishing. Founded in 1993, it was first oriented toward developing guidelines to ensure the interoperability of products supporting SGML, or the Standard Generalized Markup Language (SGML). In fact, OASIS’ original name was SGML Open, which was changed to its present moniker in 1998.

Learning Opportunities

New Functions

CMIS, whose version 1.0 was approved in 2010, has enabled connectivity among ECM vendors, and the new version offers a greater embrace of cloud-based ECM. David Choy, chair of the OASIS CMIS Technical Committee, said in a statement that CMIS “has been a game-changer for the market,” in that repository vendors “now offer CMIS services for their products, and application developers use CMIS to access and manage content.”

New functions in 1.1 include support for object retention and hold, the ability to create, modify or delete type and property definitions, and the dynamic addition or removal of named sets of properties from individual CMIS objects.

Additionally, large document uploads can be broken into smaller calls, repositories have the ability to list supported extensions or CMIS standards, and there is a JSON-based protocol binding for browser access.