INTEGRATION WITH EXTERNAL COMPONENTS Sample Clauses

INTEGRATION WITH EXTERNAL COMPONENTS. As mentioned, one of the goals of the CPN platform is to allow the integration of new components and the creation of new features by external stakeholders. To facilitate this, it is important to provide a good view on the functionality and APIs offered by the individual services of the platform, but also on the functionalities offered by the platforms as a whole, aggregating multiple services. It is critical to have clear documentation for each service. Ideally, documentation for all services should be shared within the platform. Both the REST APIs exposed by the microservices and the events that can be subscribed to through the message broker, should be documented. If a service changes its endpoints, this must be tracked and made available by the platform. Open API Documentation APIs have become the most common way for various services to communicate with each other. In order to better expose services via APIs, a common interface for these APIs needs to be present to tell exactly what each service is supposed to do. This interface is a contract that defines the SLA between the client and the services. The OpenAPI (Swagger19) Specification has emerged as the standard format for defining this contract, in a way that’s both human and machine readable, making it easier for services to effectively communicate with and orchestrate the entire application. All the information about the OpenAPI Specification can be found on: xxxxx://xxxxxx.xxx/OAI/OpenAPI-Specification 19 xxxxx://xxxxxxx.xx/swagger-ui/ Message Broker Event Documentation Message exchanged through a message broker are usually constrained with respect to the size in bytes (e.g. around 15Mb is the limit for Xxxxx messages) in order not to affect the overall performance of the messaging system. However, no assumption is made on the structure of body of the message itself that could be a sequence of bytes, a string, a number, etc. A common pattern is to send the text of the message using a structured and easily-parsable format such as XML or JSON. Each consumer can therefore receive the message, extract and parse the content of the body and access/process the information of interest. In CPN we define the very basic structure of the message to be exchanged through message brokers as the following: Table 3: Message basic structure Field Description
Sample 1
AutoNDA by SimpleDocs

Related to INTEGRATION WITH EXTERNAL COMPONENTS

  • Product Changes Vocera shall have the right, in its absolute discretion, without liability to End User, to update to provide new functionality or otherwise change the design of any Product or to discontinue the manufacture or sale of any Product. Vocera shall notify End User at least 90 days prior to the delivery of any Product which incorporates a change that adversely affects form, fit or function (“Material Change”). Vocera shall also notify End User at least 90 days prior to the discontinuance of manufacture of any Product. Notification will be made as soon as reasonably practical for changes associated with regulatory or health and safety issues.

  • Completion of Evaluation Cycle 1. The summative evaluation rating shall be based upon a preponderance of the evidence, assessed in a holistic manner, that is aligned to the Ohio Educator Standards. Only evidence gathered during the walkthroughs and formal observations that are conducted for the current school year may be used.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Follow-up Testing An employee shall submit to unscheduled follow-up drug and/or alcohol testing if, within the previous 24-month period, the employee voluntarily disclosed drug or alcohol problems, entered into or completed a rehabilitation program for drug or alcohol abuse, failed or refused a preappointment drug test, or was disciplined for violating the provisions of this Agreement and Employer work rules. The Employer may require an employee who is subject to follow-up testing to submit to no more than six unscheduled drug or alcohol tests within any 12 month period.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Innovative/Flexible Scheduling Where the Hospital and the Union agree, arrangements regarding Innovative Scheduling/Flexible Scheduling may be entered into between the parties on a local level. The model agreement with respect to such scheduling arrangements is set out below: MODEL AGREEMENT WITH RESPECT TO INNOVATIVE SCHEDULING/FLEXIBLE SCHEDULING MEMORANDUM OF AGREEMENT Between: The Hospital - And: The Ontario Public Service Employees Union (and its Local ) This Model Agreement shall be part of the Collective Agreement between the parties herein, and shall apply to the employees described in Article 1 of the Model Agreement.

  • Treatment Program Testing The Employer may request or require an employee to undergo drug and alcohol testing if the employee has been referred by the employer for chemical dependency treatment or evaluation or is participating in a chemical dependency treatment program under an employee benefit plan, in which case the employee may be requested or required to undergo drug or alcohol testing without prior notice during the evaluation or treatment period and for a period of up to two years following completion of any prescribed chemical dependency treatment program.

  • Payment for Material Completion The Contractor may request payment of the remaining contract balance, including retainage, less amounts credited the Owner or incurred as liquidated damages, and less amounts withheld for the Punchlist by reason of Minor Items or Permitted Incomplete Work (See Paragraph 6.5.3.2). Payment for Material Completion shall be made by a check payable jointly to the Contractor and Surety and shall be mailed to the Surety.

  • Separation of Components The SOFTWARE PRODUCT is licensed as a single product. Its component parts may not be separated for use on more than one computer.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!