CMIS (Content Management Interoperability Services) is a vendor-neutral OASIS Web services interface specification that enables interoperability between Enterprise Content Management (ECM) systems. CMIS allows rich information to be shared across Internet protocols in vendor-neutral formats, among document systems, publishers and repositories, in a single enterprise and between companies.
Content Services fully implements both the CMIS 1.0 and 1.1 standards to allow your application to manage content and metadata in a repository. This section gives a brief overview of the URL format for CMIS ReST API calls, and explains the format of responses.
You can use basic HTTP methods to invoke CMIS methods, or you can use one of the many language-specific libraries that wrap CMIS. One such example for the Java language is the OpenCMIS Client API provided by the Apache Chemistry project. Apache Chemistry provides client libraries for many other languages such as Python, PHP, and .NET. The OpenCMIS library is covered in this section.
You can use methods described by both CMIS 1.0 and 1.1 in the same application, although in practice it is advisable to write all new applications to the latest 1.1 specification.
- CMIS Basics: CMIS is built around a number of concepts. This information provides an overview of those that are shared between all CMIS versions.
- Content Services Configuration Settings: Information about repository configuration related to CMIS.
- Getting Started with the AtomPub Binding (XML): CMIS 1.0 introduces the XML based AtomPub binding.
- Getting Started with the Browser Binding (JSON): CMIS 1.1 introduces a number of new concepts that are supported by Alfresco. You can now use the new browser binding to simplify flows for web applications, use Alfresco aspects, and use the append data support to manage large items of content.
- Working with the CMIS API from Java: Introduction to the OpenCMIS Java library that wraps the CMIS ReST API.