Re: [Minutes] 13 January WPWG meeting on Criteo review

Hi,

Language such as “protection of user, for reasons such as security or privacy, but not self-preferencing business interests of the implementer." would be ok fur us. It tackles our competition concern and does not include an exhaustive list of dos/donts.

Lionel




From: Ian Jacobs <ij@w3.org>
Date: Thursday, 13 January 2022 at 21:40
To: Lionel Basdevant <l.basdevant@criteo.com>
Cc: Web payments WG Public <public-payments-wg@w3.org>, Joshua Koran <j.koran@criteo.com>, Wendy Seltzer <wseltzer@w3.org>, Philippe Le Hegaret <plh@w3.org>
Subject: Re: [Minutes] 13 January WPWG meeting on Criteo review
Thank you, Lionel.

I heard the following on today’s call:

* Language such as “protection of user security or privacy” would address your concern, but would likely be over-constraining from an implementer perspective.
* Language such as “protection of the user” (or similar) might be acceptable from an implementer perspective, but I think I heard would not satisfy Criteo’s concerns.

Do you have any suggestions for verbiage that is “in between” those two?

I am dubious that we will get there by growing the enumeration, for example: "for reasons of security, privacy, performance, resource consumption,  …”

I did not hear much support on the call to address the concern with references in the specification to anti-competitive behaviors or antitrust guidance.

Ian

> On Jan 13, 2022, at 2:23 PM, Lionel Basdevant <l.basdevant@criteo.com> wrote:
>
> Hi,
>
> Thanks to all who participated in today’s call.
>
> As discussed, we think that there is some open-ended language [1] in the Payment Request API proposal that could be used by an implementer to justify preferencing one or several payment solutions, for its own interests, and we think this should be addressed.
>
> To address this concern, we’ve proposed to add references to competition laws and/or the W3C Antitrust and Competition Guidance [2]. During the call, we suggested an alternate approach which would be to bound the open-ended language by further limiting it only to the “protection of user security or privacy”.
>
> We are open to both possibilities or any other suggestion that could address this concern.
>
> We wanted to also clarify for those not on the call some of the misunderstandings of the points we raised:
> We do not mean for implementers of the spec to become experts in regional laws, nor for the W3C to police whether the content of the spec or the implementersviolate these laws. Instead, our concern is focused on ensuring the spec itself abides by existing W3C policies.
>
> We’ll be raising this concern in the Jan 14 Call for Consensus, but we hope that a common agreement can be found in advance. If not, we hope today’s conversation or a summary of the three clarifications above can be sent to help in the broader W3C review process.
>
> Best,
> Lionel
>
> [1] In paragraphs 3.3.6, 3.3.12, and 3.3.18 in https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2F2021%2FPR-payment-request-20210930%2F%23show-method&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=8rsR4rBoT5P5mt4z3gcHO70LvH9OQR5ae1HEkz2tWeY%3D&amp;reserved=0
> [2] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2021%2F12%2Fprapi-objs.html%23criteo&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=VQNM5y%2Fv865FrnaI9GoCxn0KDPnk64uzUaY5%2B%2FAGyyo%3D&amp;reserved=0
>
>
> From: Ian Jacobs <ij@w3.org>
> Date: Thursday, 13 January 2022 at 18:37
> To: Web payments WG Public <public-payments-wg@w3.org>
> Cc: Lionel Basdevant <l.basdevant@criteo.com>, Joshua Koran <j.koran@criteo.com>, Wendy Seltzer <wseltzer@w3.org>, Philippe Le Hegaret <plh@w3.org>
> Subject: [Minutes] 13 January WPWG meeting on Criteo review
>
> Dear Web Payments Working Group,
>
> Here are the minutes from today’s call about the Criteo Formal Objection:
>   https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F01%2F13-wpwg-minutes&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=%2Fb4QOmIUtQsELhgWi4KcVm9pEBsrsjUtVTzWRckdflo%3D&amp;reserved=0
>
> Thank you to our Criteo colleagues and to everyone who participated.
>
> Please review the discussion before responding to the call for consensus [1] to advance
> Payment Request and Payment Method Identifiers to Recommendation; that CfC is open
> to 17h00 UTC on 14 January.
>
> Thank you,
>
> for the co-Chairs,
> Ian
>
> [1] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-payments-wg%2F2022Jan%2F0000.html&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=8s3iN0%2BAYcmVJY4%2FRCoBR5awi0NRGzzMcqBTD6r1qVc%3D&amp;reserved=0
> [2] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-payments-wg%2F2022Jan%2F0003.html&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=JFqVijCO8rN2SuVw9KhplgixTe8O%2BA6ezZUnRnOnsaM%3D&amp;reserved=0
> --
> Ian Jacobs <ij@w3.org>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPeople%2FJacobs%2F&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=XszJ%2FmzskFbkaM%2BxkhtIjCnBbEB6u1ktkqTkaLPN58w%3D&amp;reserved=0
> Tel: +1 917 450 8783
>
>
>
>
>

--
Ian Jacobs <ij@w3.org>
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPeople%2FJacobs%2F&amp;data=04%7C01%7Cl.basdevant%40criteo.com%7C28712a9a0ce34586f61908d9d6d4de4c%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637777032019250119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=XszJ%2FmzskFbkaM%2BxkhtIjCnBbEB6u1ktkqTkaLPN58w%3D&amp;reserved=0
Tel: +1 917 450 8783