The understanding towards "Type" #1066
kachunchan-analytics
started this conversation in
General
Replies: 1 comment
|
Hello, Tolaria actually predates OKF. In the repo (and in the getting started) there are various walkthroughs that show how I use types for my own workspace, but ultimately they are a device for organizing notes, so it's up to you. A note should belong to a single type, so you may consider these akin to tables in a database. More docs here: https://tolaria.md/concepts/types |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I could see Tolaria put quite a lot of focus on using "Type". It was quite a new concept for me so I explored this concept through different documentation (including the official ones). And eventually I came across Google's Open Knowledge Format (OKF).
I am not sure if Tolaria's application of "Type" were originated from OKF. But if it was indeed, Tolaria seems deviated from the original purpose and intention of OKF (e.g. bundle, concept, routing)
It would be great if Tolaria could put more explanation or examples in their documentation page, so their philosophy or opinionated way of using "Type" can be revealed.
Good To Know:
https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/README.md
https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md
https://github.com/eugeniughelbur/obsidian-second-brain/blob/main/references/ai-first-rules.md
All reactions