15:32:32 <RRSAgent> RRSAgent has joined #auto
15:32:32 <RRSAgent> logging to http://www.w3.org/2016/03/29-auto-irc
15:32:58 <jlrmagnus> jlrmagnus has joined #auto
15:34:10 <Yingying> scribe: Yingying
15:34:34 <Yingying> Chair: Philippe_Robin
15:34:56 <rstreif__> rstreif__ has joined #auto
15:35:45 <Yingying> @@@1: The Genivi side is moving forward.
15:36:03 <kaz> present: Kaz, Philippe_Robin, Rudi, Yingying, Philippe_Colliot, Magnus_Feuer, Magnus_Olsson, Ted
15:36:13 <kaz> s/@@@1/Magnus/
15:36:13 <Yingying> Don't know the @2 status.
15:37:35 <kaz> philippeR: sessions in Paris?
15:37:38 <Yingying> Philippe_Robin: there is a session with W3C. Did you check when?
15:38:05 <kaz> s/philippeR: sessions in Paris?//
15:38:24 <Yingying> Ted: the F2F is primarily on 28 and 29.
15:38:44 <kaz> s/F2F/W3C F2F/
15:39:53 <Yingying> PhilippeR: Sota session is on @3. You can arrange it on Fridy.
15:39:59 <kaz> s/Sota/SOTA/
15:40:11 <Yingying> Ted: Thursday afternoon would be more suitable.
15:40:52 <Yingying> Phi: significant progress on @4. What we would implement the javascript API?
15:41:05 <kaz> i/The Genivi/topic: f2f schedule/
15:41:18 <kaz> s/Phi:/philippeC:/
15:41:36 <Yingying> ...now I put into the Github. I am also using web socket, nodejs. It's connected to D bus.
15:42:26 <kaz> s/nodejs/Node.js/
15:42:32 <Yingying> ...it's about how to deal with WebIDL. I am waiting for somebody to add me the WebIDL.
15:42:35 <kaz> s/D bus/D-Bus
15:43:08 <Yingying> Ted: WebIDL is bounded with Browser. We prefer to Web Socket.
15:43:23 <wonsuk> wonsuk has joined #auto
15:43:28 <kaz> s/prefer to/prefer/
15:43:43 <kaz> i/significant/topic: LBS/
15:43:48 <kaz> rrsagent, make log public
15:43:53 <kaz> rrsagent, draft minutes
15:43:53 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
15:44:01 <Yingying> ...basically if you do the web socket approach, you don't need to do it in WebIDL.
15:44:23 <kaz> q+
15:44:32 <Yingying> philippeC: The data format is very different.
15:45:34 <kaz> ack k
15:46:06 <Yingying> Kaz: to Ted, even with web socket interface, WG also think about javascript/WebIDL interface as well.
15:46:59 <Yingying> ...they are equavalent.
15:47:08 <Yingying> ...one could be implemented using the other.
15:48:15 <Yingying> ...we should be careful about these two level APIs and factor the different levels.
15:49:20 <Yingying> ...@4 mentioned that high level API has been implemented based on the low level Web Socket API.
15:49:40 <Yingying> ...we should be careful to elaborate the structure/APIs.
15:49:41 <kaz> s/@4/Urata-san from ACCESS/
15:51:26 <Yingying> Ted: WebIDL we can have a high level resymbols of WebIDL, we need to think about the bindings with browser.
15:51:44 <Yingying> ...which is not necessarily for the web sockeet approach.
15:53:24 <Yingying> Magnus: how could you gurantee the integrity of the API when using Web Socket?
15:53:53 <Yingying> Kaz: yes we need to base on the SOAP?
15:54:28 <Yingying> ...we should clarify the module structure about what is expected for different module.
15:54:46 <kaz> s/yes we need to base on the SOAP?/yes, maybe we need some application protocol to guarantee data integrity like SOAP messaging/
15:55:07 <Yingying> Magnus: relationship about the Web socket and web work?
15:55:37 <rstreif> What's the rationale for SOAP over REST?
15:55:56 <Yingying> Kaz: we might use web worker to implement the multi-thread. WebRTC might also be considered.
15:56:26 <Yingying> ...it depends on the requirements of the specific applications.
15:57:22 <Yingying> ...the high speed multimedia might be handled by the WebRTC. It depends on the speed required by the application
15:57:31 <kaz> s/considered/considered if there is specific need for high-speed connection for multimedia data, etc./
15:58:20 <Yingying> Rudi: lightweight API should be considered first.
15:58:45 <kaz> present+ Paul
15:58:49 <Yingying> Kaz: it's just an example. IVI system could use @5.
16:00:08 <kaz> s/@5/light-weight protocol like MQTT/
16:00:28 <kaz> rrsagent, draft minutes
16:00:28 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
16:02:12 <Yingying> topic: vehicle signal
16:02:28 <kaz> i|vehicle signal|-> http://w3c.github.io/wot/landscape.html#protocols WoT protocols|
16:02:48 <kaz> rrsagent, draft minutes
16:02:48 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
16:03:05 <Yingying> @6: we started a project inside about the vehicle signal.
16:03:13 <kaz> s/@6/Magnus/
16:03:51 <Yingying> ...we are also working on how to distribute the signals.
16:04:16 <Yingying> ...how to transfer the signals from compass to compass.
16:04:43 <jlrmagnus> https://github.com/PDXostc/vehicle_signal_specification
16:04:49 <Yingying> ...I will show you the structure.
16:05:50 <Yingying> [Magnus shows the vehicle signal specification in github]
16:06:03 <kaz> s|https:|-> https:|
16:06:28 <kaz> s|specification|specification GENIVI Vehicle Signal Specification Repo.|
16:06:34 <kaz> rrsagent, draft minutes
16:06:34 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
16:07:02 <jlrmagnus> https://github.com/PDXostc/vehicle_signal_specification
16:07:26 <Yingying> Magnus goes through the structures.
16:08:45 <Yingying> Magnus: the structure is ready. next step is fleshout API
16:09:11 <Yingying> ...now we can have the JSON and FrancaIDL releases.
16:09:50 <kaz> q+
16:10:25 <Yingying> ...the reason we show to w3c is that it's the key integrate the car with vehicle itself
16:10:27 <kaz> -> http://rawgit.com/w3c/automotive/master/vehicle_data/data_spec.html W3C vehicle data spec
16:11:09 <Yingying> Paul: what are the signals and what are the ways to get the signals.
16:11:34 <Yingying> ...we were started with variety of signals.
16:12:01 <Yingying> ...average developers need to understand the API.
16:12:53 <Yingying> ...thousands of signals(3000), roughly 90 of them they would provide to developers for security purpose.
16:14:18 <Yingying> ...clearly want Peter from Mitsubishi electric, the guy from ACCESS, Kevin, Adam, everyone in WG understand the background.
16:15:28 <Yingying> Magnus: we hoep W3C and OEMs can pick up what they need from the signals.
16:15:47 <kaz> s/the guy from/Urata-san from/
16:16:05 <kaz> s/Kevin, Adam/Kevin and Adam from JLR/
16:16:18 <kaz> s/hoep/hope/
16:16:26 <kaz> rrsagent, draft minutes
16:16:26 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
16:17:27 <Yingying> Paul: I really hope next W3C WG call we could look at the target architecture and so on.
16:17:50 <Yingying> Magnus: good idea. I can make the presentation.
16:19:30 <Yingying> Paul: wish we could look on each other's schedule in F2F in Paris.
16:21:02 <Yingying> ...next WG call would be good to make us aligned.
16:21:34 <Yingying> Kaz: let's start with subscribing the BG and WG mailing list.
16:22:36 <Yingying> Magnus: @8 as the interface. I do agree we need to coordinate.
16:24:02 <Yingying> ...which signals are available between vehicle and the rest of the world
16:24:56 <Yingying> Paul: data to standardization methods.
16:26:19 <Yingying> PhilippeR: Magnus will present the signal struture to W3C auto WG meeting next week.
16:26:34 <Yingying> ...our next call is April 12.
16:27:16 <Yingying> ...let me show the track. The agenda has been published for some time.
16:27:38 <kaz> i/topic: Genivi AMM track/
16:27:48 <kaz> i/let me/topic: Genivi AMM track/
16:28:00 <kaz> s/...let me/PhilippeR: let me/
16:28:31 <kaz> i/let me/kaz: some of the w3c guys can join the GENIVI AMM sessions on April 27th as well./
16:29:09 <Yingying>  [ PhilippeR shows the agenda]
16:30:18 <philrob> https://at.projects.genivi.org/wiki/display/WIK4/14th+GENIVI+AMM
16:31:54 <Yingying> rrsagent, make minutes
16:31:54 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html Yingying
16:34:44 <kaz> s|https|-> https|
16:34:58 <kaz> s|AMM|AMM GENIVI AMM program|
16:35:05 <kaz> rrsagent, draft minutes
16:35:05 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
16:35:52 <kaz> Meeting: GENIVI+W3C
16:36:29 <kaz> rrsagent, draft minutes
16:36:29 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
16:36:32 <kaz> s|i/topic: Genivi AMM track/||
16:36:34 <kaz> rrsagent, draft minutes
16:36:34 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/29-auto-minutes.html kaz
18:59:15 <Zakim> Zakim has left #auto
20:16:12 <sam> sam has joined #auto