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

I think it is useful to have a separate document for several reasons:

* It most likely addresses a different audience, one that wants a big picture rather than looking at code samples. It is more approachable to have a smaller document with a consistent tone for that audience, than a larger document where the majority is not for that audience. I don't think the current architecture document is a finished product but I think it is worth publishing as a FPWD.
* It is helpful to be able to evolve that document independently of the specs.
* I think it's also helpful to have a wrapper for what is likely to be a growing number of independent specifications (especially if we start to publish more payment method specs).

I don't have a strong view of the use of the word "Architecture v. "Overview" in the title.

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