Categories database
From WhyNotWiki
This is an important table! Almost all of my other tables will link to it!
[edit] One ontology to rule them all
I want to have one ontology to rule them all. By "them all", I don't mean everyone else in the world -- I expect there would still be a need, most of the time, for each individual person / organization to have their own ontology / category tree.
What I mean by this is simply that once a person creates an ontology for themselves once -- their abstract representation of the world they live in -- they would never have to do it again. Everywhere that needs tags/categories/an ontology would share the same one. All applications would tie into this same table/database so you wouldn't have to recreate your nice organization in every application that you use.
In other words, don't repeat yourself!
Examples...
- Your wiki would use this database for organizing / classifying content
- Your book collection would tie into this database for categorizing/labeling books with topics
- Your to-do lists would use it.
- Your file system would mirror it / synchronize with it (although it probably couldn't tie into it natively)
- You would use the same list/tree of projects across your to-do list, your wiki, your blog, your file system (where you actually do your work/development on these projects), your password manager, etc., etc. They would all be parallel; they would all be in sync...
Unified. One list. One place. Once. Only.
See also: wherever I wrote about the problem of parallel "folders"/hierarchies across several different domains/applications...
[edit] Fields
Importance/weight
[edit] Data
Marketable ideas (Private = true)
Category:How stuff works (Importance = 0.8)
Aliases: Topics database, Tags database, Categories database, Topics tree, Master topics tree
See also: Relationships database
Categories edit (Category edit)
