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

@adrianhopebailie ,
> Call it what you will, our API doesn't fully support non-standard currencies unless we provide a way to help implementors displayed them properly to users so I wouldn't consider this low priority.

I want to distinguish:
 - The standard remaining silent on how to support non-standard currencies, from
 - The ecosystem being able to deal with non-standard currencies.

I don't want to prevent people from being able to deal with it. I just don't think we should
specify:

 * How to display non-standard currencies (which I'm sure is a huge topic
   that I continue to think is out of scope)
 * That the only way to provide information that might be useful is through a URI. For example, what if someone just wanted to provide a Unicode character code? 

I think we should allow for some experimentation here before we say "It MUST be a URL if it's not a three-letter ISO code."

> I don't consider a hard-coded short-list as support when there are hundreds of crypto-currencies in use today and new ones being invented all the time.

I can live without the hard-coded list.

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