Access to Authoritative Copy Clause Samples

The "Access to Authoritative Copy" clause establishes the right of certain parties to view or obtain the definitive, legally binding version of a document or record. In practice, this clause typically applies to electronic contracts or digital records, ensuring that parties such as signatories, lenders, or custodians can access the original, unaltered version maintained by a trusted system. Its core function is to guarantee transparency and trust in digital transactions by providing a clear mechanism for verifying the authenticity and integrity of the authoritative document.
Access to Authoritative Copy. Access to the Authoritative Copy will be limited by the Access Permissions, as described in Sections 2.2 and 2.3 of these System Rules.

Related to Access to 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.

  • Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to CLEC-1 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. 6.2.2 Data circuits (private line or dial-up) may be required between BellSouth and CLEC-1 for the purpose of data transmission. Where a dedicated line is required, CLEC-1 will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. CLEC-1 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 a case by 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 CLEC-1. Additionally, all message toll charges associated with the use of the dial circuit by CLEC-1 will be the responsibility of CLEC-1. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the parties. All equipment, including modems and software, that is required on CLEC-1 end for the purpose of data transmission will be the responsibility of CLEC-1.

  • Construction Reports Each Constructing Entity shall issue reports to each other Construction Party on a monthly basis, and at such other times as reasonably requested, regarding the status of the construction and installation of the Interconnection Facilities. Each Construction Party shall promptly identify, and shall notify each other Construction Party of, any event that the Construction Party reasonably expects may delay completion, or may significantly increase the cost, of the Interconnection Facilities. Should a Construction Party report such an event, Transmission Provider shall, within fifteen days of such notification, convene a technical meeting of the Construction Parties to evaluate schedule alternatives.