Skip to content

Latest commit

 

History

History
254 lines (139 loc) · 9.07 KB

data-exchange-APIs.md

File metadata and controls

254 lines (139 loc) · 9.07 KB
Raw

Data Exchange APIs

Definition

This building block facilitates the sharing and exchange of data (i.e., data provision and data consumption/use) between data space participants. An example of a data interoperability building block is the ‘Context Broker’ of the Connecting Europe Facility (CEF), which is recommended by the European Commission for sharing right-time (near real-time) data among multiple organisations.

Role and Scope

Facilitates data sharing and exchange between data space participants, ensuring semantic interoperability of data and data sources.

Features

DSBA - CTO architecture coherence
  • Common API for exchange of digital twin data among participants, supporting:
    • updates
    • queries (including geo-queries)
    • notifications
    • federation
  • Extend protocols with metadata
  • Handshake
  • REST
  • HTTP Multipart
  • IDSCP (V2)

Components and Technologies

i3-Market Project
  • DCAT-AP
EGI-ACE
  • EGI DataHub, based on Onedata technology.
i4Trust
  • FIWARE Context Broker technology implementing the standard ETSI NGSI-LD data exchange API.
Open Geospatial Consortium
  • OGC APIs and OWS building blocks for spatial data exchange including Features, Things, rasters, Observations and many more.
  • Semantic support is provided by the Vocabulary hub that is hosting OGC specific models but also some domain models, mapping between various ontologies and profiles.
IDSA Hub Finland
  • IDS connector
  • Eclipse Milo - open source implementation of OPC UA.

Technical Reference Implementation

Design Principles Position Paper

A smart city needs to calculate its environmental performance on the basis of a collection and aggregation of information about all the sustainability projects in its urban environment. This information is shared by different stakeholders, who use different formats and semantics to report CO2 emissions and other indicators. The building block enables syntactic and semantic harmonization of the different data sources, as well as effective exchange of data using a common data exchange API to enable the calculation of the KPIs (key performance indicators) needed.

DSBA - CTO architecture coherence [DRAFT. NOT APPROVED]

OpenApi data app

EGI-ACE
  • Creation of Virtual Spaces abstracting physical file location.
  • Exchange of data between distributed data providers and file publication and sharing.
  • Use of REST API or CDMI API.
i4Trust
  • Several reference open source implementations of NGSI-LD can be found in the FIWARE Catalogue.
  • Portfolio of pioneer use cases relying on the i4Trust framework and using NGSI-LD as basis for the data exchange.
Open Geospatial Consortium

OGC suite are technical level interoperability standards, both abstract and encodings. They can contain transport, encodings and data models. Combining these based on the specification is a challenging and error-prone process. In addition, generic standards often require extensions (e.g. specific additional structures) and profiles (subsets and compilations). Ultimate interface or data model definition shall be maximally reusing existing data models, support translations between others, while preserving the semantics and provenance of data.
To enable semantic representations that will enable both logical and ontological model matching, the OGC Definition Server was developed. It is maintaining OGC standards ontologies models and some domain-specific ones that bridge to the abstract secifications models.

IDSA Hub Finland
  • IDS connector implementation with OPC-UA support.
  • The connector enables exchanging data retrieved from OPC-UA servers.

Business Use Cases Implementation

Design Principles Position Paper
  • Domain Data Standard: In manufacturing data spaces, a combination of different standards is used to describe the syntax and semantics of data transactions (e.g. ISO 10303, Asset Administration Shell, eCl@ss).
IDS Hub Finland
  • INDEX - Industrial Data Excellence We have used it in the Index project in the Smart Manufacturing use case. It enables the secure exchange of data among manufacturing machines that deploy heterogeneous interfaces and communication protocols. There is a description of the project https://www.dimecc.com/dimecc-services/index/ image

Best practices identification and recommendations

Design Principles Position Paper

To ensure interoperability between all data space participants, the technical measures need to be continuously maintained. This includes general agreements and domain specific models. The continuity model provides measures for change, release, and version management.\

  • Domain Data Standard: It provides the syntax and semantics for data exchange and data sharing on different levels, in a specific sector or domain. To achieve specific goals, multiple standards can be used in combination.
Deutsche Telekom - Data Intelligence Hub

The Telekom - Data Intelligence Hub is intended to serve as a digital connection between companies and be both a source for commercial data acquisition and open data. The platform offers users tools for analysis, acquisition, exchange and processing of data. Industry experts get the possibility to develop new business models, data-driven products or services. It is relevant for companies of all sizes and industries but also for universities, for example, that develop models for the combination of data and algorithms to attain new insights.

EGI-ACE

DataHub allows you to bring data close to computing to exploit it efficiently, and to publish a dataset and make it available to a specific community, or worldwide, across federated sites.

i4Trust
  • Adoption of a common data exchange API is key to foster innovation in data spaces.
  • Common data models (defining vocabulary and semantics associated to that vocabulary) are required.
Open Geospatial Consortium
  • There are some ontologies and models already in use, practical usage examples.
  • There is also key governance aspect that needs to be handled and preserved to sustain usefulness and completeness.
  • Governance needs to be supported by some technical tools and policies.

Gap or what is missing?

EGI-ACE
  • More standard API for data access and exchange (e.g. S3)
  • Access to relational or NoSQL DB.
i4Trust
  • Data exchange based on streaming is required. The ETSI NGSI-LD standard API is evolving to cover this aspect but some Context Brokers have not yet implemented all latest features of NGSI-LD.
Open Geospatial Consortium
  • Formal definitions are not always easy to adapt, which is not the gap cannot be filled on the adopter's side, but the thresholds if high.
  • The governance administration is internal, while it is not clear if itcould be better aligned to the Access & Usage Policies building block.
  • Implementation of the Data Usage and Accounting, and Publication & Marketplace Solutions could be helpful.
  • Provenance and traceability support is not stable.

TRL

Comments

Additional Information

EGI-ACE
i4Trust
  • Latest version of the specs.
  • NGSI-LD is being adopted worldwide as a minimum interoperability mechanism for data exchange by cities. For example, in India has been adopted by the Bureau of Indian Standards.
IDS Hub Finland