Data File Format Clause Samples

Data File Format o The Contractor shall create a standard NEMSIS extensible markup language (XML) export file that meets the following minimum criteria: 2.1 Data Standards.  Includes Additional Data Elements via the NEMSIS “Research Field” including:  Consumable Items Defined in the Contractor’s Inventory 2.0 Module  All Contractor specific (IT Field – e.g. IT5.50 – Transporting Agency) data elements that are used by the OCEMS system.
Data File Format o The Contractor shall create a standard National Fire Incident Reporting System (NFIRS) XML export file that meets the following minimum criteria:  Includes all standard NFIRS Data Elements as defined by the NFIRS v5.7 (minimum) / NFIRS v5.9.1 Data Standards.  The File Format must include Series 300 (Rescue and Emergency Medical Services) data elements as defined by NFIRS.

Related to Data File Format

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.

  • Information Packages As soon as available and in any event not later than two (2) Business Days prior to each Settlement Date, an Information Package as of the most recently completed Fiscal Month.

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • COPIES OF REGULATORY REPORTS AND FILINGS Upon reasonable request, Competitive Supplier shall provide to the Town a copy of each public periodic or incident-related report or record relating to this ESA which it files with any Massachusetts or federal agency regulating rates, service, compliance with environmental laws, or compliance with affirmative action and equal opportunity requirements, unless the Competitive Supplier is required by law or regulation to keep such reports confidential. The Town shall treat any reports and/or filings received from Competitive Supplier as confidential information subject to the terms of Article 16. Competitive Supplier shall be reimbursed its reasonable costs of providing such copies.