In this, the final article in this series, we'll discuss the architecture of a hyperspatial Knowledge Management application using the MVC Model2 approach and will examine the components of two applications: a knowledge organizer, and an ontology/taxonomy manager.

Practical QuickPlace applications create value-added kCollaboration solutions
QuickPlace provides a superb user and application development platform for delivering 2G-KM (Second Generation Knowledge Management) technology applications. PlaceBots can be integrated with underlying J2EE Knowledge Transaction applications through a SDK (Systems Development Kit) API. Such an API (Application Programming Interface) can be used to build new Knowledge-enabled Applications or to knowledge-enable existing ones.

Knowledge-enabled and knowledge-sharing applications in QuickPlace can be built to be easy to install and intuitive to learn and use. They can be built so they can be modular application components plugged into a Knowledge Management framework similar to industry standards like JSP Tag Libraries, Java Servlets, and Java Beans. J2EE knowledge transaction request and response components can be transported by SOAP (Simple Object Access Protocol) XML (eXtensible Markup Language) transaction envelopes, providing a dynamically intelligent object broker payload carrier.

Here's a sample QuickPlace MVC 2G-KM Architecture:

• QuickPlace provides a user-friendly interface configuration;

• Event-driven PlaceBots fire underlying knowledge agents to work for the user, controlling the application of the 2G-KM model for populating the J2EE knowledge transaction response component;

• A 2G-KM SDK can be used to emulate an MVC architecture, much like JSPs et al, separating presentation from model logic with high reusability while providing user independence;

• The SDK provides a struts-like MVC controller for abstracting knowledge application logic into simple, reusable knowledge declarations, populating the view through the J2EE request/response pattern metaphor;

• SOAP XML envelopes provide the transaction carrier for J2EE (Java 2 Enterprise Edition) requests to the underlying knowledge engine and the resultant responses back to the user, application, or device;