Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34)

@ianbjacobs,

"We do not recommend that user agents automatically dereference these URIs because there is currently no general expectation that machine readable information will be retrieved."

I think that's ok, but seems sub-optimal. Wouldn't it be better to say it can be done but you might not get anything useful out of it? For example:

"A user agent MAY automatically dereference these URIs, but there is no general expectation that machine readable information will be retrieved."

I think saying that we don't recommend it can be taken as a suggestion that they don't do it vs. a statement that they are free to do what they want, it's not a requirement, and they might not find anything easily consumable on the other end.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/34#issuecomment-195458328