The Point Of The Content Interoperability Services (CMIS) Standard
1. The Point of the Content
Interoperability Services
(CMIS) Standard
What Problems
Does CMIS Solve?
2. You’ve probably heard of CMIS…
Content
Management
Interoperability
Services
Defines a domain model
and set of bindings,
such as Web Service
and REST/Atom, that
can be used by
applications to work
with one or more
Content Management
repositories/systems.
3. …heard about CMIS’s history…
• Need identified by AIIM’s iECM Committee
• Initial proposal drafted by EMC, IBM & Microsoft
– Reviewed by Alfresco, Open Text, Oracle, SAP
– Draft was unveiled in Sep 2008, and submitted to
OASIS
• The OASIS CMIS TC was formed in Nov ‘08
• Targeting public review early fall ‘09
• Targeting v1.0 early 2010
8. There are times you want to talk
directly between content
repositories
• Publish a document from one system into
another
• Manage records from one centralized
system
9. For example, publishing systems
that output to the web as one
medium
Content
Repository
CMIS
Interface
Content
Repository
CMIS
Interface
1) Create a
document.
2) Publish Document
to WCM System.
3) Document is
integrated into
website and
published.
*Also known as a “CMS” in the Web Content Management world
Publishing:
• Whitepapers
• Official Guidelines
• Reports
Content:
• XML
• PDF
11. What Types of Applications
are we Talking About Here?
12. There are several types of Content
Applications, three of them are…
• Collaboration/Enterprise 2.0 Applications
• Enterprise Software Applications
• Content Enabled Vertical Applications
(CEVAs)
13. First, some Collaboration/
Enterprise 2.0 Applications
• SharePoint as an interface, not repository
• Existing Enterprise 2.0 Applications
(Telligent Community, Jive SBS, CenterStage, Beehive)
• New CMIS Interfaces
“One CMIS Interface to
Rule Them All!”
14. Let us not forget traditional
Enterprise Software Applications
• Think of those massive
Enterprise 1.0 Applications
– Business Process Management (BPM)
– Customer Relationship Management (CRM)
• They are full of content that needs to be in
multiple places and collaborated upon
15. And finally, the Content Enabled
Vertical Applications (CEVAs)
• What is a CEVA?
– Electronic Medical Records
– Case Management System
– Correspondence Tracking System
• Vendors with domain expertise build the
applications with the business rules and
plug into an ECM system
16. In all cases, it is using the best
content application for the job
against a shared Content
Management system...
…not shuffling content between
systems
22. Federated repositories is interacting
with multiple repositories as if they
were one repository.
Content
Repository
Content
Repository
Content
Repository
Content
Repository
Search Manage