The ECM WSDL Discussion Leading to More

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.

Continue reading

A Timely Example of Needed ECM Standards

So the question has gone up repeatedly since this dialog began, what problems are we trying to solve? I’ve tried to explain this and I think I’ve been getting through. However, I still encounter pain in real life because of this. In fact, this just may be a punishment for raising such a ruckus.

Here is my most recent problem. A client has a legacy Records Management solution. It works well, though is a little dated. The client is now going to implement a Web Content Management solution. The approved web pages need to be automatically declared as a record. If these were the same ECM platform, there wouldn’t be any problem. However, they aren’t. In fact, one is Microsoft based and the other is Java based. Neither of them is Documentum, though that wouldn’t change the problem significantly.

Continue reading