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

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

From: David Benoit <benoit@withreach.com>
Date: Mon, 5 Nov 2018 12:25:21 -0500
Message-ID: <CAHUP1ksMuSNziQFEDQ6+v08XFLoEJWz-FDymg=+4=A_i-jcJNg@mail.gmail.com>
To: Web Payments Working Group <public-payments-wg@w3.org>
1. Reach supports the proposal.

On Mon, Nov 5, 2018 at 12:21 PM, Rouslan Solomakhin <rouslan@google.com>
wrote:

> 1. Google supports the proposal.
>
> On Mon, Nov 5, 2018 at 11:41 AM Krystian Czesak <krystian@shopify.com>
> wrote:
>
>> 1. Shopify supports the proposal.
>>
>> On Mon, Nov 5, 2018 at 9:57 AM Ian Jacobs <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>
>>> https://www.w3.org/People/Jacobs/
>>> Tel: +1 718 260 9447 <(718)%20260-9447>
>>>
>>>
>>>
>>>
>>>
>>> --
>>
>> Krystian
>>
>


-- 

David Benoit

*Chief Technology Officer*

benoit@withreach.com | +1 514 701 0419
------------------------------
You are receiving this email because you opted in and consented to
receiving information from Reach. If you would rather not receive this type
of communication please email compliance@withreach.com to unsubscribe.
Received on Monday, 5 November 2018 17:25:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 5 November 2018 17:25:45 UTC