Re: AW: AW: AW: AW: EU Payment Wallet Standard(s) - Proposed W3C Community Group

Steffen, I see a recurring pattern in these replies: the use of procedural
formalism to sidestep systemic critiques. When concerns are raised that the
EU digital identity architecture is increasingly being shaped by a small
group of incumbents, the discussion is shifted from outcomes and market
effects to questions of formal jurisdiction and process.

The issue is not whether the correct procedures were followed. The issue is
whether those procedures are producing an ecosystem that is open,
competitive, and accessible to innovators of all sizes.

What many of us are concerned about is the growing concentration of
influence among large institutions and major, politically connected,
technology vendors. When standards and architectural decisions are
effectively shaped by a small circle of well-resourced actors, smaller
companies, startups, open-source projects, and individual experts face
significant barriers to meaningful participation. That ultimately reduces
competition, limits innovation, and increases dependency on a handful of
dominant players.

This is particularly troubling when decisions affecting the EU are made
through relatively closed processes with limited visibility and
participation. W3C communities, for all their imperfections, are open to
anyone willing to contribute. That openness has been one of the Web's
greatest strengths.

Europe should be promoting openness, transparency, global collaboration,
and broad participation; not creating structures that risk concentrating
power, locking out smaller voices, enabling nepotism, and entrenching the
position of a few privileged organizations. In the long run, that harms
European citizens, European innovators, and the competitiveness of the
European technology ecosystem itself.

Best regards,
Filip
https://www.linkedin.com/in/filipkolarik/


On Wed, Jun 10, 2026 at 6:58 PM Steffen Schwalm <Steffen.Schwalm@msg.group>
wrote:

