deniz
Search Results

Discourse Graph

#
>

https://oasis-lab.gitbook.io/roamresearch-discourse-graph-extension/guides/querying-your-discourse-graph

→
#
>

relationship/by ->

→
#
>

Joel Chan

→

↑ 9 References

Building a knowledge graph in Logseq →

A basic, no-plugin version

→

Syntax: relationship + arrow

→ Pros →
#
>

Familiar to Discourse Graph users

→
Building a knowledge graph in Logseq →

Proposal for a knowledge graph plugin

→

Suggested Principles

→ Keep the grammar non-restrictive and let users create relationships between any two notes by… →
#
>

Downside, it would be harder to add inline CSS for links like Discourse Graph does

→
Building a knowledge graph in Logseq →

Proposal for a knowledge graph plugin

→

Implementation priorities

→ Option to change the syntax for identifying directionality →
#
>

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]]
→
Building a knowledge graph in Logseq →

Proposal for a knowledge graph plugin

→

Suggested Principles

→ Keep the grammar non-restrictive and let users create relationships between any two notes by… →
#
>

For one, a non-restrictive grammar allows users to not have to create prefix links in the front of every linked note like in Discourse Graph. This will be beneficial for use cases that want to connect a large volume of notes in their knowledge graph but don’t want to be restricted to a specific note naming system.

→
Building a knowledge graph in Logseq →
#
>

This is a generalized knowledge graph proposal based off of the work on Discourse Graph by Joel Chan and David Vargas, so thank you to them. Other inspiration is listed in: # Resources

→
Building a knowledge graph in Logseq →

Resources

→
#
>

Discourse Graph

→
Knowledge Graph Systems →
#
>

Discourse Graph

→
About this website → I make some of those notes public → Some nice things this system will hopefully one day support → Displaying rich link types →
#
>

e.g. Discourse Graph, or Semantic triples

→
How Logseq should build a World Knowledge Graph →

[[Logseq]] has a stated goal to build a [[World Knowledge Graph]]. Here’s what I think they…

→

Create a general knowledge ontology that users can create translations into

→
#
>

for example, a general ontology may be like Joel Chan’s Discourse Graph (types: question, claim, evidence, etc.. relationships: supports, opposes, informs, etc)

→
#
>

if a user can translate their knowledge graph into this “discourse graph ontology”, then other users can see how to utilize that user’s knowledge graph in the context of a discourse graph ontology

→
#
>

a user could create this translation / functor by describing how that user’s knowledge graph types and relationships map to the general ontology’s types and relationships

→

Receive (occasional) updates on my work

twitter email linkedin github