- From: ianbjacobs <notifications@github.com>
- Date: Fri, 27 May 2016 10:49:10 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Friday, 27 May 2016 17:50:08 UTC
@adrianhopebailie wrote: > I AM saying that we need to define a way for someone who mints a new currency identifier (i.e. non-standard) to also be able to provide display guidance to a user agent. I don't think you are saying that because "leaving the meaning up to the community" fulfills that requirement. I think you want us to define a STANDARD way to communicate how to find hints. This is also suggested when you wrote: "... how will browsers ever do this consistently?" I would not prioritize solving that problem in v1. I DO support people being able to communicate via the field and learning what communications patterns emerge, possibly for future standardization. I believe we have (at this point) understood each other's views. I'm not yet convinced we need to create a standard way to communicate information about where to find display hints (however those happen to be defined, which I believe we agree should not be us). Ian --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/185#issuecomment-222210815
Received on Friday, 27 May 2016 17:50:08 UTC