docs: add roadmap document #124
Conversation
|
|
||
| ## 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. |
There was a problem hiding this comment.
Lines 5 and 6 are duplication of contents.
| 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).
|
|
||
| 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. |
|
|
||
| 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?
| * 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 CONTRIBUTING.md. They are also part of the project webpage. We should really use the EF project website more as a marketing tool, not this repository.
| * Community Calls: Monthly on Thursday 10:30 am to 11:00 am CET to be announced via the Discussions in the Dataspace Protocol Repository | ||
| * 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.
What this PR changes/adds
Adding the roadmap
Why it does that
Stakeholder considerations
Further notes
Linked Issue(s)
Closes #123
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.