[w3c/browser-payment-api] Flows issue 32 (#131)

The flow diagram is referenced from a remote rep, but I will address that with the next PR if we agree this is a good way to proceed.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/131

-- Commit Summary --

  * Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into gh-pages
  * Added card sub-brands to payment method identifier list (based upon my understanding of option 1 in the Payment Method Identifiers spec
  * Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into gh-pages
  * Proposal for dealing with specification of required fields
  * Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into gh-pages
  * Add UML Flow as per issue 32
  * Revert "Add UML Flow as per issue 32"
  * Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into Flows,-issue-32
  * Added UML Flow diagram

-- File Changes --

    M specs/basic-card-payment.html (44)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/131.patch
https://github.com/w3c/browser-payment-api/pull/131.diff

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/131