Control Links Technical Guide
Section 2 - BACKGROUND AND MOTIVATION
The concept of <Control Link>s can be applied to a wide range of problems related to representing control over the values of fields and states of SEDRIS objects, as well as representing the behaviour of such control. This overview will begin by discussing <Control Link>s in the context of the three original issues that they were originally designed to address. Readers are encouraged to evaluate <Control Link>s and consider how they might be used or extended to solve their own problems.
The three original issues were:
Transmittals need a mechanism to allow a consuming system to dynamically control objects within a transmittal. The need for this control extends beyond extracting individual <Model> instances for use as "moving models", or objects that are moved through or within the parent transmittal; it includes the need to identify and control the state of objects that are part of the environment that have dynamic behaviour. Examples of these objects include:
Transmittals shall be able to represent how the behaviour or state of one object affects other objects in the transmittal. Examples of such objects include
Transmittals shall be able to represent instances of <Model> instances in which some of the attributes of the <Model> change from instance to instance. This type of <Model> is sometimes referred to as a "smart instance" or "basis set". Examples include: