Organic Ontology
We are pursuing the vision of a generic organisational framework composed of people working together on their projects and organisations in a defined unified way, which we shall attempt to describe in this article. The global Web3 movement and our local wiki organisation ideas form a part of our shared vision, but it is important to understand that we are not talking about a specific technology here, but rather a way of working which can be encapsulated by, or implemented within almost any collaborative environment. The key is in the definition itself and the ability for all members to work in accord with its current state and for it to be able to undergo refinement through collaboration.
The definition of this system undergoes continuous refinement as we use it to organise and manage our own jobs and projects. There are a number of top-level aspects to this way which we call classes. The whole system is encapsulated in an overall tree structure which we call the Organic Ontology, eventually we hope for this structure to be defined to the extent that a complete description of the system can be exported in an official ontology using Web Ontology Language. This exported information can then be importing into other high level environments such as project management and scheduling software, or other interactive environments like Croquet.
About the structure
The current tree is basically a two-level category tree using Category:Classes as the root, but the class nodes in the tree link to their portal article instead of the usual category page. Each of the classes have their subcategories shown within their tree node, but this level just links to normal category pages not to further portals.
Current structure
The current version of the ontology in as a TreeView is in the Tree:Ontology article, and is transcluded below. Each item in the top level is a class.
Plurals
The tree is a query of all the items in the Classes category, but those items are all named as singulars (because the names describe insgular instances, i.e. an article is a person, not a people). But the category and portals are named as plurals because they represent groups of instances. We've used the Plural template to transform a name from singular to plural.
