proto-DKR : Guiding Principles

 

This is the Spec as gone through with Doug Engelbart July 2004.

multiple authors

This should not be a system where one person controls the flow of information in (adding resources, blogging and making comment), and out (constructing views; any participant should be able to generate (and access others') editorial views of the information.) like the production of a normal web page would be.

powerful query options

The system should support more and more advanced queries to be made of the MySQL database.

facilitated evolution

scalable
We have to make sure it won't get stuck in any initial technical or working paradigm.

changeable
Modular code and architecting needs to allow for the evolution of the system, with open, clear APIs.

opensource
OpenSource to encourage further open evolution of the system, after the initial version is built and tested.

object oriented
Allows for the changing of the data, data types, tools and functions.

internet standards based
We will mess up. Other systems and other functions will prove more valuable. Therefore the data will always have to be exportable via common internet formats such as XML.

legacy support & gradual adoption support

These systems will not be adopted if they require organizations to throw away all they have now, so it's important to integrate with current practices and formats. Initially that means that the system should work through standard, modern web browsers.