BMW VISS implemention questions

Hi Andre and Adnan,

It was good seeing both of you in Porto recently, hearing more about VISS
usage in Android and how there might be support in open sourcing [parts of]
your implementation.

I hope you are progressing in being able to open it up. If there is
anything we can do to help with that please let us know. We can write
something making clear the outside interest and it might be easier to do so
with a W3C or COVESA Github repo.

We have an issue we've been stuck on for some time, raised by the W3C
Privacy Interest Group as we sought to advance the specification towards
completion. How are we addressing privacy. Part of the problem is not
having a single, consistent architecture for how VISS could be used.

Ulf would like to see VISS used for being able to pull data from the
vehicle to the cloud. I see it more useful for in-vehicle applications
performing data sampling and assessment before sending off. The BMW use is
to support apps running on Android Automotive in the head unit and
potentially also smartphone apps paired to the vehicle. Privacy obviously
not an issue in presenting vehicle data within the vehicle, but probably
something you address in allowing a smartphone to pair. Can you tell us
more about what you did there?

We are reluctant to tackle consent management in the W3C Automotive WG but
believe it should be done and VISS could and should be able to inform
client application of permissible use or even enforce 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/>