Ian McNicoll wrote: > Assumed value: This is a statement in an archetype which asserts what should > happen if a value is missing. It can really only apply safely to an element > is Observation/State or in a Cluster archetype intended for use in state.
Ian, it's not only CLUSTER archetypes that can appear within the state of an OBSERVATION archetype: * An ELEMENT archetype can similarly be slotted into the OBSERVATION.state. * We should also allow it in EVENT.state. (That's the "Person State" check box that you see in the Archetype Editor when working on an OBSERVATION.) * The Person State can be defined by an embedded archetype of type ITEM_SINGLE, ITEM_LIST, ITEM_TREE or ITEM_TABLE. So if the idea is that assumed value should be used only to describe state, then I think that the complete list of places where it would be needed is in: * OBSERVATION.state * EVENT.state * CLUSTER archetypes * ELEMENT archetypes * ITEM_SINGLE archetypes * ITEM_LIST archetypes * ITEM_TREE archetypes * ITEM_TABLE archetypes Peter
