W3C home > Mailing lists > Public > public-payments-wg@w3.org > November 2017

Call for Consensus to Publish a Group Note- RESPONSE REQUESTED by 29 November 2017

From: Ian Jacobs <ij@w3.org>
Date: Wed, 15 Nov 2017 15:33:50 -0600
Message-Id: <113C5E25-184D-47E5-8B53-846F1B7E702D@w3.org>
To: Payments WG <public-payments-wg@w3.org>
Dear Web Payments Working Group Participants,

Based on consensus at our November face-to-face meeting [1], this is a Call for Consensus 
to publish the following specification as a Group Note rather than advancing it to Recommendation

  Web Payments HTTP API 1.0

There was also consensus to:
  1) keep in-scope for our next charter a payment request message structure for out-of-browser payments. 
  2) add a liaison to the IETF’s HTTP WG for discussion of HTTP-initiated payment requests.

We have not yet updated the draft charter [2] but expect to do so as soon as time permits.

PLEASE RESPOND to the proposal by 29 November 2017 (10am ET).

For the co-Chairs,
Ian Jacobs

[1] https://www.w3.org/2017/11/06-wpwg-minutes#item07
[2] https://w3c.github.io/webpayments/proposals/charter-2017


That the Web Payments Working Group request that the W3C Director approve 
publication of Web Payments HTTP API 1.0 as a Group Note.

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 29 November 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

* 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:

Ian Jacobs <ij@w3.org>
Tel: +1 718 260 9447
Received on Wednesday, 15 November 2017 21:33:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:27 UTC