- From: POUILLARD, ANNE <anne.pouillard@worldline.com>
- Date: Mon, 18 Jul 2022 12:40:55 +0000
- To: Ian Jacobs <ij@w3.org>, Web Payments Working Group <public-payments-wg@w3.org>
1. Support the proposal. -----Message d'origine----- De : Ian Jacobs <ij@w3.org> Envoyé : lundi 11 juillet 2022 15:46 À : Web Payments Working Group <public-payments-wg@w3.org> Objet : Call for Consensus to Publish Payment Request API 1.1 as a First Public Working Draft - RESPONSE REQUESTED BY 18 JULY Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Dear Web Payments Working Group Participants, This is a Call for Consensus to publish the following specification as a First Public Working Draft: Payment Request API https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fpayment-request%2F&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5G19CiCBytMKfdcxBdORnrZZCL1gcK5xVH%2BN2jumT7s%3D&reserved=0 (8 July 2022 draft plus any non-substantive edits). Expected Title: Payment Request API 1.1 Expected short name: payment-request-1.1 Publication as a First Public Working Draft does NOT indicate that the document is complete or represents Working Group consensus. PLEASE RESPOND to the proposal by 18 July 2022 (14h00 UTC). For example, if you support the proposal, respond to this list with "1. Support the proposal." We thank the editors for preparing this document. For the co-Chairs, Ian Jacobs ---------- BACKGROUND W3C published [1] Payment Request API 1.0 as a Proposed Recommendation in September 2021. Since then, W3C has been working to resolve two Formal Objections from W3C Members; see the Team Report [2] for details. At this time, a Council is evaluating the Formal Objections to determine whether Payment Request API 1.0 should advance to Recommendation or be returned to the Working Group for changes. In the meantime, the Editors have continued to update the Editor's Draft [3]. See below for information about changes since September 2021. Developers and implementers are taking interest in the new features defined in the Editor's draft. To provide them with more confidence about these features, the Chairs would like to formally publish the Editor's Draft as a new W3C Working Draft. This will also provide the group with a foundation for potential discussion at TPAC about the future of Payment Request. It is not uncommon for a Working Group to work on different revisions of a specification simultaneously (e.g., see the CSS WG). With that in mind, and because our current charter [4] anticipates enhancements to Payment Request 1.0, we seek to publish a first 1.1 draft. Note: If Payment Request API 1.0 advances to Recommendation, the Editors will determine whether it would be preferable to fold these changes into an evolving 1.0 Recommendation, or to continue to nurture a 1.1 branch. At the current time, we do not need to make that decision. [1] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2Fblog%2Fnews%2Farchives%2F9269&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=slEvLeXUzSNK6x6jSkw5tYHr76sn0C7i543pYz4e6qo%3D&reserved=0 [2] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F03%2Fprapi-fo-report.html&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ynsomHkcLB9ir%2Fy2KPuEKuI1su0yJeQCqnf%2B%2FjTC3Zw%3D&reserved=0 [3] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fpayment-request%2F&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5G19CiCBytMKfdcxBdORnrZZCL1gcK5xVH%2BN2jumT7s%3D&reserved=0 [4] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPayments%2FWG%2Fcharter-201912.html&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0ekBzfYG5UwDMNuT5mJ8UsmreNQWH93YG5ouY5hFnNM%3D&reserved=0 -------- PROPOSAL That the Web Payments Working Group request that the W3C Director approve publication of Payment Request API 1.1 as a First Public Working Draft on the Recommendation Track. 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 PROPOSED RECOMMENDATION (PUBLISHED SEP 2021) See the diff: https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F07%2Fprapi-diff-20220707.html&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Rp%2FvE8xOcs2XXQFb4sj5zW7SU5aKrcm5XFR4ab9lwHg%3D&reserved=0 Substantive changes (the primary reason to publish): * Two new definitions for both the IDL type that PaymentMethodData/data should be converted into, and for the validation steps that a payment method will perform on it. This allows payment method specs to define these in a way that is cross-linkable to the PaymentRequest specification. This is useful for Secure Payment Confirmation. This change is mostly editorial, except that it allows for arbitrary error types to be thrown during validation (previously only TypeError would be thrown). * Passing data on complete(). This is an optional feature that allows payment handler to provide some information about the nature of a completed payment. * Validate .data on construction. This is an optional feature supported in Webkit. Non-substantive changes: * Added internationalization support for human readable labels (#971) * Low-level changes related to imported concepts (e.g., whose names changed and we needed to update our reference to them). * Editorial fixes (example, cross-reference fix) ----------------- 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. Therefore, please limit any Formal Objections to issues related to the scope of this document rather than technical content where the Working Group has not yet made a decision. * 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2021%2FProcess-20211102%2F%23Consensus&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pew0II8tdfT5HS8ofpZD5kK%2FRW%2FxqqNUdINDzTlN0BM%3D&reserved=0 ---------- 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 First Public Working Draft (including review of any Formal Objections). -- Ian Jacobs <ij@w3.org> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPeople%2FJacobs%2F&data=05%7C01%7Canne.pouillard%40worldline.com%7C1c722923e2194da9984408da6343c46d%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637931439958398188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LH%2BcJneNyc72ZVlZrUZ11EP5uThhtYxLz90hgcRZmpk%3D&reserved=0 Tel: +1 917 450 8783 Worldline, Cardlink, GoPay and Santeos are registered trademarks and trade names owned by the Worldline Group. This e-mail and any documents attached are confidential and intended solely for the addressee. It may also be privileged. If you are not the intended recipient of this e-mail, you are not authorized to copy, disclose, use or retain it. Please notify the sender immediately and delete this e-mail (including any attachments) from your systems. As e-mails may be intercepted, amended or lost, they are not secure. Therefore, Worldline’s and its subsidiaries’ liability cannot be triggered for the message content. Although the Worldline Group endeavors to maintain a virus-free network, we do not warrant that this e-mail is virus-free and do not accept liability for any damages, losses or consequences resulting from any transmitted virus if any. The risks are deemed to be accepted by anyone who communicates with Worldline or its subsidiaries by e-mail.
Received on Monday, 18 July 2022 12:41:13 UTC