[w3ctag/spec-reviews] Web Payments Working Group Specifications (#152)

Hello TAG!

I'm requesting a TAG review of:

* [Payment Request API (PR API)](https://w3c.github.io/browser-payment-api/)
* [Payment Method Identifiers (PMI)](http://w3c.github.io/webpayments-method-identifiers/)
* [Basic Card Payment](https://w3c.github.io/webpayments-methods-card/)

For more about this call for review (from early Jan 2017), see:
 https://lists.w3.org/Archives/Member/chairs/2017JanMar/0002.html

Primary contact: @ianbjacobs

Further details:

  - Relevant time constraints or deadlines: The Web Payments Working Group next meets [face-to-face 23-24 March in Chicago](https://github.com/w3c/webpayments/wiki/FTF-March2017). The meeting is just prior to the IETF meeting, so if someone from the TAG plans to be in Chicago and wants to pop over to the WPWG meeting, let me know. I realize this means there is not a lot of time to raise issues before the FTF meeting, but that would certainly be very welcome. We do not yet have time frame for going to CR, but I anticipate that we will use a portion of the FTF meeting to get our ducks in a row.
  - [ some time ago] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The [assessment from that time is here](https://lists.w3.org/Archives/Public/public-payments-wg/2016Jul/att-0013/WebpaymentsAPISecurityandPrivacyChecklist.pdf).
  - [ a long time ago ] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)

You should also know that...

  - Google, Microsoft, Facebook, Opera, Samsung, and Mozilla have begun to implement.
  - We have some initial work on a test suite but a lot more work to do.

We'd prefer the TAG provide feedback as (please select one):

  - [x] open issues in our Github repo for each point of feedback
  - [ ] open a single issue in our Github repo for the entire review
  - [ ] leave review feedback as a comment in this issue and @-notify [github usernames]

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/152