Fusion ECM

CMS Watch has this interesting post about the new CMIS specification. Roy T. Fielding (one of the *real* inventors of the web and on whose dissertation REST is based) points out on his blog that there are a number of issues with CMIS as it stands today. Among those he lists are:
1) it's not a standard, it's a proposal that hopes to become a standards effort and maybe one day a standard.
2)It's not properly RESTful. After all, REST is not a protocol, it's an architecture. The AtomPub model outlined in the proposal is not *really* a REST binding.
3)It's more a Web Services interface for cross repository document management.
Fielding writes:

CMIS is a classic example of what happens when a control-oriented interface is slapped onto an HTTP-based protocol instead of redesigning the interface to be data-oriented.

In the end, Fielding posits the following:

My bet is that the document repository vendors will continue to focus on making their own native HTTP interfaces more efficient, since that is how customers will evaluate their performance when integrated within heterogeneous architectures.

So I guess he's adopting a wait and see attitude like so many others.

I wonder what BEX and Craig have to say

UPDATE: Sam Ruby has a response here.