13:57:08 RRSAgent has joined #wpay 13:57:08 logging to http://www.w3.org/2015/06/11-wpay-irc 13:58:28 Meeting: Web Payments IG Payment Architecture Task Force (Thursday) 13:58:29 rrsagent, draft minutes 13:58:29 I have made the request to generate http://www.w3.org/2015/06/11-wpay-minutes.html manu 13:59:30 zakim, this will be wpay 13:59:30 ok, manu, I see T&S_WEBPYMT(WPAY_USE)10:00AM already started 13:59:38 zakim, who is on the call? 13:59:38 On the phone I see ??P1 13:59:58 zakim, who is on the call? 13:59:58 On the phone I see ??P1 14:00:02 zakim, code? 14:00:02 the conference code is 9729 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), manu 14:00:22 +[IPcaller] 14:00:26 zakim, ??P1 is me 14:00:26 +AdrianHB; got it 14:00:29 zakim, I am ??IPcaller 14:00:29 sorry, manu, I do not see a party named '??IPcaller' 14:00:33 zakim, I am IPcaller 14:00:33 ok, manu, I now associate you with [IPcaller] 14:00:40 zakim, who is on the call? 14:00:40 On the phone I see AdrianHB, [IPcaller] 14:00:49 zakim, IPcaller is me 14:00:49 +manu; got it 14:00:53 zakim, who is on the call? 14:00:53 On the phone I see AdrianHB, manu 14:02:55 +Katie_Haritos-Shea 14:03:06 zakim, call Ian-Office 14:03:06 ok, Ian; the call is being made 14:03:07 +Ian 14:03:24 ShaneM has joined #wpay 14:04:09 Agenda: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Jun/0043.html 14:04:16 scribe: AdrianHB 14:04:59 manu: any additions? 14:05:49 Ryladog has joined #wpay 14:05:52 Topic: Roadmap Updates 14:05:53 manu: suggest we do roadmap first 14:05:57 https://www.w3.org/Payments/IG/wiki/Roadmap 14:06:32 ian: current sense I have going into f2f is: what we are talking about now goes in 4 new groups 14:06:42 q+ to ask about Signatures WG, six groups, etc. 14:06:50 ian: waiting for settlement presentation to confirm 14:07:24 ian: in jeff's preso there is also a question about signatures (although more key management) 14:07:55 ian: roadmap says the Ig will continue to add use cases and reqs and reach out to larger community 14:08:04 ian: vision lives with the IG 14:08:15 ian: lots to do there 14:09:04 q+ to say that the "expanded list" is helpful /if people ask for it/ 14:09:05 ian: Web Payments WG - i have shrunk capabilities doc to use as working doc for f2f 14:09:31 ian: @@ is not in there but can be added in respec version 14:10:01 ian: credentials wg - manu and i have worked on a good presentation for that 14:10:11 ack manu 14:10:11 manu, you wanted to ask about Signatures WG, six groups, etc. and to say that the "expanded list" is helpful /if people ask for it/ 14:10:13 s/@@/capabilities 14:10:14 settlement - down to adrian preso 14:10:33 manu: the current roadmap has a blindspot around key man and sigs 14:10:40 +1 to adding mention of key management 14:10:50 manu: i don't think there is anther wg at w3c that can pick that up 14:11:02 q_ 14:11:03 q+ 14:11:10 manu: key man and linked data sigs need to be discussed at f2f 14:11:34 q+ to say that the "expanded list" is helpful /if people ask for it/ 14:11:35 +[IPcaller] 14:11:37 manu: linked data related work can be done in linked data wg 14:11:59 ian: jeff will be raising the question of a standard for dig sigs etc in his preso at round table 14:12:01 +??P9 14:12:06 zakim, ??P9 is ShaneM 14:12:06 +ShaneM; got it 14:12:20 ian: note that in the charter there is a now a concrete req for JSON-LD canonicalisation 14:12:40 ian: i do want to dig into why we need it lets discuss at f2f 14:12:46 s/canonicalization// 14:12:57 zakim, who is on the call? 14:12:57 On the phone I see AdrianHB, manu, Katie_Haritos-Shea, Ian, [IPcaller], ShaneM 14:13:20 zakim, disconnect IPcaller 14:13:20 [IPcaller] is being disconnected 14:13:21 -[IPcaller] 14:13:26 ack manu 14:13:26 manu, you wanted to say that the "expanded list" is helpful /if people ask for it/ 14:13:30 ChaoDuan has joined #wpay 14:13:52 manu: like the focus of the roadmap 14:14:08 ... may want to also show the prioritisation wiki 14:14:13 +[IPcaller] 14:14:34 ian: for digestability I suggest a chart or something visual 14:14:49 zakim, IPcaller is ChaoDuan 14:14:49 +ChaoDuan; got it 14:15:07 ... if not lets move the bits from the prioritization wiki over to the roadmap 14:15:43 manu: having info is [lost audio] 14:16:03 ian: i like the mapping back to use cases in the priorities 14:16:15 ... will try to fold into roadmap 14:16:27 manu: anything further? 14:16:28 Topic: Payment Architecture WG Proposal 14:16:28 https://www.w3.org/Payments/IG/wiki/Roadmap/PaymentArchitectureWG 14:17:00 ian: most NB is scope 14:17:21 ... started with basic description from discussions around payment agent integration 14:17:35 ... wrestled with folding in capabilities 14:17:55 ... realised goals are most NB thing to get consensus 14:18:08 q+ to talk to deliverables - I think we need more 14:18:12 ack Ian 14:18:16 ... kept it high level enough to not specify actual deliverables 14:18:36 ... then added deliverables with help from Wendy Seltzer 14:19:02 ShaneM_ has joined #wpay 14:19:05 ... started with a need to capture vocabs then apis then protocols 14:19:17 ... then took a stab at milestones 14:19:19 ... 14:19:41 q+ to say that browser integration /should not/ be in the critical path. 14:19:43 ... vocabs seems easier to do based on workdone already 14:19:55 ... browser related stuff will likely take longer 14:19:57 ack manu 14:19:57 manu, you wanted to talk to deliverables - I think we need more and to say that browser integration /should not/ be in the critical path. 14:20:15 manu: i think we need more deliverables 14:20:28 ... lot of the tech is already in a first draft from the CG 14:21:02 ... browser APIs need to be there but REST apis are new to W3C 14:21:15 this is the client server protocol 14:21:36 ... in the CG we have a lot of vocabularies already 14:21:52 ... we also have a browser API that was done with Mozilla a long time ago 14:22:12 ... then there is the protocol spec, the Web Commerce Spec 14:22:27 .. do we want those in yet or just notes and questions? 14:22:56 ... while we should spec out a browser API we def don't want the browser vendors in the critical path for v1 14:23:16 ... we can use polyfills for now 14:23:52 ... we also don't want banks in the ciritical path (also take a long time to move on large tech changes) 14:24:07 ... not sure there is sufficient incentives for banks (maybe for retailers) 14:24:50 ian: i don't think I have explicitly put anyone in critical path 14:25:27 manu: we need people to understand that even though we want to deliver a browser API they are not in the critical path 14:25:56 manu: for some technology that is unavoidable - like credentials 14:26:16 manu: (credential issuers are in critical path) 14:26:41 manu: need to id the industries that are in the c path and then make sure we have some implementors lined up 14:27:13 ian: let's put those ques in the deployment discussion agenda 14:27:32 manu: decisions we make on deliverables pull people into or out of critical path 14:28:17 ian: need to discuss (after establishign arch goals) who we are putting in c path 14:29:00 manu: do we want rec track deliverables added before f2f? 14:29:05 ian: what would you add? 14:29:16 manu: split apis into browser and REST 14:29:29 manu: split vocab into a few vocabs 14:29:54 manu: is it premature to have JSON-LD in there? need to still decide on data model (tree vs graph) 14:30:44 ian: let's discuss offline 14:31:03 manu: any other comments? 14:31:14 zakim, who is on the call? 14:31:14 On the phone I see AdrianHB, manu, Katie_Haritos-Shea, Ian, ShaneM, ChaoDuan 14:31:35 AdrianHB: No particular input yet - essentially the settlement stuff I've been looking at would fall into its own group. 14:31:52 AdrianHB: Based on capabilities and presentation, I think it might be something that could stand on its own. 14:32:27 AdrianHB: I don't think Settlement is going to be a v1 deliverable - version 1 payments stuff can survive w/o settlement advances. We may get it done quickly, we may not - not a dependency for v1. 14:32:38 +1 14:33:00 AdrianHB: I'd like to do settlement sooner than later, let's put ideas in front of the group to see what they think. 14:33:18 Topic: Capabilities Presentation 14:33:21 https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015/Capabilities 14:34:03 manu: pat and I discussed preso. it's geared toward getting consensus on the organisation of the doc 14:34:35 manu: looking to get agreement that the categories make sense and also get the group up to speed on what has been done 14:35:01 manu: what are the capabilities? What to do next and what to do after? Discuss roles 14:35:10 ... interactions of roles 14:35:32 ... do the groupings makes sense, anything to add/change? 14:36:01 ... avoiding details as this will be a first look for a lot of people 14:36:29 ... Was going to propose that we show what details might look like for a select set of capabilities 14:36:45 Ryladog: Will we not show the doc? 14:37:01 manu: We will but it doesn't have too much detail 14:37:12 Agree to show a sample 14:37:14 Ryladog: +1 to some examples 14:37:37 manu: need to decide the mechanics of how we'll work on this doc 14:37:47 ian: wiki? 14:38:11 manu: looks terrible and moving to respec is going to take ages 14:38:32 ryladog: suggestions: 1 save to PC and work on static html 14:38:46 ... 2) put in Word doc or similar and work on that 14:39:10 manu: will take an offline snapshot on Friday 14:40:18 AdrianHB: What are the specific mechanics for how we do this. 14:41:26 manu: we won't edit the doc directly, we will have high level discussion and capture in wiki 14:41:42 Topic: Use Cases Presentation 14:41:50 https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015/UseCases 14:42:07 manu: we may not need the full hour 14:42:41 q+ 14:42:42 manu: we will be talking capabilities before use cases 14:42:58 ... use case session is about prioritisation 14:43:20 ... determine what use cases we care about for v1 14:43:49 ... ensure everyone understands we are not going for 100% coverage in v1 14:43:59 q+ 14:44:03 ... also need to note that there are missing uses cases 14:44:24 ... diminishing returns on use cases as we are pretty clear on the req for v1 14:44:51 ack Ian 14:44:55 q+ 14:45:23 ian: 1 - got a preso today from leandro who wants to share the boleto (sp?) use case, do we have time for this? 14:46:06 manu: I want to. Not sure it will change anything ito v1 14:46:27 ian: it will sit in the "after v1" stuff discussion 14:46:44 manu: let's keep it short (5 mins) and then there shouldn't be a problem 14:47:06 ian: I want to focus on use cases from W3C IG participants 14:47:14 +1 14:47:24 ian: we will consider others but those from the group should get priority 14:47:28 +1 14:47:39 +1 to closing the loop 14:47:53 manu: I see this as mostly about closing the loop on the use cases, is that a good goal? 14:48:02 ian: yes 14:48:33 ian: getting consensus and then inviting more conversation on day 3 14:48:48 ... there are enough new people that it's worth spending time on this 14:49:16 ... also ensuring that the message is clear around not being in v1 does not mean out of scope 14:49:55 manu: we are looking at debit pull payments in v1 because it's not common to do push today 14:50:13 q+ 14:50:20 ack Ryladog 14:50:27 manu: there aren't appropriate use cases for push 14:50:32 manu: suggest we discuss 14:50:42 ryladog: +1 for discussion 14:50:56 ryladog: are we getting Gates Foundation reps? 14:51:04 manu: yes, only at round table 14:51:29 ryladog: great because having their use cases on the agenda makes them feel that their involvement is important 14:52:44 ian: +1 but let's not give the impression that we will def be adding gates foundation use cases to our document 14:53:45 manu: changing wording on F2F collatoral to reflect that 14:54:03 ian: like the goal of closing the loop and getting group up to speed 14:54:29 ... next goal is to discuss the fact that we can still process new use cases 14:54:52 ... third goal is to look at how our use cases compare with other uses cases from external orgs 14:55:56 ... part of the meeting theme is: do we have the right set and priority of work? 14:56:23 ... fourth goal is to assist participanst to submit new use cases in future 14:56:46 s/participanst/participants/ 14:57:19 manu: I also want to go over the payment agent arch priorities doc 14:57:28 ... this gives a view of what is to come 14:57:32 q+ 14:57:55 [manu talks through doc] 14:58:37 AdrianHB: Yes, today the payment flow is completely ignorant of settlement. 14:58:47 AdrianHB: In version 1, we're optimizing payments that already exist. 14:59:06 AdrianHB: The Settlement stuff may be parallel to version 2 - priority will come from how many people are ready to participate. 14:59:41 ryladog: have national payment assoc of india joined? 14:59:45 ack Ian 14:59:53 ian: they have and etherium but haven't really participated 15:00:14 ack Ryladog 15:01:20 manu: priorities doc isn't completely in alignment with capabilities doc so hope we don't cause confusion 15:01:45 ... last call tomorrow, please give thoughts to agenda 15:01:53 http://www.w3.org/Payments/ 15:02:34 -ShaneM 15:02:48 +1 I will do an update 15:03:00 -Katie_Haritos-Shea 15:04:50 -manu 15:04:53 -Ian 15:04:54 -AdrianHB 15:05:00 rrsagent, draft minutes 15:05:00 I have made the request to generate http://www.w3.org/2015/06/11-wpay-minutes.html manu 15:05:03 -ChaoDuan 15:05:04 T&S_WEBPYMT(WPAY_USE)10:00AM has ended 15:05:04 Attendees were AdrianHB, manu, Katie_Haritos-Shea, Ian, ShaneM, ChaoDuan 15:05:38 Present: Manu, Adrian, Ian, Shane, Katie, ChaoDuan 15:05:40 rrsagent, draft minutes 15:05:40 I have made the request to generate http://www.w3.org/2015/06/11-wpay-minutes.html manu 15:05:47 rrsagent, make logs public 15:05:57 rrsagent, draft minutes 15:05:57 I have made the request to generate http://www.w3.org/2015/06/11-wpay-minutes.html manu 15:06:11 chaals has joined #wpay 15:06:11 Chair: Manu 15:06:14 Regrets: Pat 15:06:49 rrsagent, draft minutes 15:06:49 I have made the request to generate http://www.w3.org/2015/06/11-wpay-minutes.html manu 15:16:39 schuki has joined #wpay 15:25:29 chaals has joined #wpay