- From: Philipp Pfeiffenberger <philippp@google.com>
- Date: Thu, 19 May 2022 11:00:47 -0700
- To: Steven Valdez <svaldez@google.com>
- Cc: sam.jackson@socure.com, public-antifraud@w3.org
- Message-ID: <CAHSzL-S-C7Aep1OrYTYG302V9op4YPPzuBTWkZSATBzyKuhurA@mail.gmail.com>
We've reviewed this within the Chrome privacy sandbox team, and it looks good to us. On Wed, May 18, 2022 at 8:13 AM Steven Valdez <svaldez@google.com> wrote: > I think the current plan would be to adopt the existing doc as is, without > any capabilities merged into the document. Then once it is a CG work item, > we can work through capabilities as they are brought up and merge them into > the work item as the CG reviews them. > > Given that the capabilities people think will be useful is likely to be > contentious, both in the capabilities themselves and what use cases they > cover, and that process might be drawn out, trying to nail down all that > before adopting this item probably would stall out. > > On Wed, May 18, 2022 at 11:05 AM Sam Jackson <sam.jackson@socure.me> > wrote: > >> Thank you Steven. Is the goal also to complete the 'capabilities' >> assessment ahead of the next meeting or is that out of scope? You probably >> saw that Philip Pfeiffenberger has opened an issue to start compiling >> capabilities. >> >> It seems to me that we should reach agreement on which use cases will be >> supported, align those with high-value capabilities, and then map proposals >> to the use cases. >> >> During the last meeting, it seemed like 'capabilities' for use cases may >> be contentious. I recall that concerns were raised about whether certain >> capabilities should be considered widespread or high value. If we want to >> reach consensus on this topic, then it may be appropriate to hear from >> industry participants in addition to the service providers, who have tended >> to be broadly represented on prior calls. >> >> I propose that we focus the next meeting on an assessment of use cases >> and capabilities, and invite some industry participants to share their >> views. I have spoken to a number of people at financial institutions who >> have expressed interest in the proceedings of this group but who haven't >> had the bandwidth to attend on an ongoing basis. We could ask them (and >> others) to opine on which specific capabilities have provided the most >> value for stopping fraud. >> >> Best, >> Sam >> >> On Tue, May 17, 2022 at 10:11 AM Steven Valdez <svaldez@google.com> >> wrote: >> >>> Hi all, >>> >>> The chairs are restarting the adoption process for the Use Cases >>> Proposal: >>> >>> https://github.com/antifraudcg/proposals/blob/main/use-cases/use-cases.md >>> >>> Please respond with any further feedback or support for the document in >>> the next week or so (try to get your feedback in by May 27th), and the >>> chairs will determine whether there is sufficient support for the document >>> to adopt it as an official CG work item to iterate on and update as an >>> official CG item. >>> >>> --- >>> >>> Additionally after discussion amongst the chairs, the next meeting on >>> May 27th has been cancelled due to the holidays, the next meeting is >>> scheduled to be June 10th. >>> >>> -Steven >>> >>> >>> >>> >>> *This email has been scanned by Inbound Shield™.* >>> >>> >>> >> >> -- >> >> *Sam Jackson* >> Vice President, Product >> sam.jackson@socure.com >> M No. (+1-503-332-0860 <(503)%20332-0860>) >> >> Get rewarded for referring <https://www.socure.com/about/careers> good >> people! We offer a non-employee referral bonus. >> >> Follow us on: LinkedIn <https://www.linkedin.com/company/socure/>, >> Instagram <https://www.instagram.com/socure.me/?hl=en>, facebook >> <https://www.facebook.com/socure/> and Twitter >> <https://twitter.com/socureme> >> >> >> REAL IDENTITY VERIFICATION <https://www.socure.com/> >> >> NOTE: This email message and any attachments are for the sole use of the >> intended recipient(s) and may contain confidential and/or privileged >> information. Any unauthorized review, use, disclosure or distribution is >> prohibited. If you are not the intended recipient, please contact the >> sender by replying to this email, and destroy all copies of the original >> message. >> > > > -- > > Steven Valdez | Chrome Privacy Sandbox | svaldez@google.com | Cambridge, > MA >
Received on Thursday, 19 May 2022 18:01:15 UTC