W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2022

Extension [Re: Call for Consensus to Publish Payment Request API and Payment Method Identifiers as Recommendations - reply requested before 11 January 2022]

From: Ian Jacobs <ij@w3.org>
Date: Thu, 6 Jan 2022 18:45:05 -0600
Message-Id: <30D99307-20F3-466C-BB77-EC5EDADF954E@w3.org>
To: Web Payments Working Group <public-payments-wg@w3.org>
Dear Web Payments Working Group,

We have scheduled an extra meeting on 13 January [1] related to this topic. We are therefore
extending the CfC to 14 January at 17h00 UTC.

for the co-Chairs,
Ian Jacobs


[1] https://lists.w3.org/Archives/Public/public-payments-wg/2022Jan/0002.html

> On Jan 4, 2022, at 8:04 AM, Ian Jacobs <ij@w3.org> wrote:
> 
> Dear Web Payments Working Group Participants,
> 
> This is a Call for Consensus to publish the following specifications as W3C Recommendations:
> 
>  Payment Request API
>  https://w3c.github.io/payment-request/
> 
>  Payment Method Identifiers
>  https://w3c.github.io/payment-method-id/
> 
> We would like to thank the editors for preparing these documents.
> 
> PLEASE RESPOND to the proposal by 11 January 2022 (17h00 UTC).
> 
> For the co-Chairs,
> Ian Jacobs
> 
> ===========================================
> BACKGROUND
> 
> On 30 September 2021 the Director invited W3C Member review of
> Proposed Recommendations of Payment Request API and Payment Method
> Identifier. The review resulted in two Formal Objections to Payment
> Request. The Editors made some non-substantive changes to the
> specification to satisfy aspects of one of the Formal Objections (see
> below).
> 
> The Editors prepared a public record of the Formal Objections:
> 
>  Advisory Committee Review of Payment Request API and
>  Payment Method Identifiers 
>  https://www.w3.org/2021/12/prapi-objs.html
> 
> We ask that the Working Group review the document and annotations
> regarding the Formal Objections. This is a proposal to request that
> the Director advance the specifications to Recommendation (per W3C
> Process [1]).
> 
> [1] https://www.w3.org/2021/Process-20211102/#transition-reqs
> 
> ===========================================
> CHANGES TO PAYMENT REQUEST API
> (Since the 30 September 2021 Proposed Recommendation)
> 
> * Changes to address aspects of one Formal Objection:
>  https://github.com/w3c/payment-request/pull/978
> 
> * Informative changes to satisfy concerns raised by the
>  Internationalization Working Group.
>  https://github.com/w3c/payment-request/pull/971
> 
> * An informative change due to a change in terminology in the 
>  URL specification:
>  https://github.com/w3c/payment-request/issues/969
> 
> * A small number of editorial changes to fix bugs.
> 
> For the full commit history, see:
> https://github.com/w3c/payment-request/commits/gh-pages
> 
> ===========================================
> PROPOSAL
> 
> That the Web Payments Working Group request that the W3C Director override the two Formal Objections and approve publication of Payment Request API and Payment Method Identifiers as Recommendations.
> 
> Please indicate one of the following in your response:
> 
> 1. Support the proposal.
> 
> 2. Do not support the proposal (please provide rationale).
> 
> 3. Support the consensus of the Web Payments Working Group.
> 
> 4. Abstain.
> 
> Rationale welcome in your response.
> 
> If there is consensus by 11 January 2022 (17h00 UTC) 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 new 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/2021/Process-20211102/#Consensus
> 
> ===========================================
> NEXT STEPS
> Transition Request Following a Working Group Decision to Publish
> 
> * In the case where this Call for Consensus results in a decision to
>  publish, the Chairs plan to request approval from the W3C Director
>  to publish Recommendations (including review of any Formal
>  Objections).
> 
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 917 450 8783
> 
> 
> 
> 
> 
> 

--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 917 450 8783
Received on Friday, 7 January 2022 00:45:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 7 January 2022 00:45:09 UTC