Fosstodon

Tantek ÇelikI’m happy to announce that something I and others have worked on very hard for the past few years has been published by the W3C Advisory Board (AB) and sent to the W3C Advisory Committee (AC) for a vote to make it official: Vision for W3C: <a class="" href="https://www.w3.org/TR/2025/NOTE-w3c-vision-20250402/" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/TR/2025/NOTE-w3c-vision-20250402/</a> Official announcement: <a class="" href="https://www.w3.org/news/2025/proposal-to-endorse-vision-for-w3c-as-a-w3c-statement/" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/news/2025/proposal-to-endorse-vision-for-w3c-as-a-w3c-statement/</a> If your company is a W3C Member<a href="https://tantek.com/2025/100/t1/vision-for-w3c-please-vote#t5bU1_note-1" rel="nofollow noopener noreferrer" target="_blank">¹</a>, please ask your Advisory Committee Representative<a href="https://tantek.com/2025/100/t1/vision-for-w3c-please-vote#t5bU1_note-2" rel="nofollow noopener noreferrer" target="_blank">²</a> to vote to support publication of the Vision for W3C as an official W3C Statement: <a class="" href="https://www.w3.org/wbs/33280/Vision2025/" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/wbs/33280/Vision2025/</a> (W3C Member-only link) Thank you for your support. <a class="" href="https://indieweb.social/tags/W3CVision" rel="nofollow noopener noreferrer" target="_blank">#W3CVision</a> <a class="" href="https://indieweb.social/tags/Vision" rel="nofollow noopener noreferrer" target="_blank">#Vision</a> <a class="" href="https://indieweb.social/tags/VisionForW3C" rel="nofollow noopener noreferrer" target="_blank">#VisionForW3C</a> <a class="" href="https://indieweb.social/tags/W3C" rel="nofollow noopener noreferrer" target="_blank">#W3C</a> (<a class="" href="https://w3c.social/@w3c" rel="nofollow noopener noreferrer" target="_blank">@w3c@w3c.social</a>) <a class="" href="https://indieweb.social/tags/W3CAB" rel="nofollow noopener noreferrer" target="_blank">#W3CAB</a> (<a class="" href="https://w3c.social/@ab" rel="nofollow noopener noreferrer" target="_blank">@ab@w3c.social</a>) <a href="https://tantek.com/2025/100/t1/vision-for-w3c-please-vote#t5bU1_ref-1" rel="nofollow noopener noreferrer" target="_blank">¹</a> <a class="" href="https://www.w3.org/membership/list/" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/membership/list/</a> <a href="https://tantek.com/2025/100/t1/vision-for-w3c-please-vote#t5bU1_ref-2" rel="nofollow noopener noreferrer" target="_blank">²</a> <a class="" href="https://www.w3.org/Member/ACList" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/Member/ACList</a> (W3C Member-only link)

Jeffrey Yasskin<a href="https://status.kinlan.me/@paul" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@paul</a> This is an important question to keep iterating on as the <a href="https://hachyderm.io/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#W3C</a> moves into its new era of having a board of directors, and the <a href="https://hachyderm.io/tags/W3CAB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#W3CAB</a> starts focusing more on their Vision work (<a href="https://github.com/w3c/AB-public/tree/main/Vision" rel="nofollow noopener noreferrer" target="_blank">https://github.com/w3c/AB-public/tree/main/Vision</a>). Us browser folks have been biased toward "practical" <a href="https://hachyderm.io/tags/WebStandards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebStandards</a> that get implemented in browsers, but <a href="https://hachyderm.io/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> is proof that the more aspirational server<->server ones can be important too.

Recent searches

Search options

Administered by:

Server stats:

#w3cab