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

* I think there is agreement this group should not be specifying how to display non-standard currencies.
* I think it's fine for people to provide hints to other people.
* The question is whether there needs to be a standard way to say "Here are some hints!". My proposal is that we do not need a standard way, but that we not prevent people from doing so. Thus, people MAY use URIs that could identify display hints (or anything else). But that in this version of the standard, we do not require conforming user agents to do anything with that data, and that formally we say that it is undefined. (This way, in the future, we can further refine the semantics of the data if we see that it is useful to do so based on experience.)
* My reasons for why I don't think that we need to are:
  - First, I hope that there won't be a lot of non-standard currencies, at least not for long. So in general I hope this is a small set of cases.
  - Second, unless there are actual display standards that people would point to, then there's not a lot of interoperability to be gained by pointing people at a bunch of different ways to do things.
 - Third, it is not clear to me that browsers would do anything with this information unless they have a lot more knowledge about what they will find.

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