- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Feb 2021 00:50:08 +0000
- To: public-i18n-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/i18n-activity: == ISO 4217 note commentary == 5. PaymentCurrencyAmount dictionary https://www.w3.org/TR/2020/CR-payment-request-20201203/#paymentcurrencyamount-dictionary > Efforts are underway at ISO to account for digital currencies, which may result in an update to the [ISO4217] registry or an entirely new registry. The community expects this will resolve ambiguities that have crept in through the use of non-standard 3-letter codes; for example, does "BTC" refer to Bitcoin or to a future Bhutan currency? At the time of publication, it remains unclear what form this evolution will take, or even the time frame in which the work will be completed. The W3C Web Payments Working Group is liaising with ISO so that, in the future, revisions to this specification remain compatible with relevant ISO registries. Currencies are occasionally issues, withdrawn, replaced, etc.: this note implies that ISO4217 is "stable" in terms of code assignment. ISO4217 *is* stable from the point of view that they never withdraw codes, leading to some countries having multiple codes for different time periods. The note here seems to be allowing for non-standard usages (which have become necessary due to non-governmental digital currencies). Perhaps make the situation clearer. Non-standard usage in particular seems like a Bad Idea. --- Instructions: This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html 1. **CREATE A PROPOSED REVIEW COMMENT BY REPLACING THE PROMPTS ABOVE THIS PARAGRAPH, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** Then ask the i18n WG to review your comment. 2. Set a label to identify the spec. This starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staffer to help. 3. After discussion with the i18n WG, raise this issue to the WG that owns the spec. Use the text above this para as the basis for that comment. 4. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue. Do NOT remove the initial '§ '. 5. Edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. 6. Remove the 'pending' label. **This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:** § link_to_issue_raised Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1045 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 February 2021 00:50:10 UTC