See also: IRC log
<scribe> scribe: Yingying
Magnus: The Genivi side is moving forward.
Don't know the @2 status.
Philippe_Robin: there is a session with W3C. Did you check when?
Ted: the W3C F2F is primarily on 28 and 29.
PhilippeR: SOTA session is on @3. You can arrange it on Fridy.
Ted: Thursday afternoon would be more suitable.
philippeC: significant progress
on @4. What we would implement the javascript API?
... now I put into the Github. I am also using web socket,
Node.js. It's connected to D-Bus.
... it's about how to deal with WebIDL. I am waiting for
somebody to add me the WebIDL.
Ted: WebIDL is bounded with
Browser. We prefer Web Socket.
... basically if you do the web socket approach, you don't need
to do it in WebIDL.
philippeC: The data format is very different.
Kaz: to Ted, even with web socket
interface, WG also think about javascript/WebIDL interface as
well.
... they are equavalent.
... one could be implemented using the other.
... we should be careful about these two level APIs and factor
the different levels.
... Urata-san from ACCESS mentioned that high level API has
been implemented based on the low level Web Socket API.
... we should be careful to elaborate the structure/APIs.
Ted: WebIDL we can have a high
level resymbols of WebIDL, we need to think about the bindings
with browser.
... which is not necessarily for the web sockeet approach.
Magnus: how could you gurantee the integrity of the API when using Web Socket?
Kaz: yes, maybe we need some
application protocol to guarantee data integrity like SOAP
messaging
... we should clarify the module structure about what is
expected for different module.
Magnus: relationship about the Web socket and web work?
<rstreif> What's the rationale for SOAP over REST?
Kaz: we might use web worker to
implement the multi-thread. WebRTC might also be considered if
there is specific need for high-speed connection for multimedia
data, etc..
... it depends on the requirements of the specific
applications.
... the high speed multimedia might be handled by the WebRTC.
It depends on the speed required by the application
Rudi: lightweight API should be considered first.
Kaz: it's just an example. IVI system could use light-weight protocol like MQTT.
<inserted> WoT protocols
Magnus: we started a project
inside about the vehicle signal.
... we are also working on how to distribute the signals.
... how to transfer the signals from compass to compass.
<jlrmagnus> https://github.com/PDXostc/vehicle_signal_specification
Magnus: I will show you the structure.
[Magnus shows the vehicle signal specification GENIVI Vehicle Signal Specification Repo. in github]
<jlrmagnus> https://github.com/PDXostc/vehicle_signal_specification
Magnus goes through the structures.
Magnus: the structure is ready.
next step is fleshout API
... now we can have the JSON and FrancaIDL releases.
... the reason we show to w3c is that it's the key integrate
the car with vehicle itself
<kaz> W3C vehicle data spec
Paul: what are the signals and
what are the ways to get the signals.
... we were started with variety of signals.
... average developers need to understand the API.
... thousands of signals(3000), roughly 90 of them they would
provide to developers for security purpose.
... clearly want Peter from Mitsubishi electric, Urata-san from
ACCESS, Kevin and Adam from JLR, everyone in WG understand the
background.
Magnus: we hope W3C and OEMs can pick up what they need from the signals.
Paul: I really hope next W3C WG call we could look at the target architecture and so on.
Magnus: good idea. I can make the presentation.
Paul: wish we could look on each
other's schedule in F2F in Paris.
... next WG call would be good to make us aligned.
Kaz: let's start with subscribing the BG and WG mailing list.
Magnus: @8 as the interface. I do
agree we need to coordinate.
... which signals are available between vehicle and the rest of
the world
Paul: data to standardization methods.
PhilippeR: Magnus will present
the signal struture to W3C auto WG meeting next week.
... our next call is April 12.
<inserted> kaz: some of the w3c guys can join the GENIVI AMM sessions on April 27th as well.
PhilippeR: let me show the track. The agenda has been published for some time.
[ PhilippeR shows the agenda]
<philrob> GENIVI AMM program
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/@@@1/Magnus/ Succeeded: s/philippeR: sessions in Paris?// Succeeded: s/F2F/W3C F2F/ Succeeded: s/Sota/SOTA/ Succeeded: i/The Genivi/topic: f2f schedule Succeeded: s/Phi:/philippeC:/ Succeeded: s/nodejs/Node.js/ Succeeded: s/D bus/D-Bus/ Succeeded: s/prefer to/prefer/ Succeeded: i/significant/topic: LBS Succeeded: s/@4/Urata-san from ACCESS/ Succeeded: s/yes we need to base on the SOAP?/yes, maybe we need some application protocol to guarantee data integrity like SOAP messaging/ Succeeded: s/considered/considered if there is specific need for high-speed connection for multimedia data, etc./ Succeeded: s/@5/light-weight protocol like MQTT/ Succeeded: i|vehicle signal|-> http://w3c.github.io/wot/landscape.html#protocols WoT protocols Succeeded: s/@6/Magnus/ Succeeded: s|https:|-> https:| Succeeded: s|specification|specification GENIVI Vehicle Signal Specification Repo.| Succeeded: s/the guy from/Urata-san from/ Succeeded: s/Kevin, Adam/Kevin and Adam from JLR/ Succeeded: s/hoep/hope/ FAILED: i/topic: Genivi AMM track/ Succeeded: i/let me/topic: Genivi AMM track Succeeded: s/...let me/PhilippeR: let me/ Succeeded: i/let me/kaz: some of the w3c guys can join the GENIVI AMM sessions on April 27th as well. Succeeded: s|https|-> https| Succeeded: s|AMM|AMM GENIVI AMM program| Succeeded: s|i/topic: Genivi AMM track/|| Found Scribe: Yingying Inferring ScribeNick: Yingying Present: Kaz Philippe_Robin Rudi Yingying Philippe_Colliot Magnus_Feuer Magnus_Olsson Ted Paul Got date from IRC log name: 29 Mar 2016 Guessing minutes URL: http://www.w3.org/2016/03/29-auto-minutes.html People with action items:[End of scribe.perl diagnostic output]