Re: [w3c/webpayments] New Architecture Proposal (#125)

@adrianhopebailie wrote: "This proposal is the second document. I think some of the confusion comes from combining the payment app and payment mediator roles in one document but I think that having hundreds of documents is a mistake."

I do not believe we will have hundreds. This diagram:
 https://github.com/w3c/browser-payment-api/issues/138#issuecomment-212582445

suggestions:

 * 2 api specs (paymentRequest, HTTP)
 * 2 specs for mediator/apps. As we discussed, I still think 2 might be better since different audiences (e.g., browser developers v. payment app developers) but I don't mind experimentation to try to come up with one.
 * N payment method specs.
 * 1 payment method identifier spec
 * 1 architecture document

>  ... I wonder if this document shoudl also be the normative reference for what a payment method is and how identifiers are defined?

How about this: let's keep it in its own document for now and then determine where the content should go after we understand better (1) how much content that turns out to be and (2) whether the evolution of the mediator/app spec really suggests that identifiers should be included...or not.

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/webpayments/pull/125#issuecomment-213117629