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

Re: [webpayments] Should we be publishing a specification for an HTTP API? (#17)

From: ianbjacobs <notifications@github.com>
Date: Wed, 27 Jan 2016 07:50:06 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/17/175698635@github.com>
My thoughts:
* Previously, I thought it would be great to strive for a March publication of an HTTP API. We are chartered to produce one, and I'd like us to show progress on this front. 
* I also thought it would be valuable to allow the APIs to evolve independently, and as we understand the needs of each more clearly, seek (but not require) harmonization between them. 
* However, I agree with Adrian's observation that the JS API feels today like the primary one, and therefore I support focusing our energies on it first. I hope this will enable us to solidify it more quickly, and ultimately reduce churn on the HTTP API design.


Reply to this email directly or view it on GitHub:
Received on Wednesday, 27 January 2016 15:51:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:13 UTC