MIT Agreement Clause Samples

The MIT Agreement clause establishes that the terms of the Massachusetts Institute of Technology (MIT) License apply to the use, distribution, and modification of the licensed software. Under this clause, users are permitted to freely use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, provided that the original copyright notice and license terms are included in all copies or substantial portions of the software. This clause's core function is to grant broad permissions while ensuring attribution, thereby promoting open-source collaboration and reducing legal barriers for software developers.
MIT Agreement. The license granted to Sangamo under the MIT Agreement is subject to the royalty-free, nonexclusive license rights of the United States government per FAR 52.227-11. Pursuant to the MIT Agreement, the Massachusetts Institute of Technology (“MIT”) reserves the right to practice under the Patent Rights licensed thereunder and to allow third parties to practice under such Patent Rights in all fields of use for noncommercial research purposes. MIT has granted the ▇▇▇▇▇▇ ▇▇▇▇▇▇ Medical Institute a paid-up, non-exclusive, irrevocable license to use the Patent Rights licensed under the MIT Agreement for its non-commercial purposes, but with no right to assign or sublicense.
View SourceView Similar (2)
MIT Agreement. The provisions of Article 2 (other than Paragraph 2.8), Article 9 and Article 10 of the MIT Agreement are hereby incorporated by reference into this Agreement and are binding upon Genentech and any of Genentech’s sublicensees under the rights licensed to Sangamo under the MIT Agreement (but in each case solely to the extent such provisions are applicable to the rights granted in this Agreement) as if each were a party to the MIT Agreement. Any sublicense granted by Sangamo to Genentech will survive as a direct license from the Massachusetts Institute of Technology (“MIT”) to Genentech pursuant to Paragraph 13.6 of the MIT Agreement provided that Genentech is not then in default under this Agreement and agrees to assume the rights and obligations of such direct license. If Genentech agrees to assume such rights and obligations, (a) such direct license shall be subject to the same non-financial terms and conditions as those in the MIT Agreement and (b) Genentech (or if there is at such time more than one sublicensee under the MIT Agreement, Genentech and all other sublicensees severally and jointly) shall pay any annual fees due pursuant to Paragraph 4.1(b) of the MIT Agreement. If Genentech becomes a direct licensee of MIT, Genentech shall make any monetary payment(s) that, had the MIT Agreement not been terminated, Sangamo would have been required to make under the MIT Agreement as a result of the activities of Genentech. The Parties agree that, in the event that the MIT Agreement is amended after the Effective Date, the provisions of this paragraph shall apply only to the extent required in any such amendment.
View SourceView Similar (2)
MIT Agreement. Except as would not reasonably be expected to result in material liability to the Transferred Assets (taken as a whole), the MIT Agreement is in full force and effect and constitutes a legal, valid, binding agreement of Seller, subject to the Enforceability Exceptions. Except as would not reasonably be expected to result in material liability to the Transferred Assets (taken as a whole), Seller has performed in all material respects all obligations required to be performed by it as of the date hereof under the MIT Agreement, and there have not been and are no material defaults by Seller, or, to the Knowledge of Seller, by the counterparties to the MIT Agreement. No event has occurred (or failed to occur) that, with the passing of time or the giving of notice or both, would constitute a material default by Seller, or, to the Knowledge of Seller, by the counterparties to the MIT Agreement. A copy of the MIT Agreement (including all modifications, amendments and supplements thereto and waivers thereunder) has been made available to Purchaser. To the Knowledge of Seller, there are no material disputes pending or threatened under the MIT Agreement.
View Source
MIT Agreement. Roche hereby acknowledges that Articles II, V, VII, VIII, IX, X, XII, XIII and XV of the MIT Agreement shall be binding upon Roche, its Affiliates and their respective sublicensees as if each of them were a party to the MIT Agreement. In particular, Roche agrees and understands that SBC’s exclusive rights, privileges and license under the MIT Agreement, and therefore Roche’s sublicense under the MIT Agreement shall terminate upon expiration or abandonment of all issued patents and filed applications within the Patent Rights (as defined in the MIT Agreement), unless the MIT Agreement is earlier terminated in accordance with the provisions of the MIT Agreement. SBC’s license under the MIT Agreement is expected to terminate on [***].
View Source
MIT Agreement. During the period in which GBP may exercise the option under Section 3.1 and while the Parties are engaged in any related good faith negotiations thereunder, CGI shall perform, in all material respects, its obligations under to the MIT Agreement, and CGI will not, through any act or omission cause any breach or default under, or otherwise cause the termination or amendment of, the MIT Agreement such that CGI cannot grant GBP such sublicense.
View Source

Related to MIT Agreement

  • One Agreement This Agreement and any related security or other agreements required by this Agreement, collectively: (a) represent the sum of the understandings and agreements between the Bank and the Borrower concerning this credit; (b) replace any prior oral or written agreements between the Bank and the Borrower concerning this credit; and (c) are intended by the Bank and the Borrower as the final, complete and exclusive statement of the terms agreed to by them. In the event of any conflict between this Agreement and any other agreements required by this Agreement, this Agreement will prevail.

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its Reliability Planning Process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Short-Term Reliability Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the STAR or Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Short-Term Reliability Process Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Sublicense Agreements Sublicenses under this Section 2.3 shall be granted only pursuant to written agreements, which shall be subject to and consistent with the terms and conditions of this Agreement. Such Sublicense agreements shall contain, among other things, provisions to the following effect: 2.3.2.1 all provisions necessary to ensure Licensee’s ability to comply with Licensee’s obligation under or not violate the provisions of Sections 4.4, 4.5, 4.6, 5.1, 5.3, 5.4, 8.1 and 11.1; 2.3.2.2 a section substantially the same as Article 9 (Indemnification), which also shall state that the Indemnitees (as defined in Section 9.1) are intended third party beneficiaries of such Sublicense agreement for the purpose of enforcing such indemnification; 2.3.2.3 in the event of termination of the license set forth in Section 2.1.1 above (in whole or in part (e.g., termination of the license as to a Licensed Product or in a particular country)), any existing Sublicense shall terminate to the extent of such terminated license; provided, however, that, for each Sublicensee, upon termination of the license, if the Sublicensee is not then in breach of the Sublicense agreement such that Licensee would have the right to terminate such Sublicense agreement, such Sublicensee shall have the right to obtain a license from Harvard on the same terms and conditions as set forth herein, which shall not impose any representations, warranties, obligations or liabilities on Harvard that are not included in this Agreement, provided that (a) the scope of the license granted directly by Harvard to such Sublicensee shall be coextensive with the scope of the license granted by Licensee to such Sublicensee, (b) if the Sublicense granted to such Sublicensee was non-exclusive, such Sublicensee shall not have the right to participate in the prosecution or enforcement of the Patent Rights under the license granted to it directly by Harvard and (c) if there are more than one Sublicensee, each Sublicensee that is granted a direct license shall be responsible for a pro rata share of the reimbursement due under Section 6.2.3 of this Agreement (based on the number of direct licenses under the Patent Rights in effect on the date of reimbursement); 2.3.2.4 the Sublicensee shall only be entitled to sublicense its rights under such Sublicense agreement on the terms set forth in this Section 2.3; and 2.3.2.5 the Sublicensee shall not be entitled to assign the Sublicense agreement without the prior written consent of Harvard, except that Sublicensee may assign the Sublicense agreement to a successor in connection with the merger, consolidation or sale of all or substantially all of its assets or that portion of its business to which the Sublicense agreement relates; provided, however, that any permitted assignee agrees in writing in a manner reasonably satisfactory to Harvard to be bound by the terms of such Sublicense agreement.