Specific Software Sample Clauses

Specific Software. ‌ As the aim of the OFERA project is to support ROS 2 in microcontrollers, there is code that only belongs to this resource-constrained devices. If we compare ROS 2 and micro-ROS stacks, we can see that the bottom part is where the most substantial differences are located. For example, micro-ROS makes use of a RTOS, which is not contemplated in ROS 2. To minimize the support effort, it is of micro-ROS interest to keep this software entities that lives outside ROS 2 as few as possible. The following table shows which are those software entities and which is the expected long-term maintainer: Tool/asset/package Software Layer OFERA Maintainer Long-term maintainer Candidate NuttX RTOS RTOS Acutronic Robotics NuttX Community & Embedded system working group RTOS ALs RTOS Acutronic Robotics Embedded system working group or RTOS vendor Tool/asset/package Software Layer OFERA Maintainer Long-term maintainer Candidate Micro XRCE-DDS Middleware eProsima eProsima rmw for Micro XRCE-DDS micro-ROS to FIWARE bridge micro-ROS to H-ROS bridge ROS RMW eProsima eProsima Other eProsima eProsima Other Acutronic Robotics Acutronic Robotics HRIM usage Other Acutronic Robotics Acutronic Robotics • NuttX RTOS The project’s RTOS is supported by Acutronic Robotics and it consist of a maintained fork of the original BitBucket NuttX repository. The fork ensures the support of the development platforms selected in the project. Nowadays, there is little divergence of both repositories, thus consortium members agreed on trying to get into upstream the changes performed in the fork, in order to be synced. This is going to be done sending patches of the development boards and drivers to the NuttX creator, Xxxx Xxxx. This will allow benefiting of the NuttX community development effort and maintenance during the project and its end. Even though NuttX RTOS would be supported by the community, the NuttX colcon-based compilation could require of maintenance, as this compilation tool belongs to ROS 2 and not to the RTOS. This is an ongoing work the consortium is performing, and, once finished, it is expected to be placed in a project’s repository. This repository should be maintained by the Embedded System working group as it is the entity bridging between ROS 2 and the embedded devices. While the project gains interest within the community and external companies, it is also expected to have support for other RTOSes, following the micro-ROS modular approach. We have already seeing interest of s...
Sample 1
AutoNDA by SimpleDocs
Specific Software. Equipment and Professional Services may be ordered by Customer under this Agreement by complying with the reasonable ordering procedures established by Softsense, which, at a minimum, will require Customer's submission of a signed Order to Softsense and Softsense's acceptance thereof. Only those terms on the face (not back) of the Accepted Order shall be enforceable. An Order for Professional Services which has been signed by an authorized representative of Softsense and returned to Customer shall be deemed accepted by Softsense ("Accepted Order"). An Order for Software and Equipment which has been signed by Softsense and returned to Customer or upon which Softsense has issued an invoice to Customer or upon which Softsense has otherwise commenced performance, shall be deemed accepted by Softsense. Unless otherwise agreed in writing by the parties, the Accepted Order listing the Software programs licensed and the Customer locations ("Licensed Sites") where the Software programs are to be installed, shall serve to conform and effectuate Customer's license to the Software at such Licensed Sites, effective as to each Licensed Site upon completion of payment of the charges stated in the Order for such Licensed Site.
Sample 1
Specific Software. Brocade will develop and provide to HP software for the Product [**] (“Specific Software”). The terms of the [**] arrangement is limited to the Specific Software [**]. The [**] term for HP[**].
Sample 1
Specific Software. Upon notification of the readiness of the WORKS AND/OR EQUIPMENT for the first operation to the BUYER (item 17 of the GENERAL CONDITIONS) the CONTRACTOR transfers to the BUYER the proprietary copyright to the SPECIFIC SOFTWARE, on the areas of exploitation specified in Article 74 and 75 of the Act of 4 February 1994 on copyright and related rights and on the areas of exploitation specified in item 31.5.2 of the GENERAL CONDITIONS.
Sample 1

Related to Specific Software

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Proprietary Software Depending upon the products and services You elect to access through Electronic Access, You may be provided software owned by BNY Mellon or licensed to BNY Mellon by a BNY Mellon Supplier (“Proprietary Software”). You are granted a limited, non-exclusive, non-transferable license to install the Proprietary Software on Your authorized computer system (including mobile devices registered with BNY Mellon) and to use the Proprietary Software solely for Your own internal purposes in connection with Electronic Access and solely for the purposes for which it is provided to You. You and Your Users may make copies of the Proprietary Software for backup purposes only, provided all copyright and other proprietary information included in the original copy of the Proprietary Software are reproduced in or on such backup copies. You shall not reverse engineer, disassemble, decompile or attempt to determine the source code for, any Proprietary Software. Any attempt to circumvent or penetrate security of Electronic Access is strictly prohibited.

  • Company Software “Company Software” shall mean any software (including software development tools and software embedded in hardware devices, and all updates, upgrades, releases, enhancements and bug fixes) owned, developed (or currently being developed), used, marketed, distributed, licensed or sold by an Acquired Corporation at any time (other than non-customized third-party software that is not incorporated into any Company Product and is licensed to an Acquired Corporation solely in object code form and solely for internal use on a non-exclusive basis).

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Intellectual Property; Software (a) Schedule 4.12 contains a list and description (showing in each case any product, device, process, service, business or publication covered thereby, the registered or other owner, expiration date and number, if any) of all Copyrights, Patent Rights and Trademarks owned by, licensed to or used by the Company.

  • Software License Subject to the terms of this Agreement, Viasat grants to you a personal, non-exclusive, non-assignable and non-transferable license to use and display the software provided by or on behalf of Viasat (including any updates) only for the purpose of accessing the Service ("Software") on any computer(s) on which you are the primary user or which you are authorized to use. Our Privacy Policies provide important information about the Software applications we utilize. Please read the terms very carefully, as they contain important disclosures about the use and security of data transmitted to and from your computer. Unauthorized copying of the Software, including, without limitation, software that has been modified, merged or included with the Software, or the written materials associated therewith, is expressly forbidden. You may not sublicense, assign, or transfer this license or the Software except as permitted in writing by Viasat. Any attempt to sublicense, assign or transfer any of the rights, duties or obligations under this license is void and may result in termination by Viasat of this Agreement and the license. You agree that you shall not copy or duplicate or permit anyone else to copy or duplicate any part of the Software, or create or attempt to create, or permit others to create or attempt to create, by reverse engineering or otherwise, the source programs or any part thereof from the object programs or from other information made available under this Agreement.

  • Software Warranty We warrant that the Tyler Software will perform without Defects during the term of this Agreement. If the Tyler Software does not perform as warranted, we will use all reasonable efforts, consistent with industry standards, to cure the Defect in accordance with the maintenance and support process set forth in Section C(9), below, the SLA and our then current Support Call Process.

  • Software Licenses Seller has all necessary licenses to use all material third-party software used in connection with the Purchased Assets, and to Sellers’ knowledge, Sellers’ use of third-party software does not infringe the rights of any Person or Entity.

Time is Money Join Law Insider Premium to draft better contracts faster.