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

@adrianhopebailie,

> but we've made the decision to put pricing UI in front of users as a feature of the flow so we need to define how that UI should handle non-standard currencies. 

We are not specifying any display behavior for any currency, however that currency is identified (ISO Code or otherwise).

@tommythorsen said:
>    the burden is upon the mediator to present this in a user-friendly way.

@adrianhopebailie said:

> 👍 - although we should provide a way browsers to do this consistently (per @rsolomakhin above)

@rsolomakhin's next sentence is "However, presentation is largely out of scope of this specification. "

I believe it would be a major rathole for this group to go down the path of actually specifying "how to display various currencies." If we do not have confidence that people will frequently use these URLs to find useful information about how to display currencies, that REQUIRING a URL for any non-ISO currency is too strong of a requirement. 

I think the odds of a currency name conflict are low, because I expect people work hard to avoid such name conflicts. Therefore URLs would likely be overkill as identifiers. Furthermore, if there were name conflicts in the industry, it would certainly not be our job to explain (in some dereferenced information) how to resolve those conflicts. And I agree with @tommythorsen that "...the problem of currency symbol conflict is not our job to solve."

This is why I think (for non-standard currency codes) I am most comfortable with:

 * Authors MAY a string that is NOT also an ISO code to represent a currency. This specification does not define the meaning of those strings or how they are to be interpreted by a user agent.
 * Among those values, authors MAY use a URL and MAY provide currency information to those who dereference the URL. This specification does not specify user agent behavior for these URLs.

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