Management
Technology
- Applications
- Business Intelligence
- Development
- Hardware
- Mobile & Wireless
- Networking
- Internet
- Operating Systems
- Security Products
- Servers & Datacentre
- Storage
Toolbox
Training
Books
White Papers
Webcast
Resource Centre
CMIS Top Ten Questions
September 16, 2008
1. What is CMIS
Posted by: Ian Howells
On September 10, 2008, OASIS member companies submitted a proposed charter for a new OASIS Content Management Interoperability Services (CMIS) Technical Committee (TC). This series of posts addresses the top ten questions that have arisen as a result of that announcement.
- What is CMIS?
- What Problem Does CMIS Address?
- What Functionality Does CMIS Address?
- How does CMIS relate to other Standards?
- Which Vendors are involved in CMIS and how long have they been working on the Draft Specification?
- What will be the Impact of CMIS on the ECM Market?
- Why CMIS?
- How do I get access to the Draft Specification and what is the OASIS process?
- How can I start developing against the CMIS API today to prepare for tomorrow?
- How can I participate and comment on the Specification
1. What is CMIS?
CMIS stands for Content Management Interoperability Services (CMIS). It is a draft specification submitted by leading ECM vendors to OASIS (the Organization for the Advancement of Structured Information Standards) with the aim of becoming an ECM industry standard. One of the key words here is "Services". We are moving from a world of locked content to a world of "Content-as-a-Service" where content is simply and consistently accessible and can be mashed up in the way we take for granted on the web today.CMIS defines a domain model which consists of a:
- Data Model - To consistently model content and properties
- Services - To access the Content in a consistent way
- Bindings - SOAP and REST/ATOM bindings
These are designed to be a layer on top of existing content management repositories offering a generic, universal set of capabilities applicable both within the enterprise and outside the firewall in the realm of Web 2.0
CMIS is not intended to:
- Prescribe how features should be implemented within an enterprise content management (CM) repository
- Expose all features provided by proprietary ECM systems
The drive towards a CMIS standard is important in order to accelerate more widespread adoption of CM and one of the reasons that all of the major ECM vendors have backed the draft specification.
Follow highlights from ComputerworldUK on Twitter
Sign up for our Daily Newsletter
The UK IT News widget Get it for your site!
<<newer entry | back to blogs index | older entry>>
Advert
Email this article to a friend or colleague:
PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.
- This article is now being printed.
What are your views on this subject? Use the form below to post a comment on this article up to 1000 characters.
Click below to add 'CMIS Top Ten Questions' to your blog.
If you do not have a ComputerworldUK Account and would like to use this feature, please Register.
If you are a registered, logged-in user, this will post the title and first paragraph of this story to your blog to share with your readers.
Advert












































Comments received
Bip Thelin said on Wednesday, 17 September 2008
I have some other questions: http://code.qbranch.se/post/show/37