#234: Vehicle Information Service Specification (VISS) CR

Visit on Github.

Opened Mar 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):

  • open issues in our Github repo for each point of feedback
  • open a single issue in our Github repo for the entire review
  • leave review feedback as a comment in this issue and @-notify [github usernames]

Discussions

2018-03-20

Minutes

Peter: Hadley isn't here, so let's punt.

2019-01-15

Minutes

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.

2019-01-22

Minutes

Peter: do we have a wrap-up for this?

Sangwhan: May need to check at F2F?