Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added BlackBerry as a user of VSS and a few minor updates

...

This page is an aggregation of links to various Vehicle Signal Specifications resources.  It is intended to provide a quick reference access to everything VSS.  If you do not find what you are looking for or see things that are missing, please let us know.

***If you want to dive right into the spec or documentation go to GitHub***

Table of Contents

Table of Contents
stylecircle

COVESA VSS Wiki

The VSS page on this wiki is a good starting point that leads/points to all of the other locations.   

Calendar and Collaboration Channels

...

Calendar and Mailing List are only accessible with a Google account.  

If you have not already done so you can create a Google account without changing their email address here:
https://accounts.google.com/SignUpWithoutGmail

(mailing lists and Slack)

The COVESA Community Calendar contains all open COVESA meetings.  

Data Expert Group Mailing List (Google Group)

https://groups.google.com/a/covesa.global/g/data-expert-group

Slack

For historic reasons VSS and VSC channels are in w3auto workspace and Data Expert Group is in covesacommunity workspace

GitHub

GitHub is where almost all of the VSS project work is maintained.  TheThe main page contains links to   

  • Documentation

    • A straight forward set of topics that give a good overview of VSS

  • Releases

    • Release links with lists of what has changed

  • Specification/Catalog

    • VSS specification refers to the standard catalog. It is maintained in yamlYAML.  It is fully expected that not everyone will implement all data elements/signals and they will likely implement some number of proprietary elements/signals.  VSS is still a useful methodology/rule set for defining interoperable models.

  • Tools

    • Tools are maintained in a separate repository

  • GitHub Project wikiWiki

    • VSS project team uses the VSS wikWiki for documenting a variety of things including releases.

  • Pull Requests 

    • All edits and updates are presented to the team through Pull Requests and are discussed in weekly meetings.

  • Issues

    • All issues are tracked through GitHub issues

...

  • Introduction to Vehicle Signal Specification at COVESA AMM October 2022 (deck)
  • Introduction to Vehicle Signal Specification (presentation) at COVESA AMM Spring April 2022 (deck)
  • VSS and VSS Ontology (presentation) at at COVESA AMM Spring 2022 (deck)

...

There are various implementations where VSS is used as data model for vehicle data.  Beside several closed-source implementations, here are the ones that are shared publicly:

...

  

OEM and Supplier Adoption

  • BMW
    • Mapped proprietary descriptions of vehicle data to VSS, for millions of cars.
    • Employing GraphQL to create a backend single access layer for querying data coming from various storage and streaming systems. Demonstrated backend application based on this solution. While for data streaming use cases, other technologies that are supporting VSS might be in place.
  • Volvo
  • Ford 
    • EV Charging Event Data Aggregation project led by Ford is actively updating the VSS model for EV Charging 
    • Internally working with VSS as a starting point for a variety of data related and development projects
  • Mercedes 
    • Internally working with VSS as a starting point for a variety of data related and development projects
  • BlackBerry
    • Used for signal normalization in the BlackBerry IVY product.

Open Source Implementations

Spotlight Series

...

COVESA Spotlight is a series where member organizations from the COVESA Community present their use/implementation of COVESA's Vehicle Signal Specification answering the following questions:

  • Why VSS was used? / The value of using VSS?
  • How VSS was used?
  • What could be improved in VSS?

You can find the past presentations from the series here.  If you are interested in presenting your VSS implementation, please contact the Community Director.

Joint Projects with W3C 


Note

VISS and VISSR are now maintained in COVESA GitHub.  This section is for historical purposes and will eventually be removed.

Covesa has joint projects to develop and standardize certain technology through the W3C process.

...