The Central Data Service Playground (CDSP) is 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.
For further information please see the CDSP documentation.
Note
CDSP is a young project and there are some gaps to fill here and there in project setup and more comprehensive documentation. Please bear with us as we do that. That said you should find the actual code works. Please ask questions on chat or join the COVESA Data Architecture team call.
A good place to start is the overview in the documentation which introduces why the project exists, the logical concept and its implementation.
Once you are ready to jump into some code the docker deployment readme explains building and starting the playground. Whilst the examples folder contains a variety of examples to explore.
The playground git source repository contains git submodules which need to be initialized either during the clone or afterwords as shown below.
Clone with git v2.13 and later:
git clone --recurse-submodules https://github.com/COVESA/cdsp.git
Clone with git v1.9 and later:
git clone --recursive https://github.com/COVESA/cdsp.git
If the repository is already cloned:
cd <path to cdsp root>
git submodule update --init --recursive
See the github issues for this project with the bug label.
The project originated in the COVESA data architecture team.
The project maintainers are:
- Stephen Lawrence, Renesas Electronics
- Christian Muehlbauer, BMW AG
| Resource | Notes |
|---|---|
| Project management | COVESA Github Project Central Data Service Playground |
| Issue tracking | Github issues for this project |
| Chat | Covesa Community Slack channel #data-architecture-pillar |
| Wiki | Data architecture team project page in COVESA Confluence |