Country and Territory Names The country and territory names (including their IDN variants, where applicable) contained in the following internationally recognized lists shall be withheld from registration or allocated to Registry Operator at All Levels: the short form (in English) of all country and territory names contained on the ISO 3166-1 list, as updated from time to time, including the European Union, which is exceptionally reserved on the ISO 3166-1 list, and its scope extended in August 1999 to any application needing to represent the name European Union <xxxx://xxx.xxx.xxx/iso/support/country_codes/iso_3166_code_lists/iso-3166-1_decoding_table.htm>; the United Nations Group of Experts on Geographical Names, Technical Reference Manual for the Standardization of Geographical Names, Part III Names of Countries of the World; and the list of United Nations member states in 6 official United Nations languages prepared by the Working Group on Country Names of the United Nations Conference on the Standardization of Geographical Names; provided, that the reservation of specific country and territory names (including their IDN variants according to the registry operator IDN registration policy, where applicable) may be released to the extent that Registry Operator reaches agreement with the applicable government(s). Registry Operator must not activate such names in the DNS; provided, that Registry Operator may propose the release of these reservations, subject to review by ICANN’s Governmental Advisory Committee and approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
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.
Territory 33.1 This Agreement applies to the territory in which CenturyLink operates as an ILEC in the State. CenturyLink shall be obligated to provide services under this Agreement only within this territory.
33.2 Notwithstanding any other provision of this Agreement, CenturyLink may terminate this Agreement as to a specific operating territory or portion thereof pursuant to Section 6.7 of this Agreement.
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
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.
Licensed Intellectual Property Section 3.17(h)(vi)...................................29
Product Trademarks BMS shall be solely responsible for the selection (including the creation, searching and clearing), registration, maintenance, policing and enforcement of all trademarks developed for use in connection with the marketing, sale or distribution of Products in the Field in the Territory (the “Product Marks”). BMS shall own all Product Marks, and all trademark registrations for said marks.
SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.
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.
Third Party Use You may allow your agents, contractors and outsourcing service providers (each a “Permitted Third Party”) to use the Product(s) licensed to you hereunder solely for your benefit in accordance with the terms of this XXXX and you are responsible for any such Permitted Third Party’s compliance with this XXXX in such use. Any breach by any Permitted Third Party of the terms of this XXXX will be considered your breach.
