Single Authoritative Copy Sample Clauses

Single Authoritative Copy. There will be a single Authoritative Copy of an eContract at all times, stored in the Owner of Record’s logical segment of the Vault unless and until the eContract is Exported, Destroyed or subject to TOLEC in accordance with these System Rules. The Authoritative Copy will be the copy held and designated as such in the System. Access to the Authoritative Copy will be limited as defined in Section 2.0 of these System Rules. The Authoritative Copy will be designated as such when viewed.
AutoNDA by SimpleDocs
Single Authoritative Copy. There will be a single Authoritative Copy of an eContract at all times. Once the Authoritative Copy is transferred to the Financing Source at the Initial Delivery, the Authoritative Copy will be stored in the Owner of Record's logical segment of the Vault unless and until the eContract is Exported in accordance with these System Rules. The Authoritative Copy will be the copy held and designated as such in the System. Access to the Authoritative Copy will be limited as defined in Section 2 of these System Rules. The Authoritative Copy will be designated as such when viewed.

Related to Single Authoritative Copy

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

  • Entity Accounts Not Required to Be Reviewed, Identified or Reported Unless the Reporting Singaporean Financial Institution elects otherwise, either with respect to all New Entity Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in Singapore provide for such election, a credit card account or a revolving credit facility treated as a New Entity Account is not required to be reviewed, identified, or reported, provided that the Reporting Singaporean Financial Institution maintaining such account implements policies and procedures to prevent an account balance owed to the Account Holder that exceeds $50,000.

  • DESCRIPTION OF CONTRACT MODIFICATION This contract modification is made in accordance with Exhibit E-Revised-1, Contractual Terms and Conditions, Section 22. CHANGES, to be made part hereof for all pertinent purposes. The changes are as follows:

  • Act Identifier Title Shoulder note Iron Ore (Robe River) Agreement Xxx 0000 First Schedule Iron Ore (Robe River) Agreement Second Schedule First variation agreement Third Schedule Second variation agreement [s. 3B] Fourth Schedule Third variation agreement [s. 2] Fifth Schedule Fourth variation agreement Sixth Schedule Fifth variation agreement

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

  • Recycled Paper 23.1 The Contractor shall ensure that all paper used in the production of reports, documents and other materials arising out of the performance by the Contractor of their duties under this Contract consists of a minimum of sixty-per-cent recycled content of which seventy-five per cent is post-consumer waste.

  • Accounts Not Required to Be Reviewed, Identified, or Reported Unless the Reporting Financial Institution elects otherwise, either with respect to all Preexisting Individual Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in the jurisdiction provide for such an election, the following accounts are not required to be reviewed, identified, or reported as Reportable Accounts:

  • CENTRALIZED CONTRACT MODIFICATIONS A. OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • Electronic Protected Health Information “Electronic Protected Health Information” means individually identifiable health information that is transmitted by or maintained in electronic media.

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