Minutes [Was: [Agenda] 29 August Payment Apps Task Force teleconference]

Minutes from today’s call:
 https://www.w3.org/2017/08/29-apps-minutes.html

Welcome Matt de Ganon!

Next call: 5 September. No call planned on 12 September.

Ian


> On Aug 28, 2017, at 12:50 PM, Ian Jacobs <ij@w3.org> wrote:
> 
> Participants in the payments app task force,
> 
> We meet 29 August from 10-11am ET.
> 
> WebEx: 
> http://www.w3.org/2017/01/paymentapps-2017.ics
> 
> Previous meeting: 22 August
> https://www.w3.org/2017/07/25-apps-minutes
> 
> Proposed next meeting: 5 September
> 
> Note: once PR API has moved to CR, the payment apps
> task force is likely to disband in favor of discussion of
> topics on the full WPWG agenda.
> 
> Ian
> 
> ==========
> Agenda
> 
> * Discussion about editing policy and tests
> 
> * Add CanMakePaymentEvent and AbortPaymentEvent
>  https://github.com/w3c/payment-handler/pull/170
>  Related issues: 157, 117
> 
>  - After discussion with Mozilla, Google, Rouslan plans
>    to pull out the AbortPaymentEvent into its own pull
>    request.
> 
>  - Rouslan is socializing the idea of:
>    a) Making "capabilities" a data parameter where the
>       semantics are defined in each payment method specification,
>       starting with basic card. For basic card, the capabilities
>       data would be filter data, thus enabling the browser
>       to do static matching.
> 
>    b) AdrianHB will also discuss an idea to perhaps drop
>       the CanMakePaymentEvent.
> 
> * Issue 173: Ability to set default instrument for given handler
> 
>  There is now a pull request about user hints
>  https://github.com/w3c/payment-handler/pull/206
> 
> * Service workers example from Rouslan to illustrate
>  how to publish two "wallets" from the origin. Should
>  we add this example to the spec? Or to the developer
>  portal? Are there issues with the example?
>  https://github.com/rsolomakhin/rsolomakhin.github.io/blob/master/pr/sw.md
> 
>  Rouslan any updates to the example?
> 
>  I believe that once we've resolved what to do with the
>  example, we can close issue 153.
> 
> * Issue 116: Relation between merchant order of payment methods and
>  payment app order of instruments.
> 
>  See Ian proposal for language (supported by Rouslan):
>  https://github.com/w3c/payment-handler/issues/116#issuecomment-317890522
> 
>  Another idea is to remove the requirement language entirely.
> 
> * Issue 203: Make explicit which origin to use in conjunction with
>  payment method manifest
>  https://github.com/w3c/payment-handler/issues/203
> 
> * Next meeting: Proposed 5 September
> 
> --
> 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, 29 August 2017 15:19:04 UTC