<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Eclipse Dataspace Components</title><link>https://eclipse-edc.github.io/blog/</link><description>Recent content in Blog on Eclipse Dataspace Components</description><generator>Hugo</generator><language>en</language><atom:link href="https://eclipse-edc.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Management API upcoming versions</title><link>https://eclipse-edc.github.io/blog/2026/02/19/management-api-upcoming-versions/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><guid>https://eclipse-edc.github.io/blog/2026/02/19/management-api-upcoming-versions/</guid><description>&lt;p&gt;The current, stable Management API of EDC Connector version 3 has served well during the last 2 years, but changes in the underlying protocols and the solidification of the EDC-V concept demand new versions.&lt;/p&gt;
&lt;h2 id="rationale"&gt;Rationale&lt;a class="td-heading-self-link" href="#rationale" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;There will be 2 new Management API version releases.&lt;/p&gt;
&lt;h3 id="version-4"&gt;Version 4&lt;a class="td-heading-self-link" href="#version-4" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;Version 4, which is already in its beta phase (as you can check in the &lt;a href="https://eclipse-edc.github.io/Connector/openapi/management-api/"&gt;OpenAPI documentation&lt;/a&gt;, so you can test it out and provide feedback), has been introduced to better align with the &lt;a href="https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1/"&gt;DSP 2025-1 spec&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Data Plane Signaling</title><link>https://eclipse-edc.github.io/blog/2026/01/19/data-plane-signaling/</link><pubDate>Mon, 19 Jan 2026 00:00:00 +0000</pubDate><guid>https://eclipse-edc.github.io/blog/2026/01/19/data-plane-signaling/</guid><description>&lt;p&gt;Data Plane Signaling is a specification for interoperable communication between Dataspace Protocol Control Planes and
Data Planes (&lt;a href="https://github.com/eclipse-dataplane-signaling"&gt;github project&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;We decided to fully adopt this specification and to deprecate the current approach. This will involve deprecating the
current implementation of the communication layer between the Control Plane and Data Plane in addition to the EDC Data
Plane Framework.&lt;/p&gt;
&lt;h2 id="rationale"&gt;Rationale&lt;a class="td-heading-self-link" href="#rationale" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;The Data Plane Signaling specification addresses key architectural ambiguities by clearly delineating the roles of the
Control Plane (orchestration and protocol-level authentication) and the Data Plane (actual data transfer and flow-specific
authentication). This separation resolves design confusion, establishes symmetry between push and pull patterns, and,
most importantly, creates a standard interface. This allows any application to become a compliant Data Plane,
fostering innovation and moving the industry toward a future where data sharing is a seamless, integrated layer within
sovereign applications, rather than a connector-centric task.&lt;/p&gt;</description></item><item><title/><link>https://eclipse-edc.github.io/blog/1/01/01/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eclipse-edc.github.io/blog/1/01/01/</guid><description>&lt;h1 id="the-path-to-version-1-for-the-eclipse-dataspace-components"&gt;The Path to Version 1 for the Eclipse Dataspace Components&lt;a class="td-heading-self-link" href="#the-path-to-version-1-for-the-eclipse-dataspace-components" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h1&gt;&lt;p&gt;The &lt;a href="https://github.com/eclipse-edc"&gt;Eclipse Dataspace Components (EDC)&lt;/a&gt; project has evolved significantly since its initial release. What started as an experimental reference implementation for dataspace connectors has grown into a mature, modular framework used in a variety of production-grade data sharing environments.&lt;/p&gt;
&lt;p&gt;Over the past few years, the project has continuously expanded its capabilities, aligned with emerging dataspace specifications, and improved its operational maturity. With these developments in place, the project is now approaching an important milestone: &lt;strong&gt;Version 1.0&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>