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

After further reviewing the Payment Request API Architecture document, I think it needs to more clearly indicate that it is just the architecture for the API, not for an overall Web Payments ecosystem or vision. The title is at least better than how the document is referenced throughout itself, where the language "Payment Request Architecture" is used, not "Payment Request API Architecture".

Is the plan to create separate architecture documents for each API? Should we just wait to publish this until we can figure that out? If we're going to have a separate document for each API, why not just include it in the API document itself?

It seems to me that we should create a single architecture document that includes all of the high-level concepts for a Web Payments vision -- and not a separate document for each API. We could put out a primer for each (or some) of the APIs -- and perhaps this current document would fit better that in that mold.

---
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-197518694