DBA format Sample Clauses

DBA format. 392. In its Year 2 report, the Monitoring Committee already mentioned the DBA’s format as a stumbling block for proper cooperation. The DBA is drafted as a corporate multi party contract, apparently not because the parties did not know each other but because they knew each other too well. Banks, CSOs and Trade Unions had a longer history of engaging with each other, both in terms of cooperation and confrontation. The parties and banks took this luggage with them and the DBA format was apparently deemed necessary to bind each other into a quasi-legal framework with a considerable input from lawyers. The result was that the DBA got off to a start based on a lack of mutual trust.
AutoNDA by SimpleDocs

Related to DBA format

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • 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.

  • Proposal Format a. Offerors shall submit an original of their proposals and the number of copies listed in paragraph “c” below.

  • Contract Formation Subject to FAR Sections 1.601(a) and 43.102, the Government Order must be signed by a duly warranted contracting officer, in writing. The same requirement applies to contract modifications affecting the rights of the parties. All terms and conditions intended to bind the Government must be included within the contract signed by the Government.

  • Deposit’s Format Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-­‐xxxxx-­‐xxxxxxx-­‐registry-­‐data-­‐escrow, see Part A, Section 9, reference 1 of this Specification and draft-­‐xxxxx-­‐noguchi-­‐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.

  • 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 XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

  • Transfer Format Transfers may include, but are not limited to, conversion of all Data into or from an industry standard format or providing application programmable interface. ENCRYPTION Data must be encrypted at all times unless specifically outlined otherwise in the Authorized User Agreement. At a minimum, encryption must be carried out at the most current NYS Encryption Standard (NYS-S14-007), (or successor policy with key access restricted to the Authorized User only, unless with the express written permission of the Authorized User. All Data in transit must be handled in accordance with ITS Policy NYS-S14-007 (or successor) or the National Institute of Standards and Technology (NIST) Federal Institute Processing Standard (FIPS)-140-2 or Transport Layer Security (TLS) 1, or TLS2 (or successor). The Authorized User Agreement shall specify the respective responsibilities of the Authorized User and the Contractor for the encryption of Data.

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Optical Plan (a) The Optical Plan shall provide for reimbursement of eligible expenses for the following:

  • Accounting Format Applications for Payment shall be broken down by CSI Category and, in certain situations, by CSI Description and capital asset category, as set forth in the form for Application for Payment. The purpose is to provide appropriate backup documents for the Contractor’s Final Certification of Costs in conformance with GASB 34 accounting standards. See Section 7 – Forms, “Application for Payment” and Final Certification of Costs.

Time is Money Join Law Insider Premium to draft better contracts faster.