06:27:49 RRSAgent has joined #auto 06:27:49 logging to http://www.w3.org/2016/06/03-auto-irc 06:49:55 * @kaz, the new call-in has been sent 06:54:00 ok 06:54:14 I've also allocated another call on the w3c webex server 06:54:18 but will use your code 06:56:15 meeting: Navigation API 06:57:17 present: Qing_An, Philippe_Colliot, Kaz_Ashimura 06:57:39 https://github.com/GENIVI/vehicle_signal_specification 06:57:49 s/https/-> https/ 06:58:00 s/specification/specification VSS/ 06:58:20 QingAn: which direction should be taken? 06:58:30 s/QingAn/qa: 06:59:04 pc: api accesses the data 06:59:16 ... launching guidance is different 06:59:21 ... there are a lot of methods 06:59:31 ... including get/set methods 07:00:03 philippec has joined #auto 07:00:08 qa: what is the relationship between vehicle data and vss 07:00:37 ka: should be done by the data comparison tf 07:03:04 ... we need to think about use cases of LBS/Navigation 07:03:10 ... also some architecture model 07:03:23 ... and in parallel we need to see the data format 07:03:37 pc: have started some work on use cases 07:04:03 ... comparison between W3C use cases and Genivi use cases 07:04:53 ... W3C data spec includes JS properties 07:05:05 ... while Genivi LBS doesn't handle properties 07:05:20 ... just use methods to access data 07:06:30 ... so would like to see the difference 07:07:17 s/see/understand/ 07:09:20 kaz: W3C Vehicle Data doesn't handle concrete location data except lane departure 07:10:02 ... so we should see the data definition/structure of Genivi LBS 07:10:09 pc: ok 07:10:18 ... would like to show it 07:10:25 ... showing part of the LBS api definition 07:11:15 ... a lot of set/get methods 07:11:54 ... there is a "position" parameter 07:12:38 ... hierarchy of the data 07:13:02 ka: any figure about the hierarchy? 07:13:11 pc: no figure at the moment 07:13:16 ... but can generate it 07:13:30 ... let's see "guidance" 07:14:29 ka: is this document public? 07:14:36 pc: this one itself is member-only 07:14:44 ... there is a public repo as well 07:16:58 ka: ok 07:17:04 ... please send the address later 07:17:17 ... btw, we should think about the basic policy/strategy for this TF 07:17:31 pc: can generate a figure on the data hierarchy 07:17:49 ... also take some examples 07:18:16 ... to explain the guidance api 07:18:37 kaz: great 07:19:01 s/kaz:/ka:/ 07:19:27 pc: you know how to deal with the data format for the W3C side, Kaz 07:19:36 s/know/know better/ 07:21:15 ka: regarding the strategy, we should involve more Tier1 companies 07:21:45 -> https://www.w3.org/community/autowebplatform/participants BG participants 07:24:04 pc: I'm leading the work on the Genivi side 07:24:08 ka: ok 07:24:21 pc: but for the W3C side we need more participants 07:26:28 ka: right 07:26:39 ... @@@ 07:26:55 pc: will be in Japan in July for an AGL meeting 07:27:02 ... and can talk with JP stakeholders 07:28:52 ka: great 07:29:04 ... getting more participants in this BG is the key 07:29:29 ... probably better to have Genivi guys as the BG participants too 07:30:04 pc: not sure Genivi guys have enough time 07:30:23 ka: ok 07:30:41 ... getting more BG participants in this TF is important 07:31:21 ... and Genivi guys are also welcome :) 07:31:24 pc: yes 07:31:36 ka: let's continue to get more participants 07:31:51 ... and also let's start detailed survey on the Genivi LBS spec 07:32:11 ... you can provide some examples with the hierarchy figure 07:32:39 Chair: Philippe, QingAn 07:33:10 s/... @@@// 07:33:16 [ adjourned ] 07:33:48 rrsagent, make log public 07:33:52 rrsagent, draft minutes 07:33:52 I have made the request to generate http://www.w3.org/2016/06/03-auto-minutes.html kaz 08:39:44 sam has joined #auto 08:59:47 Zakim has left #auto 09:06:57 sam_ has joined #auto 10:03:02 Karen has joined #auto