Repository files navigation

The overall goal of the Vehicle Signal Specification (VSS) is to create a common understanding of vehicle signals in order to reach a “common language” independent of the protocol or serialisation format.

Generated documentation from latest commit on master branch is available at:Vehicle Signal Specification Documentation.

To use a specific version of VSS in your toolchain, head over to ourreleases page.The latest official release can be foundhere.

Work towards the next version is continuously ongoing in themaster branch.To work with the specification directly, you need to clone this repository.

For more information on how to set up the development environment and to be able to transform source *.vspec files toother formats see ourbuild guideline document and documentation inVSS-tools.

The community has regular calls to discuss topics around VSS.This includes specific tickets in this repository as well as the broader direction in which VSS is evolving.You can find current call coordinates and dates inour wiki.

For detailed information see ourcontribution guide!

Both VSS (this repository) andVSS-tools use aPEPinspired version scheme.

Version is visible in theVehicle.vspec file whereVersionVSS.Label typically is-dev for ongoing work in master-branch and an empty string for released versions.

Versions are tagged in the formvX.Y(.Z) and the same syntax is used as names for VSS releases.VSS-tools is tagged but not released.For release candidates the formvX.YrcN is used. ThercN suffix is not used inVehicle.vspec files.

For more information on how versions are managed see theRelease Instruction

VSS is an open standard and we invite anybody to contribute. Currently VSS contains - among others - significant contributions from

• Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
• Volvo Cars
• Jaguar Land Rover
• Robert Bosch GmbH
• Geotab Inc.