- From: Adrian Hope-Bailie <adrian@hopebailie.com>
- Date: Tue, 18 Jul 2017 09:47:49 +0200
- To: "Bhattacharjee, Manash" <Manash.Bhattacharjee@mastercard.com>
- Cc: Jason Normore <jason.normore@shopify.com>, Ian Jacobs <ij@w3.org>, Payments WG <public-payments-wg@w3.org>
- Message-ID: <CA+eFz_KU0dfY8CnDPJExjGr2MxBXh1YhrRZ=1NOSiopdJSp5=A@mail.gmail.com>
Ripple supports the proposal On 18 July 2017 at 04:35, Bhattacharjee, Manash < Manash.Bhattacharjee@mastercard.com> wrote: > Mastercard supports the proposal. > > Sent from my iPhone > > On Jul 17, 2017, at 7:22 PM, Jason Normore <jason.normore@shopify.com> > wrote: > > Shopify supports the proposal. > > > On Mon, Jul 17, 2017 at 2:37 PM Ian Jacobs <ij@w3.org> wrote: > >> Dear Web Payments Working Group Participants, >> >> This is a Call for Consensus to publish the following specifications as >> Candidate Recommendations: >> >> Payment Request API >> https://rawgit.com/w3c/browser-payment-api/a7e1bdab27ec6ae78d56c32ec0d20b >> a3df03f387/index.html?specStatus=CR&crEnd=2017-10- >> 31&implementationReportURI=https://w3.org/tbc >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_browser-2Dpayment-2Dapi_a7e1bdab27ec6ae78d56c32ec0d20ba3df03f387_index.html-3FspecStatus-3DCR-26crEnd-3D2017-2D10-2D31-26implementationReportURI-3Dhttps-3A__w3.org_tbc&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=a-_0AH3qf4KadRu302oA_FadLKgkNlHY2pqBPoODxTY&e=> >> >> Payment Method Identifiers >> https://rawgit.com/w3c/webpayments-method-identifiers/ >> cbaf864de1d46d93ce60e34b7b3cd643073243ae/index.html? >> specStatus=CR&crEnd=2017-10-31&implementationReportURI=https://w3.org/tbc >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_webpayments-2Dmethod-2Didentifiers_cbaf864de1d46d93ce60e34b7b3cd643073243ae_index.html-3FspecStatus-3DCR-26crEnd-3D2017-2D10-2D31-26implementationReportURI-3Dhttps-3A__w3.org_tbc&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=L7xOMoTDXgvbXbAe0UfpCKDvGseiT0SJegRWup2_aYE&e=> >> >> We would like to thank the editors for preparing these documents. >> >> PLEASE RESPOND to the proposal by 26 July 2017 (10am ET). >> >> For the co-Chairs, >> Ian Jacobs >> >> ========= >> PROPOSAL >> >> That the Web Payments Working Group request that the W3C Director approve >> publication of Payment Request API and Payment Method Identifiers as >> Candidate Recommendations. >> >> 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 26 July 2017 (10am ET) for the >> proposal, it will carry. >> >> ========================== >> About Candidate Rec Status >> >> * A W3C Candidate Recommendation is a document that satisfies the >> Working Group's technical requirements, and has already received >> wide review. W3C publishes a Candidate Recommendation to: >> >> - signal to the wider community that it is time to do a final review. >> - gather implementation experience. >> - begin formal review by the Advisory Committee, who may recommend >> that the document be published as a W3C Recommendation, returned to >> the Working Group for further work, or abandoned. >> - Provide an exclusion opportunity per the W3C Patent Policy. >> >> For more information, see: >> https://www.w3.org/2017/Process-20170301/#maturity-levels >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2017_Process-2D20170301_-23maturity-2Dlevels&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=6--HL6FUx5g-5ctGs4qd4HHEGdZ2Msnq4u7aLPyFeWE&e=> >> >> ========================== >> 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/2017/Process-20170301/#Consensus >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2017_Process-2D20170301_-23Consensus&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=Z9Q19BwhtQXzLL_avE3A1ECIqkJatLSS_fp6pc-QZ0c&e=> >> >> =========================== >> Transition Request Following a Working Group Decision to Publish >> >> * In case of a decision to publish, the Chairs will request approval >> from the W3C Director to publish Candidate Recommendations >> (including review of any Formal Objections). >> >> * A Candidate Recommendation transition request to the Director will >> provide information >> required by the W3C Process: >> https://www.w3.org/2017/Process-20170301/#candidate-rec >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2017_Process-2D20170301_-23candidate-2Drec&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=Xbqxy_PhFeafpzctWaCyyAJmFtjBkJDlg6tErQ1p5G0&e=> >> >> * The Editors are tracking the required information: >> https://github.com/w3c/browser-payment-api/issues/520 >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_browser-2Dpayment-2Dapi_issues_520&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=2BlJQZO3Gfx23ur4Y1-jMuX5Tv0iclsoZByTxgYOvrM&e=> >> >> For more information about transition requests, see: >> https://www.w3.org/Guide/transitions?profile=CR&cr=new >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_Guide_transitions-3Fprofile-3DCR-26cr-3Dnew&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=RDBWIVJTPt4zc9cYsvnCYcSRrWuF3M_HF2r9ZzgrKsg&e=> >> >> -- >> Ian Jacobs <ij@w3.org> >> https://www.w3.org/People/Jacobs/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_People_Jacobs_&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=Z0alkbJlqXx-EgDxs_yyrgF_HH9fdr8jSi-zTeZfBYk&s=-wG95Qi9wDY76OkGRqvBxUTzbZV9hzQfumx8Hv7cThk&e=> >> Tel: +1 718 260 9447 <(718)%20260-9447> >> >> >> >> >> >> CONFIDENTIALITY NOTICE This e-mail message and any attachments are only > for the use of the intended recipient and may contain information that is > privileged, confidential or exempt from disclosure under applicable law. If > you are not the intended recipient, any disclosure, distribution or other > use of this e-mail message or attachments is prohibited. If you have > received this e-mail message in error, please delete and notify the sender > immediately. Thank you. >
Received on Tuesday, 18 July 2017 07:48:17 UTC