Re: [w3c/browser-payment-api] Currency Types and Rendering (#185)

* +1 for requiring conforming software to handle any 3-letter string that is an ISO currency code as such. I haven't heard anyone say otherwise, so I think we should RESOLVE this.
* +1 for +ABC for commonly used but not yet standardized codes. The WG would define a small number of these. I can live without this, however.
* Treat other strings as "undefined." This allows people to experiment with URLs if they wish.
  Another way of saying this is "-1 to requiring URLs here; +1 to enabling them."

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