- From: Jeff Hodges <jdhodges@google.com>
- Date: Thu, 21 Jan 2021 15:06:55 -0800
- To: Danyao Wang <danyao@google.com>
- Cc: Ian Jacobs <ij@w3.org>, Web Payments Working Group <public-payments-wg@w3.org>
- Message-ID: <CAOt3QXsjy819FGk-v-suF=ChTgHBJQOyuOOb8jMoNeAMehbmiA@mail.gmail.com>
1. Support the proposal On Mon, Jan 18, 2021 at 3:00 PM Danyao Wang <danyao@google.com> wrote: > 1. Support the proposal > > On Mon, Jan 18, 2021 at 11:01 AM Ian Jacobs <ij@w3.org> wrote: > >> Dear Web Payments Working Group Participants, >> >> This is a Call for Consensus to publish Payment Request API as a Proposed >> Recommendation: >> >> Payment Request API >> https://w3c.github.io/payment-request/ >> (Specific GitHub snapshot [1]) >> >> If you are a Working Group participant who supports the proposal, please >> reply with an email to on this thread list that says "1. Support the >> proposal.” We prefer explicit support to silence. >> >> We would like to thank the editors for preparing these documents. >> >> PLEASE RESPOND to the proposal by 27 January 2021 (17h00 UTC). >> >> For the co-Chairs, >> Ian Jacobs >> >> [1] >> https://github.com/w3c/payment-request/tree/137af6bbfa807f449e15b454cb4d4fb81e94703c >> >> =========================================== >> PROPOSAL >> >> That the Web Payments Working Group request that the W3C Director approve >> publication of Payment Request API as a Proposed Recommendation. The >> specification has not changed since publication as a Candidate >> Recommendation [1] in December 2020. >> >> 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 27 January 2021 (17h00 UTC) for the >> proposal, it will carry. >> >> [1] https://www.w3.org/TR/2020/CR-payment-request-20201203/ >> >> =========================================== >> 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/2020/Process-20200915/#Consensus >> >> =========================================== >> NEXT STEPS >> >> * In the case where this Call for Consensus results in a decision to >> publish, the Chairs will request approval from the W3C Director to publish >> the Proposed Recommendation (including review of any Formal Objections). >> >> * See the optimistic timeline to Recommendation: >> https://github.com/w3c/payment-request/wiki/REC_2020_Plan >> >> -- >> Ian Jacobs <ij@w3.org> >> https://www.w3.org/People/Jacobs/ >> Tel: +1 718 260 9447 <(718)%20260-9447> >> >> >> >> >> >>
Received on Thursday, 21 January 2021 23:07:45 UTC