Agenda 20160505

• July FTF meeting schedule

  • Aiming for 6-8 July in London
  • One idea with IG Chairs is to hold 1-day IG meeting in Boston alongside the Blockchain Workshop. Thoughts from the WG?

• Adopt new proposals as editor's drafts of the WG?

  • HTTP API
  • Core Messages

• Payment Method Identifiers

  • Issue 11 - URLs or other format?
  • [Issue 10] (https://github.com/w3c/browser-payment-api/issues/10) - Support for short-names/aliases?
  • Process for creating new identifiers owned by the WG (i.e. referenced in W3C published specs) and others?
  • Proposal from Zach

• Requesting user data (not just shipping address and options)

  • PR 174 - Adding support for phone and email
  • PR 65 - Change the way we request user data (PR withdrawn? - @zkoch)
  • Issue 1 - Requesting email and phone number
  • Issue 27 - Should API support billing address capture (for tax computation)?

• API design

  • Issue 15 - Combine API parameters into a single request object + options
  • Issue 16 - Use navigator.payments singleton, factory method, or PaymentRequest constructor
  • Issue 122 - Format of complete()
  • PR 179 - Add support for ShippingOption.selected

• Multi-currency

  • Issue 3 - Should it be possible to provide amounts in more than one currency?
  • Issue 178 - Dynamic Currency Conversion (DCC) Support

• Different amounts per payment method

  • Issue 4 - Should it be possible to vary amounts depending on payment method ?

• Restricting to top-level browsing context

  • Issue 2 - Should the Payment Request API only be available in a top-level browsing context?