> We already have those issues “US passed some laws around copyrights and
> then the companies like Netflix and RIAA members pushed DRM through the
> browser and made it less open“ – it`s called C/A Browser Forum where US
> browsers define their own standards incl. governance which they control at
> same time and so create closed market… - btw exactly one reason why Europe
> tightened the related regulation on QWAC in eIDAS…
>
>
>
> Long Story short: You complain about W3C governance and its execution but
> this is not related to European SDO as Manu and you suggested. The main
> take away from your descriptions is that standardization underpinning
> European Regulation shall be done in European SDO to exactly avoid those
> issues in W3C you described.
>
>
>
> Maybe chance to avoid those issues now with not doing any standardization
> for payment with EUDI in W3C and keep this subject in Europe where it
> belongs to.
>
>
>
> Thx and Best
>
> Steffen
>
>
>
> *Von:* Kyle Den Hartog <kyle@pryvit.tech>
> *Gesendet:* Mittwoch, 10. Juni 2026 18:34
> *An:* Steffen Schwalm <Steffen.Schwalm@msg.group>
> *Cc:* Manu Sporny <msporny@digitalbazaar.com>; Filip Kolarik <
> filip26@gmail.com>; Anders Rundgren <anders.rundgren.net@gmail.com>; W3C
> Credentials Community Group <public-credentials@w3.org>
> *Betreff:* Re: AW: AW: AW: AW: EU Payment Wallet Standard(s) - Proposed
> W3C Community Group
>
>
>
> *Caution:* This email originated from outside of the organization.
> Despite an upstream security check of attachments and links by Microsoft
> Defender for Office, a residual risk always remains. Only open attachments
> and links from known and trusted senders.
>
> You seem awfully confident about your position and are making a load
> bearing argument based on a misframing of the situation. As we all know
> standards don’t exist within a vacuum of a single SDO. Personally, I’m not
> too concerned with the decision made it’s how politics go and it’s why I’ve
> limited my time engaging on it. But I’ll call a spade a spade when I see
> it. EU co-opted the W3C process via the DMA and EIDAS and Big tech are
> going to massively benefit from this by keeping people on their platforms
> and devices. Especially when there’s high assurance cases where it
> won’t work on alternative OSes like Graphene creating a soft regulatory
> moat for their OSes.
>
>
>
> From the beginning I knew the formal objection process was Brave taking on
> the martyr role because EU was using legislation to force the
> standardization. I did spend 5 years helping build this tech so I’m fairly
> aware there’s very few customers who wanted this tech without regulatory
> requirements.
>
>
>
> On the specifics of the digital credentials API I’ve tried to engage on it
> a bit within the WG and faced a lot of the same as what was described
> previously where decisions are made by an inner circle elsewhere (OIDF or
> ARF it seems like but I’m not sure, I engage at W3C) and then digital
> credentials API exists downstream of their decisions and any suggestions
> are probably “out of scope” for the digital credentials API spec. Aka
> decided elsewhere. Numerous times suggestions I’ve made, like the browser
> deferring to the wallet rather than defining its own checks in the
> spec, were disregarded. This is because wallets aren’t specialists in the
> privacy problems of the Web Platform, but now take on that role for this
> API specifically. Suggesting the browser rather than a wallet handle
> this ended up being rejected by the WG. This is because EU WGs, don’t want
> Google and Apple to control things via the browser. They want the IDVs they
> choose to instead because it’s not “big tech”. In a few other circumstances
> my suggestions were relegated to non-normative notes rather than engaging
> with the substance of our follow up technical suggestions to attempt to
> address our own objections. So our current plan is to disable this API by
> default and then there will be accepted web compatibility issues on sites
> that rely on this API.
>
>
>
> It’s a bit of a shame our EU users are faced with this situation because
> of how the standards process has been co-opted. I hope it’s a lesson in the
> standards community that global consensus really should mean
> global consensus. I very much doubt you’d be making the same arguments
> about this if the US passed some laws around copyrights and then the
> companies like Netflix and RIAA members pushed DRM through the browser and
> made it less open. Oh wait that did happen and that was also a co-opting of
> the W3C process too. That’s still a contentious issue that affects browsers
> like Helium now. So, I don’t get why you’re applauding this because both
> situations are bad for the Web platform. I’m coming with substance and
> nuance for the actual politics not some surface level argument about “the
> process worked”.
>
>
>
> -Kyle
>
>
>
>
>
> -------- Original Message --------
> On Wednesday, 06/10/26 at 17:07 Steffen Schwalm <Steffen.Schwalm@msg.group>
> wrote:
>
> Long Story short: Decision made by W3C not European SDO – means you are
> proven wrong and Manu´s assumptions remain unproven as well. It seems more
> that W3C followed its own governance you obviously don’t like and blame
> European SDO for this.
>
>
>
> It`s bit like: You rob a bank and we blame Anders for this 😉
>
>
>
> *Von:* Kyle Den Hartog <kyle@pryvit.tech>
> *Gesendet:* Mittwoch, 10. Juni 2026 16:53
> *An:* Steffen Schwalm <Steffen.Schwalm@msg.group>
> *Cc:* Manu Sporny <msporny@digitalbazaar.com>; Filip Kolarik <
> filip26@gmail.com>; Anders Rundgren <anders.rundgren.net@gmail.com>; W3C
> Credentials Community Group <public-credentials@w3.org>
> *Betreff:* Re: AW: AW: AW: EU Payment Wallet Standard(s) - Proposed W3C
> Community Group
>
>
>
> *Caution:* This email originated from outside of the organization.
> Despite an upstream security check of attachments and links by Microsoft
> Defender for Office, a residual risk always remains. Only open attachments
> and links from known and trusted senders.
>
> As the person who directly engaged during the formal objection process
> with W3C management I’ll respectfully disagree. EU basically was going to
> shop the standard around and use custom schemes to force big tech to adopt
> digital credentials. Since big tech is also the makers of the browsers and
> operating systems they opted to keep it in W3C and do this API and OS
> changes instead. I’d personally call that co-opting the process via
> lawmaking and politics, but then again maybe that is “exactly how formal
> standards works” in the EU.
>
>
>
> -Kyle
>
>
>
> -------- Original Message --------
> On Wednesday, 06/10/26 at 16:39 Steffen Schwalm <Steffen.Schwalm@msg.group>
> wrote:
>
> Great Kyle, but W3C is no European SDO – but W3C using its governance
> recognized requirements from European experts and stakeholders – this is
> exactly how formal standardization works – that there`s escalation instance
> deciding about objections…
>
>
>
> But: The DC API is W3C Standard and the decision was made by W3C not
> European SDO.
>
>
>
> So unfortunately you made only evident that W3C formal process obviously
> works but the case is not related to European SDO – or joined W3C ETSI or
> CEN and we have overseen this great move in Europe?
>
>
>
> If you find something from actual European SDO please provide it – so that
> we can stay with facts instead of fiction.
>
>
>
> Best
>
>
>
> *Von:* Kyle Den Hartog <kyle@pryvit.tech>
> *Gesendet:* Mittwoch, 10. Juni 2026 16:31
> *An:* Steffen Schwalm <Steffen.Schwalm@msg.group>
> *Cc:* Manu Sporny <msporny@digitalbazaar.com>; Filip Kolarik <
> filip26@gmail.com>; Anders Rundgren <anders.rundgren.net@gmail.com>; W3C
> Credentials Community Group <public-credentials@w3.org>
> *Betreff:* Re: AW: AW: EU Payment Wallet Standard(s) - Proposed W3C
> Community Group
>
>
>
> *Caution:* This email originated from outside of the organization.
> Despite an upstream security check of attachments and links by Microsoft
> Defender for Office, a residual risk always remains. Only open attachments
> and links from known and trusted senders.
>
> I think I can answer that one for you Manu. Please see the Digital
> credentials API. We (Brave) objected, it was overruled. Worth a read of the
> rationale on that:
> https://www.w3.org/2025/02/council-report-fedid-dig-cred.html
>
>
>
> I’m really looking forward to having to present an age verification
> credential that’s been re-purposed into a “proof of personhood”
> credential in a few years. Those CAPTCHA checkpoints they run seem awfully
> convenient to collect said credentials and make sure it’s a human not a bot
> viewing their ads. Oh wait, I run an adblocker so I’m just having to prove
> I’m a human to browse the deep attributed Web now ;)
>
>
>
> -Kyle
>
>
>
> -------- Original Message --------
> On Wednesday, 06/10/26 at 15:40 Steffen Schwalm <Steffen.Schwalm@msg.group>
> wrote:
>
> Manu,
>
>
>
> thanks for your valueable input: Please provide an example where European
> standards fall right into the hands of large US tech companies since US
> companies not part of European standardization. The process is transparent
> here:
>
> https://portal.etsi.org/Resources/ETSI-Directives
>
>
>
> https://boss.cen.eu/reference-material/refdocs/pages/
>
>
>
> The alleged insiders are > 100 organizations in ETSI and > 100 European
> experts from European SDO - and easily to take part: Become member of ETSI
> or go to your national SDO, pay you annual fee - fine. Same as W3C 😉
>
>
>
> The fact that ETSI standards used worldwide e.g. on PKI and signatures and
> e.g. eIDAS for QTSP since 2014 for certification successfully it proves you
> wrong.
>
>
>
> Regarding credentials: The fact that e.g. W3C VCDM profiled in ETSI TS 11
> 9472-1 enabled it to be used in eIDAS.... same with ongoing standardization
> on DID, since W3C DDID Specs does not ensure any interoperability. So
> thanks to Europan SDO the W3C standards are useable in Europe 😉
>
> " Compare this to W3C, where every meeting and specification is open to
> public commentary from the beginning. The WGs are compelled to address all
> issues before transitioning to a global standard, which are available
> patent and royalty-free"
>
>
>
> --> Great, but only Members of W3C have voting rights, so pretty much
> similar to formal SDO - honestly a bit  intransparent since people can
> contribute but maybe not vote which creates Two-tier society which is
> exactly opposite of transparent open standardization - something
> ETSI/CEN,ISO solve that everybody has same voting rights.
>
>
>
> " the standards are created in secrecy and then put out into the world as
> complete products... sometimes for 'free'"
>
>
>
> --> no standard in ETSI/CEN/ISO is created in secret as WEG open for all
> who are member (similar to W3C but without 2-Tier society)
>
>
>
> So Manu: The outcome of European standardization enable W3C to be
> recognized in EUDI see W3C VCDM or DID 😉
>
>
>
> You may do what you want, but if you want to be successful it might be
> helpful to align with the SDO in charge.
>
>
>
> Best
>
> Steffen
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Manu Sporny <msporny@digitalbazaar.com>
> Gesendet: Mittwoch, 10. Juni 2026 14:35
> An: Filip Kolarik <filip26@gmail.com>
> Cc: Steffen Schwalm <Steffen.Schwalm@msg.group>; Anders Rundgren <
> anders.rundgren.net@gmail.com>; W3C Credentials Community Group <
> public-credentials@w3.org>
> Betreff: Re: AW: EU Payment Wallet Standard(s) - Proposed W3C Community
> Group
>
>
>
> Caution: This email originated from outside of the organization. Despite
> an upstream security check of attachments and links by Microsoft Defender
> for Office, a residual risk always remains. Only open attachments and links
> from known and trusted senders.
>
>
>
> On Wed, Jun 10, 2026 at 4:45 AM Filip Kolarik <filip26@gmail.com> wrote:
>
> > Your recent assertions regarding the W3C initiative and its relationship
> to European regulatory standards rely on assumptions that overlook the
> structural flaws within the European standardization ecosystem. This
> position ultimately favors institutional protectionism over open innovation.
>
>
>
> Just wanted to applaud all of what FIlip is saying. His experience has
> been my experience as well when "engaging" with the EU standardization
> initiatives for the most part. It's a bunch of insiders making decisions
> behind closed doors in a way that falls right into the hands of large US
> tech companies. The process doesn't work, and it's nearly impossible for
> non-insiders to engage.
>
>
>
> Compare this to W3C, where every meeting and specification is open to
> public commentary from the beginning. The WGs are compelled to address all
> issues before transitioning to a global standard, which are available
> patent and royalty-free. None of this "the standards are created in secrecy
> and then put out into the world as complete products... sometimes for
> 'free'".
>
>
>
> Now, I won't waste more electrons trying to convince you, Steffen; I know
> we disagree on the way the EU and EC are approaching the digital wallet
> work. It's not all corrupt, there are good people doing good work... but
> the outcome demonstrates the flaws in the EU process.
>
>
>
> I just wanted to note that Anders and Filip are not alone in their
> concerns around the very broken process that led to the ARF and EUDI... and
> the anti-competitive ecosystem that it is creating for Europe (and the US).
>
>
>
> At least Anders is trying to ensure that there is an open space for
> payment wallet discussion.
>
>
>
> -- manu
>
>
>
> PS: Also, don't confuse a W3C Community Group (anyone from the public can
> create one), with "the W3C" (a member organization). These are very
> different things, with different levels of community consensus.
>
>
>
> --
>
> Manu Sporny - https://www.linkedin.com/in/manusporny/
>
> Founder/CEO - Digital Bazaar, Inc.
>
> https://www.digitalbazaar.com/
>
>

Received on Wednesday, 10 June 2026 17:23:24 UTC