good overview of the current state can be found in "CMIS meeting notes".
I'd like the idea to have a common accepted and wide adopted standard to maintain resources and all related concepts.
- decoupling of client implementation dealing with standard related concepts from server implementation
- usage of several server implementations through single client implementation
- adaption of common and rich infrastructure for specific needs
core infrastructure of a content management is provided by regular OS client infrastructure and specific needs are implemented on top of those core layer. a wide range of server side infrastructure can be used and integrated without adding IT complexity.
we already heard about those vision, thats what WebDAV claim to provide....
why not working stronger on WebDAV instead of re-inventing the wheel? looking at the world of WebDAV shows the issues in this area:
- many incomplete implementation out there
- integration in regular OS infrastructure is half-assed and error prone
- WebDAV is implemented as an additional API with limited maturity and attention of CMS vendors.
- DeltaV extension only supported by a very rare and not widely used implementations
the major issue with WebDAV is simple the lack of robust and complete implementation. the main reason: it is easier to define a standard than fully implement those standard and resolve existing issues within the standard.
the major members in CMIS TC are the same as those working on WebDAV standard. i personal hope that the success and sustainability of implementation will be improved. otherwise there is just another standard no one takes care of once it is 80% complete.
i do not compare both approaches because this is another story but in terms of simplicity WebDAV is currently in pole position. more to come......