Piggyback Registration (a) If the Company proposes to register any of its Common Stock under the Securities Act (other than pursuant to a Demand Registration), it will each such time, subject to the provisions of Section 5.02(b) hereof, give prompt written notice at least 15 days prior to the anticipated filing date of the registration statement relating to such registration to all Shareholders which notice shall set forth such Shareholders' rights under this Section 5.02 and shall offer all Shareholders the opportunity to include in such registration statement such number of shares of Common Stock as each such Shareholder may request (a "Piggyback Registration"). Upon the written request of any such Shareholder made within 10 days after the receipt of notice from the Company (which request shall specify the number of shares of Common Stock intended to be disposed of by such Shareholder), the Company will use its reasonable best efforts to effect the registration under the Securities Act of all shares of Common Stock which the Company has been so requested to register by such Shareholders, to the extent requisite to permit the disposition of the shares of Common Stock so to be registered; provided that (i) if such registration involves an Underwritten Public Offering, all such Shareholders requesting to be included in the Company's registration must sell their Registrable Securities to the underwriters selected as provided in Section 5.04(f) on the same terms and conditions as apply to the Company or the Selling Shareholder, as applicable, and (ii) if, at any time after giving written notice of its intention to register any stock pursuant to this Section 5.02(a) and prior to the effective date of the registration statement filed in connection with such registration, the Company shall determine for any reason not to register such stock, the Company shall give written notice to all such Shareholders and, thereupon, shall be relieved of its obligation to register any Registrable Securities in connection with such registration. No registration effected under this Section 5.02 shall relieve the Company of its obligations to effect a Demand Registration to the extent required by Section 5.01 hereof. The Company will pay all Registration Expenses in connection with each registration of Registrable Securities requested pursuant to this Section 5.02.
Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.
Piggyback Registrations Without limiting any obligation of the Company hereunder or under the Securities Purchase Agreement, if there is not an effective Registration Statement covering all of the Registrable Securities or the prospectus contained therein is not available for use and the Company shall determine to prepare and file with the SEC a registration statement or offering statement relating to an offering for its own account or the account of others under the 1933 Act of any of its equity securities (other than on Form S-4 or Form S-8 (each as promulgated under the 0000 Xxx) or their then equivalents relating to equity securities to be issued solely in connection with any acquisition of any entity or business or equity securities issuable in connection with the Company’s stock option or other employee benefit plans) (a “Piggyback Registration”), then the Company shall deliver to each Investor a written notice of such determination and, if within fifteen (15) days after the date of the delivery of such notice, any such Investor shall so request in writing, the Company shall include in such registration statement or offering statement all or any part of such Registrable Securities such Investor requests to be registered; provided, however, (i) the Company may postpone or withdraw the filing or the effectiveness of a registration statement filed pursuant to this Section 2(g) at any time in its sole discretion and (ii) the Company shall not be required to register any Registrable Securities pursuant to this Section 2(g) that are eligible for resale pursuant to Rule 144 without restriction (including, without limitation, volume restrictions) and without the need for current public information required by Rule 144(c)(1) (or Rule 144(i)(2), if applicable) or that are the subject of a then-effective Registration Statement. If a Piggyback Registration is initiated as a primary underwritten offering on behalf of the Company and the managing underwriter advises the Company and the holders of Registrable Securities (if any holders of Registrable Securities have elected to include Registrable Securities in such Piggyback Registration) in writing that in its reasonable and good faith opinion the number of shares of Common Stock proposed to be included in such registration , including all Registrable Securities and all other shares of Common Stock proposed to be included in such underwritten offering, exceeds the number of shares of Common Stock which can be sold in such offering and/or that the number of shares of Common Stock proposed to be included in any such registration would adversely affect the price per share of the Common Stock to be sold in such offering, the Company shall include in such registration or takedown (i) first, the shares of Common Stock that the Company proposes to sell; (ii) second, the shares of Common Stock requested to be included therein by holders of Registrable Securities, allocated pro rata among all such holders on the basis of the number of Registrable Securities owned by each such holder or in such manner as they may otherwise agree; and (iii) third, the shares of Common Stock requested to be included therein by holders of Common Stock other than holders of Registrable Securities, allocated among such holders in such manner as they may agree. If a Piggyback Registration is initiated as an underwritten offering on behalf of a holder of Common Stock other than Registrable Securities, and the managing underwriter advises the Company in writing that in its reasonable and good faith opinion the number of shares of Common Stock proposed to be included in such registration , including all Registrable Securities and all other shares of Common Stock proposed to be included in such underwritten offering, exceeds the number of shares of Common Stock which can be sold in such offering and/or that the number of shares of Common Stock proposed to be included in any such registration would adversely affect the price per share of the Common Stock to be sold in such offering, the Company shall include in such registration (i) first, the shares of Common Stock requested to be included therein by the holder(s) requesting such registration or takedown and by the holders of Registrable Securities, allocated pro rata among all such holders on the basis of the number of shares of Common Stock other than the Registrable Securities (on a fully diluted, as converted basis) and the number of Registrable Securities, as applicable, owned by all such holders or in such manner as they may otherwise agree; and (ii) second, the shares of Common Stock requested to be included therein by other holders of Common Stock, allocated among such holders in such manner as they may agree.
Demand Registration (a) Subject to the provisions hereof, at any time on or after the date that is 180 days after the Closing Date, the Holders of a majority of Registrable Securities shall have the right to require the Company to file a Registration Statement registering for sale all or part of their respective Registrable Securities under the Securities Act (a “Demand Registration”) by delivering a written request therefor to the Company (i) specifying the number of Registrable Securities to be included in such registration by such Holder or Holders, (ii) specifying whether the intended method of disposition thereof is pursuant to an Underwritten Offering (as defined below), and (iii) containing all information about such Holder required to be included in such Registration Statement in accordance with applicable Law. As soon as practicable after the receipt of such demand, the Company shall (x) promptly notify all Holders from whom the request for registration has not been received and (y) use reasonable best efforts to effect such registration (including, without limitation, appropriate qualification under applicable blue sky or other state securities Laws and appropriate compliance with applicable regulations issued under the Securities Act and any other governmental requirements or regulations) of the Registrable Securities that the Company has been so requested to register; provided, however, that (i) the Holders shall not make a request for a Demand Registration under this Section 3.2(a) for Registrable Securities having an anticipated aggregate offering price of less than $5,000,000, (ii) the Holders will not be entitled to require the Company to effect more than three (3) Demand Registrations in the aggregate under this Agreement, and (iii) the Company will not be obligated to effect more than one (1) Demand Registration in any six (6) month period.
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.
Initial Registration Periods Initial registrations of registered names may be made in the registry in one (1) year increments for up to a maximum of ten (10) years. For the avoidance of doubt, initial registrations of registered names may not exceed ten (10) years.
Registration Fees 39.01 The Employer shall reimburse an employee for the employee’s payment of membership or registration fees to organizations or governing bodies when the payment of such fees is a requirement for the continuation of the performance of the duties of his or her position, or for professional development or certification purposes.
Service Registration Certain of our Services require you to register to use them. In such case, you agree that a l information you provide is truthful, current and complete. If there is any change to your registration information, you agree to provide us with updated information immediately. To the extent any of the Services are password protected, you agree to keep such password confidential and not to share it with any third party. You also agree that you wil not access any Services for which a password is required by using any third party’s password. If you discover any use of your password other than by you, you agree to immediately notify us. If you become aware of unauthorized account access, you similarly agree to immediately notify us. At the end of any use of a password protected Service, you agree to exit and logout out of your user session. Under no circumstances sha l we be responsible for any loss or damage that may result if you fail to comply with these requirements.
NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.
