Lotus ponders KM future. Collaboration drives upgrade path as knowledge management fades
SEEKING TO BOLSTER its position in the deflated KM (knowledge management) segment, IBM's Lotus Software is going back to its collaboration roots.
[InfoWorld: Top News]
A few notes about where things seem to be going:
- Microsoft is building support for collaboration into it's .Net capabilities, and connecting with (amongst others) Groove Networks. This might prove something of a threat to Lotus in the long run.
- Notes/Domino 6.0 ship next month, after a long beta. Question is, are people waiting for the next version of what has essentially become a proprietary application server?
At least, Microsoft seems to be offering "us developers" more of a choice in programming language (already tried out Perl.Net ?)
- Al Zollar (Lotus CEO) claims that Lotus Discovery Server is delivering the kind of content management customers are seeking. It is a shame, then, that it seems to be competing with the (aptly named) IBM Content Manager family of products.
- And of course, it becomes increasingly difficult to choose the right (IBM) tool for the job... should we be using Lotus Domino.Doc to store our documents, or is Content Manager CommonStore the right solution? Extended Search of Discovery Server? Will we keep on using the Lotus .nsf database format, or should we choose DB2? It is not getting any clearer.
Especially when separate products get combined... K-Station portal with WebSphere Portal, for example.
- And I could go on...
The good news is, everyone seems to agree it is a good idea to use Web Services to offer all this funtionality. Even IBM and Microsoft seem to agree on that. Now just hope those services are compatible with one another.