As I discussed yesterday, I’ve been waiting a long time for the Content Management Interoperability Services (CMIS) standard. There is still a fair amount of excitement out there as more people join the conversation. I’m still excited, but the excitement is beginning to be tempered by reality.
There are two primary factors to standard adoption:
- Is the standard technically sound? It has to actually solve the stated problem. It is okay if a standard is limited in functionality in initial drafts as long as it evolves to accomplish everything required. At the same time, it must be easy enough to use. These are not small technical challenges.
- Is there vendor support? Let’s face it, if the vendors don’t support it, then it will fail. The JSR-170 and JSR-283 standards are perfect examples. They aren’t supported by a critical mass of vendors. The reasons range from the technical (we work in Java), to the philosophical (it is a bad standard, let’s focus elsewhere), and to the lazy (nobody cares so let’s ignore it).
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. While I digest the technical aspects, take a look at the Vendor Support factor.