Meeting minutes
VSSo publication
https://
RESOLUTION: Publish as FPWD
vsso proposed shortname and vsso and vsso-core namespaces will be requested
Issues and Pull Requests
https://
Ulf: following advice from Carine and appreciate Wonsuk's contributions for Transport and Core
… my view is we should merge both of them
… any opinions?
https://
Ulf: my thought on this issue we've discussed previously is that the added complexity of adding an additional, similar method is not worthwhile
… Peter expressed that Volvo isn't interested in scenario 1 nor 2, but more toward 3
… Sebastian saw interest, wonder if Erik has had a chance to discuss with him. we could leave open if needed or close and of course revisit if people feel strongly
Erik: Sebastian's comment was based on Kuksa implementation where he used the same mechanism instead of another
… this would be for few, specific cases
… would we not add anything to the spec?
Ulf: currently we say sensors aren't writable which we might want to change to allow for scenarios discussed
Erik: in VSC call yesterday, some people raised desired value for actuators and can see that logic applying to sensors
Ted: challenge will be wording on the flexibility
Gunnar: something like: when the specification is used to present signals to the outside sensors should be read only but may be writeable for internal use
Messaging and explainer
Ted: we need to sell the specs more and improve messaging, starting to brainstorm with COVESA, W3C, NXP, WindRiver, Bosch, Geotab etc
https://
https://
Ted: Peter kicked off explainer, I made a number of proposed edits and notes on what else we need
… also we need to learn of intent to implement VISSv2 or experiment further from CVII group participants. we will need a second implementation to advance in the W3C process and heard a few were considering or actively trying it
… I'll encourage them more by email and in slack to share with us, problem with the industry is how secretive companies are about their plans