Very excited that I get to see Cornelia Davis speak this year. Last year I had to go catch a train during her presentation so I wasn’t going to miss this year. Conelia used to be part of Documentum (eRoom before that) and is now a Senior Technologist with EMC’s CTO Office. This topic is pretty important because I think that this framework is influencing the Next Generation Content Server (NGIS).
Ahson Ahmad and Norrie Quinn are starting things off this Momentum talking about the Web Services. Not expecting too much new, but you never know. Hopefully some good information on the REST interfaces.
As I covered in my last post, Implementing an ECM Strategy without a Platform, you don’t need an Enterprise CMS Platform to implement a successful Enterprise Content Management Strategy. That doesn’t mean that you can’t use one or that using one would be the wrong approach. Just like there is no one-size-fits-all CMS, there is no single way to define and implement an ECM Strategy.
I am going to look at this in two stages. The first is going to focus on the purpose of and foundation for an Enterprise CMS Platform. The second is going to look at what capabilities a CMS needs in order to be a Platform.
Victor Spivak, chief architect for the platform, is presenting on what is the most popular topic post from last year. Victor is smart and doesn’t mince words. The session was mostly packed 15 minutes before it even started.
Victor is going to breeze through many of the things that haven’t changed in a year, so supplement these notes with last year’s notes. These notes are “more accurate” if they conflict.
At the end of January, I talked about the proposed effort being undertaken by the iECM committee to create a CMIS demonstration for the AIIM Expo. Things are going well and I am working with others to build the demonstration. I wanted to share a few details with you.
- We are implementing the Web Service binding for CMIS. While REST would be better for what we are doing, it was felt that the Web Services binding would be easier for the development team to churn out.
- As a result of that, the participating vendors are Alfresco, EMC, IBM, and Nuxeo. Microsoft wanted to participate was not sure that their Web Services binding would be complete in time.
- Each vendor will have a two issues worth of articles from AIIM’s bi-monthly publication, Infonomics. In addition, each vendor is welcome to add their own white papers and collateral to the system.
- Users will search on metadata and/or full text. All searches will be round-robin sorted so that each repository has multiple hits on the first page, assuming that they have any content that meets the criteria.
- The system is being developed in .NET because we were able to identify a free hosting server that could support the effort.
- We, including myself, are going to be at the Expo on April 2nd to talk about it. I’ll share the exact time when I have it.
Time for an update on the architecture. Victor Spivak is presenting. He knows his stuff, so hopefully it’ll be a good one. I know waaay too many people in this room. I’ll never get to say hello to all of them. This is by far the most crowded session.
Running into all sorts of old colleagues and friends. Seen others that I am going to have to flag down soon. Anyway on to Kenwood Tsai and Harish Rawat of EMC.
The Big Men on Content, Lee to be precise, recently joined the ECM 2.0 discussion, stating that they are going to wait for EMC’s sp2 before they jump on-board. That could be a long wait. After all, we are still in Beta as far as I am concerned.
This was prompted by a reading OpenText’s Enterprise 2.0 Content Management strategy. Note the placement of the 2.0. We’ll be getting back to that.
Tell everyone that you aren’t going to have time to write many entries and people start blogging about cool and interesting topics. Here is a quick rundown of the ECM WSDL analysis and my thoughts.
- Our old buddy James McGovern started the whole thing off. He has apparently been sharing is frustration with his significant other and he wrote a post on the sad state of WSDLs in the ECM space. They are ugly and poorly written in his experience. Not having delved into any out of the box WSDLs in ECM, I can hardly argue. It wouldn’t shock me though. Hopefully the DFS ones will measure up better. James then starts to talk about the ECM systems having a standard Document Query Language and a common WSDL built upon that structure. Sounds good to me. In fact, it is a nice, positive contribution to the whole ECM standards issue.