Before I get to the meat of this post, I want to start with a confession. I have been a slacker. If you look at my word cloud to the right, you’ll see CMIS as a big piece of the proverbial Pie. Even before it was a public term, I railed for the need for a standard in the Content Management space.
Now that the first update to the Content Management Interoperability Standard (CMIS) has been out for nearly three months, why am I just now blogging about it? Now that browser binding, retention, holds, and type mutability have been added to CMIS, why am I not proclaiming the wonders of CMIS 1.1 from every rooftop.
What I want to do today is talk about why this update means everyone should be looking deeper into CMIS and reconsider it for every Content application created. In fact, as much as the need for standards in Content Management existed when I started writing about them, it is even more urgent today.