Single Authoritative Copy Sample Clauses

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. 4.2.1 Except for back-up copies created by the System and stored in a separate location, the Authoritative Copy will not be copied or printed without the copy or printout being watermarked or legended indicating it as a Non-Authoritative Copy. Each Participant agrees not to alter, erase, modify, or conceal such watermark or legend. The Authoritative Copy may not be altered without detection by the System. 4.2.2 Upon transfer of Control of the Authoritative Copy, the transferee will be identified in the System's records as the Owner of Record, with full Control rights and the ability to grant available permissions regarding the eContract. 4.2.3 Dealertrack will be the designated Custodian of the Authoritative Copy for the Owner of Record at all times while the Authoritative Copy is stored in the Vault. 4.2.4 The Authoritative Copy of the eContract will at all times remain the property of the Owner of Record. In no event and under no circumstances, will Dealertrack claim any ownership interest in the Authoritative Copy. 4.2.5 Dealertrack may at any time, without prior notice, restore a damaged or corrupted Authoritative Copy from System back-up. The restored copy will then be designated as the Authoritative Copy in the System in accordance with Section 4.6.
Sample 1Sample 2See All (7)
AutoNDA by SimpleDocs

Related to Single Authoritative Copy

  • Not an Authoritative Copy With respect to Contracts that are “electronic chattel paper”, the Servicer has marked all copies of each such Contract other than an authoritative copy with a legend to the following effect: “This is not an 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.

  • Borrower’s Copy Borrower shall be given one copy of the Note and of this Security Instrument.

  • BACKUP COPY You may make one backup copy of the software. You may use it only to reinstall the software.

  • Complete Copies of Materials The Company has delivered or made available true and complete copies of each document (or summaries of same) that has been requested by Parent or its counsel.

  • Foreign Assets/Account Reporting Information Italian residents who, during the fiscal year, hold investments abroad or foreign financial assets (e.g., cash, Shares and RSUs) which may generate income taxable in Italy are required to report such on their annual tax returns (UNICO Form, RW Schedule) or on a special form if no tax return is due. The same reporting obligations apply to Italian residents who, even if they do not directly hold investments abroad or foreign financial assets (e.g., cash, Shares and RSUs), are beneficial owners of the investment pursuant to Italian money laundering provisions.

  • Physical File Characteristics 7.2.1 The EODUF feed will be distributed to Comcast Phone over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among Comcast Phone’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF 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). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and Comcast Phone for the purpose of data transmission. Where a dedicated line is required, Comcast Phone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Comcast Phone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Comcast Phone. Additionally, all message toll charges associated with the use of the dial circuit by Comcast Phone will be the responsibility of Comcast Phone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. Version 4Q01 12/01/01 All equipment, including modems and software, that is required on Comcast Phone’s end for the purpose of data transmission will be the responsibility of Comcast Phone.

  • eXtensible Business Reporting Language The interactive data in eXtensible Business Reporting Language included or incorporated by reference in the Registration Statement fairly presents the information called for in all material respects and has been prepared in accordance with the Commission’s rules and guidelines applicable thereto.

  • Status Reports The Grantee shall submit status reports quarterly, unless otherwise specified in the Attachments, on Exhibit A, Progress Report Form, to Department’s Grant Manager describing the work performed during the reporting period, problems encountered, problem resolutions, scheduled updates, and proposed work for the next reporting period. Quarterly status reports are due no later than twenty (20) days following the completion of the quarterly reporting period. For the purposes of this reporting requirement, the quarterly reporting periods end on March 31, June 30, September 30 and December 31. The Department will review the required reports submitted by Grantee within thirty (30) days.

  • ELECTRONIC SUBMITTALS Contractor shall obtain a license for the State to utilize Submittal Exchange for the purposes of this project. The State and its representatives will have full control of the use of Submittal Exchange by authorized users of the State.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!