Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
Transfer Procedures 1. The transfers referred to in Article 4, 5, 6 and 7 shall be effected without undue delay and, at all events, within six months after all fiscal obligations have been met and shall be made in a convertible currency. All the transfers shall be made at the prevailing exchange rate applicable on the date on which the investor applies for the related transfer, with the exception of the provisions under point 3 of Article 5 concerning the exchange rate applicable in case of nationalization or expropriation.
Software Transfer You may permanently transfer all of your rights under this XXXX, provided you (a) retain no copies, (b) transfer all of the SOFTWARE PRODUCT (including all component parts, the media and printed materials, any upgrades, this XXXX, and, if applicable, the Certificate of Authenticity), and (c) the recipient agrees to abide by all of the terms of this XXXX. If the SOFTWARE PRODUCT is an upgrade, any transfer must include all prior versions of the SOFTWARE PRODUCT and all of your rights therein, if any.
Transfer Procedure After receipt by Silicon Valley Bank of the executed Warrant, Silicon Valley Bank will transfer all of this Warrant to its parent company, SVB Financial Group. By its acceptance of this Warrant, SVB Financial Group hereby makes to the Company each of the representations and warranties set forth in Section 4 hereof and agrees to be bound by all of the terms and conditions of this Warrant as if the original Holder hereof. Subject to the provisions of Section 5.3 and upon providing the Company with written notice, SVB Financial Group and any subsequent Holder may transfer all or part of this Warrant or the Shares issuable upon exercise of this Warrant (or the securities issuable directly or indirectly, upon conversion of the Shares, if any) to any transferee, provided, however, in connection with any such transfer, SVB Financial Group or any subsequent Holder will give the Company notice of the portion of the Warrant being transferred with the name, address and taxpayer identification number of the transferee and Holder will surrender this Warrant to the Company for reissuance to the transferee(s) (and Holder if applicable); and provided further, that any subsequent transferee other than SVB Financial Group shall agree in writing with the Company to be bound by all of the terms and conditions of this Warrant. Notwithstanding any contrary provision herein, at all times prior to the IPO, Holder may not, without the Company’s prior written consent, transfer this Warrant or any portion hereof, or any Shares issued upon any exercise hereof, or any shares or other securities issued upon any conversion of any Shares issued upon any exercise hereof, to any person or entity who directly competes with the Company, except in connection with an Acquisition of the Company by such a direct competitor.
Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of Projects Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.
Notification Procedures To address non-compliance, the receiving Competent Authority would notify the providing Competent Authority pursuant to Article 5 of the IGA. The notification procedures would differ depending upon whether the receiving Competent Authority seeks to address administrative or other minor errors or significant non-compliance.
Provide Data In Compliance With FERPA School Unit shall provide data for the purposes of the Service Agreement in compliance with FERPA, COPPA, PPRA, IDEA, MSIPA, and MUSER and all other Maine privacy statutes and regulations referenced or identified in this DPA.
