W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134)

From: ianbjacobs <notifications@github.com>
Date: Tue, 31 May 2016 15:25:02 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/134/222839873@github.com>
I am of two minds:

1) Because the browser is going to be the primary mediator, I think ideally we'd add the "browser-as-mediator" role to the paymentRequest specification, and not deal with "abstract mediators" for now at least.

2) One can design a payment app layer on top of paymentRequest. If we are going to take this approach and not touch paymentRequest, then I am ok creating a separate spec for the mediator. However, even in this case I have a much stronger preference to start with the specific case of browser-as-mediator rather than abstract without experience.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Tuesday, 31 May 2016 22:25:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 31 May 2016 22:25:33 UTC