- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 30 Aug 2016 11:11:57 -0500
- To: Payments WG Public <public-payments-wg@w3.org>
- Message-Id: <B50FDCD9-D27A-414C-AC0D-44A5105209BC@w3.org>
Participants in the payments app task force, We meet 31 August at 13:00 UTC (9am ET). Here’s the draft agenda. Please look for your action items in the agenda. Previous meeting 24 August: https://www.w3.org/2016/08/24-apps-minutes We are using the same WebEx information as previous weeks (requires Member password to access): https://www.w3.org/2016/08/payment-apps-tf.ics Ian ========= SPEC UPDATE * We updated the spec on 25 August based on discussion: https://w3c.github.io/webpayments-payment-apps-api/ Notes were added on origin information (related to issue 27 and some security considerations): https://github.com/w3c/webpayments-payment-apps-api/commit/0fb7a91a78eed64b80862e3555de06e6a5f3c26d#diff-eacf331f0ffc35d4b482f1d15a887d3b * What are goals for updates in time for TPAC discussion? ========= INVOCATION * AdamR's proposal https://github.com/w3c/webpayments-payment-apps-api/blob/gh-pages/proposals/jsapi.md There seems to be emerging consensus to model this with service workers. Do we have agreement here? Are we confident enough to move to spec text? What discussion would be useful during TPAC (e.g., in a WPWG breakout session on 20 Sep with others from the W3C community)? Action 2016-08-24: Ian to find out the status of app manifest (and objections) - My understanding is that there is not yet consensus to advance to CR and there remain some open issues. Adrian has indicated he plans to add our use case to a thread in that group. This action is not closed and I Hope to have some additional information in a couple of weeks. Action 2016-08-24: Ian to write to Mike5 with the service worker question. - I did so but Tommy did even more via his summary and subsequent thread: https://github.com/w3c/webpayments-payment-apps-api/issues/33 ========= Display and selecton of apps * Action 2016-08-24: Max to update his proposal to manage authenticity of payment apps and point Zach at it: - Max did so; we await a reply: https://lists.w3.org/Archives/Public/public-payments-wg/2016Aug/0112.html * Action 2016-08-07: Max to write up some thoughts on merchant-controlled display of payment apps for selection ======================================================= USER EXPERIENCES AROUND DISPLAY AND SELECTION OF APPS https://github.com/w3c/webpayments/wiki/PaymentApp_Notes#user-experience-descriptions ACTION 2016-08-03: Ian to organize a chat with Ben on writing down different user experiences. - Ian reached out to Ben and we have not yet scheduled a chat, but I expect we will make progress on this soon. ACTION 2016-08-10: AdrianHB to review the table ============== DESIGN CONSIDERATIONS https://github.com/w3c/webpayments/wiki/PaymentApp_Notes#design-considerations Action 2016-07-27: Conor and JasonN will send comments on the text. ============= OTHER ISSUES The full issues list in the new payment apps repo: https://github.com/w3c/webpayments-payment-apps-api/issues -- Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs Tel: +1 718 260 9447
Received on Tuesday, 30 August 2016 16:12:00 UTC