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.
Spreadsheet The Company shall prepare and deliver to Purchaser, in accordance with Section 6.11, a spreadsheet (the “Spreadsheet”) in form and substance reasonably satisfactory to Purchaser, which spreadsheet shall be dated as of the Closing Date and shall set forth all of the following information (in addition to the other required data and information specified therein), as of immediately prior to the Closing: (a) the names of all of the Selling Securityholders and their respective addresses and e-mail addresses (to the extent known), (b) the number and type of shares of Company Capital Stock held by, or subject to the Company Options held by, such Selling Securityholders and, in the case of outstanding shares, the respective certificate numbers, and if the Company Capital Stock was ever subjected to vesting or other conditions constituting a “substantial risk of forfeiture” within the meaning of Section 83 of the Code, whether a Section 83(b) election was timely and properly made in respect thereof, (c) (i) for each Company Option that was exercised, whether it was early exercised, and the Tax status of each such Company Option under Section 422 of the Code, the date of such exercise and the applicable exercise price and (ii) for each outstanding Company Option, the Tax status of each such Company Option under Section 422 of the Code, the date of such exercise and the applicable exercise price, (d) the Total Consideration (including, listed separately, the Cash Consideration, Stock Consideration and Aggregate Exercise Price, and excluding, for purposes of this clause (d), the Contingent Consideration, (e) the calculation of each Selling Securityholder’s Pro Rata Share (expressed as a percentage), (f) the calculation of the aggregate cash amounts payable to each such Selling Securityholder pursuant to each of Section 1.5(a), Section 1.5(b) and Section 1.5(c) (with respect to Section 1.5(c), assuming paid in all cash pursuant to the terms of Section 1.5(c)), (g) the calculation of the aggregate number of shares of Purchase Series B Stock issuable to each such Selling Securityholder pursuant to each of Section 1.5(a), (h) the amount of any indebtedness to the Company owed by such Selling Securityholder and to be deducted from such Selling Securityholder’s applicable portion of the Cash Consideration, (i) the calculation of the Seller Stamp Tax Amount and (j) a funds flow memorandum setting forth all Transaction Expenses incurred (whether paid or unpaid), including any Transaction Expenses to be paid by the Purchaser at the Closing and any other payments to be made by Purchaser at the Closing (including Transaction Expenses reasonably anticipated to be incurred in the future).
CONTRACT FORMS This Section contains forms which, once completed, will form part of the Contract. The forms for Performance Security and Advance Payment Security, when required, shall only be completed by the successful tenderer after contract award.
SAMPLE (If applicable and the project has specifications, insert the specifications into this section.)
ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.