15:58:29 RRSAgent has joined #wpwg-spc 15:58:29 logging to https://www.w3.org/2021/07/26-wpwg-spc-irc 15:58:33 Meeting: SPC Task Force 15:58:39 Agenda: https://lists.w3.org/Archives/Public/public-payments-wg/2021Jul/0006.html 15:58:43 Chair: Ian 15:58:45 Scribe: Ian 15:59:05 present+ 15:59:10 present+ Rouslan_Solomakhin 15:59:15 present+ Bastien_Latge 15:59:43 present+ Clinton_Allen 16:00:23 Anne has joined #wpwg-spc 16:00:54 present+ Anne_Pouillard 16:01:04 regrets+ Stephen_McGruer 16:01:29 present+ Susan_Pandy 16:02:11 present+ Gerhard_Oosthuizen 16:02:24 present+ Jonathan_Grossar 16:02:30 present+ Sameer_Tare 16:02:46 present+ AdrianHB 16:03:01 present+ Christian_Aabye 16:03:22 -> https://lists.w3.org/Archives/Public/public-payments-wg/2021Jul/0006.html Agenda 16:03:24 rouslan has joined #wpwg-spc 16:03:28 present+ 16:03:30 Gerhard has joined #wpwg-spc 16:03:30 Topic: Preparing for FPWD for SPC API 16:03:37 Christian has joined #wpwg-spc 16:03:49 -> https://w3c.github.io/secure-payment-confirmation/ SPC API 16:04:06 https://github.com/w3c/secure-payment-confirmation/wiki/Plan-2021 16:05:28 present+ Doug_Fisher 16:06:34 q+ to ask whether the major point of FPWD is the patent exclusion or something else? 16:06:47 Ian: Can we start CfC on 5 August? 16:06:49 ack rouslan 16:06:49 rouslan, you wanted to ask whether the major point of FPWD is the patent exclusion or something else? 16:08:18 werner has joined #wpwg-spc 16:08:50 present+ Werner_Bruinings 16:08:59 present+ Praveena_Subrahmany 16:10:32 Ian: I think the main reason to go to FPWD is to say "The wg plans to make this a rec (in the future)." Important industry statement. 16:10:34 q? 16:10:53 q+ to ask about timing 16:11:10 Ian: Does FPWD hinder us from making changes? 16:11:12 Rouslan: No 16:11:23 ...we like the living specification model (e.g., HTML4) 16:11:26 s/HTML4/HTML5 16:11:43 q+ to talk about living standard 16:11:44 ack AdrianHB 16:11:44 AdrianHB, you wanted to ask about timing 16:12:14 AdrianHB: My fear is that if stuff ships and people are implementing against it (irrespective of specs), browsers will be reluctant to change. 16:12:39 ...if people are implementing against what you put out in first iteration, it's very hard to make breaking changes 16:13:11 ...so my question -- is there a deadline for suggested changes? How soon would you like people to suggest changes to the spec so that it can be incorporated into chrome? 16:13:25 rouslan: Pull request this week or next week might make it into the first version we ship 16:13:31 ...the timeline is quite tight at this point 16:13:49 ...I do understand the concern about shipping things and those features being "burnt into the net" 16:14:02 ...that's the point of the origin process (we've been in trial for nearly a year on and off) 16:14:32 ...we are making spec changes and API changes based on both partner feedback and webAuthn team within Google 16:14:39 ...so we've been moving the API closer to WebAuthn 16:14:57 ...I don't think we should be too concerned about the inability to remove things from the Web...we have processes for deprecation 16:15:23 ...relies on good feature detection and availability of new improved approach 16:15:39 ...when users of old API drop below .002% of all page loads (approximately) we can remove the API from the Web 16:16:00 Bastien has joined #wpwg-spc 16:16:03 ...I envision that SPC will be a good signal to the ecosystem to start using it...and we'll get more feedback from those users 16:16:10 q+ to ask about feature detection for SPC 16:16:14 ..and we'll add new features and try to prevent old features from breaking 16:16:39 ..is chrome 93 we are switching lots of things that are breaking changes, which is ok in origin trial 16:17:00 ack AdrianHB 16:17:00 AdrianHB, you wanted to ask about feature detection for SPC 16:17:14 https://github.com/w3c/secure-payment-confirmation/issues/81 16:17:17 AdrianHB: The one thing it would be great to fix before shipping is feature detection 16:17:23 ...it's not great right now 16:17:39 ...I'm happy to help with this if that's a priority 16:17:49 rouslan: +1 16:20:44 q+ to say that updated feature detection is planned for after first ship date 16:20:51 ack me 16:20:51 Ian, you wanted to talk about living standard 16:20:55 ack rouslan 16:20:55 rouslan, you wanted to say that updated feature detection is planned for after first ship date 16:21:30 rouslan: Regarding feature detection; I think our plan is to ship without stronger feature detection and to improve it in subsequent implementation 16:22:47 Topic: SPC issues 16:22:52 https://github.com/w3c/secure-payment-confirmation/issues 16:23:29 https://github.com/w3c/secure-payment-confirmation/issues/84 16:24:42 Ian: Any more views on 84?: 16:24:43 q+ to talk about the enrollment UI 16:24:46 ack rous 16:24:46 rouslan, you wanted to talk about the enrollment UI 16:25:00 rouslan: I think a majority of the Google team is leaning to "no special enrollment UI" 16:25:08 ...to align more with WebAuthn 16:25:31 ...the reasons for enrollment UI were 2 originally: (1) icon/display information was required at enrollment, but that's no longer necessary 16:25:53 (2) privacy team had originally suggested that in order to do enrollment in a cross-origin iframe needed special UI 16:26:25 ...however, more internal discussions suggest that the enrollment UI is probably not required for privacy 16:27:26 Ian: Do you think 3p enrollment will be more generally acceptable to WebAuthn? 16:27:31 rouslan: Don't know yet 16:29:24 https://github.com/w3c/secure-payment-confirmation/issues/92\ 16:29:28 Topic: Next call 16:29:33 2 July 16:29:41 RRSAGENT, make minutes 16:29:41 I have made the request to generate https://www.w3.org/2021/07/26-wpwg-spc-minutes.html Ian 16:29:55 RRSAGENT, set logs public 16:30:22 rrsagent, bye 16:30:22 I see no action items