Automatic publishing of results in a knowledge book metaphor
When the knowledge server returns results, users can instruct the knowledge publisher component to generate and publish targeted knowledge objects and views, not only for discovery navigation and successive recontextualization for knowledge hunting, but also for a take-away published work.

This locks in findings for subsequent reference and record. You can also peruse the findings in paper form when away from a computer, or you can view them on your laptop when untethered from network access. I, myself, prefer published, printed take-away work so that I can speed-read and mark up my thoughts and ideas on paper, but this is a skill I have worked hard to hone over the years, and it appeals to my comfort zone. Members of the new generation of business users are often more comfortable reading from a browser or PDA, so all these renditions become essential to supporting a successful knowledge management application for small, medium and large corporations.

In a knowledge book (also known as a kBook) metaphor, the knowledge management server might render the results document in order of semantic fit to the discovery context. This provides a hyerplinked kBook table of contents, where the discovery document, assertion or text snippet gist would be used to form the kBook title. Thus, each discovery document in the results becomes a kBook chapter.

Upon drilling into the chapter, the chapter title would be the document name. The chapter table of contents would be a rendition of the document kSig. The chapter table of contents might be followed by a chapter abstract as a short three-line summary of what the chapter is about. Below the abstract might be a link to the chapter introduction.

Following the introduction might be the chapter body as a link to the original document that the chapter represents. Or, it might be an HTML rendition of it, and that might be followed by a chapter review as a rendition of the power-read. Here, a power-read view would represent participating document paragraphs in a document's kSig themes with paragraph headers listing the kSig themes in the paragraph and the paragraph text, semantically tagged with specified tagging dictionaries, knowledge rules, best practices, expert profiles, and kSig themes.

Finally, the kBook might have an index as a rendering of the results classification, providing a chapter paragraph index to classification themes. And, this might be followed by a rendition of the knowledge comparator as a glossary of terms with representative textual descriptions from its unique paragraph content instances, cross-linked to other associated paragraph text instances in the kBook and to related content accordingly.

Collaborating through semantic routers
Using KSig unary semantic operators and kThread unary semantic operators, corporate collaborative competency can be facilitated. Documents kSigs can be used through "goodness of fit" testing against semantic routers, which are stacked profiles representing user knowledge, interest and collaborative patterns. Leveraging a concept of knowledge refraction borrowed from light prisms, documents can be refracted or routed to respective users represented in semantic routers. The server would return resultant routing instructions, for instance, as a routing slip in XML document format to be acted upon by the requesting client.