Ok, to go on now it is really necessary to recap and put order in all that stuff I wrote about up to now.
Composable information theory is just my idea to represent evolutionary and relational information derived from the interaction with the abstracted virtual world. It is something like applying collaborative info collations (information unit chains) with an intelligence working with it.
Has been now understood that somewhat logic able to work with these information unit chains is needed. It is necessary to define this "logic" before proceeding.
Monday, December 24, 2007
If I remember correctly, two of the 5 tiers in a J2EE architecture are the resource tier and the business logic tier. So, in the resource tier normally we have informations stored in different types of repository. The other tier contains only the logic to manipulate data, and infact it is called business logic tier. Then we have a SOA architecture where all business logic functionalities are kept connected and available as services, but this is another story. Ok now, as here we have no client tier by now, no presentation tier, no integration, by now, let's remap the structure organized by the composable information units into the resource tier while we need to map the logic to manipulate this structured tree of data, into the business logic tier. This second remapping action is the second ingredient of two in the mix I told about before.