13:58:42 RRSAgent has joined #apps 13:58:42 logging to http://www.w3.org/2017/04/18-apps-irc 13:59:32 AdrianHb has joined #apps 14:00:56 rouslan has joined #apps 14:01:02 present+ 14:01:20 present+ 14:01:27 present+ Conor 14:01:39 alyver has joined #apps 14:01:46 present+ alyver 14:02:09 ConorH has joined #apps 14:02:19 present+ 14:02:26 present+ 14:02:43 zakim, who's here? 14:02:43 Present: rouslan, Ian, Conor, alyver, jnormore, ConorH 14:02:45 On IRC I see ConorH, alyver, rouslan, AdrianHb, RRSAgent, MattS, jnormore, Zakim, cweiss, adamR, Dongwoo, Ian, JakeA 14:02:54 present- Conor 14:02:55 present+ AdrianHB 14:03:00 present+ Christian 14:03:04 present+ Joseph 14:04:10 topic: Introduction 14:04:18 [Joseph Xu] 14:04:22 ..first time on the call. 14:04:32 Welcome Joseph :) 14:05:03 -> https://lists.w3.org/Archives/Public/public-payments-wg/2017Apr/0039.html Agenda 14:05:06 agenda? 14:05:29 zakim, take up item 1 14:05:29 agendum 1. "Recent changes to Payment Handler API" taken up [from Ian] 14:06:05 https://w3c.github.io/webpayments-payment-handler/ 14:06:31 * Updated short name / URL 14:06:31 * Add support for topLevelOrigin and paymentRequestOrigin 14:06:31 * Added 2 diagrams (worked on with MattS). (Can we close 49?) 14:06:31 * Issue markers 14:06:31 * Many markup fixes, tidy (please tidy edits henceforth!) 14:08:22 present+ MattS 14:08:34 present+ 14:08:48 Ken has joined #apps 14:09:03 present+ Ken 14:09:30 zakim, close item 1 14:09:30 agendum 1, Recent changes to Payment Handler API, closed 14:09:31 I see 4 items remaining on the agenda; the next one is 14:09:31 2. Adrian's edits [from Ian] 14:09:33 zakim, take up item 2 14:09:33 agendum 2. "Adrian's edits" taken up [from Ian] 14:10:24 https://github.com/w3c/webpayments-payment-handler/pull/138/commits/013db090f6513387cc401ed586bd67b5c56c1a15 14:11:11 AdrianHb: My edits were primarily editorial 14:11:40 ...the main thrust of what I was getting at was making it clear that what the spec defines is this new event handler 14:11:49 ...we are defining a way to response to a particular payment event 14:12:02 ...there's a new feature in the platform (payment handlers) that handle this new event 14:12:04 Newcomer has joined #apps 14:12:20 ..then you build on that - how do I instruct a browser to raise the event when payment events that I can handle are being processed? 14:12:32 ...that's when you bring in the term PaymentManager 14:12:48 https://github.com/w3c/webpayments-payment-handler/issues/127 14:12:58 https://github.com/w3c/webpayments-payment-handler/issues/127#issuecomment-294713131 14:13:09 Payment App? Handler? Manager? 14:13:39 AdrianHB: 14:13:52 q+ 14:14:02 1) Key thing we are defining in the platform is the payment handler. It stand on its own as a feature 14:14:24 ..it allows you to process payment requests. It makes no assumptions about where those requests originate; they don't HAVE to come through the payment request API 14:14:59 ...the focus is on payment handlers..pieces of code that are invoked when an event is raised. 14:15:17 2) Another piece of the spec is how we manage metadata about the handlers - methods, instruments, wallets 14:15:30 ...I see the PaymentManager as layering on the handler but not essential to the handler functionality 14:16:08 ...so the PaymentManager is a feature we are adding (to service worker registration) that qualifies the payment handler 14:16:25 ...I think PaymentManager but we could call it something like PaymentMethodManager or PaymentInstrumentManager 14:16:29 +1 to PaymentInstrumentManager, much more explicit 14:16:43 or in fact if thats a mouthful, InstrumentManager 14:17:23 3) A payment app is a specialization of a Web App that uses these features 14:17:28 The problem with “InstrumentManager” is that this is going in to the top-level ServiceWorker scope. It needs to make sense in the context of the broader web platform. 14:17:35 q? 14:17:36 ok 14:17:41 ack Matts 14:17:59 MattS: I appreciate AHB's description and Ian's scribing. I think the spec does not reflect that yet 14:18:18 ..the first point is that the spec is called PaymentHandler...from what you said, the spec should be called Payment App 14:19:20 IJ: Rationale against Payment App was "too broad" 14:19:36 MattS: Make sense but now too narrow, IMO 14:20:04 +1 to PaymentHandlerRequest 14:20:04 MattS: Maybe we need to change PaymentAppRequest/PaymentAppResponse => PaymentHandlerRequest/PaymentAppResponse 14:20:08 q? 14:20:49 MattS: The reason I wanted the diagram was to clarify the entities etc....the diagrams are missing PaymentManager 14:21:05 adrianHB: PaymentManager exists under service worker...you use it to register to register instruments and wallets 14:21:22 q? 14:21:49 MattS: I suggest we leave 127 open for FPWD...but would be nice to have some consistency for FPWD 14:22:05 ...at a minimum, I suggest we represent PaymentManager in the diagram (instead of PaymentHandler) 14:22:09 ...I will continue to review 14:22:47 q? 14:22:55 https://github.com/w3c/webpayments-payment-handler/pull/138/commits/013db090f6513387cc401ed586bd67b5c56c1a15 14:23:50 IJ: Why not say "one or more payment handler" (cf my proposal)? 14:24:13 https://github.com/w3c/webpayments-payment-handler/pull/138/files 14:25:07 "Payment apps make use of service workers to register their payment handling capabilities with the user agent. This is done through one or more payment handlers, which listen to PaymentRequestEvents raised through the Payment Request API." 14:26:07 IJ: My point is don't say "one" 14:27:30 why not say payment apps must each use a service worker 14:27:32 Payment apps make use of (one or more) service workers, each of which defines... 14:31:51 agenda? 14:31:57 zakim, close item 2 14:31:57 agendum 2, Adrian's edits, closed 14:31:58 I see 3 items remaining on the agenda; the next one is 14:31:58 3. Seeking additional reviewer [from Ian] 14:32:09 zakim, close item 4 14:32:09 agendum 4, Issue 127: Do we need "Payment Manager" and "Payment Handler”?, closed 14:32:11 I see 2 items remaining on the agenda; the next one is 14:32:11 3. Seeking additional reviewer [from Ian] 14:32:15 zakim, take up item 3 14:32:15 agendum 3. "Seeking additional reviewer" taken up [from Ian] 14:32:46 q+ 14:32:50 ack rouslan 14:33:05 Rouslan: I read the document. I update the android spec as well. 14:33:13 ...I had one small issue, which I will put on github 14:33:29 (IJ has read it) 14:34:39 MattS: I will review the updated doc 14:34:51 ...will review changes by Thursday 14:35:38 [Example updates?] 14:36:04 AdamR: I think one of the examples is incorrect. There are also stylistic differences... 14:36:19 ....e.g., "wait" instead of "then" could be an improvement... 14:36:29 ...I think Marco's improves would probably help a lot 14:36:33 s/wait/await/ 14:37:34 Rouslan: I will look at AHB's javascript 14:37:59 q? 14:38:21 zakim, take up item 5 14:38:21 agendum 5. "Status wrt FPWD" taken up [from Ian] 14:38:33 IJ: I would like to start a CfC around 1 May (for 1 week) 14:39:23 ...if all goes well, FPWD week of 8 May 14:40:15 PROPOSED: The task force recommends the Chairs start a CFC for Payment Handler (after last round of edits) around 1 May 14:40:24 +1 14:40:30 +1 14:40:31 +1 14:40:32 +1 14:40:52 +1 14:41:01 topic: Implementer update 14:41:25 IJ: What are the opportunities implementers will have to play with this? 14:41:43 Rouslan: Chromium has a near complete implementation of this API. 14:41:51 ...we'd like to start experimentation after FPWD 14:42:33 IJ: Any firefox updates? 14:42:48 AdamR: Marcos and Matt have been doing some work...no specific update on progress for today 14:44:04 IJ: Can we institute an implementation focused semi-regular call after FPWD so that user agents and app developers can work together 14:44:05 Conor: +1` 14:44:43 Ian: https://github.com/marcoscaceres/web-payments-proto/ 14:44:55 Ian: and https://marcoscaceres.github.io/web-payments-proto/ 14:44:57 Topic: Next meeting 14:45:06 2 May 14:45:16 +1 14:45:37 RRSAgent, make minutes 14:45:37 I have made the request to generate http://www.w3.org/2017/04/18-apps-minutes.html Ian 14:45:40 RRSAgent, set logs public 14:54:45 jnormore has joined #apps 17:14:34 cweiss has joined #apps 19:32:57 cweiss has joined #apps 20:32:02 cweiss has joined #apps 21:08:21 cweiss has joined #apps