Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]
Use of Customer Name Contractor may use County’s name without County’s prior written consent only in Contractor’s customer lists. Any other use of County’s name by Contractor must have the prior written consent of County.
COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:
Termination by Registry Operator (a) Registry Operator may terminate this Agreement upon notice to ICANN if (i) ICANN fails to cure any fundamental and material breach of ICANN’s covenants set forth in Article 3, within thirty (30) calendar days after Registry Operator gives ICANN notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that ICANN is in fundamental and material breach of such covenants, and (iii) ICANN fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) Registry Operator may terminate this Agreement for any reason upon one hundred eighty (180) calendar day advance notice to ICANN.
Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]
DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.04, the parties acknowledge that the Direct Registration System (“DRS”) and Profile Modification System (“Profile”) shall apply to uncertificated American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC pursuant to which the Depositary may register the ownership of uncertificated American Depositary Shares, which ownership shall be evidenced by periodic statements issued by the Depositary to the Owners entitled thereto. Profile is a required feature of DRS which allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register such transfer. (b) In connection with and in accordance with the arrangements and procedures relating to DRS/Profile, the parties understand that the Depositary will not verify, determine or otherwise ascertain that the DTC participant which is claiming to be acting on behalf of an Owner in requesting a registration of transfer and delivery as described in subsection (a) has the actual authority to act on behalf of the Owner (notwithstanding any requirements under the Uniform Commercial Code). For the avoidance of doubt, the provisions of Sections 5.03 and 5.08 shall apply to the matters arising from the use of the DRS. The parties agree that the Depositary’s reliance on and compliance with instructions received by the Depositary through the DRS/Profile System and in accordance with this Deposit Agreement shall not constitute negligence or bad faith on the part of the Depositary.
Use of Service Areas The service areas, as located within the Project, shall be ear- marked for purposes such as parking spaces and services including but not limited to electric sub-station, transformer, DG set rooms, underground water tanks, Pump rooms, maintenance and service rooms, firefighting pumps and equipment etc. and other permitted uses as per sanctioned plans. The Allottee shall not be permitted to use the services areas in any manner whatsoever, other than those earmarked as parking spaces and the same shall be reserved for use by the Association for rendering maintenance services.
Use of Contractors (a) If the employer wishes to engage contractors and their employees to perform work in the classifications covered by this agreement, the employer must first consult in good faith with the union. Consultation will occur prior to the engagement of sub-contractors. (b) If the employer decides to engage subcontractors, the employer shall ensure that these contractors and their employees receive wages, allowances and conditions equal to or better than those contained in this agreement. (c) The use of sham sub contracting arrangements is a breach of this agreement. The contractor who engages subcontractors is responsible for ensuring the employees of sub- contractors receive wages, allowances and conditions equal to or better those contained in this agreement, this obligation extends to liability for all outstanding wages conditions and entitlements under this agreement.
Use of websites (a) The Guarantor may satisfy its obligation to deliver any public information to the Lenders by posting this information onto an electronic website designated by the Guarantor and the Administrative Agent (the “Designated Website”) by notifying the Administrative Agent (i) of the address of the website together with any relevant password specifications and (ii) that such information has been posted on the website; provided, that in any event the Guarantor shall supply the Administrative Agent with one copy in paper form of any information which is posted onto the website. (b) The Administrative Agent shall supply each Lender with the address of and any relevant password specifications for the Designated Website following designation of that website by the Guarantor and the Administrative Agent. (c) The Guarantor shall promptly upon becoming aware of its occurrence notify the Administrative Agent if: (i) the Designated Website cannot be accessed due to technical failure; (ii) the password specifications for the Designated Website change; (iii) any new information which is required to be provided under this Guaranty is posted onto the Designated Website; (iv) any existing information which has been provided under this Guaranty and posted onto the Designated Website is amended; or (v) the Guarantor becomes aware that the Designated Website or any information posted onto the Designated Website is or has been infected by any electronic virus or similar software. If the Guarantor notifies the Administrative Agent under Section 8.3(c)(i) or Section 8.3(c)(v) above, all information to be provided by the Guarantor under this Guaranty after the date of that notice shall be supplied in paper form unless and until the Administrative Agent is satisfied that the circumstances giving rise to the notification are no longer continuing.
Use of Personal Data By executing this Stock Agreement, Participant acknowledges and agrees to the collection, use, processing and transfer of certain personal data, including his or her name, salary, nationality, job title, position and details of all past Awards and current Awards outstanding under the Plan (“Data”), for the purpose of managing and administering the Plan. The Participant is not obliged to consent to such collection, use, processing and transfer of personal data, but a refusal to provide such consent may affect his or her ability to participate in the Plan. The Company, or its Subsidiaries, may transfer Data among themselves or to third parties as necessary for the purpose of implementation, administration and management of the Plan. These various recipients of Data may be located elsewhere throughout the world. The Participant authorizes these various recipients of Data to receive, possess, use, retain and transfer the Data, in electronic or other form, for the purposes of implementing, administering and managing the Plan. The Participant may, at any time, review Data with respect to the Participant and require any necessary amendments to such Data. The Participant may withdraw his or her consent to use Data herein by notifying the Company in writing; however, the Participant understands that by withdrawing his or her consent to use Data, the Participant may affect his or her ability to participate in the Plan.
