Taxes and Fees Imposed Directly On Either Providing Party or Purchasing Party 13.2.1 Taxes and fees imposed on the providing Party, which are not permitted or required to be passed on by the providing Party to its customer, shall be borne and paid by the providing Party. 13.2.2 Taxes and fees imposed on the purchasing Party, which are not required to be collected and/or remitted by the providing Party, shall be borne and paid by the purchasing Party.
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Regarding Party A Party B acknowledges and agrees that Party A has had and will have no involvement in and, accordingly Party A accepts no responsibility for: (i) the establishment, structure, or choice of assets of Party B; (ii) the selection of any person performing services for or acting on behalf of Party B; (iii) the selection of Party A as the Counterparty; (iv) the terms of the Certificates; (v) other than as provided in the Disclosure Agreements, the preparation of or passing on the disclosure and other information contained in any offering circular or offering document for the Certificates, the Trust Agreement, or any other agreements or documents used by Party B or any other party in connection with the marketing and sale of the Certificates; (vi) the ongoing operations and administration of Party B, including the furnishing of any information to Party B which is not specifically required under this Agreement or the Disclosure Agreements; or (vii) any other aspect of Party B’s existence.
Third Party Access Client is prohibited from disclosing data from the Data Set to any third party without obtaining written permission from Oracle.
Third Party Users If required by Applicable Laws and Regulations or if the Parties mutually agree, such agreement not to be unreasonably withheld, to allow one or more third parties to use the Connecting Transmission Owner’s Attachment Facilities, or any part thereof, Developer will be entitled to compensation for the capital expenses it incurred in connection with the Attachment Facilities based upon the pro rata use of the Attachment Facilities by Connecting Transmission Owner, all third party users, and Developer, in accordance with Applicable Laws and Regulations or upon some other mutually-agreed upon methodology. In addition, cost responsibility for ongoing costs, including operation and maintenance costs associated with the Attachment Facilities, will be allocated between Developer and any third party users based upon the pro rata use of the Attachment Facilities by Connecting Transmission Owner, all third party users, and Developer, in accordance with Applicable Laws and Regulations or upon some other mutually agreed upon methodology. If the issue of such compensation or allocation cannot be resolved through such negotiations, it shall be submitted to FERC for resolution.
Receiving Party Personnel The receiving Party will limit access to the Confidential Information of the disclosing Party to those of its employees, attorneys and contractors that have a need to know such information in order for the receiving Party to exercise or perform its rights and obligations under this Agreement (the “Receiving Party Personnel”). The Receiving Party Personnel who have access to any Confidential Information of the disclosing Party will be made aware of the confidentiality provision of this Agreement, and will be required to abide by the terms thereof. Any third party contractors that are given access to Confidential Information of a disclosing Party pursuant to the terms hereof shall be required to sign a written agreement pursuant to which such Receiving Party Personnel agree to be bound by the provisions of this Agreement, which written agreement will expressly state that it is enforceable against such Receiving Party Personnel by the disclosing Party.
Providing Party A Party offering or providing a Service to the other Party under this Agreement.
Third Party Use You may allow your agents, contractors and outsourcing service providers (each a “Permitted Third Party”) to use the Product(s) licensed to you hereunder solely for your benefit in accordance with the terms of this XXXX and you are responsible for any such Permitted Third Party’s compliance with this XXXX in such use. Any breach by any Permitted Third Party of the terms of this XXXX will be considered your breach.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Third Party Data Any statistical, industry-related and market-related data, which are included in the Disclosure Package and the Prospectus, is based on or derived from sources that the Company reasonably and in good faith believes to be reliable and accurate, and such data agrees with the sources from which it is derived, and the Company has obtained the written consent for the use of such data from such sources to the extent required.