15:52:57 RRSAgent has joined #wpwg 15:52:57 logging to http://www.w3.org/2016/06/23-wpwg-irc 15:52:59 RRSAgent, make logs public 15:52:59 Zakim has joined #wpwg 15:53:01 Zakim, this will be 15:53:01 I don't understand 'this will be', trackbot 15:53:02 Meeting: Web Payments Working Group Teleconference 15:53:02 Date: 23 June 2016 15:53:14 agenda: https://github.com/w3c/webpayments/wiki/Agenda-20160623 15:58:04 rouslan has joined #wpwg 15:58:55 Present+ Rouslan 16:00:05 present+ Ian 16:00:10 zakim, who's here? 16:00:10 Present: Rouslan, Ian 16:00:12 On IRC I see rouslan, Zakim, RRSAgent, dezell, Jason_Yang, jeff, Adam_, shepazu, adamR, ShaneM, hober, adrianba, collier-matthew, dlehn, dwim, slightlyoff, davidillsley_, dlongley, 16:00:12 ... schuki, mkwst, Ian, manu, wseltzer, trackbot, AdrianHB 16:00:13 present+ Kepeng 16:00:16 present+ Jason_Yang 16:00:22 present+ BrainS 16:00:28 present- BrainS 16:00:31 present+ BrianS 16:00:46 present+ adamR 16:00:49 present+ dlehn 16:00:51 present+ AdrianHB 16:00:53 present+ Nick 16:00:59 present+ Mahesh 16:01:21 present+ Manu 16:01:34 Kepeng: Can we change the meeting time to be 1 or 2 hours earlier? 16:01:39 Ian: The Chairs and Team contacts will discuss 16:01:50 nicktr has joined #wpwg 16:01:54 alyver has joined #wpwg 16:01:54 ACTION: AdrianHB to work on regular meeting times 16:01:54 Error finding 'AdrianHB'. You can review and register nicknames at . 16:01:56 present+ dezell 16:02:07 agenda: https://github.com/w3c/webpayments/wiki/Agenda-20160623 16:02:09 brianS has joined #WPWG 16:02:09 present+ dlongley 16:02:09 present+ alyver 16:02:15 Kepeng has joined #wpwg 16:02:22 MaheshK has joined #wpwg 16:02:52 scribe: Ian 16:03:02 agenda? 16:03:03 https://github.com/w3c/webpayments/wiki/Agenda-20160623 16:03:06 present+ ShaneM 16:03:14 present+ nicktr 16:03:18 topic: FTF meeting update 16:03:34 NickTR: Updated agenda of FTF meeting 16:03:42 https://github.com/w3c/webpayments/wiki/Web-Payments-Working-Group-FTF-Meeting-%28July-2016%29#agenda 16:03:47 apaliga has joined #wpwg 16:03:57 ...moved some information around...time for payment request API, payment apps, payment method specs 16:04:00 ...testing, security review 16:04:05 ...and HTTP API work as well 16:04:22 q+ 16:04:46 ack Ian 16:04:55 Ian: Something we talked about in the Chairs meeting - Payment Request API to discuss implementation experience 16:04:57 IJ: Focus on implementer experience on day 1 16:05:01 regrets+ Zach 16:05:36 MattS has joined #wpwg 16:05:43 q+ about demos 16:05:51 q+ to talk about demos 16:05:53 Nick: We are keen to see demos...we have something to show from Worldpay 16:05:57 q- about demos 16:06:10 q+ 16:06:16 ack rouslan 16:06:16 rouslan, you wanted to talk about demos 16:06:22 rouslan: Yes, I'd be happy to show a demo 16:06:24 ack me 16:07:24 topic: Payment Architecture Summary 16:07:28 https://w3c.github.io/webpayments/proposals/wparch/ 16:08:01 Manu: Purpose of the doc is not to lay out a formal spec or detailed architecture. 16:08:12 ...more to give people an introductory summary about roles and communications 16:08:38 ...goal is to try to reflect what we have today with a slight lean to the future. 16:08:49 ...Rouslan, Katie, AHB, Ian reviewed the document 16:08:53 ..there have been some request changes 16:09:17 MikeSmith has joined #wpwg 16:09:19 [Manu walks through sections of the document] 16:09:28 Links to specifications that detail each aspect of the architecture in more detail are also provided for implementers. 16:09:38 https://w3c.github.io/webpayments/proposals/wparch/#roles-in-the-architecture 16:10:27 q+ to provide some high level feedback and discuss next steps 16:10:51 Manu: There is one item in here where I changed name from payment request to payment instruction 16:10:59 ...that was at the request of the ISO 20022 RA colleagues 16:11:07 ..and because we are going to be dealing with subscriptions at some point 16:11:10 ..that can be taken out. 16:11:18 ...also there is something that talks about payment app registration 16:11:25 q+ 16:11:43 ack AdrianHB 16:11:43 AdrianHB, you wanted to provide some high level feedback and discuss next steps 16:11:44 ack adrianhb 16:11:49 adrianhb: Thanks, Manu. 16:11:54 ...a great first stab at this 16:12:02 ...this is probably a direction than a formal architecture document 16:12:09 ..it feels like the group does not want a formal architecture document. 16:12:19 ...so for next steps, I propose that we agree to what kind of document we want 16:12:31 ..if this document looks like what we want, then we can adopt it and work on it. 16:12:46 ...so I want to understand what we want first 16:12:50 q? 16:13:21 AdrianHB: So the question is "do we want a summary doc"? 16:13:30 ...I agree with Ian that the first draft needs to reflect what we have already done 16:13:45 ...if we want to introduce a new concept like payment instruction, we should discuss further before introducing the new terms 16:13:52 ...our process has been to lead with low-level documents. 16:14:01 ...and then we are summarizing what we've done 16:14:10 q? 16:14:20 ...if we want to proceed in a different fashion, we should make a conscious decision to do otherwise. 16:14:24 ack Ian 16:14:39 +1 to AdrianHB, another option for things where we don't yet have consensus is to put them as issues in the spec 16:15:42 +1 to issue markers for discussion points 16:16:03 +1 to both dlongley and AdrianHB on markers 16:16:10 +1 to ian - we should not prioritize this document yet 16:16:32 q? 16:16:33 q+ to note that W3C has NOTEs, and that it's difficult to prep discussions for face-to-face without some of these documents - like WP architecture summary. 16:16:38 -1 to wiki first. I think this is mature enough 16:16:40 +1 to Ian’s point also. This is useful information, but I don’t think we need to take it on as a formal document 16:16:50 ack Manu 16:16:50 manu, you wanted to note that W3C has NOTEs, and that it's difficult to prep discussions for face-to-face without some of these documents - like WP architecture summary. 16:17:05 q+ 16:17:07 Manu: It's ok for this to be in a document format. 16:17:10 +1 to publishing as a note 16:17:25 ...I don't think anyone is asking to prioritize the document without this sort of document. 16:17:41 +1 to manu 16:17:46 ..there is an issue that we want to talk about around payment instructions...it's earlier to make the architectural point though this doc. 16:17:59 ...I'm saying let's get this in as a work item then refine it. 16:18:10 ..the ask today is to bring it into the group and work on it as an ED ... it doesn't have to be high priority 16:18:18 ack kep 16:18:28 Kepeng: I think it's useful to have this document for newcomers 16:18:46 ..also I suggest we can take some content from the Payment App Notes wiki. 16:18:50 ...some of that might be useful here. 16:19:01 https://github.com/w3c/webpayments/wiki/PaymentApp_Notes 16:19:11 nicktr: From my perspective it feels like this is a useful document. 16:19:23 ...my position it that it would be better if it reflected what we have today 16:19:34 ...and we could use issue markers 16:19:46 ...I'm also conscious that this went to the mailing list Friday 16:19:54 +1 to reflect what we have today - I can make those edits quickly, and put in issue markers for future direction. 16:19:58 ..I think it would be great to take this up as a WG item as a Note. 16:20:10 ..let's give the group a week to do that and then bring this back to the agenda next week. 16:20:18 ...make sure it is clear that this Note exists as an explainer text 16:20:34 ...let's put the question to the group next week. 16:20:41 ..people can request changes to Manu over the next week. 16:20:55 W3C MIT - but can publish it anyway 16:21:08 Nick: I"m keen to have this done before FTF, even if done by email 16:21:09 +1 to CfC before F2F one way or another 16:21:13 Topic: Payment Method Identifires 16:21:38 https://github.com/w3c/webpayments-method-identifiers/issues/5