<commit_before># VEHICLE SIGNAL SPECIFICATION


[![License](https://img.shields.io/badge/License-MPL%202.0-blue.svg)](https://opensource.org/licenses/MPL-2.0)
[![Build Status](https://travis-ci.org/GENIVI/vehicle_signal_specification.svg?branch=master)](https://travis-ci.org/GENIVI/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. 

Please find the official documentation at: [Vehicle Signal Specification](https://genivi.github.io/vehicle_signal_specification/)

## Getting started

### Using VSS
To use a specific version of VSS in your toolchain, head over to our [releases page](https://genivi.github.io/vehicle_signal_specification/releases/).


**Latest release:** [2.1](https://github.com/GENIVI/vehicle_signal_specification/releases/tag/v2.1)


### Contribute to VSS
Work towards version 2.2 is continuously ongoing in the [master branch](https://github.com/GENIVI/vehicle_signal_specification/tree/master)

To work with the specification directly, you need to clone this repository.

This repository uses git submodules.  Please make sure you clone recursively,

```
git clone --recurse-submodules https://github.com/GENIVI/vehicle_signal_specification
```


Alternatively, just init and update the submodules after the initial cloning:

```
git clone https://github.com/GENIVI/vehicle_signal_specification
git submodule update --init<commit_msg>README.md: Update build badge to refer to Github actions workflow instead of Travis<commit_after># VEHICLE SIGNAL SPECIFICATION


[![License](https://img.shields.io/badge/License-MPL%202.0-blue.svg)](https://opensource.org/licenses/MPL-2.0)
[![Build Status](https://github.com/GENIVI/vehicle_signal_specification/actions/workflows/buildcheck.yml/badge.svg)](https://github.com/GENIVI/vehicle_signal_specification/actions/workflows/buildcheck.yml?query=branch%3Amaster)

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. 

Please find the official documentation at: [Vehicle Signal Specification](https://genivi.github.io/vehicle_signal_specification/)

## Getting started

### Using VSS
To use a specific version of VSS in your toolchain, head over to our [releases page](https://genivi.github.io/vehicle_signal_specification/releases/).


**Latest release:** [2.1](https://github.com/GENIVI/vehicle_signal_specification/releases/tag/v2.1)


### Contribute to VSS
Work towards version 2.2 is continuously ongoing in the [master branch](https://github.com/GENIVI/vehicle_signal_specification/tree/master)

To work with the specification directly, you need to clone this repository.

This repository uses git submodules.  Please make sure you clone recursively,

```
git clone --recurse-submodules https://github.com/GENIVI/vehicle_signal_specification
```


Alternatively, just init and update the submodules after the initial cloning:

```
git clone https://github.com/GENIVI/vehicle_signal_specification
git submodule update --init
{'fraction_non_alphanumeric': 0.10392824002474482, 'fraction_numerical': 0.007732755954222085, 'mean_word_length': 5.6, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 20, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '159064', 'n_tokens_mistral': 997, 'n_tokens_neox': 916, 'n_words': 271}