Blimey, two in such a short space of time. This one has been rattling around in my head for some time and I was prompted to write based on the post from Real Story Group.
Now I am not a subscriber so I have not read the full report but the mere fact that there is interest in this subject prompted me to write this. I think CMIS and SharePoint is a difficult topic and I think it is a difficult topic for the SharePoint world. Why? Well its not a simple answer but take a look at this diagram. This describes how SharePoint has been built from the UI backwards. It is the UI which has pushed the development and growth of SharePoint and it is the UI which people focus on.
As a sample when I asked a number of SharePoint Consultants how to integrate SharePoint with an ERP solution they ALL assumed that I meant to have the ERP solution as the back-end repository but with the front end being SharePoint. When I clarified that I wanted SharePoint to be used as the document store for content which is used in ERP transactions then they simply didn’t get this.
CMIS is disruptive to this view in that it puts an unknown on the UI and relegates SharePoint to be a document repository. I use the word relegate on purpose as I believe this is how the SharePoint community would view this Use Case. This is wrong, this is an opportunity to open up a new set of solutions for SharePoint, for it to become more embedded in organisations and be more of a platform service.
I’d love to see some uses of SharePoint with CMIS and how this can open up new opportunities for SharePoint usage in organisations.