Although we have several repositories of information/knowledge that resemble, in varying degrees, a wiki it appears that the time of the true wiki (what is that?) may finally have arrived. The challenge is developing a solution that fits both with our current and future architecture (Enterprise Architecture) and our strategy around Knowledge Management.
I'll post more as we go.
UPDATE: The reason I ask what a true wiki is, is that so many solutions try to cover a large functional part of the social software domain rather than just being a wiki. Look at this quote from the Blogtronix web site (I pick this as an example, not to single this company out, even Confluence looks vulnerable to this charge):
BlogtronixEnterprise is the first service to offer secure Enterprise 2.0 blogs with wikis, RSS, document management, CMS, communities and corporate social networking built on the Microsoft .NET 2.0 architecture.I don't want another DM solution, I already have a CMS and blog platform, so how can I seriously consider implementing this.
Then there's another class of solutions that are available online only. I don't think EY is ready to trust another organisation with its data in the way that solutions such as CentralDeskop and PBWiki require.
