Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89)

Here is my prioritized list of questions that probably need to be answered for us to get to a March 2016 FPWD goal:

### Technical 
1. Are we doing a high-level API (Checkout) AND a low-level API (Payment)? Or just a high-level API (Checkout)?
2. What if we get the Checkout API wrong? Should we specify APIs to get shipping address, request payment, and polyfill the rest until we can figure out the best way to do it?
3. Are we going to support "payment app" registration via the API or is it going to remain unspecified?
4. How are Web-based payment apps going to receive a payment request and respond with a payment acknowledgement?
5. What are the combinatorial issues with adding the ability to "get more payer information" to the Checkout API?
6. Is the interaction pattern for the Checkout API going to be promises, events, or a hybrid? How does one request payer information (like shipping option) when processing a shipping address change option.

### Strategic
1. What are the goals of the Checkout API? What are the goals of the Payment API? Are they different?
2. What data do we have to study in order to see if the APIs will meet their goals?
3. How does one extend the type of information you can ask for via the Checkout API? For example, is a WG required to add a Billing Address request? 

### Operational
1. Who are the editors of the WG specs going to be and when are we putting the specs into the WG repo?
2. How are we going to fix the transparency issues and backchannel discussions in the group?
3. Is the "incubate the specs in a CG" model working?


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