Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| projects:quantum:knowform [2026/05/21 07:32] – [Design] kymki | projects:quantum:knowform [2026/05/21 07:34] (current) – [Current State] kymki | ||
|---|---|---|---|
| Line 44: | Line 44: | ||
| Rust was chosen because the project depends heavily on type safety. The data model has many entity types and relationship rules, so compile-time checks are useful. Rust also fits the performance side of the idea: ingesting larger datasets, processing relationships, | Rust was chosen because the project depends heavily on type safety. The data model has many entity types and relationship rules, so compile-time checks are useful. Rust also fits the performance side of the idea: ingesting larger datasets, processing relationships, | ||
| + | |||
| + | Also writing Rust code makes me happy. | ||
| ===== Ontology Support ===== | ===== Ontology Support ===== | ||
| Line 57: | Line 59: | ||
| ===== Current State ===== | ===== Current State ===== | ||
| - | Knowform is a personal | + | Knowform is a piece in a framework |
| The main value of the project is the architecture and the exploration of how organisational knowledge can be modeled as a graph. The codebase contains support for REST endpoints, JSON ingest, graph construction, | The main value of the project is the architecture and the exploration of how organisational knowledge can be modeled as a graph. The codebase contains support for REST endpoints, JSON ingest, graph construction, | ||
| - | Some parts are still rough. Some model fields are pragmatic rather than elegant. The project also reflects experimentation with graph theory, category theory concepts, and Rust application structure. | + | Some parts are still rough. Some model fields are pragmatic rather than elegant |
| ===== Direction ===== | ===== Direction ===== | ||