Re: Call for Consensus to Publish Secure Payment Confirmation as a First Public Working Draft - RESPONSE REQUESTED BY 19 AUGUST

Not sure if I get a vote anymore as an Invited Expert...
But I support the proposal if I do

On Thu, Aug 12, 2021 at 11:36 AM Manish Garg <manish@thebanksly.com> wrote:

>
> 1. Support the proposal.
>
> *Manish Garg*
> manish@thebanksly.com
> +44-(0)7749187729
>
> <https://www.linkedin.com/in/mgdotonl/>
> [image: logo_1.png]
> 86-90 Paul Street, London EC2A 4NE
> *https://www.thebanksly.com* <https://www.thebanksly.com>
>
>
>
> On Tue, 10 Aug 2021 at 22:19, Ian Jacobs <ij@w3.org> wrote:
>
>> Dear Web Payments Working Group Participants,
>>
>> This is a Call for Consensus to publish the following specification as a
>> First Public Working Draft:
>>
>>   Secure Payment Confirmation (SPC)
>>   https://w3c.github.io/secure-payment-confirmation/
>>
>> 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 19 August 2021 (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
>>
>> ===========================================
>> PROPOSAL
>>
>> That the Web Payments Working Group request that the W3C Director approve
>> publication of Secure Payment Confirmation 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.
>>
>> ===========================================
>> 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 these documents 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://www.w3.org/2020/Process-20200915/#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 First Public Working Draft (including review of any
>>   Formal Objections).
>>
>> --
>> Ian Jacobs <ij@w3.org>
>> https://www.w3.org/People/Jacobs/
>> Tel: +1 718 260 9447
>>
>>
>>
>>
>>
>>