Graph-as-infrastructure
versus
Graph-as-diagram (diagraph?)
What if part of the problem is that we conflate graph structure (a -[r]-> b) with the visualisation of the graph? Sometimes these are do match but other times we need distance from the structure in order to model diagrammatically. We could mix graph + SVG shapes + text.
We could think of graph-as-diagram as separation of concerns from the graph structure itself ...
Wouldn't it be interesting to see a knowledge graph version of Da Vinci's notebooks where ideas, trains of thought, work sketches, etc., can be traced through his entire corpus?
E.g., show on a timeline all drawing and writing on the Sforza monument + related material.
A panel in two parts where you can see events both on a map and in a timeline. They are synched.
You can add event streams based on people, places, actions, etc.
You can filter streams by date ranges, geographical areas, entities, etc.
Of course, the content of this panel can be piped (UNIX-style) to any other panel.
In fact, this will be one of the primitives of the system.
You can also zoom in and out semantically. Imagine starting with all "sieges" visualised and then pulling back and seeing all "military actions" of any kind.