Re: Call for Consensus to Publish Secure Payment Confirmation as a Candidate Recommendation - RESPONSE REQUESTED BY 2 MAY

1. Support the proposal.

On Tue, Apr 25, 2023, 4:26 p.m. Ian Jacobs <ij@w3.org> wrote:

> Hi all,
>
> Based on a question I received I want to add what I hope is useful
> information to this CfC. Here’s a list of the non-substantive changes we’ve
> made to the specification since September 2022:
>
> * Removed the user activation requirement:
>   https://github.com/w3c/secure-payment-confirmation/pull/236
>
> * Related to that change, and based on Privacy review, SPC can only be
> called in a foreground tab:
>    https://github.com/w3c/secure-payment-confirmation/pull/238
>
> * Added an opt-out feature in the UX:
>   https://github.com/w3c/secure-payment-confirmation/pull/215
>
> * Made editorial changes based on Internationalization review.
>    https://github.com/w3c/secure-payment-confirmation/pull/232
>    https://github.com/w3c/secure-payment-confirmation/pull/234
>    https://github.com/w3c/secure-payment-confirmation/pull/229
>
> Ian
>
> > On Apr 25, 2023, at 11:57 AM, Ian Jacobs <ij@w3.org> wrote:
> >
> > Dear Web Payments Working Group Participants,
> >
> > This is a Call for Consensus to publish Secure Payment Confirmation
> (SPC) as a Candidate Recommendation:
> >
> >   https://w3c.github.io/secure-payment-confirmation/
> >   (24 April 2023 draft plus any non-substantive edits)
> >
> > PLEASE RESPOND to the proposal by 2 May 2023 (16h00 UTC).
> >
> > For example, if you support the proposal, respond to this list with "1.
> Support the proposal."
> >
> > We thank the editors Stephen McGruer and Rouslan Solomakhin for
> preparing this document.
> >
> > Congratulations to the Working Group!
> >
> > For the co-Chairs,
> > Ian Jacobs
> >
> > ----------
> > BACKGROUND
> >
> > * August 2021: W3C publishes [1] the First Public Working Draft of SPC.
> >
> > * August 2022: The Web Payments Working Group anticipates [2]
> > advancing SPC to Candidate Recommendation and initiates horizontal
> > review of the specification [3].
> >
> > * The Working Group addresses all issues raised in horizontal reviews.
> > However, before reaching a decision to advance to Candidate
> Recommendation,
> > in light of deployment feedback from Stripe and Adyen the
> > Working Group discusses [4] making two substantive changes
> > to the specification before advancing version 1 of SPC CR:
> >
> >   - Additional of an opt-out feature
> >     https://github.com/w3c/secure-payment-confirmation/issues/172
> >
> >   - Remove of a user activation requirement
> >     https://github.com/w3c/secure-payment-confirmation/issues/216
> >
> > * January 2023: The Working Group requests horizontal review of
> > these changes [5].
> >
> > * April 2023: The Working Group completes horizontal review and
> > resolves all related issues (see links from [5] and list of
> > changes in GitHub).
> >
> > [1] https://www.w3.org/blog/news/archives/9243
> > [2] https://www.w3.org/2022/09/12-wpwg-minutes.html#t08
> > [3]
> https://lists.w3.org/Archives/Public/public-payments-wg/2022Aug/0009.html
> > [4] https://www.w3.org/2022/12/08-wpwg-minutes.html
> > [5]
> https://lists.w3.org/Archives/Public/public-payments-wg/2023Jan/0000.html
> >
> > --------------------
> > ADDITIONAL RESOURCES
> >
> > * Explainer
> >
> https://github.com/w3c/secure-payment-confirmation/blob/main/explainer.md
> >
> > * Implementation report
> >
> https://wpt.fyi/results/secure-payment-confirmation?label=master&label=experimental&aligned
> >
> > --------
> > PROPOSAL
> >
> > That the Web Payments Working Group request that the W3C Director
> approve publication of Secure Payment Confirmation as a Candidate
> Recommendation.
> >
> > 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.
> >
> > ------------------------------------------------
> > CHANGES SINCE FIRST PUBLIC WORKING DRAFT (PUBLISHED 31 AUG 2021)
> >
> > For the commit history since FPWD:
> >
> https://github.com/w3c/secure-payment-confirmation/compare/ae515e2dfeb4e86a1bdc4756e36fb5f7d2487a93...main
> >
> > For the (many) changes:
> >
> https://github.com/w3c/secure-payment-confirmation/compare/ae515e2dfeb4e86a1bdc4756e36fb5f7d2487a93...main#diff-6f5a1d8263b0b0c42e2716ba5750e3652e359532647ac934c1c70086ae3cedda
> >
> > -----------------
> > 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/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 a Candidate Recommendation (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
>
>
>
>
>
>
>