13:00:16 RRSAgent has joined #autopay 13:00:16 logging to http://www.w3.org/2017/10/26-autopay-irc 13:00:43 Meeting: Automotive Web Payments Task Force 13:00:46 Chair: Rodrigo 13:00:53 Agenda: https://github.com/w3c/automotive-pay/wiki/Agenda-20171109 13:00:55 present+ 13:00:58 present+ Rodrigo 13:01:00 present+ Marty 13:01:01 Rod has joined #autopay 13:02:21 present+ Nicola 13:03:17 present+ Ted 13:07:08 present+ Dezell 13:07:55 dezell has joined #autopay 13:07:59 https://github.com/w3c/automotive-pay/wiki/Agenda-20171026 13:08:54 Ian: today we should go over TPAC plans and use cases 13:08:59 scribe: Ted 13:09:14 previous minutes => https://www.w3.org/2017/10/19-autopay-minutes.html 13:09:52 Rodrigo: I read the wiki explainer page, anyone raise any red flags? 13:10:08 Ian: no, we did delve a bit into toll road scenario 13:10:59 … either you are debiting an account you already funded (stored with regional provider, eg Maine DOT for EZpass) or you are billed 13:11:01 q+ 13:11:17 … pay at the pump and parking seem like better fits 13:11:35 IJ: Sounded to me like tolls less interested given how funds are collected today (either billed or pre-funded account) 13:11:54 Rodrigo: today the UI component can capture the proper credentials and send to the merchant 13:12:16 Rodrigo: But one way to think about this is get previously stored credentials 13:12:17 ack ted 13:12:40 ted: We had someone from Jaguar/Landrover explain today's toll collection scenarios 13:13:00 ...either you have an account or you are billed (based on your license plate) 13:14:04 .....but another option is for the car to recognize the toll beacon and to do a push payment (before you are invoiced) 13:15:02 ...another topic is reconciliation across different DOTs 13:15:10 ...so you might address this by paying directly to a payment provider 13:16:48 [agree we should focus on other use cases first. tolls are complicated by existing infrastructure and practices but web payments is not necessarily ruled out] 13:17:25 Rodrigo: let's focus on the primary use cases first. the UI component would be different, Ian can say if we can evolve that piece to be more flexible for the car 13:18:04 Ian: given how our F2F meeting is approaching, at least for now we should focus on the pay at the pump scenario 13:18:14 +1 for fueling being primary use case 13:18:15 https://github.com/w3c/automotive-pay/wiki/PayAtPumpExplainer 13:18:35 Ian: I discussed this a bit at Money 2020 this week 13:19:06 … it is a simplistic representation of the world where hardware is needed to initiate the payments 13:19:33 … David and I have been talking with FirstData about their implementation 13:20:41 … we should seek input from auto on the viability of this scenario 13:21:04 Rodrigo: agree, should we have some required reading or other primers in preparation for the meeting 13:21:45 ted: Adam (from Jaguar) will not be able to attend 13:22:03 ...I do expect some other people who are in the group to attend, however. 13:22:15 ...makes sense to share what we have in advance 13:24:02 Ted: Web can help with some security challenges 13:24:16 ...eg., using user location as a way to get the user to a relevant web page 13:25:07 q+ 13:25:38 rodrigo: Let's prep people so that they come prepared to the FTF meeting 13:25:56 IJ: I'd like to articulate some questions for discussion at the face-to-face meeting 13:26:33 ...and get questions BEFORE the face-to-face meeting that we can address in Burlingame 13:26:35 Ian: we should encourage more review of these materials and respondes in advance for a more fruitful f2f discussions 13:28:28 ack de 13:29:03 David: I don't think John is coming since IFSF has a meeting in France the following week 13:29:53 … I will ask him about upcoming infrastructure considerations 13:30:26 dezell: People are using RFID 13:30:33 … many are starting to use NFC and RFID 13:30:40 Ted: Also DSRC 13:30:52 "DSRC (Dedicated Short Range Communications) is a two-way short- to- medium-range wireless communications capability that permits very high data transmission critical in communications-based active safety applications." 13:31:16 dezell: there is a relationship between card schemes and oil companies that also needs to be taken into consideration 13:31:31 [which is for V2x space, in flux but standards work at SAE and aligns with NHTSA] 13:32:12 s/which is/DSRC is being considered/ 13:32:25 Email template: 13:32:29 * We are meeting 9 Nov 13:32:37 * Would love feedback and questions about this use case description 13:33:04 * Also any relevant experience you have on similar systems and constraints or considerations you discovered in doing so 13:33:05 Ian: if people here have specific individuals we want to seek input from we should send them emails in advance 13:33:37 … it was great to hear what FirstData did with regulatory considerations, eg requiring the car at rest 13:34:22 [I may be attending a US DOT/DOE/UK DfT meeting in DC shortly after TPAC on EV infrastructure requirements] 13:35:02 Ian: please cc Ted and myself so we avoid overlap and are generally aware. we can collect and document responses 13:36:06 IJ: We should include rationale in the email (e.g., why the web can help reduce friction) 13:36:23 Ted: Let people know that they should tell us how we can share their comments (e.g., attributed or non-attributed) 13:36:48 Rodrigo: Ted and Ian can write the auto and IG groups 13:37:08 ACTION: Ian to send email template to the autopay list today 13:37:30 topic: Face-to-face meeting 13:37:31 https://github.com/w3c/automotive-pay/wiki/Agenda-20171109 13:37:43 [I am meeting with US DOT on Monday on several topics, different focus than payments but will seek appropriate contacts] 13:38:35 Ian: Part of the F2F agenda is about attracting observers and W3C participants from other organizations to get involved 13:39:15 … we want incubators, people to experiment in this space 13:39:33 Rodrigo: do you want me to put this together in a powerpoint 13:40:25 ACTION: Rodrigo to put together deck for TPAC to walk through charter, use case 13:40:58 Ian: that would be helpful 13:42:34 Ian: there may be additional flows for this use case others come up with 13:43:37 Rodrigo: what was your reaction to the previous conversation on flows? 13:43:46 q+ 13:44:15 Ian: I see it as incremental improvements especially if we want to rely on hardware that isn't rolled out universally 13:44:31 … some parts were not a great fit from the UX perspective 13:44:57 … we should focus on leveraging our existing payments standards work where possible 13:45:10 … we didn't get some of the other use cases 13:45:55 … there are other topics in our charter besides use cases like distractability. those are more challenges and have not covered 13:46:11 [distractability only a concern for use cases when vehicle is in motion] 13:46:34 q+ to comment on incremental and flows 13:47:14 Rodrigo: should we iterate over the use cases, summary of focuses so far, challenges and see what their challenges are 13:47:27 q+ to comment on time allotment 13:47:53 Ian: identifying similar use cases and how they differ seems useful for me and add to the agenda 13:48:22 … you mentioned identifying the actors and roles which is somewhat done in the flow diagrams 13:48:33 … I would be happy to explain in detail who the different parties are 13:49:26 +1 to understanding roles and business motivations 13:49:44 Rodrigo: the goal is really the flow of the use case, with pay of the pump being a focus for sure 13:50:33 … we want a clear consisent understanding since some are coming from different industry perspecitives 13:51:05 Topic: Next meeting 13:51:07 TPAC 13:51:17 (no TF meeting on 2 Oct) 13:51:34 [no call next week, Ian, Ted and Rodrigo to meet beforehand] 13:51:44 ted, you wanted to comment on incremental and flows and to comment on time allotment 13:53:55 ted; We can also provide for remote attendance 13:54:38 summary next steps: 13:54:44 * Ian to send out minutes from today's call 13:54:50 ...and announce next meeting is at TPAC 13:55:00 * Ian to draft email template to get feedback on pay at the pump explainer 13:55:17 * Rodrigo to draft slides for presentation at TPAC of task force scope + explainer 13:55:29 * Ted and Ian to write to the respective groups to get feedback in advance 13:55:54 * Other people will ping other people with the email template, cc Ted and Ian 13:56:05 I have made the request to generate http://www.w3.org/2017/10/26-autopay-minutes.html ted 14:04:19 https://w3c.github.io/payment-method-manifest/#validate-and-parse 15:06:30 want me to cleanup and send to the list? 15:16:43 cool tx 16:14:13 Zakim has left #autopay 16:19:12 I see 2 open action items saved in http://www.w3.org/2017/10/26-autopay-actions.rdf : 16:19:12 ACTION: Ian to send email template to the autopay list today [1] 16:19:12 recorded in http://www.w3.org/2017/10/26-autopay-irc#T13-37-08 16:19:12 ACTION: Rodrigo to put together deck for TPAC to walk through charter, use case [2] 16:19:12 recorded in http://www.w3.org/2017/10/26-autopay-irc#T13-40-25