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

Previously I proposed a three-tiered approach:
1) Anything that is an ISO 3-letter code is treated as such
2) Non-standard 3-letter codes are prefixed with "+"
3) Anything else is undefined for now. You can put whatever data you want there and some parties may make use of it.

But 2 and 3 both amount to "you can do other non-standard things." So a simpler proposal would be:

1) Anything that is an ISO 3-letter code is treated as such. 
   (Note that the standard set of codes may expand over time, so there may be times when some 
    browsers recognize standard codes, but others have not yet been updated.)
  
2) Anything else is undefined. So you can put whatever data you want there and some parties may make use of it.

By the way, this seems to be where ECMAScript defines its use of currency codes:
 https://tc39.github.io/ecma402/#sec-currency-codes

It talks about normalization of the 3-letter codes, which we should consider.

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