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.
Access to Authoritative Copy Sample Clauses
Related to Access to 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.
Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.
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. Contractor shall maintain all Records, fiscal and otherwise, directly relating to this Contract in accordance with generally accepted accounting principles so as to document clearly Contractor's performance. Following final payment and termination of this Contract, Contractor shall retain and keep accessible all Records for a minimum of three years, or such longer period as may be required by law, or until the conclusion of any audit, controversy, or litigation arising out of or related to this Contract, whichever date is later.
DOCUMENTATION; RECORDS OF PROCESSING Each party is responsible for its compliance with its documentation requirements, in particular maintaining records of processing where required under Data Protection Law. Each party shall reasonably assist the other party in its documentation requirements, including providing the information the other party needs from it in a manner reasonably requested by the other party (such as using an electronic system), in order to enable the other party to comply with any obligations relating to maintaining records of processing.
PRESERVATION OF CONTRACTING INFORMATION 2.27.1 The requirements of Subchapter J, Chapter 552, Texas Government Code, may apply to this Agreement and the Contractor agrees that this Agreement can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter. If the requirements of Subchapter J, Chapter 552, Texas Government Code, apply to this Agreement, then for the duration of this Agreement (including the initial term, any renewal terms, and any extensions), Contractor shall preserve all Contracting Information, as defined by Section 552.003 of the Texas Government Code, related to this Agreement as provided by the records retention requirements applicable to the City pursuant to federal or state law or regulation, city ordinance or city policy, which record retention requirements include but are not limited to those set forth in Chapters 201 and 205 of the Texas Local Government Code and Texas Administrative Code Title 13, Chapter 7. Within five business days after receiving a request from the Director, Contractor shall provide any Contracting Information related to this Agreement that is in the custody or possession of Contractor. Upon the expiration or termination of this Agreement, Contractor shall, at the Director’s election, either (a) provide, at no cost to the City, all Contracting Information related to this Agreement that is in the custody or possession of Contractor, or (b) preserve the Contracting Information related to this Agreement as provided by the records retention requirements applicable to the City pursuant to federal or state law or regulation, city ordinance or City policy.
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.
CONTROL SYSTEM (a) SELLER shall provide and maintain a quality control system to an industry recognized Quality Standard and in compliance with any other specific quality requirements identified in this Contract.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
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.
Management and Control Systems Grantee will:
