Demo@50 | Doug Engelbart | The Demo | What Is Still Missing | What We Are Building | The Collaboration | Who We Are


What We Are Building : 21st Century DKR



Our aim is to start building infrastructures and services to enable a DKR fit for the 21st Century. We aim to do this by integrating with and extend current infrastructures and projects to make it possible to deliver at least some of the functionality described in What is Still Missing. During these early days we are looking at what is possible, what is useful and what reflects Doug’s vision to inspire, not simply impress in a flashy ‘demo’ but to truly demonstrate something useful. We have no finish line, the 9th of December 2018 is simply a useful deadline to get as far as we can by then – we aim to continue this work into the forseeability future.


We are planning to discuss the work (through requesting interviews which will hopefully lead to useful dialogue) with a wide group of people to get many different human perspectives on what and how we should build on Doug's work – the issues are too wide and varied for us to simply start building tools. However, this will not stop us getting on with the job as best we understand it, the dialogue will help shape the continued development.


The record of the dialogue with the wider community plus our own internal dialogue will go into some sort of a ‘Journal’. If we have the time and capability we will also invite the general visitor group for the event to add to this Journal.


We will work on inter-operability of our personal systems - what we are building is an ecosystem, not a monolithic system, however, some of us will also build a basic open OHS system. Ideally, the software should be available to use right after the demo.





This demonstrates a basic 'wireframe' of how we see the demo going. The magic of how we hope to inspire the audience will come from how powerful each aspect turns out to be:


  1. The demo will start with a user going through a linear traditional document and doing advanced operations on it to explode it into powerful views, in order to better understand an issue and the issue is how to continue with the project after the 9th of December.
  2. User enters into one or more knowledge graph spaces to further increase understanding.
  3. User then produces a document (a frozen view) based on their understanding.
  4. This document is then shared with another user (also on stage) and the Open Source and legacy compatible mechanism of the sharing is made clear.
  5. The second user performs similar operations and additionally annotates and adds comments or other information to the document and sends it back to the first user.
  6. Along this path it shown and demonstrated how a large number of users can constructively engage with the data, on disparate platforms and systems.


What we aim to demonstrate through this very basic workflow will be:


  • Powerful collaboration systems for large numbers of users to deal with complex issues.
  • Real utility for the users to better approach complex problems, through powerful dynamic interactions of Views both with symbols and other visual means, in document and knowledge graph spaces
  • A capability infrastructure which enables such augmented work, including high resolution addressing and other features Still Missing.


“Better and Perfect are the enemies of What-Is-Actually-Needed”
Alan Kay





The work is mostly about interoperability between projects we are building separately, as listed here:


Projects on Google Spreadsheet






There are many different perspectives coming together and to build we need to be able to use a vocabulary. Our initial way of trying to create this vocabulary is simply by listing each term used (conceptual or specific implementation project) here and have the definitions in the Journal Blog under the Category Glossary Entry: DKR Glossary


To add to this list please email the webmaster ( to get an account so you can start posting. PLEASE try to link to the Glossary Entries we have here in your own Diagram, so that we are working in the same conceptual space.


 Document Diagram | Info Flows | DKR Components





Don Nielson suggested three levels of discussion, which we are using here, of which the above mentioned DKR fits in all levels for different parts of what we are working to build and present:


  • 1 repeating HISTORY We ask the question: What did Doug and his team demonstrate either at the demo or perhaps beyond, which is not available now, with the aim to bring to life as much of that as possible?
  • 2 pondering COMPLETION What of Doug’s vision was never realized, either in his mind or in a more absolute sense, and can that shortfall be demonstrated today?
  • 3 forecasting a PROJECTION What of the future, striving to meet his original expectations or natural extensions of them or even something more bold? What can we extract and project from that? This is a section for the long-distance thinkers...