Erik Jaegervall (Jägervall)

I would appreciate any proposal (that possibly could be added to our [guidelines](https://github.com/COVESA/vehicle_signal_specification/blob/master/CONTRIBUTING.md#guidelines-and-recommendations)) on how to organize data/branches. As of today when discussed we have said that the tree structure...

I assume no one would object to adding a jsonschema, could be a good addition. I assume it needs to be used after converting *.vspec files to json as the...

MoM - WI-FI/WIFI - PP: No major preferences, we could align with old `WIFI - Stefan: Does not matter - Erik: Please review/discuss, continued discussion next meeting

Trying to summarize my view on this PR. - At last meeting we agreed to use `WIFI` rather than `WI-FI` to avoid changing name of other already existing signals using...

MoM: - OK to merge if resolution signal removed - Richard Fernandes - Resolution can be complex due to DRM, we from AOSP could possibly contribute

Is this a request of support for some type of enum-support where we with some synatx (VSS-like or totally different) give a more formal definition? Like for `Vehicle.Powertrain.FuelSystem.SupportedFuel`, one could...

It is a recurring discussion if the terms sensor/actuator/attribute are good, or if there are some better terms. As you say, people often think of sensors and actuators as something...

Discussed in recent VSS meeting - conclusion let us put VSS 5.0 for hold right now, i.e. only release 4.1. But be prepared to release 5.0 when considered needed.

No requests for 5.0 yet, but we should better decide. Suggestion: - Prepare for a 5.0 release around AMM (April) - Plan for the last 4.X release 6 months later...

MoM: - Sebastian: We should release 5.0, when we release a 5.X we should check if we also release a 4.X - Nick: Release around AMM would be good