ITEM_STRUCTURE & ITEM / CLUSTER / ELEMENT
Needs:
- solve the pizza problem - multi-value items
- ITEM_SINGLE, ITEM_LIST etc are not used much in archetyping, and are also not flexible enough because they cannot occur anywhere in a CLUSTER structure
- add a type that is a mixture of CLUSTER and ELEMENT, i.e. has a value and also children, to allow for the fractal nature of data, with a 'summary' value, plus underlying detail
The current data structure models are shown below.
Candidate A - make ITEM_STRUCTURE inherit from CLUSTER
Proposal - Thomas Beale
Status - under construction
Design concept:
- Keep ITEM_STRUCTURE and chilren, but just make them a variety of CLUSTER. Impact remaining model as little as possible.
Changes:
- ITEM_STRUCTURE now inherits from CLUSTER.
- all static declarations in the remainder of the RM for ITEM_STRUCTURE changed to CLUSTER. In theory they should stay ITEM_STRUCTURE, but the problem is that with no static declarations anywhere for CLUSTER or ITEM, CLUSTER archetypes have no place to go, and the CLUSTER type is not detected by my current 'type closure' detecting algorithm. This should probably be changed.
Impact:
Component
|
Impact
|
On RM
|
|
On existing archetypes |
|
On archetype tooling |
|
On existing RM-1.0.2 based software |
|
On existing RM 1.0.2 data |
|
