Glenn Engstrand

Maybe it is just the inner entrepreneur but I really enjoy getting to explore an innovative idea and bringing it to the light of day. That was perhaps the main reason why I enjoyed working on the Conversational Content Management beta so much.
What was innovative about this project was in the way that the collaboration problem was addressed. In most online collaborative document creation environments, the actual editing is the visual equivalent to what was used to be called half duplex. If you move the mouse and started typing, then you rudely took away control from whoever was editing last. This has a very chilling effect on the fragile process of group creative interaction.
Have you ever served on a board of directors? The monthly board meeting usually looks like this. A group of people discuss the agenda while an assistant takes notes. Later on, the highlights (i.e. the actionable summary) get published.
What if you could have access to that assistant in any meeting? That is what the Conversational Content Management beta is all about. All collaboration is done in the chat room itself. A robot records the entire conversation and extracts out the actionable summary later. The following technical white paper discusses how and introduces the following open source projects used to create this beta and accelerate its time to market.
Hippo CMS is an open source Content Management System written in Java. Its emphasis is on publishing with a limited number of authors with access available to the anonymous public at large.
Strophe is an open source Java Script library that permits web pages to access an XMPP chat server via BOSH.
Code Igniter is a PHP MVC framework for writing web applications hosted by the Apache web server.
Jack Rabbit is an implementation of the Java Content Repository which is how the chat reporter publishes content in the CMS.
Tigase is the open source XMPP server, written in Java, that serves as the chat room implementation.
Thrift is the communications layer between Tigase and the chat session manager.
MySql is the open source relational data base where the web site and the chat server store their data.

Maybe it is just the inner entrepreneur but I really enjoy getting to explore an innovative idea and bringing it to the light of day. That was perhaps the main reason why I enjoyed working on the Conversational Content Management beta so much.

What was innovative about this project was in the way that the collaboration problem was addressed. In most online collaborative document creation environments, the actual editing is the visual equivalent to what was used to be called half duplex. If you move the mouse and started typing, then you rudely took away control from whoever was editing last. This has a very chilling effect on the fragile process of group creative interaction.

Have you ever served on a board of directors? The monthly board meeting usually looks like this. A group of people discuss the agenda while an assistant takes notes. Later on, the highlights (i.e. the actionable summary) get published.

What if you could have access to that assistant in any meeting? That is what the Conversational Content Management beta is all about. All collaboration is done in the chat room itself. A robot records the entire conversation and extracts out the actionable summary later. The following technical white paper discusses how and introduces the following open source projects used to create this beta and accelerate its time to market.

Conversational Content Management