The Content Management Interoperability Services (CMIS) Standard What is it and Where is it Going? Saravanan Rajan Laurence Hart Vice President, CM Pros Chair, CMIS Group, CM Pros CTO, COSI Consulting Director, Washington Consulting, Inc.firstname.lastname@example.org email@example.com
Overview• Introduction• What is the CMIS Standard?• How CMIS can be used• Benefits of CMIS• Industry support• Future of CMIS
Thanks to Our Host -Developers ofLearn more at BridgelineDigital.com
About CM Pros• Helps over 15,000 associate members all over the world to enhance their knowledge and expertise• Provides a collaborative community of practice advancing the field of content management• Enhances the knowledge and expertise of our community by sharing practices, providing leadership and connecting members• Offers online and offline opportunities to interact with members through our website, LinkedIn, webinars, events and seminars• http://www.cmprofessionals.org/
You’ve probably heard of CMISContent Defines a domain model and set of bindings, suchManagement as Web Service andInteroperability REST/Atom, that can beServices used by applications to work with one or more Content Management repositories/systems.
Basic History• 2005 – iECM Committee begins discussing need for a new standard – ODMA: Desktop dependent – WebDAV: Limited capability – Java Content Repository: Technology specific, API-base• 2006 – EMC, IBM, and Microsoft leave the iECM Committee and begin developing CMIS• 2008 – Initial proposal drafted by EMC, IBM & Microsoft – Reviewed by Alfresco, Open Text, Oracle, SAP – Draft was unveiled and released to OASIS• 2008 – The OASIS CMIS Technical Committee formed• 2009 – CMIS 1.0 released for public comment• 2010 – CMIS became an official standard
Three Fundamental Use Cases• Repository to Repository• Application to Repository• Federated Repository
Repository to Repository 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
CMIS in a Publishing System Publishing: • Whitepapers • Official Guidelines • Reports 3) Document is 1) Create a Content: integrated into document. • XML website and • PDF published. CMIS 2) Publish Document CMIS Content ContentRepository Interface Interface Repository to WCM System.
Application to Repository• Sharing Content across applications• Collaboration/Enterprise 2.0 Applications – SharePoint as an interface, not repository – Content in collaborative platorms• Enterprise Software Applications• Generic Content Management Applications• Composite Content Applications (CCAs)
Composite Content Applications• What is a CCA? – Formerly known as 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 Content Management System
In all cases, it is using the bestcontent application for the job against a shared Content Management System...…not shuffling content between systems
Industry Support• Large Content Management vendor support base – Support: IBM, EMC, Open Text, Microsoft, and Alfresco – Missing (so far): Hyland and Autonomy• Microsoft support – SharePoint 2010 as both a repository and application – Released as part of SharePoint Administrator Toolkit• Open Source Content Management support – Chemistry project provided open source implementation – All supporters of previous Java Content Repository standard will be able to claim CMIS compliance• Next step is application builders
Future of CMIS• Version 1.1 – Type Mutability – Browser binding (JSON)• Version 2.0 – Increased Records Management support – Support for Semantic functionality – Ability to have domain models
Getting Involved• CM Pros is working to improve CMIS – Educate the Content Management world – Collect real-world experiences – Suggest areas for improvement• Interested in joining the CM Pros CMIS Group? – Contact Laurence Hart – Email: firstname.lastname@example.org – Twitter: piewords
Summary• Content Management Interoperability Services – Official OASIS standard now – Planned evolution to stay relevant• Defines Content Management Domain Model – Content model the same across all bindings/implementations – Web Services and Atom bindings are ways to access model, not defining part of standard• CMIS is not the lowest common denominator – Defines functionality that is needed – Some parts are optional to provide for a greater ecosystem• It is in use now
Thank You Laurence Hart http://wordofpie.com @piewords
About the Speaker Laurence Hart is a Director of Technology Solutions for Washington Consulting, Inc. and the author of the blog "Word of Pie". Over his 15+ years in the InformationManagement industry, he has led a wide-range of efforts including content digitization, Records Management, BPM, and Collaboration for both the commercial and public sectors. Recently, Laurence has been focused onhelping organizations in assessing, defining, and building their Information and Content Management strategies. As an active member of AIIM and the Chair of the CMPros CMIS Group, Laurence has focused on educating theContent Management industry on the standards needed for successful growth.