Professional Component Source Files Clause Samples

The 'Professional Component Source Files' clause defines the ownership, use, or handling of source files created or used by professionals, such as software developers or engineers, during the course of a project. This clause typically specifies whether the client or the professional retains rights to the source files, and may outline conditions for access, delivery, or modification of these files. Its core function is to clarify intellectual property rights and responsibilities regarding source files, thereby preventing disputes over ownership and usage after project completion.
Professional Component Source Files. Subject to the terms and conditions of this Agreement, with respect to each Professional Component Source File, Adobe grants Licensee a non-exclusive, nontransferable license to (A) modify and reproduce such Professional Component Source File (as defined below) for use as a component of Developer Programs that add Material Improvements to such Professional Component Source File, and (B) distribute such Professional Component Source File in object code form and/or source code form only as a component of Developer Programs that add Material Improvements to such Professional Component Source File, provided that (1) such Developer Programs are designed to operate in connection with Adobe Flex Builder, Adobe Flex Data Services Software, Adobe LiveCycle Data Services Software or the SDK Components, (2) Licensee distributes such object code and/or source code under the terms and conditions of an End User License Agreement,
Professional Component Source Files. With respect to each Professional Component Source Files and subject to the terms and conditions of this Agreement, if your version of the SDK includes Professional Component
Professional Component Source Files. Subject to the terms and conditions of this Agreement, with respect to each Professional Component Source File, Adobe grants Licensee a non-exclusive, nontransferable license to (A) modify and reproduce such Professional Component Source File (as defined below) for use as a component of Developer Programs that add Material Improvements to such Professional Component Source File, and (B) distribute such Professional Component Source File in object code form and/or source code form only as a component of Developer Programs that add Material Improvements to such Professional Component Source File, provided that (1) such Developer Programs are designed to operate in connection with Adobe Flex Builder, Adobe Flex Data Services Software, Adobe LiveCycle Data Services Software or the SDK Components, (2) Licensee distributes such object code and/or source code under the terms and conditions of an End User License Agreement, (3) Licensee includes a copyright notice reflecting the copyright ownership of Developer in such Developer Programs, (4) Licensee shall be solely responsible to its customers for any update or support obligation or other liability which may arise from such distribution, (5) Licensee does not make any statements that its Developer Program is “certified,” or that its performance is guaranteed, by Adobe, (6) Licensee does not use Adobe’s name or trademarks to market its Developer Programs without written permission of Adobe, (7) Licensee does not delete or in any manner alter the copyright notices, trademarks, logos or related notices, or other proprietary rights notices of Adobe (and its licensors, if any) appearing on or within such Professional Component Source File and/or SDK Components, or any documentation relating to the SDK Components, (8) Licensee causes any modified files to carry prominent notices stating that Licensee changed the files, (9) Licensee does not use “mx,” “mxml,” “flex,” “flash,” “livecycle” or “adobe” in any new package or class names distributed with such Professional Component Source File, and (10) Licensee complies with the below Adobe® AIR™ Trademark Use Terms. Any modified or merged portion of Professional Component Source Files is subject to this Agreement. For the avoidance of doubt, Licensee shall have no rights to the Professional Component Source Files (or the object code form of such files), except to the extent such Professional Component Source Files are provided to Licensee in connection with Licensee’s lice...

Related to Professional Component Source Files

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

  • Development Records Each Party shall maintain complete, current and accurate records of all Development activities conducted by it hereunder, and all data and other information resulting from such activities. Such records shall fully and properly reflect all work done and results achieved in the performance of the Development activities in good scientific manner appropriate for regulatory and patent purposes. Each Party shall document all non-clinical studies and Clinical Trials in formal written study reports according to Applicable Laws and national and international guidelines (e.g., ICH, cGCP, cGLP, and cGMP).

  • PRODUCT MANUFACTURER'S SUPPLIERS Only those dealers/distributors listed by the manufacturer will be considered authorized to act on behalf of the Product Manufacturer.