W3C home > Mailing lists > Public > public-payments-wg@w3.org > September 2018

Re: Call for Consensus to Remove languageCode from Payment Request API - Review Requested by 20 September

From: Adam Solove <asolove@stripe.com>
Date: Mon, 10 Sep 2018 10:31:57 -0600
Message-ID: <CAOJy8x5Q3+e+t8Xe3aBF_e9ERGb-aoDrXSTeAZwiEMaJ---SgQ@mail.gmail.com>
To: Ian Jacobs <ij@w3.org>
Cc: Web Payments Working Group <public-payments-wg@w3.org>
1. Stripe support the proposal.

On Fri, Sep 7, 2018 at 6:55 AM, Ian Jacobs <ij@w3.org> wrote:

> Dear Web Payments Working Group Participants,
>
> In the Candidate Recommendation of Payment Request API, we have identified
> "languageCode" as a feature at risk (see issue 608 [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, only one browser (Chrome) has implemented the
> feature.  There is consensus among the browser vendors to remove the
> feature in favor of superior approaches that may be developed in
> coordination with the W3C Internationalization Working Group.
>
> This is a call for consensus to remove the "languageCode" feature from
> Payment Request API. Removal at this time does not preclude inclusion of
> languageCode or a similar feature in a future version of the API.
>
> In parallel, the Web Payments Working Group will continue to coordinate
> with the Internationalization Working Group and possiblyother bodies such
> as ECMA TC39.
>
> Working Group participants are invited to respond to this proposal by 20
> September 2018 (10am ET).
>
> For the co-Chairs,
> Ian Jacobs
>
> [1] https://github.com/w3c/payment-request/issues/608
>
> =========
> PROPOSAL
>
> That the Web Payments Working Group drop the languageCode feature from the
> Payment Request API Candidate Recommendation by adopting this pull request
> (possibly with minor editorial changes):
> https://github.com/w3c/payment-request/pull/765
>
> 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 20 September (10am ET) for the proposal,
> it will carry.
>
> ==========================
> 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 Monday, 10 September 2018 16:34:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:30 UTC