Frode’s Doug Priorities

Here is my list of what Doug had which I think we should work to implemented.

Link Related

  • High Resolution Linking, so that a link can point to a specific sentence, paragraph or any other object within a document, not just to the document as a whole. We should at least implement paragraph level addressability in wordpress. Potentially the Time Browser with real-world time code inside media should be added to this to provide high resolution temporal linking.
  • Implicit Links through which the user can choose to view any corpus entry the text is implicitly linked to, such as a dictionary entry or a glossary entry. This is what my Liquid macOS utility does and I would be happy to extend its functionality.
  • Glossary System where the user can easily add to their glossary and insert/use items and readers can access. This also seems like a natural feature to build in to wordpress. My project is called Liquid Glossaries.
  • Links in Images. It is of course possible to create image maps but the current tools do not support this for non-graphics people. Doug had the example of showing a basic map where each location name could be clicked on to jump to its corresponding document. This is not quick to do today but we can develop something like a web Scapple I think.
  • A Journal which is a repository to which documents can be posted but cannot be deleted, only increased in version number if a new version is submitted. A basic and robust versioning system. I would also like to add a way of publishing documents where the name is a unique, universal ID so if the initial host disappears the document can still be searched for on other hosts. This relates to my Rich PDF project as well.

Threaded Dialog with Advanced Views. Not explicitly written by Doug but which I think is cruelly important is to build a dialog system (in wordpress or not) where users can choose to see a thread by people, topics, keywords or any other criteria.


These are very much what my Liquid Views PhD project is about;

  • Rich ViewSpecs to allow the user to decide how to view a document, including options to show only the first sentence of every paragraph and so on.
  • User-Specified Content Filters. A simple content-analysis language may be used in a ‘Set Content Pattern’ command, which compiles a little content-checking program. One of the view-specification options will cause the system to display only those statements which satisfy both the structure and level conditions imposed by other viewspecs, and which also pass the content-analysis test applied by this program. Where desired, very sophisticated content-analysis programs may be written, using a full-blown programming language, and placed on call for any user.


  1. I agree with Frode that these word processor add-ons should be available on a global scale. That is only achievable the 124 word processors developers, whose programs are still in the marketplace. I would recommend that the Doug@50 group, as an open-source group committed to achieve the ‘greater-good’, prepare a Developer Guide of the add-ons functional specification, including illustrative use-case scenarios, distribute it to all existing word processor development teams. Once in the hands of all remaining developers, the marketplace will determine their true value and we will have maximally helped Doug achieve his unfinished quest.

  2. In terms of “threaded dialogue”, Doug was a huge fan of Jeff Conklin and the IBIS “structured dialogue” approach. Threads are just one part of the concept; nodes (think: tweets with explanation) are typed, e.g. questions, answers, pro or con arguments, meaning that the arcs between nodes were also typed (meaningful).

Leave a Comment