- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 24 Apr 2018 11:30:12 -0500
- To: Web Payments Working Group <public-payments-wg@w3.org>
Dear Web Payments Working Group Participants, In the Candidate Recommendation of Payment Request API, we identified "currencySystem" as a feature at risk (see issue 617 [1]). This was done so that we could drop the feature from the specification in case of issues or insufficient implementation, without having to delay the advancement of the specification. To date, no browser has implemented the feature. Participants at the Singapore face-to-face meeting discussed the situation. Ripple, Facebook, Google, Airbnb, Mastercard, Mozilla, and JCB expressed support for removing the feature [2] and there were no objections. This is a call for consensus to remove the ”currencySystem” feature from Payment Request API. Removal at this time does not preclude it being added to a future version of the API. If you expressed support in Singapore, you do not need to take any action (unless you wish to revise your response). Other Working Group participants are invited to respond to this proposal by 1 May 2018 (10am ET). I have added a small FAQ to this email to address implications of removing the feature. The content for the FAQ will appear in the specification after merging the relevant pull request. For the co-Chairs, Ian Jacobs [1] https://github.com/w3c/payment-request/issues/617 [2] https://www.w3.org/2018/04/19-wpwg-minutes.html#currencySystem ========= PROPOSAL That the Web Payments Working Group drop the currencySystem feature from the Payment Request API Candidate Recommendation by adopting this pull request: https://github.com/w3c/payment-request/pull/694 (Note: Minor editorial changes to the pull request are expected and are already available in the pull request thread.) Please indicate one of the following in your response: 1. Support the proposal. 2. Request some changes, but support the proposal even if suggested changes are not taken into account. 3. Request some changes, and do not support the proposal unless the changes are taken into account. 4. Do not support the proposal (please provide rationale). 5. Support the consensus of the Web Payments Working Group. 6. Abstain. We invite you to include rationale in your response. If there is strong consensus by 1 May (10am ET) for the proposal, it will carry. ========================== FAQ Q. What currency codes does Payment Request API support? A. ISO 4217 3-letter codes. Q. How do implementations behave when checkout pages use codes not in ISO 4217? A. Current implementations of Payment Request API allow the use of well-formed currency codes that are not part of the official ISO4217 registry. If the provided code is a currency that the browser knows how to display, then an implementation will generally display the appropriate currency symbol in the user interface. When a code cannot be matched, the specification recommends browsers show a scarab symbol. Q. How will Payment Request API evolve as ISO registries evolve? A. 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. ========================== Formal Objections * If you wish your LACK of support to publish to be conveyed to the Director and reviewed, please include the phrase "FORMAL OBJECTION” in your response and be sure to include substantive arguments or rationale. The W3C Director takes Formal Objections seriously, and therefore they typically require significant time and effort to address. * Silence will be taken to mean there is no Formal Objection. * If there are Formal Objections, the Chairs plan to contact the individual(s) who made them to see whether there are changes that would address the concern and increase consensus to publish. For more information, see: https://www.w3.org/2018/Process-20180201/#Consensus -- Ian Jacobs <ij@w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447
Received on Tuesday, 24 April 2018 16:30:20 UTC