Re: [w3c/payment-request] remove currencySystem member (#694)

@marcoscaceres, @adrianhopebailie,

Here's what I learned from my conversation with our ISO 4217 colleagues:

 * There will be a registry for non-fiat digital currencies (which they may call "digital tokens" so as not to clash with the definition of "currency" in ISO 4217)
 * These codes most likely not be 3-letter strings (due to name conflicts and scarcity).
 * It is possible (but not known for sure) that they will be 4-letter strings.
 * The time frame for the specification and registry is not known, but a guess is "1 year from now."

I don't currently have a proposal, but:

 * I am hearing people want to be able to use non-4217 codes with PR API.
 * I assume people want to avoid name conflicts (e.g., does BTC refer to Bitcoin or
   to a Bhutan currency according to the 4217 naming convention?) 
 * This suggests some naming convention could help the browser recognize that someone has intentionally provided a non-standard code. 
 *  If ISO is likely (but not guaranteed) to use a letter-based code system, would it be appropriate for authors that wish to specify a non-4217 code (or other future ISO registry) to use a non-letter prefix (e.g., "-")? Would this enable the browser to help the user recognize "potential error" from "seeming intentional use of a non-standard code"?
 * Should there be consistent display guidance to implementations for non-standard codes? (e.g.,
   if the merchant-provide code is -BTC, display "BTC")? Or should the browser be free to show other symbols?
 * How are other errors handled (e.g., a string of 47 characters)?

I think we should add an informative note to the specification that we are liaising with ISO regarding updates to 4217.

Ian

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/694#issuecomment-378758195