Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.
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.
Data To permit evaluation of requests under paragraph (c) of this clause based on unreasonable cost, the Contractor shall include the following information and any applicable supporting data based on the survey of suppliers: Foreign and Domestic Construction Materials Cost Comparison Construction material description Unit of measure Quantity Cost (dollars) * Item 1: Foreign construction material Domestic construction material Item 2 Foreign construction material Domestic construction material [List name, address, telephone number, and contact for suppliers surveyed. Attach copy of response; if oral, attach summary.] [Include other applicable supporting information.] (*Include all delivery costs to the construction site.]
Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.
Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.
Contract Data The Consultant is advised to read the NEC3 Professional Service Contract (Third edition with amendments of June 2006 and April 2013) and the relevant Guidance Notes and Flow Charts, published by the Institution of Civil Engineers, in order to understand the implications of this Data which is required. Copies of these documents may be obtained from the Engineering Contract Strategies (telephone (00) 000 000 0000). Each item of data given below is cross-referenced to the clause in the NEC3 Professional Service Contract to which it mainly applies.
CONTRACT INFORMATION 1. The State of Arkansas may not contract with another party:
Product Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.
MASTER CONTRACT INFORMATION Enterprise Services shall maintain and provide information regarding this Master Contract, including scope and pricing, to eligible Purchasers.
Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.
