Re: [Agenda] 21 Feb 2017 Payment Apps task force call

I guess you mean tomorrow? Sure!

On Mon, 20 Feb 2017 at 15:01 Ian Jacobs <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-20170130
>
> 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#issuecomment-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/proposals/Apps%20and%20Workers.md
>
> In particular, see discussion starting from:
>
> https://github.com/w3c/webpayments-payment-apps-api/issues/98#issuecomment-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#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
>
> * 28 February
>
> ========
> 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 <+1%20718-260-9447>
>
>
>
>
>