Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/blog/20260519-data-plane-migration/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ The current EDC-DataPlane implementation will be removed soon. DPS support will
downstream projects that still rely on it must fork the codebase and own the implementation going forward.

Data-plane implementations that already speak DPS are expected to emerge, such as
[`siglet`](https://github.com/eclipse-dataplane-core/dsdk-facet-rs/tree/main/siglet).
[`siglet`](https://github.com/eclipse-dataplane-core/siglet).

## Seamless upgrade

Expand Down Expand Up @@ -191,7 +191,7 @@ and compatibility work with no upstream support.

The recommended long-term approach is to adopt a data-plane built on the
[Data Plane SDKs](https://github.com/eclipse-dataplane-core) and the DPS protocol natively — for example
[`siglet`](https://github.com/eclipse-dataplane-core/dsdk-facet-rs/tree/main/siglet). These implementations are
[`siglet`](https://github.com/eclipse-dataplane-core/siglet). These implementations are
designed around the DPS specification from the ground up and are the supported path forward.

Plan to retire the shim-based data-plane as soon as the migration window closes.
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ plane registers with a control plane, which in turn directs the data plane throu
EDC doesn't include a data plane. Any application that implements DPS can be one:

- an existing data plane that speaks DPS, such as
[`siglet`](https://github.com/eclipse-dataplane-core/dsdk-facet-rs/tree/main/siglet);
[`siglet`](https://github.com/eclipse-dataplane-core/siglet);
- a data plane of your own, built with one of the [Data Plane SDKs](https://github.com/eclipse-dataplane-core)
([Java](https://github.com/eclipse-dataplane-core/dataplane-sdk-java),
[Go](https://github.com/eclipse-dataplane-core/dataplane-sdk-go),
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ including the data address and the credentials of the data flow.

Any application that implements DPS and registers with the control plane can be a data plane: one built with the
[Data Plane SDKs](https://github.com/eclipse-dataplane-core), an existing one such as
[`siglet`](https://github.com/eclipse-dataplane-core/dsdk-facet-rs/tree/main/siglet), or one written directly on the
[`siglet`](https://github.com/eclipse-dataplane-core/siglet), or one written directly on the
specification.

This section covers:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ describes what the EDC control plane expects of it; the protocol itself is defin

## 1. Where to start

- **Use an existing data plane.** [`siglet`](https://github.com/eclipse-dataplane-core/dsdk-facet-rs/tree/main/siglet),
- **Use an existing data plane.** [`siglet`](https://github.com/eclipse-dataplane-core/siglet),
from the Data Plane Core project, is driven by DPS and issues, verifies and renews the access tokens of the data flows,
so that existing APIs and data infrastructure can serve the data.
- **Build one with a Data Plane SDK.** The [Data Plane SDKs](https://github.com/eclipse-dataplane-core) implement the
Expand Down
Loading