Awesome
VEHICLE SIGNAL SPECIFICATION
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.
Getting started
Using VSS
To use a specific version of VSS in your toolchain, head over to our releases page. The latest official release can be found here.
Work towards the next version is continuously ongoing in the master 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 to other formats see our build guideline document and documentation in VSS-tools.
Discuss all things VSS, "meet" the community
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 in our wiki.
Contribute to VSS
For detailed information see our contribution guide!
VSS version and release handling
Both VSS (this repository) and VSS-tools use a PEP inspired version scheme.
Version is visible in the Vehicle.vspec file where VersionVSS.Label typically is
-dev for ongoing work in master-branch and an empty string for released versions.
Versions are tagged in the form vX.Y(.Z) and the same syntax is used as names for VSS releases.
VSS-tools is tagged but not released.
For release candidates the form vX.YrcN is used. The rcN suffix is not used in
Vehicle.vspec files.
For more information on how versions are managed see the Release Instruction
Contributors
VSS is an open standard and we invite anybody to contribute. Currently VSS contains - among others - significant contributions from