#234: Vehicle Information Service Specification (VISS) CR
Discussions
2019-01-15
Dan: I don't have a car.
Hadley: I haven't driven a car in ages! (But we have a fresh perspective.) Summary: They couldn't break out of the manufacturing idea; couldn't handle the constantly-updating idea. [Gives brief history of issue]
- Wanted to bundle car sensors, but there were complications... wanted to push them to HTTP to handle diverse topologies, etc.
- Clarified what a phone that plugs into the car could get access to; infotainment system capabilities.
- The web has many of the same primitives they were trying to re-invent...
- Issue on liability; if 3rd party builds a poor infotainment system, that has liability on the manufacture.
Dan: Any updates since we last looked at this?
Hadley: The crew is in CR and want more feedback/revisions before finalizing. Have pinged Yves on a different issue... May be able to close this out (process wise), but should ensure we can circle back later.
Yves: There is danger to them re-inventing the wheel--protocol-wise. I've been prompting them over time. I will communicate to Ted to have them send issues our way over time.
OpenedMar 6, 2018
こんにちはTAG!
I'm requesting a TAG review of:
Further details (optional):
You should also know that...
TAG has reviewed issues with VISS. We would appreciate a formal review of the CR version of the spec.
We'd prefer the TAG provide feedback as (please select one):