Re: Call for Consensus to Publish Payment Request API as Candidate Recommendations-- reply requested before 31 July 2024

1. Support the proposal.

Thanks Ian and Marcos for your hard work on this!

On Fri, Jul 12, 2024, 12:00 p.m. Ian Jacobs <ij@w3.org> wrote:

> Dear Web Payments Working Group Participants,
>
> This is a Call for Consensus to republish Payment Request API as Candidate
> Recommendations to re-incorporate address features. See below for more
> details about the specification and how to respond to this Call for
> Consensus.
>
> We would like to thank the editors for preparing these documents.
>
> PLEASE RESPOND to the proposal by 31 July (17h00 UTC).
>
> For the co-Chairs,
> Ian Jacobs
>
> ===========================================
> BACKGROUND
>
> Payment Request API was published as a Recommendation on 8 September 2022
> [1]. As part of that journey the Working Group removed some features [2]
> related to addresses (shipping and billing) in response to feedback
> received during privacy and internationalization reviews. However, both
> Chromium and Webkit browsers had already shipped with support for the
> address features and, several years later, they continue to support those
> features. The browser implementers have requested that we re-align the
> specification with implementations and endeavor to resolve any previously
> raised issues.
>
> In February 2024 we announced [3] a plan to republish Payment Request as a
> Candidate Recommendation in order to re-introduce the address features and
> to make a small number of changes introduced in drafts since September 2022.
>
> [1] https://www.w3.org/TR/payment-request/
> [2] https://github.com/w3c/payment-request/pull/996
> [3]
> https://lists.w3.org/Archives/Public/public-payments-wg/2024Feb/0004.html
>
> ===========================================
> THE PLAN
>
> We plan to request publication of two Candidate Recommendations in quick
> succession (for process reasons):
>
> * A Candidate Recommendation Snapshot [4], consisting exclusively of the
> text of the 8 September 2022 Recommendation.
>
> * A Candidate Recommendation Draft [5] to reintroduce features related to
> addresses and add back other changes that have been made since publication
> of the Recommendation (see below for more details about changes).
>
> Following these publications, we plan to restart discussions around the
> features that were removed before publication of the Recommendation. We
> have already re-opened relevant issues [6] raised through privacy and
> internationalization reviews. We will then follow the usual W3C Process to
> work through those issues with the Privacy Interest Group and
> Internationalization Working Group before requesting to advance again to
> Proposed Recommendation.
>
> [4] https://www.w3.org/2023/Process-20231103/#publishing-crrs
> [5] https://www.w3.org/2023/Process-20231103/#publishing-crud
> [6] https://github.com/w3c/payment-request/issues/
>
> ===========================================
> CHANGES BETWEEN CR SNAPSHOT AND CR DRAFT
>
> See diff:
> https://www.w3.org/2024/07/prapi/diff-20240710.html
>
> Summary of change:
>
> * Re-introduce addresses. Some of the material has been moved to another
> specification --Contact Picker API [7]-- because standardized addresses are
> useful on the Web beyond payments. The updated Payment Request API retains
> much of the original text related to addresses, but also includes some
> references to Contact Picker API.
>
> * Changes related to user activation.
> https://github.com/w3c/payment-request/pull/1009
>
> * Editorial fixes (e.g., due to changes in referenced specifications) and
> a bug fix (related to show() only being callable in a foreground tab).
>
> For the full commit history, see:
> https://github.com/w3c/payment-request/commits/gh-pages
>
> [7] https://w3c.github.io/contact-picker/
>
> ===========================================
> PROPOSAL
>
> That the Web Payments Working Group request approval for publication of
> Payment Request API as a Candidate Recommendation Snapshot followed by a
> Candidate Recommendation Draft.
>
> Candidate Recommendation Snapshot:
> https://www.w3.org/2024/07/prapi/CR-payment-request-20240710.html
>
> Candidate Recommendation Draft:
> https://www.w3.org/2024/07/prapi/CRD-payment-request-20240710.html
>
> 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.
>
> If there is strong consensus by 31 July (17h00 UTC) for the proposal, it
> will carry.
>
> ===========================================
> FORMAL OBJECTIONS
>
> * If you wish your LACK of support to publish to be conveyed and reviewed,
> please include the phrase "FORMAL OBJECTION" in your response and be sure
> to include substantive arguments or rationale. W3C 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/2023/Process-20231103/#registering-objections
>
> ===========================================
> 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 to publish Candidate
> Recommendations (including review of any Formal Objections).
>
>  --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 917 450 8783
>
>
>
>
>
>
>