Header/Subheader Field Specification Clause Samples

Header/Subheader Field Specification. The specification of the fields in the various Headers/Subheaders found within a NSIF File is provided in a series of tables in Appendix 1. Each table includes a mnemonic identifier (ID) for each field within a Header/Subheader, the FIELD's name, a description of the valid contents of the field, and any constraints on the field's use, the field SIZE in bytes, the VALUE RANGE it may contain, and an indication of its TYPE (paragraph 8). The NSIF File Header Fields are specified in Table C-1-1. The Standard Data Segment Subheader Fields are specified in Tables C-1-3, C-1-5, and C-1-6. The TRE Subheaders (paragraph 27a) and RES (paragraph 27d) are defined in Tables C-1-7 and C-1-9. Finally, the DES Subheader Fields (paragraphs 27b and 27c) are defined in Tables C-1-8, C-1-8(A), and C-1-8(B).
View Source

Related to Header/Subheader Field Specification

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.