Common use of Technical Briefing/Collaboration Clause in Contracts

Technical Briefing/Collaboration. The parties agree to meet to discuss in detail the function and general manner of operation of each New API referred to in subsection (a) above on a monthly basis, and any substantially similar API that PalmSource may be researching and/or developing in the same area of functionality, if any. The parties agree to discuss in good faith the release of a uniform API, either (i) by way of PalmSource developing such API and including it in the respective PS Licensed Product, or licensing such API from, or co-developing the API with, Licensee on terms to be agreed upon by the parties, including, without limitation, the parties respective intellectual property rights in such APIs and responsibilities for costs, support and maintenance, or (ii) otherwise as mutually agreed. This Section 7.3 shall not be construed as granting to PalmSource any license to any New API developed by Licensee, except as set forth in Section 7.3(c) (Delivery of API Definition) or as may be agreed by the parties in writing. Notwithstanding the foregoing, Licensee shall not be required to obtain PalmSource’s approval prior to the release of any New API, subject to Section 2.3 (Compatibility and Trademark License) above.

Technical Briefing/Collaboration. The parties agree to meet to discuss in detail the function and general manner of operation of each New API referred to in subsection subsection (a) above on a monthly basis, and any substantially similar API that PalmSource may be researching and/or developing in the same area of functionality, if any. The parties agree to discuss in good faith the release of a uniform API, either (i) by way of PalmSource developing such API and including it in the respective PS Licensed Product, or licensing such API from, or co-developing the API with, Licensee on terms to be agreed upon by the parties, including, without limitation, the parties respective intellectual property rights in such APIs and responsibilities for costs, support and maintenance, or (ii) otherwise as mutually agreed. This Section 7.3 shall not be construed as granting to PalmSource any license to any New API developed by Licensee, except as set forth in Section 7.3(c) (Delivery of API Definition) or as may be agreed by the parties in writing. Notwithstanding the foregoing, Licensee shall not be required to obtain PalmSource’s approval prior to the release of any New API, subject to Section 2.3 (Compatibility and Trademark License) above.