docs: add roadmap document #124
+45
−0
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| # Dataspace Protocol Specification - Scope, Roadmap and Milestones | ||
|
|
||
| ## Scope | ||
|
|
||
| The Dataspace Protocol is a set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications define the schemas and protocols required for entities to publish data, negotiate Agreements, and access data as part of a federation of technical systems termed a Dataspace. | ||
| The web rendering of the Dataspace Protocol represents the current state on this repo's main branch: https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/ | ||
|
|
||
| The Dataspace Protocol aims a release as Eclipse Specification combining this specification with the Dataspace TCK (https://projects.eclipse.org/projects/technology.dataspacetck ) and at least one conformant implementation. The Eclipse Dataspace Components EDC (https://projects.eclipse.org/projects/technology.edc ) are planned as compliant implementation, others are welcome. The Dataspace Protocol targets a PAS transposition to ISO during 2025. | ||
|
There was a problem hiding this comment. First sentence sounds weird, as the DSP is not combined with other projects.. there are interdependencies defined by EF. Maybe we can link to that. Second sentence makes a statement about another project + marketing speech - inappropriate. Would probably rather fit to the project webpage, not the sources (repository). |
||
|
|
||
| ## Status (February 2025) | ||
|
|
||
| The Dataspace Protocol project is approved by the Eclipse Dataspace Working Group (EDWG) and the Eclipse Foundation. International Data Spaces Association IDSA contributed the specification document as the initial contribution in summer 2024. The first progress review is scheduled for Q1/2025 and the release 1 is scheduled for summer 2025. | ||
|
|
||
| The Dataspace Protocol has a healthy number of committers (4 organizations and 7 individuals) and contributors, see https://projects.eclipse.org/projects/technology.dataspace-protocol-base/who . 72 commits have been provided to the main branch since the project start. | ||
|
|
||
| The Dataspace Protocol is adopted by various industrial users. | ||
|
|
||
|
|
||
| ## Resources | ||
|
There was a problem hiding this comment. Sounds like information that is visible within the repositories. Why do we need this here? |
||
|
|
||
| * Source Code Management: A new organization has been created on GitHub for the project: | ||
| https://github.com/eclipse-dataspace-protocol-base | ||
| * Repositories: The Dataspace Protocol specification document is in the repository https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol. Otterdog is enabled for the GitHub organization and maintained in the https://github.com/eclipse-dataspace-protocol-base/.eclipsefdn Repository | ||
| * A repository for the website is added. See below | ||
| * Issue Tracker: | ||
| * GitHub issues have been enabled for the project. | ||
| * Outbound Communication: | ||
| * Mailing list: https://accounts.eclipse.org/mailing-list/dataspace-protocol-base-dev | ||
| * Website: The: https://github.com/eclipse-dataspace-protocol-base/website repo has been created and added to our publishing tool. The website is available at https://eclipse.dev/dataspace-protocol-base. | ||
| * The Dataspace Protocol human-friendly rendering is available at https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/ | ||
| * Downloads: http://download.eclipse.org/dataspace-protocol-base | ||
| * Archives: http://archive.eclipse.org/dataspace-protocol-base | ||
| * Community Calls: Monthly on Thursday 10:30 am to 11:00 am CET to be announced via the Discussions in the Dataspace Protocol Repository | ||
|
There was a problem hiding this comment. The meetings and communication should be added to |
||
| * Committer Calls: Weekly on Thursday between 10:00 am and 10:30 am CET | ||
|
|
||
| ## Roadmap and Milestones | ||
|
There was a problem hiding this comment. Wouldn't it be good to use the GitHub milestones for this? It provides a numbering, offers to set a title and due date. Then, we could also use assignment of issues to milestones instead of adding labels. |
||
| * MS 1: Initial Contribution, July 2024 (achieved) | ||
| * MS 2: Project is fully operational, October 2024 (achieved) | ||
| * MS 3: DSP Editor’s Draft and TCK alpha 1, February 2025 | ||
| * MS 4: Successful Progress Review, March 2025 | ||
| * MS 5:DSP TCK alpha 2, April 2025 | ||
| * MS 6: DSP Release Candidate and TCK Beta, May 2025 | ||
| * MS 7: DSP Release review, May to June 2025 | ||
| * MS 8: DSP Release 1, July 2025 | ||
| * MS 9: Start of PAS Transposition to ISO, August 2025 | ||
| * MS 10: Initiating planning for the next release, October 2025 | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lines 5 and 6 are duplication of contents.