- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 2 Aug 2016 19:49:30 -0500
- To: Payments WG <public-payments-wg@w3.org>
- Message-Id: <1E53EFF7-F1C3-4D4F-9DBC-5D97E63EFCA3@w3.org>
Participants in the payments app task force, We meet 3 August at 13:00 UTC (9am ET). Here’s the draft agenda. Ian ============== REGISTRATION - Optimizing user experience Issue 8: Is registration "necessary"? https://github.com/w3c/webpayments-payment-apps-api/issues/8 Action: JasonN to write a proposal about minimizing the effort to register payment apps, calling out merchant recommendations, browser recommendations, and user initiated registration ============== SELECTION Issue 14: Optimizng for one match https://github.com/w3c/webpayments-payment-apps-api/issues/14 Issue 11: What should be the user experience when an app is recommended for two methods? https://github.com/w3c/webpayments-payment-apps-api/issues/11 ============== TRUST Issue 1: Should merchants be able to limit matching to trusted apps? https://github.com/w3c/webpayments-payment-apps-api/issues/1 Issue 9: “Security Error” on different origins and localhost https://github.com/w3c/webpayments-payment-apps-api/issues/9 ============== DESIGN CONSIDERATIONS https://github.com/w3c/webpayments/wiki/PaymentApp_Notes#design-considerations Action: Conor and JasonN will send comments on the text. ============== NEXT DRAFT - Priority edits? ============== TPAC PLANNING - What are our goals for payment apps at TPAC? Also, see 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 Wednesday, 3 August 2016 00:49:48 UTC