- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 14 Dec 2016 05:38:14 +0900
- To: "Streif, Rudolf" <rstreif@jaguarlandrover.com>
- Cc: "public-autowebplatform@w3.org" <public-autowebplatform@w3.org>
- Message-ID: <CAJ8iq9XZ9UZMHfHnxDbEQ_FxUDX8w1aYWzbhPbsEgGgdFtvt1Q@mail.gmail.com>
On Wed, Dec 14, 2016 at 4:49 AM, Streif, Rudolf <rstreif@jaguarlandrover.com > wrote: > Thank you, Kaz. > > I think the attendee list is missing Philippe Robin (GENIVI). You have > Philippe Colliot (PSA) on the list. > Thanks, Rudy! And very sorry, Philippe! The minutes at: https://www.w3.org/2016/12/13-auto-minutes.html are fixed accordingly. Kazuyuki > > Rudi > > On Tue, Dec 13, 2016 at 10:19 AM, Kazuyuki Ashimura <ashimura@w3.org> > wrote: > >> available at: >> https://www.w3.org/2016/12/13-auto-minutes.html >> >> also as text below. >> >> Thanks, >> >> Kazuyuki >> >> --- >> [1]W3C >> >> [1] http://www.w3.org/ >> >> - DRAFT - >> >> Automotive BG >> >> 13 Dec 2016 >> >> [2]Agenda >> >> [2] https://lists.w3.org/Archives/Public/public-autowebplatform/ >> 2016Dec/0002.html >> >> See also: [3]IRC log >> >> [3] http://www.w3.org/2016/12/13-auto-irc >> >> Attendees >> >> Present >> Kaz_Ashimura, Paul_Boyes, Philippe_Colliot, Qing_An, >> Ryan_Davis, Wonsuk_Lee, Ted, Adam_Crofts, >> Shinjiro_Urata, Rudi_Streif, Tatsuhiko_Hirabayashi >> >> Regrets >> Chair >> Wonsuk, Paul, Qing_An >> >> Scribe >> kaz, ted >> >> Contents >> >> * [4]Topics >> 1. [5]Media tuner >> 2. [6]Redefining the role of the BG >> 3. [7]Test environment >> * [8]Summary of Action Items >> * [9]Summary of Resolutions >> __________________________________________________________ >> >> Media tuner >> >> <inserted> scribenick: kaz >> >> -> [10]https://www.w3.org/2016/12/13-tvapi-minutes.html TV >> Control minutes >> >> [10] https://www.w3.org/2016/12/13-tvapi-minutes.html >> >> ryan: working on media tuner topic >> ... discussion with the TV Control guys >> ... really productive >> ... based on a common ground >> ... brought use cases from auto >> ... the way the tuner spec is written is hardware-centric >> ... not only a tuner but collection of tuner and player would >> be needed >> ... "tuner" is confusing from technical viewpoint >> ... I'm submitting some high-level architecture >> ... getting out of the concept of "tuner" and use another >> concept of "player" >> ... playing/decoding media >> ... a player may be responsible some media stream >> ... and another player might be responsible to another resource >> ... this morning all the TV Control guys agreed >> >> paul: sounds good >> >> kaz: yes >> >> ryan: the original use cases I had on the spreadsheet >> ... will be rewritten >> ... the architecture is in question >> ... they're looking the recorder capability as a different >> entity >> ... but a player could be simply connected to a recorder >> ... the other issue is audio zones >> ... can be solved by the multiple player approach >> ... a tuner entity can be actually a player which is tied with >> tuner >> ... make sense? >> >> kaz: agree :) >> >> wonsuk: one question >> ... there was a proposal by VW >> ... included media tuner capability >> ... something like spotify >> ... possible application in vehicle >> >> ryan: current spec doesn't handle that >> ... currently specific to TV tuner >> ... rather tied with hardware >> ... while I myself don't care about hardware >> ... but concentrate on resources >> ... have not looked at VW's proposal itself, though >> >> wonsuk: good question >> >> ryan: have worked with several OEMs >> ... players play media based on user's requests >> ... haven't work with VW but might be similar >> >> wonsuk: ok >> ... can we share the VW proposal with the other group >> participants? >> ... want to check >> >> ted: I'm working on VW's Member submission >> ... which will be public >> ... including car library, media tuner, etc. >> ... also CDN service >> ... hoping we'll publish it before the publication moratorium >> ... will send announcement once it's published >> >> wonsuk: ok >> ... I'm curious about the Member submission >> ... standardization based on a submission by a W3C Member? >> >> ted: formal submission by a Member to W3C >> ... which can be discussed by the BG >> >> wonsuk: ok >> ... after we have the document from VW, we can share it with >> other W3C Members. right? >> >> ted: yes >> ... expected next week >> >> wonsuk: ok. good. >> ... any comments? >> >> ryan: interested to see that as a Christmas present :) >> >> Redefining the role of the BG >> >> wonsuk: we've discussed this topic before >> ... at that time, I mentioned we needed to form a TF to revisit >> use cases >> ... and we need to try to add more use cases >> ... like payments use cases >> ... also lots of different use cases >> >> <paul> >> [11]https://www.w3.org/community/autowebplatform/wiki/Potential >> _Work_Areas >> >> [11] https://www.w3.org/community/autowebplatform/wiki/Potential_ >> Work_Areas >> >> kaz: do you confirm that direction? >> >> wonsuk: yes >> >> kaz: as Paul put on IRC, there were several work areas >> >> paul: yes, and there were some more from VW >> ... how should we handle this? >> >> ted: announcement will be made during the Member submission >> procedure >> ... have conversation >> ... talking with Ian Jacobs about Payments >> ... possibly we could have discussion on vehicle-specific use >> cases >> >> paul: traffic API as well? >> ... HERE is not a W3C Member yet. right? >> >> ted: no >> ... but recently joined GENIVI >> >> rudi: we're waiting for their input >> ... maybe we could draft a new charter for backend APIs >> >> paul: the BG is free to explore any use cases >> >> ted: that's correct >> >> kaz: right >> >> <ted> scribenick: ted >> >> kaz: BGs are encouraged to define charter in order to clarify >> scope to prospects but it does not have to be rigidly defined >> (unlike WG) >> >> <scribe> scribenick: kaz >> >> paul: ADAS use cases? >> >> rudi: part of the discussion within GENIVI >> ... GENIVI is collaborating with OCF >> >> philippe: concerning HERE, not sure about their intention yet >> ... their work is very important for the LBS topic >> ... we'll likely have a meeting in January >> >> <ted> scribenick: ted >> >> kaz: I was wondering how to handle Geolocation mapping and >> traffic data in context of LBS topic >> ... it should probably be in a single task force >> ... later it might make sense to create a separate one >> >> <scribe> scribenick: kaz >> >> wonsuk: also thinking about that >> ... open APIs on the cloud side for traffic data >> >> paul: could be interested >> ... what about mapbox? are they a W3C Member? >> ... monitoring and checking the stuff >> ... connected with PSA guys? >> >> ted: they're interested in REST APIs but still need some more >> time >> >> (discussion on infographic about vehicle industry stakeholders) >> >> <ted> [12]http://pass-projekt.de/ >> >> [12] http://pass-projekt.de/ >> >> <ted> [agree it would be helpful to have a map of different >> standards bodies involved in auto and their areas. we keep >> learning of new/duplicate efforts] >> >> <paul> >> [13]http://23je8jawagt19m8da2cje4yb.wpengine.netdna-cdn.com/wp- >> content/uploads/2016/06/Ecosystem-Infographic.png >> >> [13] http://23je8jawagt19m8da2cje4yb.wpengine.netdna-cdn.com/wp-c >> ontent/uploads/2016/06/Ecosystem-Infographic.png >> >> <ted> [OMA is trying to have an authorative document along >> those lines] >> >> <ted> >> [14]https://wiki.openmobilealliance.org/display/OI/OMA+Report+o >> n+Automotive+Opportunity >> >> [14] https://wiki.openmobilealliance.org/display/OI/OMA+Report+ >> on+Automotive+Opportunity >> >> <paul> lochbridge infographic connected car >> >> <paul> >> [15]http://lochbridge.com/blog/next-big-automotive-revolution/ >> >> [15] http://lochbridge.com/blog/next-big-automotive-revolution/ >> >> paul: Lochbridge's whitepaper >> >> wonsuk: interesting item to me >> ... what about cloud APIs like Amazon? >> ... we can also sync with existing cloud APIs >> ... there are companies provide APIs for smart home >> ... we can think about how to integrate existing APIs like >> smart homes and speech APIs >> >> rudi: interesting to me too >> ... OCF is working on that kind of APIs >> ... automotive profile is one of their defining profiles >> >> paul: there is a WoT group within W3C as well >> >> rudi: we can integrate capabilities >> >> paul: HERE has mechanism to integrate location data >> ... interesting to research quickly >> ... btw, is anybody could join the call for security? >> >> ted: security call on Thursday >> >> rudi: they're modeling security portion >> ... vehicle signal server to get connected >> ... lot of good momentum >> >> kaz: info on the WoT IG >> ... they'are launching a WG shortly >> ... also have restarted the discussion on security and privacy >> from the viewpoint of WoT >> ... and would like to invite experts from related groups >> including the Automotive group >> ... Hashimoto-san should be a good starting point for the >> collaborators >> >> paul: what about OCF liaison? >> >> kaz: WoT group is forming liaison with OCF as well >> >> paul: good >> ... Hashimoto-san's joining the WoT security discussion would >> be great >> ... there are different domains >> >> kaz: also my second point is that some of the vehicle >> capability could/should be handled by a bit more abstract layer >> like WoT rather than the Vehicle Signal Server >> >> paul: yeah >> >> Test environment >> >> paul: btw, wondering about the test environment >> ... Urata-san mentioned he was working on the Web Platform >> Testing environment >> >> kaz: yes >> ... as you know, there is the Web Platform Testing >> infrastructure >> ... but the framework is developed mainly for pc/mobile Web >> browsers >> ... we should be able to use the framework for part of the >> Vehicle Signal Spec features since the framework includes >> WebSocket capability (for pc/mobile browsers) as well >> ... however, we need to add modules to get vehicle data on the >> Vehicle Signal Server side and send the data to the Vehicle >> Signal Client side >> >> Kaz's note on the resources from the Web Platform Tests >> Project: >> - [16]Web Platform Tests Project >> - [17]Test Suite for Web Platform Testing infrastracture >> - [18]Web Platform Test Runner site >> >> [16] https://github.com/w3c/web-platform-tests/blob/master/README.md >> [17] https://github.com/w3c/web-platform-tests >> [18] http://w3c-test.org/tools/runner/index.html >> >> paul: ok >> ... this topic itself is not really the topic for the BG but >> I'll put it together >> ... anything else for today? >> >> wonsuk: anything else? >> >> (none) >> >> [ adjourned ] >> >> Summary of Action Items >> >> Summary of Resolutions >> >> [End of minutes] >> __________________________________________________________ >> >> >> Minutes formatted by David Booth's [19]scribe.perl version >> 1.148 ([20]CVS log) >> $Date: 2016/12/13 18:14:29 $ >> >> [19] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm >> [20] http://dev.w3.org/cvsweb/2002/scribe/ >> >> > > > -- > *Rudolf J Streif* > System Architect - Open Source Initiative > Open Source Technology Centre > > *M:* +1.619.631.5383 <%28619%29%20631-5383> > *Email:* rstreif@jaguarlandrover.com > > > > UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR > US: 1419 NW 14th Ave, Portland, OR 97209 > jaguar.com | landrover.com > ------------------- > Business Details: > Jaguar Land Rover Limited > Registered Office: Abbey Road, Whitley, Coventry CV3 4LF > Registered in England No: 1672070 > > This e-mail and any attachments contain confidential information for a > specific individual and purpose. The information is private and privileged > and intended solely for the use of the individual to whom it is addressed. > If you are not the intended recipient, please e-mail us immediately. We > apologise for any inconvenience caused but you are hereby notified that any > disclosure, copying or distribution or the taking of any action in reliance > on the information contained herein is strictly prohibited. > > This e-mail does not constitute an order for goods or services unless > accompanied by an official purchase order. > > -- Kaz Ashimura, W3C Staff Contact for Auto, WoT, TV, MMI and Geo Tel: +81 3 3516 2504
Received on Tuesday, 13 December 2016 20:39:32 UTC