Guiding questions
Purpose: Identify core transmission protocols and sector-specific APIs that enable seamless data exchange.
Protocol Selection
Which generic transmission protocols (e.g., REST/HTTP, NGSI-LD, LDES, MQTT) should be adopted?
Which domain-specific APIs are required for sectoral use cases?
Should a “preferred protocol set” be provided for faster onboarding?
Are Event Streaming (HTTPS or MQTT), IDSCP, or Protocol Buffers used for transmission?
Purpose: Define when data should be exchanged via push, pull, streaming, or batch transfers to meet diverse use cases.
Modes of Exchange
Will data be exchanged as push (provider sends) or pull (consumer requests), or both?
Which scenarios require continuous streaming versus finite batch transfers?
How will real-time updates and triggered exchanges be handled?
Purpose: Ensure protocols are aligned with semantic models and discoverable through catalogs.
Integration with Semantics & Discovery
How will protocols link to the agreed semantic data models?
How will API specifications and protocol details be published for discoverability?
Purpose: Implement mechanisms for ensuring accuracy, resilience, and compatibility in data transfers.
Quality & Reliability
How will completeness and accuracy of data transfers be ensured?
What mechanisms for error handling, reconnection, and version compatibility will be in place?
Purpose: Guarantee interoperability with other EU data spaces through shared protocols and a common inventory.
Federation Readiness
How will interoperability with other EU data spaces’ protocols be ensured?
Will a shared “protocol inventory” be maintained for federated connections?
Last updated