Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73)

-1 for the following reasons:

1. We have enough for a rough-cut at an FPWD right now. 
2. The HTTP API is less contentious than the Browser API.
3. We should send a clear message that a browser API *and* an HTTP API are equally important to the group.
4. Assertions made in the HTTP API may influence the Browser API. We shouldn't merely focus on the browser. There are many other types of HTTP clients out there than just browsers.

We just need a few folks to review the HTTP API and raise issues. At the very worst, we highlight those issues in the spec and push out a FPWD.

COUNTERPROPOSAL: We get 2-3 people to review the HTTP API and raise issues, include those issues in the spec, and push out a FPWD in March.

Reply to this email directly or view it on GitHub:

Received on Thursday, 28 January 2016 04:20:10 UTC