Common use of Interface Definition Document (IDD) Version Clause in Contracts

Interface Definition Document (IDD) Version. Each message shall contain the version identification of the Interface Definition Document (IDD) from which its structure was defined. This version identification shall be placed in a fixed 10 byte field and filled with a null-terminated string of ASCII characters. Version identification management shall be used by error checking functions to validate format consistency. Table B1-3 shows the current version of the IDD that has been assigned. STANAG 4586 Document Version IDD Version Identification Edition 1 “1.0” Edition 2 “2.0” Edition 2, Errata 1 “2.1” Edition 2, Errata 2 “2.2” Edition 2, Errata 3 “2.3” Edition 2, Errata 4 “2.4” Edition 2, Errata 5 “2.5”

Appears in 1 contract

Sources: Standardisation Agreement

Interface Definition Document (IDD) Version. Each message shall contain the version identification of the Interface Definition Document (IDD) from which its structure was defined. This version identification shall be placed in a fixed 10 byte field and filled with a null-terminated string of ASCII characters. Version identification management shall be used by error checking functions to validate format consistency. Table B1-3 shows the current version of the IDD that has been assigned. STANAG 4586 Document Version IDD Version Identification Edition 1 “1.01Draft Edition 2 “2.02Draft Edition 2, Errata 1 “2.13Draft Edition 2, Errata 2 “2.24Draft Edition 2, Errata 3 “2.35Draft Edition 2, Errata 4 “2.46Draft Edition 2, Errata 5 “2.57” Edition 2 “8” Edition 2, Amendment 1 “9

Appears in 1 contract

Sources: Nato Standardization Agreement (Stanag)