The Eclipse Data Plane Signaling specification defines an interoperable protocol for DSP control planes to communicate with data planes. The scope of the specification includes:
- A protocol for control planes to manage data transfers using a variety of wire protocols, ranging from HTTP-based to streaming event systems.
- A registry of data transfer types so that other projects can define non-clashing identifiers for those types.
- An associated TCK in the [Eclipse Dataspace TCK](https://github.com/eclipse-dataspacetck) project.
The following are out of scope for Eclipse Data Plane Signaling:
- The definition of specific wire protocol formats and data transfer types
- Any data plane implementation
| Repository | Commits | Reviews | Issues |
|---|---|---|---|
| https://github.com/eclipse-dataplane-signaling/dataplane-signaling | 30 | 12 | 13 |
| https://github.com/eclipse-dataplane-signaling/.eclipsefdn | 5 | 0 | 0 |
There have been 35 commits made by 5 people on 2 repositories over the last 12 months.
There have been 13 issues submitted by 4 people on 1 repositories over the last 12 months.
There have been 12 reviews submitted by 2 people on 1 repositories over the last 12 months.
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/technology.dataplane-signaling
TruewriteThis project has a total of 1 repositories in its associated GitHub organization eclipse-dataplane-signaling
.
The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset:
