Groups & Projects
Central Data Service Playground
The Central Data Service Playground was conceived to meet various COVESA community needs including:
- A neutral playground to investigate the 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, and shared costs in development and can lead to quicker outcomes. For example, jump from “What is the box” to “How are we using the box”.
Project Page: https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground
| Lead: | Stephen Lawrence (Renesas) |
| Meetings: | Weekly on Wednesdays at 17:00 CET / 11:00pm ET / 8am PT (Community Calendar) |
| Project Page: | https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground |
| License: | MPL-2.0 |
| GitHub: | https://github.com/COVESA/cdsp |
| Slack Workspace: | https://covesacommunity.slack.com; Channel: #data-architecture-pillar |
| Parent: | Data Expert Group |
COVESA Spotlights
Commercial fleets run on data. These fleets include a wide range of vehicle classes ranging from passenger cars, delivery vans, and heavy-duty trucks to construction equipment, and are owned and operated by a commercial entity instead of an individual....
Consumers expect the absolute best, safest, and problem-free content and experiences integrated into their digital world from their phones, smart home devices, computers, and electronic devices immediately as they become available. Why would they expect less from their vehicles? The reality today is not quite so simply in the Automotive industry and the vehicle’s data space is often messy and disconnected...
Collaboration to unify guidelines and interoperability for vehicle applications, primarily within the Android open source environment (AOSP). With mutual requirements, guidelines for APIs and reference implementations we can reduce cost and speed up time to market while enabling app developers to develop once and then easily deploy to many OEMs...