W3C home > Mailing lists > Public > public-payments-wg@w3.org > March 2019

Re: Call for Consensus to Publish Two Candidate Recommendations - RESPONSE REQUESTED by 25 March 2019

From: David Ezell <dezell@conexxus.org>
Date: Fri, 15 Mar 2019 15:08:40 +0000
To: Ian Jacobs <ij@w3.org>, Web Payments Working Group <public-payments-wg@w3.org>
Message-ID: <6DAE208D-85D7-4432-87AF-9DA1F0AEEB47@conexxus.org>
Conexxus supports publication of these documents.
Thank you for all the work.

´╗┐On 3/14/19, 1:16 PM, "Ian Jacobs" <ij@w3.org> wrote:

    CAUTION: This email originated from outside of the organization.
    
    
    Dear Web Payments Working Group Participants,
    
    This is a Call for Consensus to publish the following specifications as revised Candidate Recommendations:
    
       Payment Request API
       https://raw.githack.com/w3c/payment-request/768128f2bd94e022a9810eff7e60fee7fa13db30/index.html

    
       Payment Method Identifiers
       https://raw.githack.com/w3c/payment-method-id/146c22f045185e3f4c00944d1abcaf895e8116aa/index.html

    
    We would like to thank the editors for preparing these documents.
    
    PLEASE RESPOND to the proposal by 25 March 2019 (10am ET).
    
    Note: We also anticipate publishing Basic Card [1] as a Working Group Note along with these Candidate Recommendations.
    
    For the co-Chairs,
    Ian Jacobs
    
    [1] https://www.w3.org/TR/payment-method-basic-card/

    
    =========
    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 25 March 2019 (10am ET) for the proposal, it will carry.
    
    ==========================
    CHANGES
    
    In a 5 February message we documented the primary changes to Payment Request since it was published as a Candidate Recommendation on 9 July 2018:
      https://lists.w3.org/Archives/Public/public-payments-wg/2019Feb/0003

    
    In addition to those changes we made a number of changes based on reviews that resulted from outreach to the Privacy Interest Group in February and March:
      https://lists.w3.org/Archives/Public/public-payments-wg/2019Mar/0007

    
    History of changes to Payment Request API:
      https://github.com/w3c/payment-request/commits/gh-pages

    
    Note: The "diff" file for changes to Payment Request API between July 2018 and March 2019 was too complex to be considered useful as part of the review materials.
    
    There have been only editorial changes since the 14 September 2017 Candidate Recommendation of Payment Method Identifiers.
    
    History of changes to Payment Method Identifiers:
      https://github.com/w3c/payment-method-id/commits/gh-pages

    
    ==========================
    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.
    
    * We request that any Formal Objections be limited to changes made to
      Payment Request API since the 9 July 2018 draft:
      https://www.w3.org/TR/2018/CR-payment-request-20180830/

    
    * 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/2019/Process-20190301/#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 will request approval from the W3C Director to
      publish Candidate Recommendations (including review of any Formal
      Objections).
    
    * Sam Weiler has indicated [2] that he wishes to see a new feature
      added to version 1 of Payment Request API. We are handling this
      request as a Formal Objection to discuss with the W3C Director.
    
    [2] https://github.com/w3c/payment-request/issues/842#issuecomment-469379019

    
    --
    Ian Jacobs <ij@w3.org>
    https://www.w3.org/People/Jacobs/

    Tel: +1 718 260 9447
    
    
    
    
    
    

Received on Friday, 15 March 2019 15:09:06 UTC

This archive was generated by hypermail 2.3.1 : Friday, 15 March 2019 15:09:07 UTC