Chapter 6:
Semantics: Transient Data

6.1 Script Logical Record (SCRIPT)

Script Logical Records are Explicitly Formatted Logical Records of Type SCRIPT that contain Objects that carry textual information. Script Logical Records may contain Set Types Message and Comment.
6.1.1 Message Objects
Message Objects carry messages generated by the interaction of the operator with the system, for example, a "scroll" of the logging session or informational messages concerning events that occur during the session. It is up to the Producer to determine which messages are of use to the Consumer. Figure 6-1 defines the Attributes of a Message Object.

Label Restrictions Comments
TYPE C=1, R=IDENT 1
TIME C=1 2
BOREHOLE-DRIFT C=1 2
VERTICAL-DEPTH C=1 2
RADIAL-DRIFT C=1 2
ANGULAR-DRIFT C=1 2
TEXT R=ASCII 3
Figure 6-1. Attributes of Message Object

Comments:

6.1.2 Comment Objects
Comment Objects carry arbitrary textual information considered interesting to the Consumer, for example, a drilling report. Figure 6-2 defines the Attributes of a Comment Object.

Label Restrictions Comments
TEXT R=ASCII 1
Figure 6-2. Attributes of Comment Object

Comments:

6.2 Update Logical Records (UPDATE)

Update Logical Records are Explicitly Formatted Logical Records that contain information about changes that have been made to Objects in the Static Information. Update Logical Records occur irregularly, usually intermixed with Frame Logical Records, and may require some recognition and action on the part of the Consumer. Update Logical Records contain the Set Type UPDATE.
6.2.1 Update Objects
Update Objects record changes, i.e., updates, that have been made by the Producer to Objects in the Static Information. Use of the Update Object provides both opportunities and obligations for the Consumer. On the one hand, the information carried by Update Objects provides more knowledge about the processes associated with the data in the Logical File. On the other hand, presence of certain Update Objects (for example, those reflecting updates to Channel Objects) requires action by the Consumer. Some actions, e.g., those associated with reading Frames, must be taken by the Consumer. Other actions, e.g., those associated with changes in Parameters, are at the discretion of the Consumer, depending upon whether the data is simply being "read" or whether it is being used to recompute or display other data.

The Producer's obligation is to provide Update Objects in such a way that the influence of the change applies to data that follows the Update Object. That is, changes must not be recorded "after the fact". Nevertheless, the influence of changes may not apply immediately, and most of the Attributes of the Update Object exist to help the Consumer determine precisely at what point the change takes effect.

Not all Objects may be updated. Those Objects and their Attributes that are allowed to be updated are listed in Appendix D. Attributes not listed in Appendix D or not otherwise specified as changeable by this standard must remain constant throughout a Logical File, and all data that is influenced by any such Attribute must correspond to a constant Value of that Attribute. Figure 6-3 defines the Attributes of an Update Object.

Label Restrictions Comments
TIME C=1 1
BOREHOLE-DRIFT C=1 1
VERTICAL-DEPTH C=1 1
RADIAL-DRIFT C=1 1
ANGULAR-DRIFT C=1 1
TAG-CHANNEL C=1, R=OBNAME 2
TAG-VALUE - 3
FRAME-TYPES R=OBNAME 4
FRAME-NUMBERS R=UVARI 5
COMMENT C=1, R=ASCII 6
OBJECT C=1, R=OBJREF 7
ATTRIBUTE C=1, R=IDENT 8
NEW - 9
OLD - 10
Figure 6-3. Attributes of Update Object

Comments: