• Implicit Linking

    Let users select any arbitrary text and perform searches based on the text, such as we have experimented with for Liquid | Flow and in wordpress here wordpress.liquid.info both of which are already developed and owned by us. A blog post with illustration of the blue dot. This is a Doug Engelbart Term. https://www.theguardian.com/technology/2004/nov/18/onlinesupplement 
jrnl post Category: Implicit Linking

  • Document ViewSpec

    A flexible view where the user can control the presentation of the article, including collapsing into outline modes, expanding into Flow mode, colour coding of key text and more. This is a Doug Engelbart term. Cited from Authorship Provisions in Augment jrnl post Category: ViewSpecs

  • High Resolution Addressability

    The ability for a link to be created which does not just link to the document but to a specific section within the document, such as a paragraph or a sentence, so that the reader can instantly jump to the cited section. This is a high-resolution version of pages in physical documents and can be used for further interaction. Related to the issue of pointing and addressing: http://wordpress.liquid.info/the-fine-art-of-addressing/ This is a Doug Engelbart term. jrnl post Category: High Resolution Addressability

  • RFC: Glossary Data Formats

    First stage For now, we can use the following format to specify glossary entries for the Journal: <dl> <dt>Media Fragment</dt> <dt>Media Fragments</dt> <dd>Paragraphs, datasets, images, topic maps, glossaries… that go into forming one or more document(s).</dd> <dd>This glossary entry is a media fragment, and each of its parts could be as well.</dd> </dl> As the Journal is currently stored in WordPress, we might use its data model to some extend, but will abandon that more and more by abusing it as generic online data storage, where any arbitrary data is stored in the content-body of a blog post. This will render all plugins, themes and administrative tools on the server…