CMIS: My Take & Link Roundup

Well the hand waving around CMIS is in full swing but the actual impact is yet to be determined. CMIS is the Content Management Interoperability Services specification that is being submitted to OASIS for standards ratification (download it here). Oracle is a member of the CMIS community and helped to review/vet/confirm the spec along with others such as EMC, IBM, Microsoft, SAP, OpenText, and Alfresco.

By now you should have read that it is a Web Services/REST/Atom/SOAP specification for getting at your unstructured content regardless of what content management system it lives in. With the CMIS-defined HTTP calls, standard create, read, update, delete operations against a compliant repository are the same regardless of the vendor repository architecture. If this sounds like JCR (in purpose not API) to you then you're on the right track. But while .Net shops were never going to participate in a java spec, CMIS invites them into the fold.

CMIS is the big tent content management specification. Honestly, I like it because, as David Nuescheler point out in the CMS Watch article linked below, "...the arrival of a high-level content protocol that transcends any one programming language..." is a good thing. The reality is that many organizations operate in heterogeneous ECM environments. All of us vendors spend cycles on producing system specific components, web parts, adapters, and agents to talk with, store in, migrate from our competitors' systems. This will make that easier.

What I don't buy (just yet) is that this proposed standard is all that was missing to allow customers to keep their content just where it is and usher in a new and glorious era of enterprise mashups. The standard provides the common baseline of access/retrieval/interaction with unstructured content and its metadata across the participating ECM systems. You can bet the vendors will start here and differentiate on top.

But just the fact that we're all starting here is a very good step in the right direction. Keep in mind that, right now, this is a .5 draft specification so we will see maturation as time goes on and folks sign on.

CMIS Link Roundup:
ZD Net

...there's a heightened need for interoperability between the vast and diverse sources that manage this content. Today's agreement is a major step forward in achieving this goal.

Bex

now I can FINALLY tap-dance on the grave of that awful JSR170 standard...

BMOC

It is not necessarily vendor involvement that drives the adoption of standards. Often it is the success of products that use them that causes standards to take off.

Pie

Customers are important, but it takes a large mass of them to force the vendors to act. I would qualify them as a secondary factor.

CMS Watch

We've heard these sorts of claims made before, of course.

Craig Randall

I’m optimistic about the kind of emergence with the announcement of CMIS.

InfoWorld


...an API that can be used to develop write-once, run-anywhere, next generation content and social applications.

ECM Stuff

I truly hope all the vendors put their money where their standard is

Information Technology News

The main aim of CMIS is to considerably reduce the IT burden around multivendor, multirepository content management environments

CMSWire

There are a number of benefits of interoperability according to the group, including:
* Improved user access:
* Cost Reduction:
* Protection of Current Environments (clipped)

Comments:

I agree that, although it's nice to see the level of support and visibility online for CMIS, what matters more is what comes next (i.e. actions more than words). I'm glad that Oracle has already partnered in this effort. Just to put the above quote from my post in better context, here is the complete thought: "One of the impacts Kyle [McNabb of Forrester] sees as a result of CMIS particularly resonates with me: separation of content repositories from content-centric applications in a manner similar to how SQL standardization enabled separation of the relational database from data-centric applications. Entirely new classes of applications (e.g. ERP) emerged with the arrival of SQL, and I’m optimistic about the [same][ kind of [potential] emergence with the announcement of CMIS." Cheers... -Craig

Posted by Craig Randall on September 12, 2008 at 07:51 AM CDT #

Content management becoming a hot topic. Now that there are better front-end channels pushing information. People are expecting a better delivery of information.

Posted by Enterprise Content Management System India on September 14, 2008 at 07:16 PM CDT #

Post a Comment:
Comments are closed for this entry.
About

Enterprise 2.0 and Content Management

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today