Current solutions also lack interconnectivity. Many files are divorced from context; cast into a drawer, rather than methodically fitted into a broader framework of knowledge. Knowledge trees can create pseudo-relationships between files nested within a given hierarchy, but these are not explicit, and can only describe a vertical ‘parent and child’ taxonomy. Some tools, such as web pages and wikis, also allow for orthogonal linking between related files, but this takes place in an ad hoc fashion, and again, there is no ability to explicitly define relationships.

关系明确与否取决于具体的分类目的,每个人的标准都不一样, 这不是简单的扣上一个"父子"关系就可以全盘否定的."父子关系"的表达能力比你想象的要多的多..

A unit of knowledge is saved to a certain file path, which places it within a taxonomy of folders, chapters or categories. Tags may be applied when an item relates to many things, but each file is generally only stored within one nested hierarchy. To access the information, the user must remember where they stored the file, what they tagged it with, or use a search function to locate it.

这是前提, 然而后面提到:

Unlike the brain, the file cabinet approach makes it difficult or impossible to remix or reuse the same piece of information. Each time a change is made to any given file, it has to be tracked down and updated in every location in which it exists. This leads to redundancy, with a cluttering of near-identical ideas, and significant work any time a system-wide change is required.

这里提到的观点与前提矛盾, 一边说文件夹结构仅存于单一位置, 一边又说需要修改文件的各个位置, 精神分裂?

解决该问题的知识管理工具：

• Trilium(Clone)
• TiddlyWiki(标签即文件)
• Workflowy(Mirror)
• Dendron(Alias 未来可能)

基于多级标签的解决方案

• 思源笔记
• Obisidan
• Flomo
• 操作系统快捷方式（如果你把文件夹视为标签的话）