...

Sub-pages below this one:

Introduction

The playground is Central Data Service Playground (CDSP) serves as a neutral, open playground for data services both within and outside the vehicle in the context of data-centric architectures. It enables investigation into the internals of these services and how they can be combined. Furthermore, the playground provides a means to publish and collaborate on such work in the open.

Further information can be found in the project documentation site.

The playground was conceived to meet various Covesa needs:

• A neutral playground to investigate internals of data services. In the context of data-centric architectures for example.
• A neutral playground to investigate, illustrate and disseminate combining data services and the Covesa eco-system with other parts of the vehicle and off-board. For example, to demonstrate how VSS data can be used with VISS for newcomers.
• Repeated use of shared terminology, patterns and tools leads to quicker understanding in discussions, shared costs in development and can lead to quicker outcomes.
  • Jump from 'what is the box' to 'how are we using the box' for example.

In the interim before the project itself provides the necessary explanations, for a better explanation of why, what and how please read the The original proposal for the project can be found here.

Project resources

<planning links, e.g. kanban board, to go here>

Project management: Github

Here you will find information on how the project is managed.

...

Resource	Notes
Source repository	https://github.com/COVESA/cdsp
Documentation	https://covesa.github.io/cdsp/
Project management	COVESA Github Project Central Data Service Playground
Chat

Covesa Community Slack channel #data-architecture-pillar: https://covesacommunity.slack.com/archives/C06353TRF5F

Presentations

Early planning

The Early planning can be found in the sub-page Early planning. As early planning for a new project is typically messy and can make it hard for later newcomers to the project to figure out what the project is for. To avoid the problem of trying to clean it up later early planning is taking place in a sub-page Early planning. That allows us to keep this landing page cleaner in preparation for a more appropriate progress summary as the project gets under wayit is being done there to avoid the later problem of a messy landing page that is hard for later newcomers to understand.