RE: Call for Consensus to Remove supportedTypes from Basic Card - Review Requested by 15 November

NACHA supports this proposal.

Best Regards,
Luis

From: Michel Weksler [mailto:michel.weksler@airbnb.com]
Sent: Tuesday, November 6, 2018 2:14 PM
To: Ian Jacobs <ij@w3.org>
Cc: Payments WG <public-payments-wg@w3.org>
Subject: Re: Call for Consensus to Remove supportedTypes from Basic Card - Review Requested by 15 November

1. Airbnb supports this proposal.

- Michel


On Mon, Nov 5, 2018 at 6:57 AM Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> wrote:
Dear Web Payments Working Group Participants,

During TPAC we discussed [1] the removal of the “supportedTypes" feature from the Basic Card specification [2] due to the implementation challenge of consistently determining card type using available databases. The strong consensus during TPAC was to remove the feature.

This is a call for consensus to remove "supportedTypes" from Basic Card. Removal at this time does not preclude it being added to a future version of the specification.

Working Group participants are invited to respond to this proposal by 15 November 2018 (10am ET).

For the co-Chairs,
Ian Jacobs

[1] https://www.w3.org/2018/10/22-wpwg-minutes#item03

[2] https://w3c.github.io/payment-method-basic-card/


=========
PROPOSAL

That the Web Payments Working Group drop the supportedTypes feature from the Basic Card specification by adopting this pull request (possibly with minor editorial changes):
 https://github.com/w3c/payment-method-basic-card/pull/62


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 15 November 2018 (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/2018/Process-20180201/#Consensus


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

Tel: +1 718 260 9447







----------------------------

Are you preparing for the October AAP exam? Getting ready for ACH audit season? Take advantage of discounts now available for the 2018 NACHA Operating Rules & Guidelines products and product bundles. View our Special Offers at https://www.nacha.org/estore/category/special-offers.


This message is intended for use by the addressee only and may contain privileged and confidential information. If you are not the intended recipient, dissemination of this communication is prohibited. If you have received this communication in error, please delete all copies of the message and attachments and notify the sender immediately.

----------------------------