Erik Jaegervall (Jägervall)

@gunnarx @tguild - do you know the status of the Android implementation (branch `code_generation`). Anyone actively working on it?

Some historic background: In the past the VSS standard catalog quite often had arbitrary min/max limits. Like specifying that speed had `max: 300`. They were removed as available min/max values...

Some info on overlays can be found at https://covesa.github.io/vehicle_signal_specification/rule_set/overlay/. You could also look on some of the test cases that exist, like https://github.com/COVESA/vss-tools/tree/master/tests/vspec/test_overlay

> I am willing to take up this feature addition. Is there any document or diagram which may help me briefly understand the flow of code in the py files....

See #340 for an example on how DDSIDL struct support works as of today, that could help identifying improvement areas. If we think it is good enough we should close...

There is a small note in https://github.com/COVESA/vehicle_signal_specification/blob/master/CONTRIBUTING.md#use-existing-style that American English is preferred, but having it in the general documentation as well makes sense. From my perspective a Pull Request from...

Some answers: **Detection of broken links in generated documentation** Would indeed be a good improvement. A pull request checking it as part of CI would be gladly accepted. Added #600...

Meeting notes: - Fulup: If interested please feel to test the parse, requests and pull requests welcome - Achim: unit conversion discussed also in AUTOSAR

PR updated to use version from https://github.com/COVESA/vss-tools/blob/master/setup.py

MoM: - Please review - Possible merge decision next meeting