License to Create Independent Implementations Sample Clauses

License to Create Independent Implementations. For any Specification produced under a new JSR, the Spec Lead for such JSR shall offer to grant a perpetual, non-exclusive, worldwide, fully paid-up, royalty free, irrevocable license under its licensable copyrights in and patent claims covering the Speci- fication (including rights licensed to the Spec Lead pursuant to Section 4.A and 4.C) to anyone who wishes to create and/or distribute an Independent Implementation of the Spec. Such license will authorize the cre- ation and distribution of Independent Implementations provided such Independent Implementations: (a) fully implement the Spec(s) including all its required interfaces and functionality; (b) do not modify, subset, superset or otherwise extend the Licensor Name Space, or include any public or protected packages, classes, Java interfaces, fields or methods within the Licensor Name Space other than those required/authorized by the Spec or Specs being implemented; and (c) pass the TCK for such Spec. For the purposes of this Section 5.B, patent claims covering the Specification shall mean any claims for which there is no technically feasible way of avoiding infringement in the course of implementing the Spec- ification.
View SourceView Similar (8)
License to Create Independent Implementations. For any Specification produced under a new JSR, the Spec Lead for such JSR shall offer to grant a perpetual, non-exclusive, worldwide, fully- paid-up, royalty free, irrevocable license under its licensable copyrights and patent rights in the Speci- fication (including rights licensed to the Spec Lead pursuant to Section 4.A and 4.C) to anyone who wishes to create and/or distribute an Independent Implementation of the Spec. Such license will autho- rize the creation and distribution of Independent Implementations provided such Independent Imple- mentations: (a) fully implement the Spec(s) including all its required interfaces and functional- ity; (b) do not modify, subset, superset or otherwise extend the Licensor Name Space, or include any public or protected packages, classes, Java interfaces, fields or methods within the Licensor Name Space other than those required/authorized by the Spec or Specs being implemented; and (c) pass the TCK for such Spec. For the purposes of this Section 5.B, patent rights in the Specification shall mean any patent rights for which there is no technically feasible way of avoiding infringement in the course of implementing the Specification. The Spec Lead may condition its offer of the license described in this Section 5.B upon its licensee’s commitment to offer to any party seeking a license from such licensee, if requested, a license under such licensee’s patent rights which are or would be infringed by all technically feasible implementations of the Spec on terms consistent with the provisions of Section 6.A excluding, for non- Members, its subsections (bb) and (ee). The Spec Lead also may condition its offer of the license described in this Section 5.B under its own applicable patent rights (as opposed to rights licensed to the Spec Lead by other Contributors pursuant to Section 4.A.II) on a licensee not initiating a claim that the Spec Lead’s making, having made, using, offering to sell, selling or importing an implementation of the Spec that satisfies requirements (a) - (c) above infringes such licensee’s patent rights. Other than as set forth above, the Spec Lead agrees not to impose any contractual condition or cove- nant that would limit or restrict the right of any licensee to create or distribute such Independent Imple- mentations. The Spec License may otherwise include as additional terms and conditions only those that do not relate to the license grant but govern issues such as, without limitation, confidentialit...
View Source
License to Create Independent Implementations. For any Specification produced under a new JSR, the Spec Lead for such JSR shall make the following commitments offer to grant a perpetual, non- exclusive, worldwide, fully paid-up, royalty free, irrevocable license under its licensable copyrights in and patent claims covering the Specification (including rights licensed to the Spec Lead pursuant to Section 4.A and 4.C) to anyone who wishes to create and/or distribute an Independent Implementation of the Spec: 1. offer to grant a perpetual, non-exclusive, worldwide, fully paid-up, royalty-free, irrevocable license under such Spec Lead's licensable copyrights, where. Ssuch license will authorizes the cre- ation and distribution of Independent Implementations provided such Independent Implementations: (a) fully implement the Spec(s) including all its required interfaces and functionality; (b) do not modify, subset, superset or otherwise extend the Licensor Name Space, or include any public or protected packages, classes, Java interfaces, fields or methods within the Licensor Name Space other than those required/authorized by the Spec or Specs being implemented; and (c) pass the TCK for such Spec. 2. covenant not to assert any essential patent rights against anyone who creates and/or distributes an Independent Implementation of the Spec provided that conditions (a) - (c) under section 5.B.1 above are met. With respect to Specifications which explicitly authorize Non-Java Implementation, (i) condition 5.B.1(b) above does not apply to such implementations, and condition (c) is waived for the Non-Java Implementation unless the Specification expressly states that passing the TCK is necessary for Non-Java Implementations. 3. the commitments described under Section 5.B.1 and 2 above with respect to Independent Implementations for which the development process includes public disclosure of source code (and optionally binaries) before such implementation is complete, but only where such implementation is of the most recent draft of the Specification and provided that any distribution of such implementation must be clearly and
View Source

Related to License to Create Independent Implementations

  • COOPERATION IN IMPLEMENTATION On demand of the other Spouse and without undue delay or expense, each Spouse shall execute, acknowledge, or deliver any instrument, furnish any information, or perform any other acts reasonably necessary to carry out the provisions of this Agreement. If a Spouse fails to execute any document as required by this provision, the court may appoint the court clerk or his or her authorized designee to execute the document on that ▇▇▇▇▇▇’s behalf.

  • Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this Agreement.

  • Project Implementation The Borrower shall:

  • Inconsistencies with Other Documents; Independent Effect of Covenants (a) In the event there is a conflict or inconsistency between this Agreement and any other Loan Document, the terms of this Agreement shall control; provided that, other than for purposes of Article XI, any provision of the other Loan Documents which imposes additional burdens on any Borrower or its Subsidiaries or further restricts the rights of such Borrower or its Subsidiaries or gives the Administrative Agent or any Lender additional rights shall not be deemed to be in conflict or inconsistent with this Agreement and shall be given full force and effect. (b) Each Borrower expressly acknowledges and agrees that each covenant contained in Article VIII, IX, or X hereof shall be given independent effect. Accordingly, no Borrower shall engage in any transaction or other act otherwise permitted under any covenant contained in Article VIII, IX, or X if, before or after giving effect to such transaction or act, such Borrower shall or would be in breach of any other covenant contained in Article VIII, IX, or X.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.