Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138)

Having recently done a more thorough review of the architecture document I have a slightly different take on this. I don't see enough content for that document if we describe the core components in other specs.

I propose that the architecture spec should define the roles of the payment app and the payment mediator in the form of conformance criteria for those roles. It should describe payment methods and how these are used to provide extinsibility and then refer to another spec (currently the Payment Method Identifiers spec) which provides details on how to define a payment method and the minimum requirements for a new payment method specific spec.

The HTTP and browser API specs will depend on these two and define the implementation specifics of implementing:
 1. A payment mediator in a user agent
 1. A payment app as a web app
 1. A payment mediator as a web service

We could have a stand alone messages spec which defines the base schema of the messages and the rules for encoding these in different forms but this could also be encapsulated in the two API specs.

I am working on a concrete proposal following this approach and will share it in the next few days.

---
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/138#issuecomment-210115104