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

This proposal is related to the question at #17.

__ Background __
* The WG decided that we should produce an HTTP API and we are chartered to so.
* There will be benefit to aligning the messaging used in both the HTTP API and JavaScript API.
* The group's efforts are currently focused on the JavaScript API and the design of this API is likely to impact the design of any messages that are exchanged via the API.

__PROPOSAL__
The WG should wait until the JavaScript API is sufficiently mature that the messaging schemas have stabilized and then design an HTTP API based on these schemas. This would mean not publishing an FPWD of an HTTP API in March.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/73