Building a knowledge graph in Logseq →

Proposal for a knowledge graph plugin

→
#
>

Implementation priorities

→
#
>

Make relationships visible on any page that has them.

→
#
>

From what I can tell plugins can’t integrate into pages yet, but I think ideally there would be a section above “Linked References” that shows “Relationships” and all the pages with relationships to this page grouped by relationship type (Supports ->, <- Supports, etc)

→
#
>

Create a query interface.

→
#
>

First basic single queries (all notes that support note x)

→
#
>

Supports chained queries

→
#
>

Return all blocks that support any blocks that have author)

→
#
>

Support AND and OR on pages (all notes that support block x OR block y)

→
#
>

Create a graph interface

→
#
>

See a visual graph of all the pages (and blocks) with their labeled connections

→
#
>

I believe this would be more valuable than the existing global graph

→
#
>

Option to change the syntax for identifying directionality

→
#
>

Users may not want to use ->

→
#
>

Users may prefer to use semantic complements like in discourse graph (supports and supported by)

→
#
>

This could be done by creating a special reserved relationship called complements, and allowing a user to create a complement as follows

→
#
>
- [[supports]]
	- [[complements]] ->
    	- [[supported by]]
→
#
>

and now the plugin can treat the following two aspects as equivalent

→
#
>
- [[some evidence]]
	- [[supports]] ->
    	- [[a claim]]
→
#
>
- [[a claim]]
	- [[supported by]] ->
    	- [[some evidence]]
→
#
>

Allow for blocks to be part of the knowledge graph like pages

→
#
>

Requires updating the query

→
#
>

Requires figuring out how to handle when a block contains text and page references, both the block and the page references will be considered part of the relationship? Not sure.

→