[Agenda] 17 January Payments Apps Task Force Call

Participants in the payments app task force,

We meet 17 January at 10am ET. Draft agenda below.  Please let me know
if there are other topics you would like to discuss.

Previous meeting 10 January:
  https://www.w3.org/2017/01/10-apps-minutes

WebEx: http://www.w3.org/2017/01/paymentapps-2017.ics

Ian

========
Recent changes to Payment App API
https://w3c.github.io/webpayments-payment-apps-api/

Integrated revised model text (notably around recommended apps)
  https://github.com/w3c/webpayments-payment-apps-api/commit/5de10a295f00c1161a55d286413253e8467491a5#diff-eacf331f0ffc35d4b482f1d15a887d3b

========
Payment app identifiers
Issue 48: https://github.com/w3c/webpayments-payment-apps-api/issues/48

We are still wrestling with what identifiers we have and what they
identify. The spec now talks about PAI's identifying service worker code:
 https://w3c.github.io/webpayments-payment-apps-api/#identification

AdrianHB has a counter proposal:
 https://github.com/w3c/webpayments-payment-apps-api/issues/48#issuecomment-261775283

I have also asked Jake Archibald to weigh in on the discussion on GitHub

========
Tommy's pull request regarding PaymentAppResponse Dictionary:
 https://github.com/w3c/webpayments-payment-apps-api/pull/84

Please let us know whether you support this change. (Tommy is unlikely
to be able to join the call.)

========
Issue 73: Need to specify behavior for Clients.openWindow
https://github.com/w3c/webpayments-payment-apps-api/issues/73

Action 20170104: Rouslan to look into how progress web apps could help
us understand how to manage UI in different contexts.

========
Issue 83: payment-manifest.json and canHandle function
https://github.com/w3c/webpayments-payment-apps-api/issues/83

Conor raised this issue last week.

========
Planning for FPWD

I heard last week that we are going to try to resolve the following
before requesting to advance to FPWD:

 * 48: Payment App Identifiers
 * 81: Tommy's dictionary request
 * 79: Adam's text (next week) on how PR API would need to change
       for recommended payment apps.
 * 73: Clients.openWindow 
 * 69: Relationship to App Manifest spec

Any others (e.g., issue 83)?

Are there any of these we can live with not resolving before FPWD?

========
For next week

Issue 79: How does the payee provide information about recommended payment apps?
https://github.com/w3c/webpayments-payment-apps-api/issues/79

  Action AdamR 20170110: Draft how PR API would change to allow-payee
                         recommended payment apps, due 24 January.

=======
Next meeting

* 14 January

========
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

Received on Monday, 16 January 2017 19:24:28 UTC