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

> Here is my thinking in a nutshell:
* We need identifiers.
* We also need documentation of the shape of payment request and payment response data for different payment methods.
* People who are using the identifiers need that documentation to use the payment method.
* Therefore, the identifiers should be (good practice) URIs to documentation on how to use the payment method associated with the identifier.

I don't think it follows that because developers need documentation then the identifiers that they use should point to the documentation. In fact, I think this is back-to-front. Developers will need to find the documentation in order to know if there is any payment method specific information needed on request, to know what the response message looks like, and to know what options are available for complete(). It seems simple to me that they can also find the payment method identifier from the same document and nobody is going to assume that the identifier must naturally be what's in the address bar of their browser while reading it.

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