A 21st Century Dynamic Knowledge Repository ‘DKR’, will have some differences to Doug’s model, which was created in an era of mainframes with limited bandwidth, processing capacity and ecosystems. Note, the term ‘document’ as used here refers to any data set which can be stored or transported on its own but does not at all need to carry the baggage of the term and is expected to evolve substantially.
A dynamic knowledge repository is a living, breathing, rapidly evolving repository of all the stuff accumulating moment to moment throughout the life of a project or pursuit.
These are the criteria as we understand them at the end of 2017:
• The system needs to have provisions to co-evolve with the end users
• The system needs to be explicitly designed to bootstrap itself into ever more powerful versions
• The design direction is to imagine and build powerful tools first, then on making them as useable as possible second
• The design direction will furthermore focus on high performance users while always allowing novice users basic interactions
• The DKR needs to support the CoDIAK process of concurrent development, integration, and application of knowledge
• The focus needs to be on rich interactions, where the user should be able to achieve high performance through powerful tools, not on ease-of-use for the sake of it
• Creating powerful views, or ViewSpecs, of the information space is a prime challenge
• Representing, analysing, creating and modifying information connections through links, associations, bindings, dimensions, searches and more, will further be a prime interaction challenge
The system will need to support multiple data spaces, including but not limited to:
• Live Database Interaction of Knowledge Gardens
• Collaboratively authored Documents
• Individually authored Documents
• A Journal for publishing Documents which are highly interrogable with a robust versioning system
• All current and future media types and meta data
• All material needs to be archived in a usable and accessible way for the distant future
• The system needs to be able to interchange data with legacy systems
• The system needs to be able to interchange data with different components among a heterogenous DKR
• The DKR will be heterogenous, meaning that anyone can build components
• Must be massively scalable and robust, in order to deal with ever growing profusion of data and links.
Questions raised from Dialog
Vint Cerf asks: “What kind of scaling problems might we encounter? will increasing numbers of documents produce increasing amounts of references that have to be repeatedly updated? the one-way links of the WWW escape this problem at the cost of broken links and lack of backward references.”. This was entered in the list as ‘Must be massively scalable and robust, in order to deal with ever growing profusion of data and links.’ In the Underpinning This section.