A schema to capture a set of data that is relevant for many exchange documents. It includes information about the file that was created, and high-level information about the data that is being exchanged within the file. An identifier for the document. This is intended to be unique within the context of the NamingSystem. Zero or more alternate names for the document. These names do not need to be unique within the naming system. The date of the creation of the document. This is not the same as the date that the file was created. For this date, the document is considered to be the set of information associated with this document information. For example, the document may be a seismic binset. This represents the date that the binset was created. The FileCreation information would capture the date that the XML file was created to send or exchange the binset. A document class. Examples of classes would be a metadata classification or a set of keywords. The information about the creation of the exchange file. This is not about the creation of the data within the file, but the creation of the file itself. Information about the security to be applied to this file. More than one classification can be given. A free-form string that allows a disclaimer to accompany the information. A collection of events that can document the history of the data. The owner of the data. An optional comment about the document. A block of information about the creation of the XML file. This is different than the creation of the data that is included within the file. The date and time that the file was created. If appropriate, the software that created the file. This is a free form string, and may include whatever information is deemed relevant. The person or business associate that created the file. Any comment that would be useful to further explain the creation of this instance document. Information about the security classification of the document. This is intended as a documentation of the security so that the file will not inadvertently be sent to someone who is not allowed access to the data. This block also carries a date that the security classification expires. For example, a well log is confidential for a period of time, and then becomes open. All security classes are characterized by their classification systems. The security class in which this document is classified. Examples would be confidential, partner confidential, tight. The meaning of the class is determined by the System in which it is defined. The security classification system. This gives context to the meaning of the Class value. The date on which this security class is no longer applicable. A general comment to further define the security class. The audit records what happened to the data, to produce the data that is in this file. It consists of one or more events. An event type captures the basic information about an event that has affected the data. The date on which the event took place. The party responsible for the event. A free form comment that can further define the event that occurred.