License Obligations Sample Clauses

License Obligations. Nothing in this Agreement imposes any obligation upon a PARTY to enter into any other license or agreement with the other PARTY.
AutoNDA by SimpleDocs
License Obligations. It is the exclusive responsibility of the Licensee to determine the appropriate end use for the Software, including but not limited to determining if the Software is appropriate for the Licensee’s information systems; installing the Software, establishing adequate back-up procedures; and implementing procedures to satisfy Licensee’s security requirements. Licensee assumes complete responsibility and expressly acknowledges that the Licensor has no responsibility or liability, for the selection of the software and support services required to achieve Licensee’s intended results, and for the installation, use and results obtained from the Software, OGS and any other programs.
License Obligations. (i) With respect to the Program(s), any Participant making a Contribution to the Project shall be deemed, by taking such action, to have agreed that if the Draft Software in connection with which the Contribution made is finally approved by the Forum, the Contributor will provide a License under the 3-Clause BSD License (xxxxx://xxxxxxxxxx.xxx/licenses/BSD-3-Clause). Note: For the avoidance of doubt only the terms of the 3-Clause BSD License apply to Program(s) and not the BBF IPR Policy. (ii) With respect to all other Submissions (i.e., Artifacts) any Submitter agrees to make such Submissions pursuant to the terms of the BBF IPR Policy. To the extent that any other Submissions would result in the infringement of a patent, they will be considered a “Draft Specification” under the BBF IPR Policy.
License Obligations. (i) With respect to the Program(s), any Participant making a Contribution to the Project shall be deemed, by taking such action, to have agreed that if the Draft Software in connection with which the Contribution made is finally approved by the Forum, the Contributor will provide a License under Apache 2.0 (xxxx://xxx.xxxxxx.xxx/licenses/LICENSE-2.0).
License Obligations. 9.11.1. Nothing in this Agreement imposes any obligation upon a Party to enter into any other license or agreement with the other Party. 9.11.2. The Parties agree that (i) either Party shall be entitled, to the full extent permitted by applicable bankruptcy law, to elect to retain of its rights as a licensor or licensee respectively, in the event that the other Party files for bankruptcy in any jurisdiction or has any petition for bankruptcy filed against it, and (ii) either Party may, to the fullest degree permitted by applicable bankruptcy law, exercise all of its rights and elections under the relevant bankruptcy law, including but not limited to retention of its rights as a licensor or licensee respectively, regardless of whether either Party files for bankruptcy in the United States or any other jurisdiction or has any petition for bankruptcy filed against it.
License Obligations. In consideration for the license granted by Codexis under Section 8.2 (License to Codexis Technology), Customer agrees to the following payment and purchase obligations: (a) Upon Customer receiving the first approval of a Health Registration for Product in any of the United States, Europe or Canada (“First Health Registration”), Customer shall pay Codexis a one-time, non-refundable, non-creditable milestone payment of US$500,000. Customer shall notify Codexis in writing of Customer’s receipt of such First Health Registration, and Codexis shall invoice Customer for such milestone payment. Such payment shall be made by Customer to Codexis within [***] from the date of such invoice from Codexis. (b) [***.] (c) [***.]
License Obligations. Nothing in this Agreement imposes any obligation upon a Party to enter into any other license or agreement with the other Party. The Parties agree that (i) either Party shall be entitled, to the full extent permitted by applicable bankruptcy law, to elect to retain of its rights as a licensor or licensee respectively, in the event that the other Party files for bankruptcy in any jurisdiction or has any petition for bankruptcy filed against it, and (ii) either Party may, to the fullest degree permitted by applicable bankruptcy law, exercise all of its rights and elections under the relevant bankruptcy law, including but not limited to retention of its rights as a licensor or licensee respectively, regardless of whether either Party files for
AutoNDA by SimpleDocs
License Obligations. Under certain territorial regulatory requirements where the Distribution Partner provides the OneWeb Services to its Sub Distributors or to End Customers using and reliant upon OneWeb’s license, Distribution Partner shall comply with all such (OneWeb’s) license obligations and requirements for the provision of the OneWeb Services into that Territory, including any obligation to comply with legally required lawful intercept, or similar requirement, and other national Laws related to telecommunications, spectrum and OneWeb Approved Equipment deployment in the Territory. OneWeb agrees that it shall provide all necessary details regarding any relevant license conditions to Distribution Partner.
License Obligations. Licensed Organization agrees: 4.1 to integrate and use the Licensed Software only as a part of Integrated Product(s), and not with any other software system; 4.2 to modify the Licensed Software only in accordance with the Documentation to allow for interoperability with Integrated Product(s), and not to create any derivative work from the Licensed Software; 4.3 to preserve all marks and proprietary notices and labels contained in the Licensed Software; 4.4 not to reverse compile, reverse engineer, disassemble, unobfuscate, reformat, or otherwise attempt to read or make readable any portion of the code (or the underlying ideas, algorithms, structure or organization) of the Licensed Software; 4.5 not to combine the Licensed Software with “open source” software licensed under the GNU General Public License, or under any other license agreement, in a manner that would require the Licensed Software in source code form to be made publicly available; 4.6 not to provide or expose the APIs of the Licensed Software for use by any third party. 4.7 to provide Integrated Product(s) to third-party End Users only under written terms and conditions which prohibit End Users from: (i) modifying the Licensed Software or creating any derivative work of the Licensed Software; (ii) removing or altering any marks or proprietary notices or labels contained in the Licensed Software; (iii) reverse compiling, reverse engineering, disassembling, unobfuscating, reformatting, or otherwise attempting to read or make readable any portion of the code (or the underlying ideas, algorithms, structure or organization) of the Licensed Software; or (vi) renting, leasing, selling, sublicensing, granting a security interest in, or otherwise transferring any rights in the Licensed Software
License Obligations. Supplier shall provide to Purchaser copies of current medical professional licenses that permit any physician who under the Agreement provides medical services within the state where Work is performed. Copies must be provided at each renewal period to ensure licenses remain active.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!