RFC for a system which support object persistence across a workflow of multiple views. A central idea is that while having different views of your information, this is particularly the case if the information is actually the same and only the views change: A term is always the same ‘object’, whether in a glossary, a Liquid Space view or in a word processing document, and can be interacted with as thus.
The central connector of the system is graph view called Liquid Space: liquidspace.global
User create and save nodes as ordinary WordPress posts, allowing for openness and interoperability. This is referred to as the hyperGlossary method: hyperglossary.info
Users can create a node/element manually in WordPress or by using Liquid | Flow (or any other software) to create a structured node with indications of type and type of connections: liquid.info
Accessing The Liquid Space View
From Liquid | Author (or any other software which supports this), a user can click on a term and choose ‘View in Liquid Space’ and the software will send a URL to the user’s web browser specifying the term as a node to be shown centrally and (optionally, which type of view to show if not the default, how many connections deep to show the connections and so on).
User can select a term and a blue dot will appear. An option will be to ‘Show in Liquid Space’ and it will show the Liquid Space in the same way as if launched from the word processor. This is with the same interaction as we have on wordpress.liquid.info at the moment.
User can additionally click to download a PDF from a repository and the plugin will take whatever meta-information for citations (linked Bibtex etc.) and append it to the PDF on download so that in the future when the user copies from the PDF they will copy as citation automatically (with supported PDF reader) and the Liquid Space will be able to open the document for the user since it ‘knows’ the local location of the document.
The plugin will also support augmented copying to allow for quick citation-paste.