Middleware Profiles Sample Clauses

Middleware Profiles. Apart from micro-ROS profiles, DDS-XRCE standard defines a set of profiles modularising the mid- dleware capabilities. In the micro-ROS platform, these profiles are also configurable per middleware implementation. • Read Access profile. Provides the clients with the ability to read data on pre-configured Topics with pre-configured QoS policies. • Write Access profile. Provides the clients with the ability to write data on pre-configured Topics with pre-configured QoS policies. • Configure Entities profile. Provides the clients the ability define DomainParticipant, Topic, Publisher, Subscriber, DataWriter, and DataReader entities using pre-configured QoS policies and data-types. • Configure QoS profile. Provides client with the ability to define QoS profiles to be used by DDS entities. • Configure types profile. Includes middleware client the ability to set data types to be used for DDS topics. • Discovery access profile. Provides the middleware clients to discover entities. • File-based configuration profile. micro-ROS Agent core could be configured using a file system. • UDP Transport profile. It provides UDP transport. • TCP Transport profile. It provides TCP transport. • Complete profile. It allows the complete functionality of the middleware. Micro-ROS profiles require some of the specific middleware profiles. This profile dependencies are resolved automatically at build time selecting those middleware profiles required by micro-ROS profiles. This table represents dependencies between micro-ROS components and Micro RTPS profiles. micro- ROS/Micro read write configureconfigureconfigure file RTPS nodes access access entities QoS types discoveryconfiguration udp tcp complete lifecycle x x publish x subscribe x services x x timers clock logging parameters x x executor discovery x
AutoNDA by SimpleDocs

Related to Middleware Profiles

  • Firmware The Contractor shall deliver firmware required for production acceptance testing in accordance with CDRL A009 Contractor’s Supplier Configuration Management Plan. The Contractor shall use Government furnished software for testing. Deliverable Data Item (See DD-1423): CDRL A009: “Contractor’s Supplier Configuration Management Plan”

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Servers Marco backs up the following servers only: Windows Servers, SQL servers, Exchange server, and Virtual Machines images running VMWare or Hyper V.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • 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.

  • Analytics 1.1. IFS may track and analyze the usage of the IFS Offering for purposes of determining usage made of the IFS Offering, for the purposes of security, to assist customers, and for improving the Software and Services and the user experience in using such Software and Services. For example, IFS may use this information to help customers derive more value from the Software and Services, to understand and analyze trends, or to track which features are used most often in order to improve the Software and Services. IFS may share anonymous usage data with its service providers for the purpose of helping in such tracking, analysis and improvements. Additionally, IFS may share such anonymous usage data on an aggregate basis in the normal course of operating their business; for example, IFS may share information publicly to show trends about the general use of its software and services. TERMS - SERVICES

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

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