Sunday, December 28, 2008
Enter CMIS, a Proposed ECM-SOA Standard
Laurence Hart provided an insightful blog entry entitled: Enter CMIS, a Proposed ECM-SOA standard. Still there are lots of unanswered questions...
The likes of Nick Patience, Chuck Harris, Craig Randall, Cornelia Davis, Bex Huff and others have chimed in on the CMIS specification. I wonder if any of them have thoughts on the following:
| | View blog reactionsThe likes of Nick Patience, Chuck Harris, Craig Randall, Cornelia Davis, Bex Huff and others have chimed in on the CMIS specification. I wonder if any of them have thoughts on the following:
- Should EMC/Documentum dump their fugly DFS implementation once CMIS support is released?
- Will CMIS implementations support important security standards such as SAML?
- While we understand that ECM systems should store content, not users, do the ones that store users require junking up the specification in order to accomodate?
- How should ECM incorporate? Do you prefer content server --> CMIS or content server --> DFC --> DFS --> CMIS?
- Once an implementation of CMIS is released, should vendors make it work with prior versions or should they force upgrades?
- How self-describing should the WSDL be? For example, should each element have a choice type or should we resort to less optimal "helpers"?
- Should CMIS support WS-Transactions?
- The conversation to date has been all about producers. Any thoughts on how consumers will embrace? Thoughts on how Siebel, SalesForce, etc could leverage?
- How should compression be handled within an ECM SOA?
