Re: Call for Consensus to Request Formal Review of WPWG Charter - Review Requested by 14 December

Ripple supports this proposal

On 4 December 2017 at 19:11, Steve Sommers <steve@shift4.com> wrote:

> Shift4 supports the proposal.
>
>
> Steve Sommers
> Senior Vice President, Applications Development
>
> Shift4 Corporation
> 1491 Center Crossing Road
> Las Vegas, NV  89144-7047
>
> 702.597.2480 ext. 40400
> fax 702.597.2499
> www.shift4.com
> steve@shift4.com
>
> facebook.com/shift4corp
> twitter.com/shift4corp
> linkedin.com/companies/shift4-corporation
> shift4.com/blog
>
>
> This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee you should not
> disseminate,distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. E-mail transmission cannot be
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> The sender therefore does not accept liability for any errors or omissions
> in the contents of this message, which arise as a result of e-mail
> transmission. If verification is required please request a hard-copy
> version.
>
> -----Original Message-----
> From: Ian Jacobs [mailto:ij@w3.org]
> Sent: Monday, December 4, 2017 6:22 AM
> To: Payments WG <public-payments-wg@w3.org>
> Subject: Call for Consensus to Request Formal Review of WPWG Charter -
> Review Requested by 14 December
>
> Dear Web Payments Working Group Participants,
>
> The Web Payments Working Group's charter [1] expires 31 December 2017.
> We began discussions about our revised charter in August [2] and since
> then have periodically reviewed updated drafts, including most recently
> during our TPAC face-to-face [3]. The charter has been revised based on
> TPAC discussion and subsequent review by the W3C staff.
>
> This is a call for consensus to request that the W3C Director submit a
> revised Web Payments Working Group charter for formal review by the W3C
> Membership.
>   https://w3c.github.io/webpayments/proposals/charter-2017
>
> PLEASE RESPOND to the proposal by 14 December 2017 (10am ET).
>
> NOTES:
>
>  * One goal of this review is for your organization to begin to look at
> the scope
>    section of the charter. We would like to reduce the likelihood
> organizations
>    raising scope-related concerns during the formal Advisory Committee
>    review, expected to begin in January 2018.
>
>  * The Working Group's charter will be extended until 1 March 2018 as we
>    go through the rechartering process.
>
> For the co-Chairs,
> Ian Jacobs
>
> [1] https://www.w3.org/Payments/WG/charter-201510.html
> [2] https://www.w3.org/2017/08/31-wpwg-minutes#item05
> [3] https://www.w3.org/2017/11/06-wpwg-minutes.html#item07
>
> =========
> PROPOSAL
>
> That the Web Payments Working Group request that the W3C Director submit
> this revised Web Payments Working Group charter for formal review by the
> W3C Membership:
>    https://w3c.github.io/webpayments/proposals/charter-2017
>
> Here is the specific source document:
>    https://github.com/w3c/webpayments/blob/9494ad51bd26ba3646ee913ddff412
> 00f2dbe015/proposals/charter-2017.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.
>
> We invite you to include rationale in your response.
>
> If there is strong consensus by 14 December 2017 (10am ET) for the
> proposal, it will carry.
>
> ==========================
> 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
>
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 718 260 9447
>
>
>
>
>
>