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

@mattsaxon I have put a proposal together that shows what an architecture document looks like that would combine descriptions of the roles of payment mediator and payment app.

https://w3c.github.io/webpayments/proposals/architecture/

I don't agree that they will target different audiences as it's quite possible that in many implementations both roles will be assumed by the same system (e.g. In a browser or in a head-less IoT system where the payer is a device that implements both roles using HTTP APIs).

My proposal is that the payment apps document (https://w3c.github.io/webpayments/proposals/paymentapps/payment-apps.html) is now split into three parts:
 1. Some elements of it will be incorporated into the new architecture document (where similar content is not already there)
 1. The user agent specific elements regarding registration and passing payment messages between the user agent and apps should be in-corproated into the browser API
 1. The manifest specific elements should be submitted for inclusion into the manifest spec (I have already started engaging the editors on this).

What we will have are two base specs, the Architecture and the Payment Method Identifiers which provide the foundation for all implementations.

On top of these we will have specs that define how the roles are implemented in different ways (in browser or as HTTP client/server) and specs that define the specifics of how a payment method works.

I realize that this has now dropped the information about what specs we have produced and how they relate. This COULD be included in the architecture document or in a stand-alone note from the WG.

@mountainhippo said:
> getting proposals for payment mediator and payment app are now super important and I will be looking for volunteers to push this forward on the call today.

I'm hoping that the WG will build on the new arch proposal I have made and that other editors will step up to flesh this document out to meet our needs.

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