Putting THEE into Software

The Proposition

THEE is a system of systems.

So it ought to be natural for a software version to be developed.

However, THEE is unusual and complicated which raises issues of feasibility and cost.

Goals

The major benefits of programming THEE could include:

The precision demanded by representation in software will force greater clarity on myself, and bring new taxonomic issues out into the open—it may also raise challenging issues of computability.
Even partial success should help taxonomic investigators by enabling rapid juxtaposition of similar elements and movement around the architecture, so as to reveal interactions, associations and new relationships amongst elements.
Success should enable visualizations and animations that will help people grasp and apply taxonomic frameworks more easily, and see themselves as part of humanity in a refreshing and fundamental way.

There may also be other potentials in relation to artificial (general) intelligence, the semantic web's need for taxonomies, and commercial possibilities of various sorts.

Requirements

The Architecture Room is generally about clarifying fundamentals of the taxonomy. It treats THEE as a «scientific object».

Coding is not something I have any expertise in. However, I am sure that the primary requirement in coding THEE within a database and having a usable interface is to grasp what is involved.

Like the Periodic Table of Chemical Elements, the taxonomy of human elements is not a simple parent-child structure. In devising any system, it will be essential to ensure that relationships are properly incorporated.

Most of the relevant knowledge and information is provided elsewhere in the Architecture Room. This section is specifically about providing additional ideas and information to support the coding effort.

So far, I have provided:

A list of elements with formulae.
Some ideas for the inputs and outputs.
A possible way to dramatically reduce the number of elements.

Posted: 9-Jun-2013