slmader wrote:

Hi Pranav,
The major trends I see, especially with regard to wiki use in organizations, are:

Integration - making sure a wiki integrates well with other business tools, like SharePoint, content and document management systems, Microsoft Office, etc. This is important because as usage of wikis in organizations grows, they need to present a familiar interface to people who aren't early adopters or the highly tech-savvy.

Structured Data - This includes everything from spreadsheets becoming equal to text pages in wikis to support for handling and exporting data in formats like XML and DITA. Two of the most common tools used in offices today are Microsoft Word and Excel, and for wikis to get the attention of Office users, they need to provide equivalent functionality so that people will take advantage of them and get the added benefits of the centralized knowledge storage and access, easy editing, content and conversation on the same page, etc.

Here are two posts from my blog that discuss this in more detail:
http://www.ikiw.org/2008/09/03/sure-wik … -business/
http://www.ikiw.org/2008/08/05/5-differ … ise-wikis/

Regards,
Stewart

Hi Stewart,
          THANK YOU very much for your detailed and prompt response to my post. It is very helpful. The blog posts are great too!!! Thank you once again.

Regards,

Pranav

I suggest another point: contextual integration. It's great to connect the wiki to other systems, it's even better to have "contextual" or semantic integration. This is the difference between "data" and "information."

zAgile can help there with an open source solution: Wikidsmart for Confluence.

It turns Confluence into a semantic wiki so that you may contextually capture information in a structured way. Here's a bit more about it:
http://www.zagile.com/products/project- … wikidsmart

plus you can see an example of integration in action with this video:
http://www.zagile.com/products/Semantic … ility.html

here's a rough look at semantic search with Wikidsmart on youtube:
http://www.youtube.com/watch?v=jtQJxxgkq3o

and here's more description in a blog:
http://www.zagile.com/blogs/confluence-is-n.html

Pranav,

At eTouch we have seen the following trends in the marketplace:

1. Need for multi-tenanted, on-premise solutions: - These cater to the needs of large enterprises that have multiple siloes of content and also the need for centralized Wiki administration/monitoring.

2. Need for personalized dashboards to drag and drop widgets to display relevant and interesting content based on a users preference.

3. Bundling of 'adjacent' features within the Wiki - Blogs, Forums, Social directories etc

4. Need to publish content through API's based on REST - those in turn can be consumed by other Web-based applications.

Cheers,

SamePage Team