- From: Ian Jacobs <ij@w3.org>
- Date: Wed, 4 Jan 2017 09:19:32 -0600
- To: Payments WG <public-payments-wg@w3.org>
- Message-Id: <E90D5DFB-6D67-4A49-B390-0EB75C361CFA@w3.org>
Hi all, Minutes from today’s call: https://www.w3.org/2017/01/04-apps-minutes.html Next call is 10 January at 10:00 ET. Thank you, Ian > On Jan 3, 2017, at 11:55 AM, Ian Jacobs <ij@w3.org> wrote: > > Participants in the payments app task force, > > Happy new year! We meet 4 January at 9am ET. Draft agenda below. > Please let me know if there are other topics you would like to > discuss. > > NEXT meeting (note day / time change): 10 January, 10:00 ET. > > Previous meeting 14 December: > https://www.w3.org/2016/12/14-apps-minutes > > WebEx: > https://www.w3.org/2016/08/payment-apps-tf.ics > > Ian > > ======== > Developer call > > Conor is organizing the next payment app developer call: > https://lists.w3.org/Archives/Public/public-payments-wg/2017Jan/0000.html > > Please let me know if 12 January works for you! > > ======== > Issue 63: Should payment apps implement payment method-specific filters? > https://github.com/w3c/webpayments-payment-apps-api/issues/63 > > There is support from Rouslan, AdrianHB, Dave Longley, and Ian for > AdamR's proposal (with some minor changes, e.g., sequence of > dictionaries returned and some editorial tweaks). > https://github.com/w3c/webpayments-payment-apps-api/pull/76 > > PROPOSED: To adopt this proposal into the specification taking into > account 14 December discussion: > https://www.w3.org/2016/12/14-apps-minutes.html#item01 > > ======== > Issue 73: Need to specify behavior for Clients.openWindow #73 > https://github.com/w3c/webpayments-payment-apps-api/issues/73 > > Please review Ian's edits to section 10.3 for inclusion: > https://github.com/w3c/webpayments-payment-apps-api/pull/78/commits/855790ae19152678a2f8f1695b1563ccb84fbd2e > > Based on 14 December discussion: > https://www.w3.org/2016/12/14-apps-minutes.html#item02 > > ======== > Issue 74: Fleshing out Recommended payment apps > https://github.com/w3c/webpayments-payment-apps-api/issues/74 > > See Rouslan's and Ian's notes in the issue. Would someone > like to offer to review the text in the spec and propose > changes? > > ======== > Planning for FPWD > > We resolved to request a call for consensus to advance Payment App API > to FPWD at the end of this month. What do we want to have accomplished > by then? > > ======== > Issue 48: Payment app identifier to payment app manifest filename mapping > https://github.com/w3c/webpayments-payment-apps-api/issues/48 > > Relates to PMI issue 19; we should discuss that one first: > https://github.com/w3c/webpayments-method-identifiers/issues/19 > > See also from Adrian: > https://github.com/w3c/webpayments-payment-apps-api/issues/48#issuecomment-261786242 > > ======== > Other issues > https://github.com/w3c/webpayments-payment-apps-api/issues > > -- > Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs > Tel: +1 718 260 9447 > > > -- Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs Tel: +1 718 260 9447
Received on Wednesday, 4 January 2017 15:19:43 UTC