Sublicense under CAT Product License Sample Clauses

Sublicense under CAT Product License. Subject specifically to the terms and conditions set forth in Section 2.3, Dyax hereby grants to Licensee a worldwide, non-exclusive sublicense of the rights granted to Dyax under Clause 2.1 of the CAT Product License (the “CAT Sublicense”) to use, research, develop, offer for sale, sell, have sold, import and export and have imported and exported, Licensed Products, and to make or have made Licensed Products for such purposes.
AutoNDA by SimpleDocs

Related to Sublicense under CAT Product License

  • SOFTWARE PRODUCT LICENSE The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Xxxxx of License Georgia Institute of Technology shall grant the Student a limited, nonexclusive, nontransferable and revocable license to use and occupy an assigned space in a Georgia Institute of Technology facility in accordance with the terms and conditions of this Contract (the “License”). The parties to this Contract do not intend that an estate, a tenancy or any other interest in property should pass from Georgia Institute of Technology to Student. Instead, it is the intention of the parties that the relationship between Georgia Institute of Technology and Student be that of licensor and licensee and the sole right of Student to use the assigned space as a living unit shall be based upon the License granted in this Contract.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

  • Sublicense SONY shall be permitted to sublicense the rights ---------- granted in Section 2.1 only to: (a) wholly-owned subsidiaries of SONY; provided that SONY shall promptly notify LEXAR in writing of sublicenses granted to subsidiaries and SONY shall acknowledge responsibility for such subsidiary's compliance with the terms of this Lexar Technology License Agreement; and (b) any parties for the manufacture, use, offer for sale, import and sale of Host Devices and any components of Host Devices, provided that such third parties shall only be sublicensed under LEXAR Intellectual Property Rights for that portion of a Host Device or of any component of a Host Device that communicates directly with a Licensed Memory Stick. SONY's sublicense rights under this Section 2.2(b) shall be contingent upon SONY entering into a written agreement with each sublicensee in the form of Exhibit C. SONY will provide LEXAR with a copy of each such --------- sublicense agreement immediately after execution thereof. Nothing in this Agreement shall be construed as permitting SONY to reveal LEXAR Confidential Information, as such term is defined in Section 6, to sublicensees under this Section 2.2(b). In the event that SONY determines that the Memory Stick Specification contains LEXAR Confidential Information, LEXAR and SONY agree to negotiate in good faith additional specific provisions to the form sublicensee agreement to sufficiently protect LEXAR's Confidential Information. LEXAR and SONY acknowledge that in the course of these negotiations, the parties' mutual interest in making the Host Device manufacturing license available as broadly as possible should be weighed against the importance of protecting LEXAR's Confidential Information. Sublicensees under this Section 2.2 shall not have the right to sublicense the rights granted under this agreement. * Material has been omitted and filed separately with the Commission.

  • Patent License For patent claims including, without limitation, method, process, and apparatus claims which You or Your Affiliates own, control or have the right to grant, now or in the future, You grant to Us a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable patent license, with the right to sublicense these rights to multiple tiers of sublicensees, to make, have made, use, sell, offer for sale, import and otherwise transfer the Contribution and the Contribution in combination with the Material (and portions of such combination). This license is granted only to the extent that the exercise of the licensed rights infringes such patent claims; and provided that this license is conditioned upon compliance with Section 2.3.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Sublicense Rights Licensee shall not have the right to grant sublicenses under the licenses granted to it under Section 2.1(a) (Development and Commercialization License to Licensee) and Section 6.3(d) (Use of Coherus Trademark), without the prior written consent of Coherus, which consent may be withheld [***], except with respect to [***], in which case [***]. For the avoidance of doubt, it shall be [***] with respect to [***]. If Coherus consents in writing to allow Licensee to grant a sublicense, then Licensee may grant such sublicense, through [***], subject to the following: (a) each Sublicensee shall agree to be bound by all of the applicable terms and conditions of this Agreement; (b) the terms of each sublicense granted by Licensee shall provide that the Sublicensee shall be subject to the terms and conditions of this Agreement; (c) Licensee’s grant of any sublicense shall not relieve Licensee from any of its obligations under this Agreement; (d) Licensee shall be liable for any breach of a sublicense by a Sublicensee to the extent that such breach would constitute a breach of this Agreement, and any breach of the sublicense by such Sublicensee shall be deemed a breach of this Agreement by Licensee to the extent that such breach would constitute a breach of this Agreement as if Licensee had committed such breach; provided, however, that in each instance of any breach, Licensee and/or Sublicensee shall have the right to cure any such breach pursuant to the terms of this Agreement; and (e) Licensee will notify Coherus of the identity of any Sublicensee, and the territory in which it has granted such sublicense, promptly after entering into any sublicense. Notwithstanding anything to the contrary in this Agreement, for clarity, Licensee shall not have the right to grant sublicenses under Section 2.1 (License Grants) to any Third Party to Manufacture Products or to conduct Process Development.

  • 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!