Minutes [Was: [Agenda] 28 February Payment Apps Task Force Meeting]

Minutes from today’s call:
 https://www.w3.org/2017/02/28-apps-minutes

Next call: 7 February

Ian


> On Feb 27, 2017, at 10:43 AM, Ian Jacobs <ij@w3.org> wrote:
> 
> Participants in the payments app task force,
> 
> We meet 28 January at 10am ET. 
> 
> Previous meeting 21 February:
>  https://www.w3.org/2017/02/21-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-20170130
> 
> I would like to review the updated summary since last week's call.
> (I welcome people's review between now and the meeting. It's not very long.)
> 
> Also, I'd like to discuss spec updates based on our increasing convergence. I would
> like to have an updated spec in time for the FTF meeting.
> 
> Issues list:
> https://github.com/w3c/webpayments-payment-apps-api/issues
> 
> ----------------------------------------
> Issue 99: New request/response objects for payment apps
> Issue 95: Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete()
> Issues 98, 90, 70, 69: Apps, wallets, and options
> 
> We merged AdamR's proposal:
> https://github.com/w3c/webpayments-payment-apps-api/commit/4430d10f1b0957196576b8018a095a4b5a26eb81
> 
> AdamR, what are next steps for this proposal?
> 
> ----------------------------------------
> Issue 91: Line items and privacy
> 
> Reopened based on Marcos privacy question:
> https://github.com/w3c/webpayments-payment-apps-api/issues/91#issuecomment-279904374
> 
> ----------------------------------------
> Issues 73, 97: Opening Windows
> 
> Action: Marcos and Tommy to draft a proposal for openClientWindow.
> 
> ----------------------------------------
> Issues 83, 96: Filters/capabilities
> 
> At the 23 Feb WPWG call, we discussed Rouslan's proposal
> https://github.com/w3c/browser-payment-api/pull/420
> https://www.w3.org/2017/02/23-wpwg-minutes#item02
> 
> Rouslan is planning to make some updates regarding (1) explicit
> identification of filters with (2) limited backwards compatibility for
> managing the way basic card has been implemented up to now. We also
> want to check with MS on the proposal.
> 
> ----------------------------------------
> 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#issuecomment-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#issuecomment-278941318
> 
>                  Some were discussed 31 Jan: https://www.w3.org/2017/01/31-apps-minutes#item01
> 
> 
> =======
> Next meeting
> 
> * 5 March
> 
> ========
> Other issues
> https://github.com/w3c/webpayments-payment-apps-api/issues
> 
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 718 260 9447
> 
> 
> 
> 

--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447

Received on Tuesday, 28 February 2017 16:15:45 UTC