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: Elizabeth Koumpan <ekoumpan@ca.ibm.com>
Date: Fri, 15 Mar 2019 17:12:02 -0500
To: Ian Jacobs <ij@w3.org>
Cc: Web Payments Working Group <public-payments-wg@w3.org>
Message-Id: <OF16DA7121.242B703C-ON852583BE.00795F78-852583BE.0079F33E@notes.na.collabserv.com>
IBM - I support the proposal ( reviewed payment request  API; payment 
method identifiers)



Best Regards,

Elizabeth (E.) Koumpan
Executive IT Architect, Data and AI Leader
IBM - First Data Corp Account
Academy of Technology Member
IBM Global Markets

Phone: 1-416-478-8211 | Mobile: 1-416-817-9393
E-mail: ekoumpan@ca.ibm.com
"Learn from yesterday, live for today, hope for tomorrow. The important 
thing is to not stop questioning." - Albert Einstein, Relativity. The 
Special and the General Theory



3600 Steeles Ave East
Markham, ON L3R 9Z7
Canada





From:   Ian Jacobs <ij@w3.org>
To:     Web Payments Working Group <public-payments-wg@w3.org>
Date:   2019/03/14 01:16 PM
Subject:        Call for Consensus to Publish Two Candidate 
Recommendations -  RESPONSE REQUESTED by 25 March 2019



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://urldefense.proofpoint.com/v2/url?u=https-3A__raw.githack.com_w3c_payment-2Drequest_768128f2bd94e022a9810eff7e60fee7fa13db30_index.html&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=CJSyojfP8NJiscVaWwnSCl0H6daRS4YmQ-EZZwqUVa8&e=


   Payment Method Identifiers
   
https://urldefense.proofpoint.com/v2/url?u=https-3A__raw.githack.com_w3c_payment-2Dmethod-2Did_146c22f045185e3f4c00944d1abcaf895e8116aa_index.html&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=KnK95XKzn6W1iJhHS6a8ToeTFATPbXtxa2A0KZ-sYYQ&e=


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://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_payment-2Dmethod-2Dbasic-2Dcard_&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=VL5gjaOFv4oaSGRkrcZbofcH9Qd8avc39MzS_iUb3SM&e=


=========
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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Public_public-2Dpayments-2Dwg_2019Feb_0003&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=dZX0umMK-cAtw9Y1InFsvCxWhCHdOmZi9uVoTH1Fe8g&e=


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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Public_public-2Dpayments-2Dwg_2019Mar_0007&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=vZncXCFBdDgfKSioEjvWF9iElGa7htQv25-A8L3Kco4&e=


History of changes to Payment Request API:
  
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_payment-2Drequest_commits_gh-2Dpages&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=A49Zu3D5eYJWvHseVSfkf9rE8-Wd3pDlkU0LcoT5LP4&e=


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://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_payment-2Dmethod-2Did_commits_gh-2Dpages&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=jQ1JYKYAsp5jonA4m2tRq9Fv8h4ajykjIXt2chssldo&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.

* We request that any Formal Objections be limited to changes made to
  Payment Request API since the 9 July 2018 draft:
  
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_2018_CR-2Dpayment-2Drequest-2D20180830_&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=k_ickvxgxsV8UBVfhzVGT7_pocnk58i2iayLws6ojE0&e=


* 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2019_Process-2D20190301_-23Consensus&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=DRmG69Fz7ICg71SIkdkoVIpnD8wHVWyCxV0Fs1rzgOQ&e=


===========================
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://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_payment-2Drequest_issues_842-23issuecomment-2D469379019&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=NLc2OLcSVWKu-kv5HEANVPSB-maB-dXZPJALozyrwm0&e=


--
Ian Jacobs <ij@w3.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_People_Jacobs_&d=DwIFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=tXNa9GhuTHdV-D0t1LlEZQq-pzCYTcEA5U5MgO3IzMk&m=UqVY7swJ4xw7GmtlhKbf2TmR9PCVNBrTQuf7lEONiXY&s=91KGpZ1GazAfD-mT0MYz2L4jBZ6-lbA9BRdRC4qRJ4M&e=

Tel: +1 718 260 9447
Received on Friday, 15 March 2019 22:23:17 UTC

This archive was generated by hypermail 2.3.1 : Friday, 15 March 2019 22:23:17 UTC