Erik Jaegervall (Jägervall)
Erik Jaegervall (Jägervall)
This is a PR for cherry-picking items from vss/vss-tools master to 4.X_branch. This PR shall not be merged "as is" but rather be added by a push directly to 4.X....
This PR introduces signals like `Vehicle.Driver.HeadPosition.X` and `Vehicle.Driver.MidEyeGaze.Azimuth`. They can be useful in driver monitoring system to detect what the driver is looking at, and/or to monitor that the driver...
We have decided to release 4.1 before year end. It will contain all minor (not backward incompatible changes) from master, see current content at 4.X branch. In addition to those...
Now and then we discuss if the current instance solution is sufficient. We have some issues and pull requests currently opened: #564 suggests to be able to have instances on...
In https://github.com/COVESA/vehicle_signal_specification/blob/master/spec/units.yaml we use units like `m/s^2`, but we do not specify the format we use for describing units, like why we use `^` for acceleration. Preferably we shall add...
A topic that comes up now and then is removal of the [OBD](https://github.com/COVESA/vehicle_signal_specification/blob/master/spec/OBD/OBD.vspec) branch. Sometimes the rationale is that COVESA should not care about diagnostics data at all, sometimes that...
The `instantiate: false` attribute is described in VSS documentation but not actively used in current VSS standard catalog. It is intended to give something similar to C++ static class members,...
We need to agree on a process for how to handle major vs minor releases. **Background** Now and then we see a need to do backward incompatible changes, like changing...
**Background** We try as much as possible to reuse signals for recurring purposes like `IsOpen` and `Position`. That works quite well with the `#include` concept, but as of today that...
A recurring topic is how to handle vehicle variation - how can you find out which signals that are supported by a specific vehicle? This issues intends to capture the...