Agenda 20161208 - w3c/webpayments GitHub Wiki

Coming soon:

  • Issue 311. We discussed on 1 December 2016 and indicated that more GitHub discussion of a transition plan was in order. Any updates?
  • Deployment
    • Who would like to work with Nick and Ian on updated communications around the benefits (to merchants (and merchant service providers)) of the payments APIs?
    • Samsung colleagues and Ian have been chatting about organizing business-level support for merchant adoption; Ian is preparing to reach out to WPWG member business/PR for unified outreach effort and welcomes expressions of interest.
  • Updated publications milestones
  • Recently raised issues
    • Issue 330: Making this API work with HTML Forms

Notes on manifest file addressing

  • Hard-coded URL
    • Pro: Simple configuration
    • Con: Limits server to one manifest file per payment method. Squats URI space.
  • HTTP Link header (used in conjunction with caching)
    • Pro: Greater flexibility in naming, serving multiple resources.
  • Content negotiation
    • Pro: One URL
    • Con: May be challenging to configure; support may not be as widespread as we'd like (@@to be fleshed out@@).
  • Serve JSON for PMI; link to human readable content from there
    • Pro: Optimizes for the information we know today we want to associate with a PMI. Still allows follow your nose to get more information.
    • Con: People get back data instead of human readable info by default so less friendly.