Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42)

@dlongley,

My understanding is that the editors have chosen to break the content into (at least) four pieces: API, identifiers, basic card payments, registration. Three of those are available today. It makes sense to me to keep a "how all these things fit together" description as a separate document rather than inside one of them. 

This has been done for previous sets of specifications (e.g., OWL, PROV, RIF).

Ian

---
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/issues/42#issuecomment-197533446