III.C. File Rendering Metadata (Repeatable for each file)
Identifies how the record appeared in order to recreate it as it would have been viewed at the time of receipt.

III.C.1.Application-Dependency [Mandatory, Repeatable]
Indicates which applications, if any, the record is dependent upon. If there are dependencies, the name of one application, the version, and registration information is recorded in each occurrence of the field at the time of record creation. This information is intended to serve as a pointer to a registered library maintained by the creating organization or a public entity such as the Copyright Office or Patent Office.

III.C.2.Software-Environment-Dependency [Mandatory - Repeatable]
Indicates what software, including operating systems and API's, if any, the record is dependent upon. If there is a dependency, the name of the software package(s), the version, registration information, and display information (such as font sets or other software dependent attributes] is recorded at the time of record creation.

III.C.3.Hardware-Dependency [Mandatory - Repeatable]
Indicates what hardware, if any, the record is dependent upon. If there is a dependency, the hardware needed, model number, configuration, and output information (such as printers or viewers required or other hardware dependent attributes] are recorded at the time of record creation.

III.C.4.Rendering-Rules [Mandatory - Repeatable]
Identifies the procedures necessary to enable the record to be displayed, printed, or otherwise represented as it had been at the time of creation (macros, dimension, spatial reference data, etc.) - may operate at different levels.

III.C.5.Representation-Standard/De Facto Standard [Mandatory - Repeatable]
Identifies any standard(s) applied to the file that affect how the file is rendered (ex: SGML, Postscript, TIFF, etc.).and which version of the standard was used.


III.D.1.File-Linking-Rule/Standard [Mandatory]
Identifies the rules or standards required to enable the necessary linkages between files that make up the record. Contains textual information regarding the actual rules or standards applied.


III.E.1.Content-Structure [Mandatory]
Indicates whether the content of the record is structured or unstructured.

III.E.2.Content-Data Set [Optional]
If the content is identified as being structured, this cites the data set whcih indicates how it is structured. Consists of the actual name of the data set definition. If a data set definition is neither registered or a well-known registered identity, then it will need to be registered.

III.E.3.Application-Dictionary [Mandatory, if structured and no content data set]
Identifies the data dictionary for the entire database. This consists of the actual data dictionary itself - or it could take the form of a set of referential integrity controls.

III.E.4.Delimiters/Labels [Optional, good practice]
Consists of the actual delimiters/labels used throughout the data and their usage rules.

III.E.5.Data Value-Lookup Tables [Mandatory, where present - Repeatable]
Consists of the authority file containing the values of the codes used throughout the record and their usage rules.

III.E.9.Dynamic-Relationships [Mandatory, if higher/lower exists]
Identifies what data is required from other records/files in order to populate other values. This is active in set relationships where a record cannot be opened unless the contents of other records are available.