14:59:46 RRSAgent has joined #wpwg 14:59:46 logging to http://www.w3.org/2017/02/23-wpwg-irc 14:59:48 RRSAgent, make logs public 14:59:48 Zakim has joined #wpwg 14:59:50 Zakim, this will be 14:59:50 I don't understand 'this will be', trackbot 14:59:51 Meeting: Web Payments Working Group Teleconference 14:59:51 Date: 23 February 2017 15:00:05 agenda: https://github.com/w3c/webpayments/wiki/Agenda-20170223 15:00:11 Ian has changed the topic to: 23 Feb agenda => https://github.com/w3c/webpayments/wiki/Agenda-20170223 15:00:24 present+ 15:00:26 regrets+ Molly 15:00:54 present+ 15:01:05 present+ AdamR 15:01:33 rouslan has joined #wpwg 15:02:05 present+ Pascal 15:02:27 present+ Rouslan 15:03:06 present+ Mathieu 15:03:59 Guest91 has joined #wpwg 15:05:17 present+ Max 15:05:25 present+ 15:05:30 present+ Olivier 15:05:47 Topic: PMI pull request 15:06:23 https://github.com/w3c/webpayments-method-identifiers/pull/21/commits/42b022563e337f195758eed2dd22f7cde09620a6 15:06:30 https://github.com/w3c/webpayments-method-identifiers/pull/21/files 15:06:40 betehess has joined #wpwg 15:06:57 present+ 15:07:05 present+ 15:07:29 https://github.com/w3c/webpayments-method-identifiers/pull/21/files 15:07:53 Chair: AdrianHB 15:08:05 PROPOSED: Adopt AHB's pull request for PMI => https://github.com/w3c/webpayments-method-identifiers/pull/21/files 15:08:06 present+ 15:08:25 AdrianHB: No longer requires HTTPS ; instead refers to URL spec and secure contexts and use concept that is more general 15:08:35 "potentially trustworthy URL" 15:08:38 mathp has joined #wpwg 15:08:53 AdrianHB: I added info to the matching algorithm to throw out query string/fragments 15:09:11 s/throw out query string/fragments/throw out URL if it contains query string or fragment id 15:09:13 dezell has joined #wpwg 15:09:45 AdamR: Looks good in general. One additional fix is "hard abort" still there on line 136 15:09:59 AdrianHB: Thanks, I will fix that 15:10:29 Ken has joined #wpwg 15:10:31 s/hard abort/will be ignored/ 15:10:36 IJ: Any other comments on the changes? 15:10:42 present+ Ken 15:10:54 present+ dezell 15:10:56 q? 15:11:20 +1 15:11:21 +1 15:11:24 +1 15:11:30 +1 15:11:30 +1 15:11:36 {No Objections} 15:11:37 alyver has joined #wpwg 15:11:46 RESOLVED: Adopt pull request 21 for PMI spec with AdamR's fix 15:12:23 RRSAgent, make minutes 15:12:23 I have made the request to generate http://www.w3.org/2017/02/23-wpwg-minutes.html Ian 15:12:27 RRSAgent, set logs public 15:12:42 https://github.com/w3c/webpayments-method-identifiers/issues 15:13:27 Topic: Payment option filtering 15:13:32 https://github.com/w3c/browser-payment-api/pull/420 15:13:32 q+ 15:14:08 ack rouslan 15:14:18 IJ: This is a PR for simple browser-based comparison of filters / capabilities 15:14:53 rouslan: The proposal says: when payment method specific data that has a list of strings, the browser treats them like potential filter 15:15:00 ...when a payment app registers it will specify capabilities 15:15:08 ...the capabilities are payment method specific 15:15:51 ...the PR is about how to do matching between merchant filter and payment app capabilities 15:16:11 ...the difference between my proposal and AdamR's proposal on this is that Adam proposes a specific label for filters. 15:16:19 q+ 15:16:24 ...I prefer not labeling filters; easier for backwards compability 15:16:43 (IJ: But labeling filters gives you better forwards-compatibility I think) 15:16:57 rouslan: We could use a shim for older uses of API to newer uses, but I'd rather avoid 15:17:10 ...I've asked AdamR and Domenic to review the proposal 15:17:38 ...Domenic has been helping to make the spec more explicit (to foster interop) 15:17:52 ...they have made comments on the thread and I've not addressed them yet 15:17:54 ack AdrianHB 15:17:57 ack Ad 15:18:15 AdamR: There is one comment that merits discussion here - where we want filters to be separated out from request data or mixed in 15:18:47 +1 to have them outside the payment method data 15:18:51 ..while I am sympathetic to existing implementation, my concern here is that for yet-to-be-defined payment methods, there may come a time when a payment method wants to define a list of string, and they could accidentally be treated as filters 15:19:30 ...I prefer the slight hit today of calling out filters today in favor of an easier future 15:20:42 https://github.com/w3c/webpayments-payment-apps-api/issues/96#issuecomment-276416457 15:21:54 AdamR approach: 15:21:55 const methodData = [{ 15:21:55 supportedMethods: ["basic-card"], 15:21:55 filters: { 15:21:56 supportedNetworks: ['visa', 'mastercard'], 15:21:57 supportedTypes: ['credit'] 15:21:59 }, 15:22:01 data: { 15:22:03 // Any payment-method-specific fields go here. 15:22:05 } 15:22:07 }]; 15:22:09 Rouslan approach: 15:22:11 hypothetical.api.register( 15:22:13 "basic-card", 15:22:15 "MyBank's Debit Card", 15:22:17 data: { 15:22:19 supportedNetworks: "visa", 15:22:21 supportedTypes: "debit" 15:22:23 }); 15:22:50 ==== 15:23:06 We could special case the existing names and say "those are treated as filters for backwards compatibility; so avoid them" 15:23:08 q+ 15:24:37 ack rous 15:24:37 ack rouslan 15:25:00 q? 15:25:05 rouslan: +1 to that compromise - recommend people use filters, but for basic card the two filters are treated specially 15:25:08 AdamR: I can live with that 15:25:36 Rouslan: I propose to update the pull request and bring back to the group 15:26:03 q? 15:26:08 Q? 15:26:28 AdrianHB: This would still mean a change to PR API to add a filters member. 15:26:54 Rouslan: Google implementation will still look for filters in data 15:27:48 q+ 15:27:57 IJ: Do we want to treat BC specially? 15:28:04 q+ 15:28:08 AdamR: I would hesitate to have BC remain an exception 15:28:25 ...would prefer "filters" as the primary mechanism and deprecate in the long term having filters in data 15:28:30 +1 to AdamR 15:28:51 rouslan: I think what we'll do in chrome is print a console warning when BC is used with data instead of filters. We'll deprecate over time in favor filters 15:29:21 q+ 15:29:24 nicktr: Let's also check in with other implementers 15:29:33 q+ to ask about basic card spec change 15:29:36 Q+ 15:29:42 ack 15:29:42 ack ad 15:29:50 ack rou 15:30:17 rouslan: You mentioned Molly...we should definitely check with MS 15:30:37 ACTION: Rouslan to check with Molly about this proposal re: filters 15:30:37 Created ACTION-52 - Check with molly about this proposal re: filters [on Rouslan Solomakhin - due 2017-03-02]. 15:30:39 ack me 15:30:39 Ian, you wanted to ask about basic card spec change 15:31:10 Ian: Do we also need to update BC to reflect the filtering? 15:31:30 (this affects the credit transfer and tokenization specs) 15:32:22 Rouslan: Yes, that's correct. 15:32:37 IJ: Do you want to augment your pull request with changes to BC? 15:32:53 Rouslan: I would need a new one? 15:33:15 AdamR: If you just make changes to your repo and click on the PR button, it will pile the new commitments on top 15:33:23 Rouslan: But it's two repos 15:33:29 ...so I need a new pull request 15:33:41 Rouslan: I propose to wait to hear from MS first, then proceed 15:33:45 q? 15:33:48 ack nick 15:34:08 nicktr: This has highlighted for me what we need to get to by FTF meeting - inbound changes to PR API 15:34:19 ...that's going to to be part of the conversation to get to CR 15:34:39 topic: FTF meeting agenda 15:34:46 https://github.com/w3c/webpayments/wiki/FTF-March2017 15:35:00 nicktr: I have started with a detailed agenda...got as far as day 1 15:35:06 https://github.com/w3c/webpayments/wiki/FTF-March2017#proposed-agenda-times-are-local 15:35:31 q+ 15:36:53 IJ: I think testing as "separate" from PR API 15:37:10 ...let's ask for clarification 15:37:43 IJ :Can we have more time on payment app 15:37:48 Nick: that will be continued on day 2 15:38:27 IJ: We will have 2 more payment method specs 15:39:03 IJ: suggest 30 mins each 15:39:13 +30 mins merchant adoption 15:39:26 IJ: Any demo commitments? 15:40:23 Nick: I want to demo Conor's work 15:41:00 IJ: Would love to see Microsoft implementation 15:41:42 Guest91 has joined #wpwg 15:42:15 Let's review the next draft in a week 15:43:13 Nick: Will there be remote access? 15:44:17 ACTION: Ian to set up WebEx for the 2-day meeting 15:44:18 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., IFSF-EFT-WG-Lead, ijacobs, ijmad). 15:44:29 q? 15:44:31 ack me 15:44:33 +1 to having significantly more time on day 2 for Payment Apps. 15:44:56 nicktr: Should we spend the entire morning on payment apps? 15:44:59 AdamR: I think it's possible 15:45:24 ...there are a number of open issues...we are converging on a few of them but I think some are suffering from lack of input from broader group 15:46:27 nicktr: Would be prepared to lead that session 15:46:28 AdamR: Yes 15:46:54 q+ 15:47:04 q? 15:47:11 ack me 15:47:13 https://github.com/w3c/webpayments-payment-apps-api/wiki/Proposal-20170130 15:49:26 Ian: I updated that yesterday. We are making progress and at a minimum we should share where we've arrived 15:49:37 adrianhB: Regarding the agenda, let's leave time on both days for things that come up in discussion 15:50:22 +1 to beer 15:51:42 topic: 15:51:42 Payment Method Manifest Specification 15:51:46 Topic: Payment Method Manifest Specification 15:51:56 Max: We made some progress and updated the draft 15:51:59 ...but not yet on GitHub 15:52:08 ...hope to have that by FTF meeting 15:52:28 IJ: How much time on FTF agenda for it? 15:52:39 Max: I'd like to finish it soon for people to review it 15:52:49 ...before the meeting 15:53:17 +1 to 30 minutes on payment app manifest to start 15:53:18 notes another 30 minutes for manifest 15:53:47 nicktr: What about breakout sessions? 15:54:22 propose we only do breakouts if we are time limited 15:54:24 IJ: Logistically, it's feasible 15:54:36 AdamR: I don't object in principle but I would not want to treat payment apps as a breakout session 15:54:36 +1 15:54:45 +1 to payment apps being in the main group 15:55:22 alyver has left #wpwg 15:55:25 AdrianHB: I propose that if we don't have enough time for topics, we breakout to optimize 15:55:48 Nick: I want to put the "get to CR" conversation early afternoon on Day 2 15:55:49 +1 15:56:28 zakim, who is here? 15:56:28 Present: Ian, AdrianHB, AdamR, Pascal, Rouslan, Mathieu, Max, oyiptong, Olivier, Guest, spolu, nicktr, Ken, dezell 15:56:31 On IRC I see Ken, dezell, mathp, betehess, rouslan, Zakim, RRSAgent, pascal_bazin, Max, adamR, hober, canton_, pea13, slightlyoff, ShaneM, trackbot, Ian, dlehn, adrianba, Dongwoo, 15:56:31 ... JakeA, emschwartz, oyiptong, davidillsley_, nicktr, AdrianHB, mkwst, schuki, manu, dlongley 15:56:42 Guest91 has joined #wpwg 15:56:46 Topic: Testing 15:56:52 IJ: How is testing going? 15:56:58 Stan: I am iterating; adding a few tests 15:57:17 ...my first goal is to build a mock version of the payment request that I inject in a page, so that I can progress on running the test suite 15:57:28 ..I hope to show you something next week 15:58:15 IJ: Maybe have something to show at FTF? 15:58:22 ...or issues riased 15:58:30 Stan: I won't be at the FTF but could present over WebEx 15:58:49 Topic: Next meeting 15:58:55 2 March 15:59:00 RRSAgent, make minutes 15:59:00 I have made the request to generate http://www.w3.org/2017/02/23-wpwg-minutes.html Ian 15:59:04 RRSAgent, set logs public 15:59:14 Nick: Please send regrets/issues to the chairs 15:59:21 Regrets for 2 March 15:59:24 AdrianHB: Regrets for me for next week; but will be at chairs meeting 15:59:26 RRSAgent, make minutes 15:59:27 I have made the request to generate http://www.w3.org/2017/02/23-wpwg-minutes.html Ian 15:59:27 thanks everyone 15:59:37 RRSAgent, set logs public 15:59:40 Guest91 has joined #wpwg 17:53:31 betehess has joined #wpwg 18:06:40 Guest91 has joined #wpwg 18:20:35 Zakim has left #wpwg 19:03:11 Guest91 has joined #wpwg 20:15:21 Guest91 has joined #wpwg 20:23:09 Guest91 has joined #wpwg 21:48:31 Guest91 has joined #wpwg 23:36:17 Guest91 has joined #wpwg 23:42:21 Guest91 has joined #wpwg 23:49:08 Guest91 has joined #wpwg 23:53:02 Guest91 has joined #wpwg 23:58:26 Guest91 has joined #wpwg