Automotive Working Group Teleconference

<scribe> Agenda: https://lists.w3.org/Archives/Public/public-autowebplatform/2017Feb/0005.html

Discussion of myriad of teleconferences

Ted will create an ical with the various calls, people should feel comfortable to only attend which are pertinent to them and not interfere with sleep. Minutes will be taken and shared plus summaries in BG and WG meetings.

LBS update

Wonsuk: we will skip the LBS update given holidays in China

Media tuner update

Wonsuk: I am hoping Ryan can give us an update on the status of his activity

Ryan: I plan on being on for the time being but expect iHeart might be leaving the activity
... even without our participation, I would be welcome to provide any feedback
... I can take a look at ViWi for the next month to see how that might work for auto
... it is very similar in the direction we have been discussing with the TV Controller API

Kaz: are you planning to participate in the Auto BG and TV Control WG as a public commenter or as an Invited Expert
... you can send feedback and comments to the public lists. let's talk about the detail later.

Wonsuk: this might be more pertinent to discuss in the ViWi call next week

Kaz: Ryan's participation in the TV Control group has been beneficial there as well

<kaz> viwi.service.media

Ted: I am interested in hearing more from Ryan if he can elaborate on the comparison between ViWi and TV Control WG is considering
... the participation concerns in that group makes ViWi more pertinent

[Ryan is on WebEx but seems to have dropped audio]

Wonsuk: PatrickL perhaps you can elaborate on the higher level Media services in ViWi

PatrickL: it can provide play lists from cd, usb, other libraries, renderers etc
... that is what it is currently able to do. it is quite easy to extend

Wonsuk: it already has various applications like Spotify and such, correct?

PatrickL: there is no Spotify viwi api available right now publicly, internally we have a mapping available

Wonsuk: I am hoping this architecture is something that can be used by app developers to interact with eg Spotify

PatrickL: the developer can go directly to spotify api. it is possible for app developers (spotify etc) can follow our general model and make their content available that way similar to Android Auto approach

<Zakim> kaz, you wanted to mention that TV Control WG's work is defining high-level JS API: https://www.w3.org/TR/tvcontrol-api/

Kaz: TV control WG is working on a higher level JS API and ViWi could be on layer underneath

Ted: I think that is enough for now, good to hear about layered approach and we will discuss additional domains including media

Discussion for VIWI proposal

Wonsuk: I see Kevin added some text to the wiki

Kevin: contributing to the debate

https://www.w3.org/community/autowebplatform/wiki/ViWi

Kevin: there are benefits listed for REST, there are others for web sockets

<kaz> Why to REST?

<kaz> Pros and Cons

Ted: there have been a number of good conversations and encourage people to continue contributing to the wiki

<kaz> Convergence call minutes

Wonsuk: any more on ViWi discussion?

Ted: another point was Urata-san wisely encouraged us to come up with a timetable for next gen and other WG deliverables with the VISS spec going to CR in April

Wonsuk: Patrick, what do you see as more important domains after vehicle signals?

<kaz> VIWI submission including 6 documents

PatrickL: media certainly, navigation, car data are the three biggest
... we were not allowed to share too much on navigation at this point
... once we get really started with the other domains it would be a good starting point

Ted: can you elaborate on navigation plans?

PatrickL: it is possible to get a version that would be pertinent for W3C with possibly some things ommitted
... there are clear advantages to have navigation information available to multiple applications
... there will be differences, a subset of what we are using internally
... after that it can evolve independently in W3C and we will be adapting ourselves
... there is clear need for navigation information in this space

Kaz: does this include map and geolocation information?

PatrickL: you get location objects, current GPS coordinates and other dead reckoning of the car
... this is something that should be available to every app developer within vehicle space
... there are some early considerations for bringing this to W3C

Kaz: I have been working with Geolocation WG at W3C but they are not well suited for these purposes

-> https://www.w3.org/2015/10/26-27-auto-minutes.html TPAC Sapporo minutes

PatrickL: yes we need to handle non-JS applications as well, running on a phone in the car for instance

Ted: the kid in the back seat asking "are we there yet" (incessently) use case...

Wonsuk: are you looking at notifications as well?

PatrickL: yes

[W3C Geolocation and Automotive met in Sapporo and resolved their needs are too different]

Payments within vehicle

-> https://lists.w3.org/Archives/Public/public-autowebplatform/2017Feb/0001.html update on Automotive Web Payments

Ted: also at Sapporo TPAC we met with Web Payments IG where Kevin made a presentation on auto use cases. That group is vibrant and acts as an incubator of future work much like our BG with spec work taking place in a WG. They are starting to look at specific needs in addition to general payments. I made sure we circled back as they were doing so and our proposed coordination work is being well received. I will attend their F2F meeting on 22 March and hope we can get going in April. I touched on Distraction, connectivity and shared vehicle concerns.

-> https://www.w3.org/2017/Talks/tg-autopay/ slides on proposal

<kaz> joint discussion with the Payments IG in Sapporo

<kaz> Payments f2f in Chicago in March

Wonsuk: I think it is a very interesting item. Carsharing services are being more widely used in Korea
... people can schedule taking a car and using a smartphone application can unlock the reserved car
... cost is based on usage
... we need to describe these type of use cases clearly
... and from there what to standardize

Ted: agree, we are seeing car sharing models emerge in urban centers elsewhere as well
... I will continue to keep the BG appraised

Wonsuk: next BG meeting

Kaz: Second Tuesday of the month so March 14th

their F2F meeting on 22 March and hope we can get going in April. I touched on Distraction, connectivity and shared vehicle concerns./