We are starting this journey using our WordPress blog jrnl both as a place for discussion and implementation and testing of text interaction ideas. initial functionality : glossary Authoring The user will select any text while authoring and in the text tools dialog a ‘g’ will appear, which the user can click on to view a list of all posts which have been categorised in the [Glossary Term] Category. Selecting such a term will mark the selected term has having that Glossary Term associated with it. Shane, how should we do this exactly, how should it be marked up? Creating a Glossary Term Creating a glossary term…
- API, Authoring, jrnl, Perspective, RFC
The “htx” parts in digital_publishing_workflow_tools with the earlier predecessor automated_digital_publishing comprise the early stages of a system that implements an abstract capability architecture standard (think POSIX) around the notion of small, independent tools/components supporting each other to perform higher-level operations. The goal is to build an Open Hypertext System for document aspects to follow later once the foundation is in place. Integration can happen by adding a capability implementation or the whole system to an existing application or to call it as an external function/service. Another way would be to register an existing application or capability as the implementation for the system to invoke it, which requires the conformance of…
This is a first explanation of the Graph API that I’ve added to this blog to allow it to be explored within our Liquid Space interface. To try it out, go to http://liquidspace.global/ and use the [G] icon in the tools menu, and enter this “endpoint” https://jrnl.global/wp-json/graph-api/v1/query This lets you explore this blog as a graph. Currently it’s really inefficient in several ways, but the ways to optimise it are obvious, but not worth worrying about until after our Demo in December. It also has a feature that lets you request a list of types from the blog, and retrieve nodes by type. I think I want to get rid…
A WIP implementation of hyperknowledge api can be found on gitlab. See in particular the OpenAPI specification (yaml) and the section on the event model (see source).
Things to have relationships with in the glossary
So, we have this now in Liquid | Flow. Select text, keyboard shortcut for the menu and then simply ‘g’ for Add to Glossary. In this case I’ve added Chris: At the bottom we have this pop-up for relationships which is are so far only relationship terms for concepts. But what about for other types of entries, such as people (in the case of Chris), places, documents, things, projects, companies and so on? How should we organise the types? For example, if the entry is about a person, we should have at least these options for defining the relationship with another entry: Works with Works for Works on Created Created…