Closed tguild closed 4 years ago
@gunnarx on Auto WG call suggested including this information directly in VSS itself which was received favorably.
I will raise as an issue in VSS repo and leave this open until accepted if not resolved there. At that point I will create wording to include in the spec as to how to identify the VSS version.
https://www.w3.org/2019/10/22-auto-minutes toward the end of the call but lacking an agenda item anchor.
Gunnar: for versioning, I want to keep it minimal. one idea would be a data item in VSS itself that includes the value in tree itself ... you handle it directly in Git when you make a branch for a release
Created issue in VSS repo, will reopen the issue in this repo if they reject
https://github.com/GENIVI/vehicle_signal_specification/issues/132
We should update VISS to convey what version of VSS is being exposed. My initial thinking is it would be appropriate to handle this in the getMetaData() method.