How to Get Involved with the Web Machine Learning Group
Updated
You can get involved by joining the group and contributing to its web specifications, such as WebNN and WebMCP. The site's invitation to "Join us" points to two distinct venues, and which one fits you depends on what you want to contribute: the W3C Web Machine Learning Working Group is where standards are formalized, while the Web Machine Learning Community Group is where new proposals are incubated and discussed before formal standardization. If your idea is early-stage, start in the Community Group; if you want to work on existing specifications, the Working Group is the relevant body.
What the group actually does
The Working Group standardizes Web APIs for in-device machine learning inference, working within the W3C ecosystem and using well-received Community Group incubations as its seeds. The Community Group is its sister group: it incubates new proposals and is the place where new ideas are discussed and explored before formal standardization.
The site frames the underlying goal as making machine learning a first-class web citizen — enabling efficient ML inference in the browser by combining performant numerical computation with the reach of the web.
Choose your entry point
| If you want to… | Go to | Why |
|---|---|---|
| Propose or shape a new idea | Community Group | New proposals are incubated and explored here before formal standardization |
| Contribute to existing specifications like WebNN and WebMCP | Working Group | This group standardizes the Web APIs |
| Follow how incubations become standards | Both | Community Group incubations serve as seeds for Working Group standardization |
Why contributing matters here
The benefits the site cites for in-browser inference are the same ones your contributions would support:
- Low latency — in-browser inference enables novel use cases with local media sources.
- Privacy preserving — user data stays on-device.
- High availability — no reliance on the network after initial asset caching, enabling offline use cases.
- Low cost — computing on client devices means no server farms needed.
Practical steps
- Read the site's scope statement so your proposal matches the group's focus on in-device ML inference APIs for the web.
- Decide on the venue using the table above — early ideas to the Community Group, specification work to the Working Group.
- Use the "Join us" invitation on the site to begin participating, then contribute to specifications such as WebNN and WebMCP.
- Expect iteration: ideas are discussed and explored in the Community Group before they reach formal standardization, so early feedback is part of the process rather than a detour.
The site does not publish membership requirements, meeting schedules, or contribution mechanics beyond the join invitation and the Working Group/Community Group split, so confirm those details through the join path itself.