Call to Vote: Ballot for OASIS Standard - Content Management Interoperability Services (CMIS) V1.1

The OASIS Content Management Interoperability Services (CMIS) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS membership to a membership vote for OASIS Standard:

Content Management Interoperability Services (CMIS) Version 1.1
Candidate OASIS Standard 01
01 February 2013

This is a call to the primary or alternate representatives of OASIS Organizational Members to vote. The Technical Committee has satisfied all requirements of the OASIS TC Process and the Candidate OASIS Standard is now submitted to the voting representatives of OASIS organizational members.

-- Voting Details --

The ballot opens on 09 May 2013 at 00:00 GMT and closes on 23 May 2013 at 23:59 GMT. You can access the ballot to cast your vote at:

Internal OASIS link:

Publicly visible link:

The minimum number of affirmative votes required to approve this ballot is 49 (15% of 323 member organizations).

Each OASIS organizational member has one vote. OASIS members should ensure that their organization's voting representative votes according to the organization's wishes. If you do not know the name of your organization's voting representative is, go to the My Account page at

then click the link for your Company (at the top of the page) and review the list of users for the name designated as "Primary".

-- Information about the Candidate OASIS Standard and the OASIS Content Management Interoperability Services (CMIS) TC --

CMIS specifies a protocol-layer interoperability interface for content management. It addresses the widespread “content silo” problem whereby enterprise contents are trapped in disparate repositories. CMIS also facilitates the emerging “content in the cloud” paradigm and mobile computing. The CMIS v1.0 OASIS Standard contains a domain model with a set of services, and two protocol bindings: a WSDL-based Web Services binding (serviceoriented), and a “RESTful” Atom Publishing Protocol binding (resource-oriented). The interface is designed to be easily layer-able on top of most content management systems to provide a common interface for generic content management functions. CMIS is not intended to expose or replace all the capabilities of every proprietary full-function content management system. A summary of CMIS v1.0 can be found at

Since the publication of the CMIS v1.0 standard, many repository vendors have offered CMIS v1.0 services for their products, and many application developers have used CMIS v1.0 to access/manage content. Based on the CMIS v1.0 experience and feedback, the v1.1 specification is developed to further enrich the CMIS functionality and protocol support. Specifically, CMIS v1.1 adds to CMIS v1.0 the following new features:

- Type Mutability
Allow CMIS clients to create, modify, and delete Type Definitions and Property Definitions for a given repository.

- Repository Features
Allow CMIS clients to discover any extensions or additional CMIS-based standards supported on each repository.

- Secondary Object Type
Named sets of properties that can be dynamically added and removed from individual CMIS objects.

- Retention and Hold
Use secondary types to support Retention and Hold on CMIS objects. A Retention protects an object from deletion, while a Hold protects an object from modification.

- “cmis:item” Object Type
A new top-level data model type that is an extension point for repositories that need to expose other object types via CMIS that do not fit the CMIS model's definition for document, folder, relationship, or

- “bulkUpdateProperties” Service
A method for supporting bulk property updates on a set of objects within a single service call.

- Append to a content stream
Support for appending to a content stream. Allow clients to break a very large upload of document content into many smaller calls.

- Browser Binding
A new optional binding specifically designed to support applications running in a web browser or other clients without the need for any additional client library. Notable among the differences in this binding are the use of JSON (Java Script Object Notation) instead of XML and the exclusive use of HTTP GET and POST for all operations.

CMIS V1.1 received Statements of Use from SAP AG, the Apache Chemistry OpenCMIS subproject and Alfresco Software Inc. [2]

The prose specification document and related files are available here:

PDF (Authoritative):


Editable source:
The CMIS TC generates PDF and HTML versions of the specification from TeX source. The editable TeX source files are availalbe at:

Schemas and WSDL:


Distribution ZIP files:

For your convenience, OASIS provides a complete package of the prose specifications and related files in a ZIP distribution file. You can download the ZIP file here:

-- Additional information --

[1] OASIS Content Management Interoperability Services (CMIS) TC

TC Charter

[2] Statements of Use:

The Apache Chemistry OpenCMIS subproject

Alfresco Software Inc.:

Associated TC: