|
The data for an entity is encapsulated in the order of its derivation from the basic
ENTITY, from left to right. This is in the opposite order of the derivation of the identifier. The data for
ENTITY is written first, followed by the data for the class directly derived from
ENTITY, continuing down to the leaf class. For readability in the SAT file, each data field is separated by white space: a space, carriage return, or new line.
|
|
|
Because it is known that the encapsulation (and derivation) starts from
ENTITY, the
ENTITY save identifier is not written. In figure 9-1, this is shown in the middle by the empty double quotation marks, ("").
|
|
|
|
|
Figure 9-1. Format Entity Record
|
|
|
Starting from inside and going out, the
ENTITY data is preceded by identifiers and is followed by the data for the identifiers. The identifiers correspond to classes derived directly from
ENTITY. This type of encapsulation continues for all class derivations until the leaf class is reached.
|
|
|
In figure 9-1 for a SAT file, the class identifiers are separated from one another with dashes, while their data fields are separated with white space. The white space is typically a space, but may also be a new line. The last element of the record is the terminator character (#).
|