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…

 →

Allow users to build knowledge graphs with their notes

 →
#
>

Allow users to check that their knowledge graph is a category, and treat it as one

→
#
>

do I mean bicartesian closed category?

→
#
>

this would probably be in the category of “sets of notes”, and if a user has not stated a relationship between two notes, then that relationship can return the “empty set”

→
#
>

this also means allowing for users to treat combinations of notes like notes of their own

→
#
>

AND

→
#
>

[[organization]] [[meeting]] [[date]]

→
#
>

If in one block I link to all of these names together then I am essentially linking to this page which is an AND of all these three other pages

→
#
>

The key functionality here is for Logseq to treat this combination page like it is a page of its own, and allowing for natural navigation to related pages.

→
#
>

Related pages include: [[organization]] [[meeting]] to zoom out to all meetings with that organization

→
#
>

This is different from namespaces because we don’t want to dictate a hierarchy:

→
#
>

[[organization]] [[date]] and [[organization]] [[meeting]] should be “siblings”

→
#
>

[[organization]] [[meeting]] [[date]] does not need meeting to be the namespace for date or vice versa

→
#
>

allowing for links in names should take care of a lot of this

→
#
>

OR

→
#
>

[[organization a]], [[organization b]], [[project c]]

→
#
>

this is a bit harder, but I think it could have some interesting uses

→
#
>

The default syntax for this feels like it should be to use commas

→
#
>

This is OR page is then treated like a page of its own

→
#
>

notably a link to any of the pages in the OR page shows up as a reference in the OR page

→
#
>

this is different from AND because only references that mention all of the pages in the AND show up in references

→