fixed: backlinks are now in their own group at the end of pages, to be compatible with popular graph based app.
Next is to add short transclusion for points (aka regular blocks in other apps)
@brunowinck@syncretizm@Obsidian the layout engine has several layout mode (cf @Olicav books for more ideas) and is coded in wasm for blazing fast speed.
It's not adapted from a data visualization tool but a visual thinking took. It makes a _major_ difference.
@brunowinck@syncretizm@Obsidian Templates and scripting have direct access, including the semantic inference engines
It's a plugin, you reuse the components to build one of your own, or add a new visualization mode
../..
@brunowinck 2/ It's not made for academic writing. There is a powerful system to link ideas, sources, claims, but the goal is not to maintain a zettelkasten, permanent notes and finally produce papers, thesis or books. That's what roam does better together with @JoelChan86 work
../..
9) The night brought the solution for the third edge, sufficed to add a simple form building the passive wasTaught link, no coding.
I'm still puzzled by the result. A link to statement links all the relations like an umbrella.
8) with predicate forms and less tweaking it's possible to do more from a single statement.
Last relation (topic <-> student ) will be for tomorrow :)
8) with predicate forms and less tweaking it's possible to do more from a single statement.
Last relation (topic <-> student ) will be for tomorrow :)
7) Playing with facets (similar to Shapes in Shakl) can be claimed or inferred. That's what make group of attributes @ relations easy to organize.
Syntax had to be tweaked to fit in repl.
Next are predicate forms ...
@ZornGerhard@codexeditor@brunowinck@neo4j It goes in this direction but there is no node supporting the 3 relations. The node would be a teaching, with a teacher, a student, a topic, a time etc ..
6) A new relation is created
Leonardo taught drawing
and a relation between two relations (Leonardo taught Drawing) relates to (Leonardo taught Boltraffio)
In the spirit of what rdf-star does. AFAIK noe4j can't do it.
A statement (pointType) was attached with the text.
@codexeditor@brunowinck@neo4j It's maybe not the best use case in @kneaver either because it creates a disymmetry in the schema.
Next I'll look in shapes (what I call facets)
@codexeditor@brunowinck@neo4j what I was not sure is the subject of his teaching. I'll have to check.
So Leonardo, Boltraffio, and Drawings as vertices, and 3 edges joining them?
What if the information comes progressively? Do you need a preconceived design?
4) more complex, relations can have semantic attached like being the opposite of another. This allows to inform in one direction and query in the other
4) more complex, relations can have semantic attached like being the opposite of another. This allows to inform in one direction and query in the other
Little experiment. I wrote a REPL (instant interpreter) to have direct access to Kneaver Semantic graph/NLP features.
First detecting errors :) and warming up my sharing process