CMIS was submitted to Oasis for becoming an open standard on Content Management Interoperability.
What’s fun, is that almost every single blog / newsfeed I monitor in the Content Management area addressed the subject. It was fun to see my dashboard with the acronym popping up in all sections (i keep it organized by different vendors).
This definitely got the attention of the ECM professionals. I’ll not write too much on it since a lot of bytes are already out there commenting the event.
What I want to point is that this needs the proper amount of luck and environment in order to succeed (unlike JSR 170 and 283).
It needs to be the SQL of Content Management. On one blog entry, Pie noted that the new standard needs support from the vendors in order to make it into the real world. This is essential of course, but another thing is to also be embraced by the application builders as a core CM layer of their architecture.
Declarative support is there (e.g. Microsoft) . At least from the vendors – the first being obviously the standard promoters. But even most of them were giving only the marketing speech (with the notable exception of Alfresco who already has an implementation).
I think this is a great opportunity for the ones building CEVAs as it might reduce their costs on supporting several platforms for their solution. Unfortunately there is a difference between SQL and CMIS 🙂 – databases are well established in IT architectures as foundation technologies for various solutions. Content Management is more seen as a top level application.
It will take time for IT Managers, Solution Architects, CIOs, ISVs and others to look at CM and think of it as middleware (at least, if not infrastructure) in order to start building applications which are independent of the ECM product.