What remains to be seen is to what extent the ECM vendors support the standard in their products. A vendor could claim to support it but do so only minimally. Also, this is not the first time the ECM community has attempted a cross-platform standard. The Java Content Repository (JCR), which aimed at cross-platform compatibility for Java-based CMSes, never took hold due to relatively poor adoption.
Thus far the vendors that have participated in CMIS seem enthusiastic. They have held a number of plug-fests to demonstrate that front-end querying software can draw data from a variety of back-end repositories.
And products are coming out that support CMIS: Earlier this month, Alfresco included support for the draft CMIS 1.0 standard with version 3.3 of its Alfresco Community Edition.
But even if the vendors are enthusiastic about the standard, it will take years for most of them to work it into their products, Byrne said. He also cautioned that the standard addresses only repository independence. It does not address process integration. "Because I have an application that can talk to a neutral standard doesn't mean my business processes have gotten integrated," he said.
Still, that the major vendors are participating in this standard speaks well for its adoption. "They all clearly see CMIS in their interest," Byrne said.