Hi Andrew
The principles of specialisation have been described in our development
environment and there is a placeholder for the documentation in the
archetype system document.
Our initial thoughts are at:
http://www.deepthought.com.au/it/archetypes/output/specialisation.html
The rules that
Op zondag 29 mei 2005 23:42, schreef MD:
What information consumes is rather obvious: it consumes the attention of
its recipients. Hence, a wealth of information creates a poverty of
attention and a need to allocate that attention efficiently among the
overabundance of information sources that
Maybe the amount of Entropy (disorder) is reduced by information but
increases by too much data? I agree that one should be offered the
information that one needs at a given time but that implies that one can
define the scope in the information request,
Best wishes
Nick
- Original Message
Not necessarily - it is the 'stuff' that surrounds information that gives
meaning. Reduce too far and information loses its context and is at risk of
being meaningless information - a blood pressure of 120/80 is meaningless
unless context is supplied? Ape, human, earthworm about to explode!
To
The message did not appear on the list at first send, so I try again
Bert
Op zondag 29 mei 2005 23:42, schreef MD:
What information consumes is rather obvious: it consumes the attention of
its recipients. Hence, a wealth of information creates a poverty of
attention and a need to allocate
Hi Ed,
One needs to distinguish between System Designers and Application
Designers and both can be
subdivided further, e.g., Fault-Tolerant. System Designers 'handle' the
data and information;
Application Designers 'handle' the content.
Understanding the difference between data and information
6 matches
Mail list logo
