- From: Bazin Pascal <Pascal.Bazin@gemalto.com>
- Date: Wed, 1 Mar 2017 17:22:47 +0000
- To: Ian Jacobs <ij@w3.org>
- CC: Payments WG <public-payments-wg@w3.org>
- Message-ID: <606A05ACDEE9F74E877F3472E959FA47014AAD7A51@A1GTOEMBXV005.gto.a3c.atos.net>
Hi Ian, I reviewed the status of Key Issues, https://github.com/w3c/webpayments-payment-apps-api/wiki/Proposal-20170130 Not much to say, a few remarks and some questions, but please read the following with a lenient attitude, I may missed that some of those points have already been raised and closed. - Permission o The user must grant permission to an origin. Should we explain that the permission is possibly bound to a limited payment-app scope. - Registration/Capabilities o Is the reference to the Payment Method Manifest Specification<https://w3c.github.io/webpayments/proposals/Payment-Manifest-Proposal> still relevant ? and what about the use cases described there (payment app authorized origins, digital signature,…) ? - Invocation o A payment handler having zero payment methods is not very useful ! - Selection of Options o Am I right to think that whatever the app option selected, it refers to the same and only one registered app-related payment handler ? - Implementation questions o Could start with a list of possibly not-supported features. III Pascal BAZIN<http://gsearch.gemalto.com/search/people/detailspeople.jsp?q=gin:10021956> -----Original Message----- From: Ian Jacobs [mailto:ij@w3.org] Sent: mardi 21 février 2017 17:47 To: Payments WG <public-payments-wg@w3.org>; Jake Archibald <jakearchibald@google.com> Subject: Minutes [Was: [Agenda] 21 Feb 2017 Payment Apps task force call] Hi all, Minutes from today’s call: https://www.w3.org/2017/02/21-apps-minutes (Corrections to the minutes welcome!) Over the next couple of days I will update this document to reflect the conversation: https://github.com/w3c/webpayments-payment-apps-api/wiki/Proposal-20170130 Next call: 28 February, 10-11am ET Ian > On Feb 20, 2017, at 9:01 AM, Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> wrote: > > Participants in the payments app task force, (Jake, I’m wondering > whether you might be able to attend for discussion on service workers > / identity) > > We meet 21 January at 10am ET. > > Previous meeting 14 February: > https://www.w3.org/2017/02/14-apps-minutes > > WebEx: > http://www.w3.org/2017/01/paymentapps-2017.ics > > Ian > > ======== > For reference > > Proposal (summary of where we are on key issues): > https://github.com/w3c/webpayments-payment-apps-api/wiki/Proposal-2017 > 0130 > > Issues list: > https://github.com/w3c/webpayments-payment-apps-api/issues > > ---------------------------------------- > Issue 99: New request/response objects for payment apps > > Action AdamR 20170214: Write a pull request to align the payment app > spec with payment request objects > > ---------------------------------------- > Issue 95: Replace setManifest()/getManifest() with > set()/get()/keys()/has()/delete() > > Action AdamR 20170214: Incorporate capabilities in his pull request on > granular data get/set > > ---------------------------------------- > Issue 91: Line items and privacy > > Reopened based on Marcos privacy question: > https://github.com/w3c/webpayments-payment-apps-api/issues/91#issuecom > ment-279904374 > > ---------------------------------------- > Issues 73, 97: Opening Windows > > Action: Marcos and Tommy to draft a proposal for openClientWindow. > > ---------------------------------------- > Issues 83, 96: Filters/capabilities > > Action Rouslan 20170214: Work on text that would go in payment request > API regarding capabilities > > Done: > https://github.com/w3c/browser-payment-api/pull/420 > > See comments from AdamR and Domenic. > > ---------------------------------------- > Issues 98, 90, 70, 69: Apps, wallets, and options > > Action: Andre to write up use cases for "wallet" containers within a > payment app. > > Action: AdamR to write a proposal for providing icons and labels for > different granularities. > > Related: Tommy algorithms around Payment Apps and Service Workers > https://github.com/tommythorsen/webpayments-demo/blob/gh-pages/proposa > ls/Apps%20and%20Workers.md > > In particular, see discussion starting from: > https://github.com/w3c/webpayments-payment-apps-api/issues/98#issuecom > ment-280456005 > > ---------------------------------------- > Recommended payment apps (74, 79) > (Discussed 14 Feb but no resolution) > > ACTION: Task force to review Ian's proposal (to drop Recommended payment apps > from the payment app API but continue to investigate as a separate layer): > https://github.com/w3c/webpayments-payment-apps-api/issues/74#issuecom > ment-278340715 > > ACTION: Task force to review Tommy's approach to recommending apps when none available: > https://github.com/w3c/webpayments-payment-apps-api/issues/74#issuecom > ment-278941318 > > Some were discussed 31 Jan: > https://www.w3.org/2017/01/31-apps-minutes#item01 > > > ======= > Next meeting > > * 28 February > > ======== > Other issues > https://github.com/w3c/webpayments-payment-apps-api/issues > > -- > Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> > https://www.w3.org/People/Jacobs/ > Tel: +1 718 260 9447 > > > > > -- Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> https://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447 ________________________________ This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Received on Wednesday, 1 March 2017 17:23:24 UTC