Guiding questions

Protocol Selection

Purpose: Identify core transmission protocols and sector-specific APIs that enable seamless data exchange.

  1. Which generic transmission protocols (e.g., REST/HTTP, NGSI-LD, LDES, MQTT) should be adopted?

  2. Which domain-specific APIs are required for sectoral use cases?

  3. Should a “preferred protocol set” be provided for faster onboarding?

  4. Are Event Streaming (HTTPS or MQTT), IDSCP, or Protocol Buffers used for transmission?

Modes of Exchange

Purpose: Define when data should be exchanged via push, pull, streaming, or batch transfers to meet diverse use cases.

  1. Will data be exchanged as push (provider sends) or pull (consumer requests), or both?

  2. Which scenarios require continuous streaming versus finite batch transfers?

  3. How will real-time updates and triggered exchanges be handled?

Integration with Semantics & Discovery

Purpose: Ensure protocols are aligned with semantic models and discoverable through catalogs.

  1. How will protocols link to the agreed semantic data models?

  2. How will API specifications and protocol details be published for discoverability?

Quality & Reliability

Purpose: Implement mechanisms for ensuring accuracy, resilience, and compatibility in data transfers.

  1. How will completeness and accuracy of data transfers be ensured?

  2. What mechanisms for error handling, reconnection, and version compatibility will be in place?

Federation Readiness

Purpose: Guarantee interoperability with other EU data spaces through shared protocols and a common inventory.

  1. How will interoperability with other EU data spaces’ protocols be ensured?

  2. Will a shared “protocol inventory” be maintained for federated connections?

Last updated