For Everyone: Towards a Sustainable Future for Independent Standards Work

[LeaVerou]

Session description

The bulk of today’s web platform design is done in-house at major browser vendors. This deprives the Web of vital diversity of perspective and naturally favors work with visible short-term impact over the exploratory, bigger picture R&D needed to tackle deeper architectural issues.

For most other web stakeholders, the standards process remains an intimidating black box — so rife with misconceptions and barriers to entry that spending millions on workarounds can seem easier than fixing shortcomings at the source.

And for most other web standards designers, it is a labor of love, disincentivized by employers or as an unpaid side project.
The web platform is one of the most impactful products in the world.
Shaping its evolution requires a rare combination of deep, broad, and interdisciplinary expertise. When the few who can do it well are driven away from it in order to make ends meet, the entire Web loses.

These issues are intertwined. To make independent standards work sustainable, we need to expand the pool of available funding — and the only lasting way to do that is by helping more organizations see web platform design as a path to solving their own problems.

Session goal

This session aims to explore potential structures, governance models, and outreach strategies for a new, independent entity with the mission of addressing both issues. The goal of this new entity is not to compete with any existing organization, but to strengthen the entire ecosystem by increasing awareness and abstracting the complexity of the standards process.

Additional session chairs (Optional)

@frivoal, @mirisuzanne

Who can attend

Anyone may attend (Default)

Instructions for meeting planners (Optional)

Please avoid TAG sessions, Web Components CG sessions, CSS sessions, as well as #61 and #46

IRC channel (Optional)

#webplatform-design

Agenda for the meeting.

TBD

Scheduling conflicts to avoid (For meeting planners only)

• WebSpatial API for Spatialized HTML/CSS and Spatialized PWAs on spatial and multimodal AI devices #22
• Fixing HTML element references (IDREFs) on the Web #61
• Custom attributes for all elements #46

Links to calendar

• Wednesday, 08:30 - 09:30

Meeting materials

• Minutes

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular.

Bots and W3C TPAC breakouts organizers may update the description at any time, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C TPAC breakouts organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[LeaVerou]

How are Scheduling conflicts to avoid (For meeting planners only) determined? #22 seems unrelated