Data Spine Sample Clauses

Data Spine. ‌ The EFPFInterop ecosystem consists of distributed, heterogeneous digital platforms, tools, and components provided and hosted by independent entities. The technical features, including its interfaces, protocols, data formats, data models, identity and access management mechanisms, etc., differ significantly from each other, thus making a direct communication between EFPFInterop services problematic. As described in chapter 4.1, there could be many different ways to address this problem – one such way could be to design standardized APIs based on the identification of common standards and abstractions and ask Service Providers and Service Consumers to implement specific connectors/plugins, in order to align their proprietary APIs to these standard APIs and enable communication. However, such approaches are not desirable as they need significant modifications to the existing tools, services, systems, and platforms that need to communicate with each other, among other shortcomings. Hence, a novel solution enabling a communications layer, acting as a translator/adapter between these heterogeneous tools, services, systems, and platforms, and providing data handling, routing capabilities and API adaptation functionalities is needed. EFPF offers an interoperability enabler, the Data Spine, designed to address these challenges. The requirements identified in chapter 4.2 guide the design of the Data Spine. The Data Spine is designed as the interoperability backbone of the EFPFInterop ecosystem that interlinks heterogeneous platforms, establishes interoperability between their services and enables the creation of cross-platform applications. The Data Spine is aimed at bridging the interoperability gaps between services at three different levels: • Protocol interoperability: The Data Spine supports two communication patterns:
Sample 1
AutoNDA by SimpleDocs
Data Spine. ‌ The components of the Data Spine described in chapter 5.2 can be realised using the some of the tools and technologies available today or can be implemented from scratch. Table illustrates one such reference implementation of the Data Spine components using open-source technologies. These technologies are further described in the subsequent sections. Table 1 — Data Spine Reference Implementation Data Spine Conceptual Component Technology Version Security Portal Keycloak 3.4.0 Integration Flow Engine Apache NiFi 1.11.4 Message Broker RabbitMQ 3.8.5 Service Registry LinkSmart Service Catalog 3.0.0-beta.1 API Security Gateway Apache APISIX 2.3.0
Sample 1

Related to Data Spine

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Data Services In lieu of any other rates or discounts, the Customer will receive a discount of 20% for the following Data Services: Access: Standard VBS2 Guide local loop charges for DS1 and DS-3 Access Service.

  • Digital Health The HSP agrees to:

  • Mobility 7.1 There may also be a business need to travel and work on a temporary basis at any premises which the Corporation currently has or may subsequently acquire or at any premises at which it may from time to time provide services. This would be subject to discussion and agreement giving due regard to the following considerations: - The location and arrangements for travel and subsistence; - The length of the working day with increased travel time; - The hours of work; - The timescale and duration of the proposed arrangements; - The employee’s personal and family circumstances.

  • Verizon OSS Services Access to Verizon Operations Support Systems functions. The term “Verizon OSS Services” includes, but is not limited to: (a) Verizon’s provision of Reconex Usage Information to Reconex pursuant to Section 8.1.3 below; and, (b) “Verizon OSS Information”, as defined in Section 8.1.4 below.

  • Data Access Services State Street agrees to make available to the Fund the Data Access Services subject to the terms and conditions of this Addendum and such data access operating standards and procedures as may be issued by State Street from time to time. The Fund shall be able to access the System to (i) originate electronic instructions to State Street in order to (a) effect the transfer or movement of cash or securities held under custody by State Street or (b) transmit accounting or other information (the transactions described in (i)(a) and (i)(b) above are referred to herein as “Client Originated Electronic Financial Instructions”), and (ii) access data for the purpose of reporting and analysis, which shall all be deemed to be Data Access Services for purposes of this Addendum.

  • Use of Verizon Telecommunications Services 2.1 Verizon Telecommunications Services may be purchased by Connectel under this Resale Attachment only for the purpose of resale by Connectel as a Telecommunications Carrier. Verizon Telecommunications Services to be purchased by Connectel for other purposes (including, but not limited to, Connectel’s own use) must be purchased by Connectel pursuant to other applicable Attachments to this Agreement (if any), or separate written agreements, including, but not limited to, applicable Verizon Tariffs.

  • Data Subjects The categories of Data Subjects who we may collect Personal Data about may include the following where they are a natural person: the Customer, the directors and ultimate beneficial owner(s) of the Customer, your customers, employees and contractors, payers and payees. You may share with Airwallex some or all of the following types of Personal Data regarding Data Subjects: • full name; • email address; • phone number and other contact information; • date of birth; • nationality; • public information about the data subject; • other relevant verification or due diligence documentation as required under these terms; and • any other data that is necessary or relevant to carry out the Agreed Purposes.

  • Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.

  • Cornerstone shall notify the LLC and confirm such advice in writing (i) when the filing of any post-effective amendment to the Registration Statement or supplement to the Prospectus is required, when the same is filed and, in the case of the Registration Statement and any post-effective amendment, when the same becomes effective, (ii) of any request by the Securities and Exchange Commission for any amendment of or supplement to the Registration Statement or the Prospectus or for additional information and (iii) of the entry of any stop order suspending the effectiveness of the Registration Statement or the initiation or threatening of any proceedings for that purpose, and, if such stop order shall be entered, Cornerstone shall use its best efforts promptly to obtain the lifting thereof.

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