Re: [w3c/browser-payment-api] Change the way we request user data (#65)

Also note the significant discussion on #1 including comments from TAG review by @triblondon 

There seems to be consensus that the tokenized approach is preferred however we need to accommodate @adrianba 's requirement for more granularity in the request (i.e. is this data mandatory or optional)

@zkoch perhaps this could be updated to use the *Descriptor* pattern in the same vein as the Permissions API to accommodate @adrianba 's requirement?

Something like:

```
dictionary DataDescriptor {
  required DOMString name;
  required boolean optional = false;
};

dictionary ShippingAddressDataDescriptor : DataDescriptor {
  sequence<ShippingOption> shippingOptions = false;
};

dictionary PaymentOptions {
  sequence<DataDescriptor> requestData;
  ...
};
```
Two things to note from the discussion on #1:
 1. the arguments against explicitly listing the set of data that can be requested.
 1. the arguments for a fluid API for setting these requirements which looks like it will be a lot more developer friendly if this list grows (see also #51).


---
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-211848205