My understanding was that Zach was [proposing a mechanism](https://github.com/w3c/browser-payment-api/pull/65#issue-141070003) to indicate to the user agent that the page wanted to request email and phone number. This was modeled on the Permissions API, which also has a concrete list of allowed data. One problem I have with Zach's proposal is that, compared to the Permissions API where you are either asking for a permission or you are not, we might have situations is which collecting a value is desirable but not required. As I understand it now, @adrianhopebailie's [most recent proposal](https://github.com/w3c/browser-payment-api/pull/65#issuecomment-212488768) is trying to turn this into a general purpose "gather any kind of data" proposal. I do not support this. I support the idea that the web page should be able to ask for specific data with known semantics such as, in Zach's proposal, email and phone number. This allows the user agent to provide an informed user experience that can make it clear to the user what data they are sharing. It also allows us to offer data that we already know about the user (such as their email address or phone number). I don't want to try to build a user experience for the collection of arbitrary data with unknown semantics. --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/pull/65#issuecomment-212532480
Received on Wednesday, 20 April 2016 17:47:55 UTC