Approach
IKS has developed a working hypothesis which we call the Interactive Knowledge Stack. We are trying to start a dialogue in the developer community, about the need for a conceptual layering. As a start, we developed the following concepts, visualized in below diagrams.
 |
 |
| IKS layers: behavioural/interface, descriptional/middleware, distribution&storage/repository. | Simplified view of the LAMP, Java and IKS Stacks put next to each other. |
IKS does not say anything about implementation technology, but it tries to say something about translation from behavioural layers (at the level of interfaces) to descriptional layers (in the middle) and to distribution and data storage layers (at the level of repository backends).
Join the dialogue
We invite people who have an interest in future, advanced forms of interaction with "intelligent" content on the Web, and how such future forms of content can be managed. This sounds very futuristic, but here is the qualifying statement: we want to show practical pathways for current CMS technology providers to move to such advanced platforms piece by piece, in manageable steps! That's why we need the practitioners amongst you, too!
The IKS Thesis and Approach in a Nutshell
This is a good document to start with for a basic understanding of IKS the project. It takes a closer look at the vision, goals and implementation plan of the IKS project. The document is structured according to the sections: Executive Summary, Main Innovations, Success Indicators, and Implementation Plan.