VISS stage in W3C process

While various parts of this has been expressed on both COVESA CVII and W3C
calls, it is probably worth writing out and sharing.

VISSv2 is considered feature complete
---------------------------------------------------

We do not have any outstanding, substantive requests we are currently
considering for version 2.

It is currently at Working Draft state and want to advance in the
recommendation process but more importantly we want to see uptake.

Need for feedback, encourage adoption
----------------------------------------------------

BMW will be sharing their implementation for Android Automotive at the
upcoming COVESA All Member Meeting.

We want to hear from others who are considering, evaluating or
moving forward with VISS based solutions whether you are a member of
COVESA, W3C or neither. You would be most welcome as observers if not
presenters in our group calls. Please let Peter, Ulf or I know of your
interest.

Ulf and I are starting to work with another, undisclosed OEM on
experimenting with VISS in their platform. Unfortunately this is under NDA
for now but we hope it may lead to production use and (or at least) can
share the results. We have vehicle to cloud and in-vehicle uses to test. We
are open to doing similar "consulting" on adopting these COVESA/W3C
standards for others.

We have on a few occasions deferred on feature requests for version 2, we
can now start thinking about version 3 especially if people are starting to
use it and can provide meaningful input on what would be helpful to have in
it.

-- 

Ted Guild (he, him, his)
Geotab

Connectivity Standards Lead

Direct
Toll-free

Visit

+1 (702) 283-0208
+1 (877) 431-8221
www.geotab.com

Twitter <https://twitter.com/geotab> | Facebook
<https://www.facebook.com/Geotab> | YouTube
<https://www.youtube.com/user/MyGeotab> | LinkedIn
<https://www.linkedin.com/company/geotab/>