In theory, in a Linked-notes system can be used also for journaling, task management, people relations (CRM) etc.
Notes-can-store-structured-information-in-YAML-header. YAML schemas could be used for different entities (people, books, …), and even type validation for YAML values. Things like Obsidian Dataview allow you to query notes, but the query language is non-standard: Files-should-outlive-the-application. This remark plugin allows you to lint frontmatter based on defined schemas.
uid: 123456 type: note schema: type: person first_name: George last_name: Michael from: Cyprus phone: 123456 # ...
uid: 123457 type: note schema: type: book title: Agonies of a millenial author: [[George-Michael]] publication_year: 2023 # ...
How does one keep the YAML header thing from exploding? This can easily end up in a terribly convoluted situation, especially without strong typing and consistency. But strong typing and consistency without a careful thinking leads to other problems in itself. You very soon end up with taxonomies and their problems.
How do you get the perfect thinking API without killing it’s simplicity, responsiveness, and immediacy?
Related wikipedia topics: knowledge graphs, knowledge base, entity linking, information science, information theory, note taking
Schema validation repos:
Links to this note
To use Writing-as-a-user-interface-that-facilitates-thinking effectively, we should be able to find information flexibly in our notes. We should be able to do searches similar to: FIND notes that contain "deep learning"...