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

@dlongley,

Yes, the references to the document internally should reflect this is for the API architecture.

> Is the plan to create separate architecture documents for each API? 

I don't think there is a plan in the sense that nothing has been proposed yet.

> Should we just wait to publish this until we can figure that out?

I prefer to publish this document because it helps to understand how this set of documents works together. It does not preclude later changes, later descriptions, etc.

> If we're going to have a separate document for each API, why not just include it in the API document itself?

Once we have proposals, we can decide whether they are most well-suited (e.g., separate architecture documents or within this one).

In short: I would like to publish this one with the others we currently have. This is expected to be a NOTE and therefore we have a lot of flexibility in how it evolves. Publishing it today should help readers understand the current set of documents, and does not constrain us in the future if we want to make changes.

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