License Terms This license is for one full Semester. It cannot be cancelled or terminated except under the conditions cited in this license.
Development License Subject to the terms and conditions of this XXXX, You are licensed to perform an installation of the SOFTWARE for an unlimited use in designing, testing and creating Developed Software by unlimited Developers on one or more computers.
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.
Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.
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.
Grant and Scope of License 2.1. Subject to Licensee’s compliance with the License Agreement, and except as otherwise stated herein, Licensor hereby grants Licensee a non-exclusive, revocable and non-transferrable license to: 2.1.1. permit Authorized Users to access the Content for the duration and in the manner set forth in the License Agreement; 2.1.2. incorporate links on Licensee’s intranet websites to the Content in full text format on the Platforms; 2.1.3. transmit to a non-commercial library single articles, book chapters or portions thereof only for personal educational, scientific, or research purposes (“Interlibrary Loans”). Such transmission shall be reviewed and fulfilled by Licensee’s staff, and shall be made by hand, post, fax or through any secure document transmission software, so long as, in the case of any electronic transmission, the electronic file retains the relevant copyright notice. The right set out in this clause does not extend to centralized ordering facilities, such as document delivery systems, nor the distribution of copies in such quantities as to substitute for a subscription or purchase of the distributed Content. 2.2. Authorized Users may solely for their personal educational, scientific, or research purposes: 2.2.1. access (including by remote access, with the exception of walk-in-users), browse, view, collate, display, search and retrieve the Content, 0.0.0. xxxxxxxx, store on a hard drive or removable media drive, print and copy in paper and digital form single articles, eBooks and portions thereof, individual database outputs, graphs, reports, or other individual items of the Content, 2.2.3. use single articles, eBooks and portions thereof, individual database outputs, graphs, reports or other individual items of the Content for the preparation of academic course materials with all rights notices duly presented. 2.2.4. use the Springer Nature SharedIt functionality when available, or other means when necessary, to transmit single articles, chapters or other individual items of Content to third-party members of the Authorized Users’ research group(s) for personal, scholarly, educational, or research use, but in no case for commercial purposes, nor in any manner that would serve as a replacement for a subscription to the Content.
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.
SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:
Commercialization License Subject to the terms of this Agreement, including without limitation Section 2.2 and Theravance's Co-Promotion rights in Section 5.3.2, Theravance hereby grants to GSK, and GSK accepts, an exclusive license under the Theravance Patents and Theravance Know-How to make, have made, use, sell, offer for sale and import Alliance Products in the Territory.
License Rights The Recipient must provide a license to its “subject data” to the Federal Government, which license is: (a) Royalty-free, (b) Non-exclusive, and (c) Irrevocable, (2) Uses. The Federal Government’s license must permit the Federal Government to take the following actions provided those actions are taken for Federal Government purposes: (a) Reproduce the subject data, (b) Publish the subject data, (c) Otherwise use the subject data, and (d) Permit other entities or individuals to use the subject data, and
