OASIS Content Management Interoperability Services (CMIS) TC
Using Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors
David Choy, firstname.lastname@example.org, Chair
Table of Contents
- Subcommittees and Groups
- TC Liaisons
- Technical Work Produced by the Committee
- Expository Work Produced by the Committee
- External Resources
- Mailing Lists and Comments
- Additional Information
Participation in the OASIS CMIS TC is open to all interested parties. Organizations that use or provide Enterprise Content Management (ECM) systems, including Independent Software Vendors (ISVs) and integrators who build applications that support multiple content management systems, are invited to join the CMIS TC. Contact email@example.com for more information.
The OASIS CMIS TC works to standardize a Web services interface specification that will enable greater interoperability of Enterprise Content Management (ECM) systems. CMIS uses Web services and Web 2.0 interfaces to enable rich information to be shared across Internet protocols in vendor-neutral formats, among document systems, publishers and repositories, within one enterprise and between companies.
No TC Liaisons have been announced for this TC.
- Latest List of TC-approved CMIS Feature Extensions
- OASIS CMIS 1.1 Specification
- OASIS CMIS 1.0 Approved Errata 01
- OASIS CMIS 1.0 Specification
- OASIS Technical Committees Issue Tracker
- CMIS TC Wiki
There are no approved expository work products for this TC.
Although not produced by the OASIS CMIS TC, the following information offers useful insights into its work:
- Book: CMIS and Apache Chemistry in Action by Florian Müller, Jay Brown, and Jeff Potts
- CMIS LinkedIn Group
- "CMIS: Addressing Contemporary Requirements for Content Integration," by Dale Waldt, Gilbane Report
- Cover Pages Technology Report: Content Management Interoperability Services (CMIS)
- OpenCMIS Apache Chemistry Project
Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.