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

> I should have said, actually visa versa.

I knew what you meant :), and I think that the reverse would not be good either (having the Browser API spec depend on the HTTP API). I'm concerned about the notion of a "web based payment app" - as one could argue that the Browser API is a perfectly valid way to talk to a "web based payment app"... and that the HTTP API is a perfectly valid way to talk to a "web based payment app". I can see both arguments and am worried that we're headed down a path where we have two mechanisms of talking to a web based payment app. 

Instead, we may want to say that a payment app can support two different protocols - an HTTP API based protocol, or a browser API based protocol. The first is non-interactive, the second is interactive. In any case, just pointing out that we still have a bit to go wrt. understanding how this entire ecosystem fits together (but are making progress).

Can we have a call where we hash this stuff out? Trying to do this on an issue thread is taking forever and leading to a good bit of miscommunication and (possibly) selective hearing.

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