FEED Validator

Sorry

This feed does not validate.

• line 17, column 47: Invalid email address: Seth Dobbs, W3C CEO and President (25 occurrences) [help]

        <author>Seth Dobbs, W3C CEO and President</author>
                                                 ^

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 21, column 6: An item should not include both author and dc:creator (25 occurrences) [help]

        <dc:creator>Seth Dobbs, W3C CEO and President</dc:creator>
        ^

• line 23, column 0: content:encoded should not contain extension attribute (15 occurrences) [help]

          <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-cente ...
  

• line 23, column 0: content:encoded should not contain sizes attribute (15 occurrences) [help]

          <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-cente ...
  

• line 23, column 0: content:encoded should not contain loading attribute (15 occurrences) [help]

          <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-cente ...
  

• line 36, column 4: Ensure lastBuildDate is present when slash:comments is used (25 occurrences) [help]

      </item>
      ^

• line 151, column 7: content:encoded should not contain relative URL references: /blog/tags/ceo/ (3 occurrences) [help]

      ]]></content:encoded>
         ^

• line 352, column 0: content:encoded should not contain iframe tag (2 occurrences) [help]

                                                      <iframe src="https://www ...
  

Source: http://www.w3.org/QA/atom.xml

1. <?xml version="1.0" encoding="UTF-8"?>
2. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
3.  <channel>
4.    <language>en</language>
5.    <title>W3C - Blog</title>
6.    <description>The W3C blog is for in-depth Web standards topics and educational materials.</description>
7.    <pubDate>Tue, 26 Aug 2025 10:21:44 +0000</pubDate>
8.    <generator>Laminas_Feed_Writer 2 (https://getlaminas.org)</generator>
9.    <link>https://www.w3.org/blog/</link>
10.    <atom:link rel="self" type="application/rss+xml" href="https://www.w3.org/blog/feed/"/>
11.    <item>
12.      <title>Vision for W3C to reach durable and sustainable success</title>
13.      <description><![CDATA[In this blog post about the newly published W3C Statement “Vision for W3C”, W3C CEO Seth Dobbs emphasizes the importance of principle-driven leadership and how vision gives clarity to move towards meaningful goals.]]></description>
14.      <pubDate>Thu, 31 Jul 2025 06:59:00 +0000</pubDate>
15.      <link>https://www.w3.org/blog/2025/vision-for-w3c-to-reach-durable-and-sustainable-success/</link>
16.      <guid>https://www.w3.org/blog/2025/vision-for-w3c-to-reach-durable-and-sustainable-success/</guid>
17.      <author>Seth Dobbs, W3C CEO and President</author>
18.      <comments>https://www.w3.org/blog/2025/vision-for-w3c-to-reach-durable-and-sustainable-success/#comments</comments>
19.      <category><![CDATA[corporate]]></category>
20.      <category><![CDATA[blogs]]></category>
21.      <dc:creator>Seth Dobbs, W3C CEO and President</dc:creator>
22.      <content:encoded><![CDATA[            <figure class="component component--image">
23.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/compass-map-denise-jans-IJy2ZUex0-Y-unsplash.jpg" extension="jpg"             sizes="100vw"
24.            loading="lazy"
25.                            alt=""
26.                       />
27.            <figcaption>
28.            <p>Photo by <a href="https://unsplash.com/@dmjdenise">Denise Jans</a> on <a href="https://unsplash.com/photos/round-brass-colored-compass-on-map-IJy2ZUex0-Y">Unsplash</a></p>
29.        </figcaption>
30.    </figure>
31.                <div class="component component--text">
32.                    <p>Some of you may know that I host the “Principle Driven Leadership” Podcast, so in a sense, I am in my element in this blog post because the essence of the podcast is how to lead through principles and the importance of providing vision in order to grow, resolve problems effectively and create durable results.</p><p>With that in mind, I am excited that the <a href="https://www.w3.org/groups/other/ab/">W3C Advisory Board</a> has published as a W3C Statement the document <a href="https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/">Vision for W3C</a>, which articulates W3C’s core vision for the web. W3C Statements provide a stable reference for documents that W3C Members formally endorse after review. “Vision for W3C” defines the values of W3C’s mission as well as the shared principles that guide our decisions for the web, as new technologies enable new possibilities. I can not emphasize enough the importance of vision. Vision matters. It is my first core principle of leadership (the second and third being “leaders resolve problems” and “leaders create more leaders”), because vision drives impact.</p><p>Vision, paired with robust guiding principles, enables organizational alignment and begets positive outcomes. These key words describe a virtuous positive cycle: Clear vision and stated common outcomes (the “why”), and refined principles that drive forward motion (the “how”), create the alignment required for an organization to reach durable and sustainable success.</p><p>W3C’s vision provides our community that clarity: it is that the web is for all humanity, it is designed for the good of all people, it must be safe to use, and there is one interoperable world-wide web.</p><p>Our operational principles encompass user-first, multi-stakeholder, diversity, thorough review, consensus, royalty-free and voluntary implementation, open participation, transparency, interoperability, incubation, decentralization, and collaboration. These principles stake out the path towards the sustainable success of W3C.</p><p>Furthermore, the core sections on vision in “Vision for W3C” and the aforementioned operational principles for W3C, are the drivers behind the <a href="https://www.w3.org/blog/2025/public-release-of-w3cs-2025-2028-strategic-objectives-initiatives/">Strategic Objectives and Initiatives</a> that we developed and made public last month. Vision enables purposeful change, and “Vision for W3C” is what underpins W3C’s mission. In all of our four strategic objectives, we will be centering our guiding star on the impact W3C has. That will ensure that we navigate challenges and opportunities in a way that fulfills our mission of making the web work, for everyone, by bringing together global stakeholders to develop open standards that enable a World Wide Web which connects and empowers humanity.</p><p>I want to thank and <a href="https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/#acknowledgements">acknowledge</a> the individuals and our collective community for bringing this foundational document to life. I see this as a key component of leading the World Wide Web Consortium.</p>
33.            </div>
34.    ]]></content:encoded>
35.      <slash:comments>0</slash:comments>
36.    </item>
37.    <item>
38.      <title>Vision for W3C: a manifesto for our operations and decision making</title>
39.      <description><![CDATA[Today, W3C is pleased to announce the publication as a W3C Statement of Vision for W3C. W3C Statements provide a stable reference for documents not intended to be formal standards but that have been formally reviewed and are endorsed by W3C.]]></description>
40.      <pubDate>Tue, 29 Jul 2025 10:27:00 +0000</pubDate>
41.      <link>https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/</link>
42.      <guid>https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/</guid>
43.      <author>Coralie Mercier, W3C Marketing &amp; Communications Director, Max Gendler, W3C AB and chair of the Vision Task Force</author>
44.      <comments>https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/#comments</comments>
45.      <category><![CDATA[blogs]]></category>
46.      <dc:creator>Coralie Mercier, W3C Marketing &amp; Communications Director, Max Gendler, W3C AB and chair of the Vision Task Force</dc:creator>
47.      <content:encoded><![CDATA[            <figure class="component component--image">
48.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/Telescope-by-Daniel-Appelquist.png" extension="png"             sizes="100vw"
49.            loading="lazy"
50.                            alt="Blog post illustration: Telescope,  by Daniel Appelquist"
51.                       />
52.            <figcaption>
53.            <p>Blog post illustration: Telescope,  by Daniel Appelquist</p>
54.        </figcaption>
55.    </figure>
56.                <div class="component component--text">
57.                    <p>Today, W3C is pleased to announce the publication as a W3C Statement of <a href="https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/">Vision for W3C</a>. W3C Statements provide a stable reference for documents not intended to be formal standards but that have been formally reviewed and are endorsed by W3C.</p><p class="show_items">Vision for W3C articulates the World Wide Web Consortium’s core vision and operational principles, with goals to:</p><ul style="list-style-type:disc;"><li>Help the world understand what W3C is, what it does, and why it matters</li><li>Communicate shared values and principles of the W3C community</li><li>Be opinionated enough to provide guidance and a framework for making decisions, particularly on controversial issues</li><li>Be timeless enough to remain relevant without needing frequent revision, while being open to evolving based on the needs of the community&nbsp;</li></ul><p>The World Wide Web Consortium, as a community leader in defining technical standards and guidelines for a World Wide Web that connects and empowers humanity, has a role to provide a neutral open forum where diverse voices from around the world work together by consensus. The web has had a tremendous impact on the world, and its impact will continue to grow in the future as it expands reach, knowledge, education, and services even more broadly.&nbsp;</p><p>Vision for W3C was produced by the W3C Advisory Board (AB) as a work item that it has been tracking as a <a href="https://www.w3.org/wiki/AB/Vision">priority since 2021</a>, and builds on the W3C Technical Architecture Group’s excellent Ethical Web Principles, as it fits into the same framework and promotes many of the same goals. Where Ethical Web Principles focuses on the “what” - what we produce - Vision for W3C focuses more on the “how” - by writing down core operational principles. We are grateful to the AB Members, W3C Member representatives and W3C Team Members who joined them in the Vision Task Force, for shepherding this important work.&nbsp;</p><p>A few weeks ago we <a href="https://www.w3.org/blog/2025/public-release-of-w3cs-2025-2028-strategic-objectives-initiatives/">released</a> to the public the initiatives for 2025-2028 that will support W3C’s strategic objectives. Both Vision for W3C and Ethical Web Principles provide the foundational basis upon which to envision how to exercise our social responsibilities through rigorous consideration of accessibility, internationalization, privacy, and security.&nbsp;</p><p>Written in the spirit of taking responsibility to address the impact of our work, Vision for W3C defines the <strong>values of W3C’s mission and the shared principles that guide our decisions</strong> as new technologies enable new actions and new possibilities. Vision for W3C allows us to take deliberate steps to address the many harmful unintended and undesirable consequences that arose from the web’s amazing success, and to continue to provide the consistent architecture that enables a World Wide Web that works, for everyone.</p>
58.            </div>
59.    ]]></content:encoded>
60.      <slash:comments>0</slash:comments>
61.    </item>
62.    <item>
63.      <title>W3C Digital Credentials API publication: the next step to privacy-preserving identities on the web</title>
64.      <description><![CDATA[W3C recently published specifications will build foundations for new ways to represent identity on the web. Verifiable Credentials 2.0 and the first draft of Digital Credentials API enable the secure, seamless exchange of digital credentials on the web, emphasizing flexibility, emerging cryptography, compliance with regulation, and W3C principles related to privacy and security. All of these topics will be on the agenda of the Global Digital Collaboration, co-organized by W3C.]]></description>
65.      <pubDate>Tue, 01 Jul 2025 06:29:00 +0000</pubDate>
66.      <link>https://www.w3.org/blog/2025/w3c-digital-credentials-api-publication-the-next-step-to-privacy-preserving-identities-on-the-web/</link>
67.      <guid>https://www.w3.org/blog/2025/w3c-digital-credentials-api-publication-the-next-step-to-privacy-preserving-identities-on-the-web/</guid>
68.      <author>Simone Onofri, W3C Security Lead</author>
69.      <comments>https://www.w3.org/blog/2025/w3c-digital-credentials-api-publication-the-next-step-to-privacy-preserving-identities-on-the-web/#comments</comments>
70.      <category><![CDATA[privacy-and-security]]></category>
71.      <category><![CDATA[blogs]]></category>
72.      <dc:creator>Simone Onofri, W3C Security Lead</dc:creator>
73.      <content:encoded><![CDATA[            <figure class="component component--image">
74.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/amelie-mourichon-hcLSA1MiU3A-unsplash.jpg" extension="jpg"             sizes="100vw"
75.            loading="lazy"
76.                            alt="an LSP landscape"
77.                       />
78.    </figure>
79.                <div class="component component--text">
80.                    <p>This week some W3C staff members, including myself, will contribute to a series of conversations about the future of identity on the web at the <a href="https://globaldigitalcollaboration.org/?utm_term=global%20digital%20collaboration&amp;utm_campaign=GDC25&amp;utm_source=adwords&amp;utm_medium=ppc&amp;hsa_acc=2081606813&amp;hsa_cam=22600997684&amp;hsa_grp=183972760470&amp;hsa_ad=754456651326&amp;hsa_src=g&amp;hsa_tgt=kwd-2424281420544&amp;hsa_kw=global%20digital%20collaboration&amp;hsa_mt=e&amp;hsa_net=adwords&amp;hsa_ver=3&amp;gad_source=1&amp;gad_campaignid=22600997684&amp;gclid=CjwKCAjwvO7CBhAqEiwA9q2YJT2GVwEvpk7CJeC-jcwlaHEMsQJ0m3xPH8U_4dKy-ub3QWzOYXXKHBoCb34QAvD_BwE">Global Digital Collaboration in Geneva</a>. The timing is great from a W3C perspective because we have recently published multiple specifications that I believe will contribute to the next chapter of identity on the web.&nbsp;</p><h2>Verifiable Credentials 2.0</h2><p>Credentials such as driver’s licenses, passports, diplomas, and payment methods all play an important role in our daily lives. In a growing number of situations, people want to exchange these credentials digitally, and governments are beginning to push for interoperable technologies to support the demand. The foundation of trust in a credential ecosystem is that parties can cryptographically verify these credentials. I lead W3C’s security activities, and so am particularly focused on the secure exchange of these credentials.&nbsp;</p><p>In May, W3C published version 2 Recommendations of the Verifiable Credentials family of standards (see the <a href="https://www.w3.org/press-releases/2025/verifiable-credentials-2-0/">press release</a>). These standards enable the <strong>secure, privacy-respecting, and cryptographically verifiable expression of digital credentials</strong>.&nbsp;</p><p>For flexibility across a broad range of applications and governmental mandates, the new standards support a variety of encoding schemas (e.g., JSON-LD, SD-JWT). The Verifiable Credentials family also provides multiple ways to attach or embed cryptographic proofs to claims. Because the crypto landscape is quickly evolving, the standards are designed to be “crypto-modular” to accommodate emerging cryptographic approaches such as Post-Quantum Cryptography (PQC) and Zero-Knowledge Proofs (ZKP). With selective disclosure and the capability to combine multiple credentials into verified presentations, this model ensures secure, efficient, and privacy-preserving user data management.&nbsp;</p><h2>Digital Credentials API</h2><p>The unifying goal of the standards is to <strong>empower people to exchange verifiable information securely, privately, and seamlessly</strong> on the web. But how do people exchange these credentials, for example, when prompted by a site to provide a national identity? That is the role of the <a href="https://www.w3.org/TR/2025/WD-digital-credentials-20250701/">Digital Credentials API</a>, conceived in the Web Incubator Community Group, and now on the standards track in the Federated Identity Working Group. That group published the First Public Working Draft on 01 July 2025.</p><p>The Digital Credentials API enables websites to request credentials, and for users to consent to return credentials that they carry around in digital wallets. Above, I said “seamlessly” and that’s where the user agent (browser typically) plays a critical role. The user experience of understanding what is being requested by a site, selecting from among relevant credentials, consenting to share the credentials, and getting new credentials from issuers (e.g., universities, the department of motor vehicles, a bank) must be excellent, and the browser is uniquely positioned to support that experience.&nbsp;</p><p>Because the Digital Credentials API has been incubated for some time, both Google and Apple are already shipping early implementations, so people can <a href="https://digitalcredentials.dev">check out demos and conduct experiments</a>. This experimentation will inform the evolution of the specification.&nbsp;</p><p>This is only the First Public Working Draft, and the Working Group still needs to address some important security and privacy issues. For example, one of the hot topics is how to balance data privacy with the ability of the user agent to create a secure credential selection experience. Although the Digital Credentials API already expects credentials to be encrypted and signed by wallets (before being handed back to the user agent as output from the Digital Credentials API), there are ongoing conversations about the role of unlinkability for data input to the API. There is more work to do on this and other topics, and I encourage people to join the Federated Identity Working Group discussions.</p><h2>The ecosystem</h2><p>As I mentioned, the APIs being standardized at W3C involve interactions with wallets. The current W3C expectation is that the wallet ecosystem will be enabled by a broader ecosystem of operating systems and standards from partner SDOs, including the FIDO Alliance, OpenID Foundation, IETF, and ISO. A lot of the current push for all of these parties to work together comes from the <a href="https://ec.europa.eu/digital-building-blocks/sites/display/EUDIGITALIDENTITYWALLET/EU+Digital+Identity+Wallet+Home">European Union’s Digital Identity Wallet (EUDI)</a> initiative. A number of large-scale pilots are underway, and they will inform the ultimate EU regulation around the wallet ecosystem.</p><p>The Open Wallet Foundation has organized next week’s <a href="https://globaldigitalcollaboration.org">Global Digital Collaboration</a> to bring together the broader ecosystem, including governments interested in open standards for wallets, certification programs, and a role for governments. W3C is one of the event’s co-organizers, and W3C staff will host sessions on Threat Modeling Digital Wallets, focusing on Privacy, a Holistic Security view for Digital Identities, one focused session on the Digital Credentials API, and one for W3C Verifiable Credentials.</p><p>My colleagues and I look forward to joining these conversations to represent core values of the W3C mission, such as those reflected in recent W3C Statements such as <a href="https://www.w3.org/TR/2025/STMT-privacy-principles-20250515/">Privacy Principles for the Web</a> and <a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a>. For example, a core principle upheld in the W3C APIs is that users maintain control over their digital identities, which need not correspond directly to their legal identities. W3C emphasizes enabling users to present multiple identities across contexts, including ephemeral or anonymous identities, when necessary. User agents (such as browsers or other user interfaces) thus play a critical role in mediating interactions between users and online services, dynamically ensuring digital privacy and security. This approach balances user protection from undesired identification while facilitating intentional recognition, in simultaneous pursuit of both privacy and usability.</p><p>I look forward to sharing my experiences from the conference in a follow-up post.</p>
81.            </div>
82.    ]]></content:encoded>
83.      <slash:comments>0</slash:comments>
84.    </item>
85.    <item>
86.      <title>Public release of W3C’s 2025-2028 strategic objectives initiatives</title>
87.      <description><![CDATA[In this blog post, W3C President and CEO Seth Dobbs introduces the initiatives for 2025-2028 that will support W3C’s strategic objectives.]]></description>
88.      <pubDate>Mon, 30 Jun 2025 21:30:00 +0000</pubDate>
89.      <link>https://www.w3.org/blog/2025/public-release-of-w3cs-2025-2028-strategic-objectives-initiatives/</link>
90.      <guid>https://www.w3.org/blog/2025/public-release-of-w3cs-2025-2028-strategic-objectives-initiatives/</guid>
91.      <author>Seth Dobbs, W3C CEO and President</author>
92.      <comments>https://www.w3.org/blog/2025/public-release-of-w3cs-2025-2028-strategic-objectives-initiatives/#comments</comments>
93.      <category><![CDATA[corporate]]></category>
94.      <category><![CDATA[blogs]]></category>
95.      <dc:creator>Seth Dobbs, W3C CEO and President</dc:creator>
96.      <content:encoded><![CDATA[            <figure class="component component--image">
97.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/icons-collage.png" extension="png"             sizes="100vw"
98.            loading="lazy"
99.                            alt=""
100.                       />
101.            <figcaption>
102.            <p>Icons by Flaticon.com</p>
103.        </figcaption>
104.    </figure>
105.                <div class="component component--text">
106.                    <p>I joined the World Wide Web Consortium at the end of 2023, the year it was established as a US 501(c)(3) public-interest non-profit organization. After meeting the people (staff, W3C Members, collaborators from the community, etc.), taking stock of what the almost-thirty-year-old organization needed to be stronger, and to plan our efforts to move the world forward through the web platform, I then started expanding our connections to liaise with organizations and counterparts. We used the whole first semester of 2025 to iterate and finalize W3C’s strategic objectives and thematic initiatives spanning the next 3 to 5 years, that I’m pleased to introduce publicly today.</p><p>We will be centering our guiding star on the impact W3C has, to ensure that we navigate challenges and opportunities in a way that fulfills our mission of making the web work, for everyone, by bringing together global stakeholders to develop open standards that enable a World Wide Web which connects and empowers humanity.</p><p>W3C’s impact is through its broad mandate and all-encompassing methodology: since our founding 30 years ago, W3C has played an essential role in driving to trustworthy global solutions by creating trustworthy international standards that rigorously consider accessibility, internationalization, privacy, and security. From our continued work on web standards stems a single, open, interoperable platform that interconnects humanity. That is our impact.</p><p>The following commitments serve to illustrate by way of examples the four strategic objectives for W3C:</p><ol><li>Even though the web caters to over 5 billion people, the gap represented by the digital divide is increasing and we must consider what a “web for all” truly means and how to sustain expanding our support.<br>Strategic objective: <strong>Diversify our support</strong><br>→&nbsp;Ensure we have access to appropriate resources to protect our future even in the face of change.</li><li>We want our trusted gathering place to welcome more far-seeing technical experts and advocates about, and for, the web, so our standards work must consider the impact it has on the world.<br>Strategic objective: <strong>Enhance our impact</strong><br>→&nbsp;Direct our standards work through a framework that enables us to qualitatively and quantitatively define, analyze, and communicate the impact W3C intends to have.</li><li>Owing to our role in educating and promoting awareness of ethical and principled behaviors on the web, we must increase relationships with policymakers and regulatory bodies to advise on technical aspects and ensure that our values are represented, and to ensure we understand their needs as they impact the work that we do.<br>Strategic objective: <strong>Broaden our footprint</strong><br>→&nbsp;Expand our reach to involve communities and community representatives to ensure a truly world-wide perspective.</li><li>And finally, while the landscape of our work has changed significantly in large part because of the work of our community, we must examine how well-prepared and organized we are to face these challenges and perform the necessary structural evolution and operational optimization.<br>Strategic objective: <strong>Solidify our structure</strong><br>→&nbsp;Ensure W3C is set up to be a more resilient, adaptive, and durable organization to deliver on our mission well into the future.</li></ol><p>These long-term objectives will be supported by five strategic initiatives that the W3C Team will execute and track over 2025-2028:</p><ul><li>Structural evolution: Ensure that our underlying structure and processes are fit for purpose and can effectively enable our future work.</li><li>Impact framework: Enable W3C to qualitatively and quantitatively define, analyze, and communicate the impact we have on the world.</li><li>Stakeholder outreach strategy: Improve our overall effectiveness by reinforcing and enhancing relationships with existing stakeholders (e.g., W3C Members, implementers, web developers, etc.) as well as finding new stakeholders that can help further advance our mission.</li><li>Technology strategy: Maintain relevance through a focus on navigating technology evolution and newly emerging web and web-adjacent technologies.</li><li>Policy engagement: Provide expertise and insight from our community to governing bodies and policymakers to ensure future policies are better informed by our collective knowledge and values.</li></ul><p>In summary, we should work towards diversifying our support, finding new stakeholders that can contribute, and strengthening existing work with membership to rapidly adapt to and mitigate risks posed by our rapidly changing environment, while strengthening our organization’s structure and operations. Our positive impact will help ensure we attract more people to shape and strengthen the web, and grow ourselves in the process so we can further the virtuous circle. By adopting initiatives that support strategic objectives, we can truly realize our vision of making the web work, for everyone – a web designed for the good of its users, that is safe and secure.</p><p>I invite you to read <a href="https://www.w3.org/2025/06/w3c-2025-2028-strategic-objectives-and-initiatives/index.html">World Wide Web Consortium (W3C) 2025-2028 Strategic Objectives and Initiatives</a>, a public document streamlined from a document that the W3C Board of Directors approved a few weeks ago, following W3C Team and Members iteration and review.</p>
107.            </div>
108.    ]]></content:encoded>
109.      <slash:comments>0</slash:comments>
110.    </item>
111.    <item>
112.      <title>W3C seeks community input for Board of Directors appointments</title>
113.      <description><![CDATA[The W3C Board of Directors has open seats that can be appointed by the Board of Directors itself for two-year terms. W3C is seeking community input to identify Board Director candidates with financial skills, legal acumen, and fundraising experience, as well as with connections to other SDOs, who might improve the collective skills of the existing W3C Board of Directors.]]></description>
114.      <pubDate>Tue, 17 Jun 2025 13:47:00 +0000</pubDate>
115.      <link>https://www.w3.org/blog/2025/w3c-seeks-community-input-for-board-of-directors-appointments/</link>
116.      <guid>https://www.w3.org/blog/2025/w3c-seeks-community-input-for-board-of-directors-appointments/</guid>
117.      <author>Chris Wilson, W3C Board of Directors Development Committee Chair</author>
118.      <comments>https://www.w3.org/blog/2025/w3c-seeks-community-input-for-board-of-directors-appointments/#comments</comments>
119.      <category><![CDATA[corporate]]></category>
120.      <category><![CDATA[blogs]]></category>
121.      <dc:creator>Chris Wilson, W3C Board of Directors Development Committee Chair</dc:creator>
122.      <content:encoded><![CDATA[            <div class="component component--text">
123.                    <p>The <a href="https://www.w3.org/groups/other/board/">Board of Directors</a> has open seats that can be appointed by the Board of Directors itself for two-year terms. The Development Committee has been considering what skill areas the current Board needs to level up. We are seeking the community’s help in order to identify candidates who might fill those gaps.</p><p>Based on self-assessment of the current Board Directors, we believe the Board would significantly benefit from increased <strong>financial skills, legal acumen, and fundraising experience</strong>. We have additionally identified that <strong>connections to other standards-defining organizations</strong> would be beneficial, as well as improving our geographic balance - in particular, our current Board Directors under-represent North America in terms of geographic distribution of our members.</p><p>As a reminder, the Board maintains documents on the <a href="https://www.w3.org/Member/bod/board-explainer">role of the Board</a> as well as the <a href="https://www.w3.org/2024/06/w3c-board-of-directors-skills-description.html">expected skills and expectations for Directors</a>.</p><p>We are looking for suggestions of potential Board Director candidates who might improve our collective skills. We would particularly encourage suggestions of people with <strong>experience on non-profit boards</strong>, especially of national or international organizations.</p><p>We want to ensure we have a broad candidate pool. If you have any, we would encourage you to send suggestions of candidates to <code>board-appointee-suggestion@w3.org</code>. This list reaches the W3C Board of Directors Development Committee and W3C Officers. You may self-nominate or suggest other people. Please, be as specific but also as brief as you can.</p><p>Please note this is not an election. As part of the appointments the Board will discuss, and select candidates to explore further with (if any) based on how well they would round out our collective skills to improve the Board.</p>
124.            </div>
125.    ]]></content:encoded>
126.      <slash:comments>0</slash:comments>
127.    </item>
128.    <item>
129.      <title>Privacy on the web: creating a more trustworthy web</title>
130.      <description><![CDATA[In this blog post, W3C CEO Seth Dobbs explains why and how privacy on the web as a requirement for humanity is central to W3C’s mission, mentions current focus on Global Privacy Control (GPC), private advertising, and the recent W3C Statement on privacy principles.]]></description>
131.      <pubDate>Wed, 28 May 2025 08:26:00 +0000</pubDate>
132.      <link>https://www.w3.org/blog/2025/privacy-on-the-web-creating-a-more-trustworthy-web/</link>
133.      <guid>https://www.w3.org/blog/2025/privacy-on-the-web-creating-a-more-trustworthy-web/</guid>
134.      <author>Seth Dobbs, W3C CEO and President</author>
135.      <comments>https://www.w3.org/blog/2025/privacy-on-the-web-creating-a-more-trustworthy-web/#comments</comments>
136.      <category><![CDATA[privacy]]></category>
137.      <category><![CDATA[blogs]]></category>
138.      <dc:creator>Seth Dobbs, W3C CEO and President</dc:creator>
139.      <content:encoded><![CDATA[            <figure class="component component--image">
140.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/annie-spratt-YopBL6zM7F8-privacy.jpg" extension="jpg"             sizes="100vw"
141.            loading="lazy"
142.                            alt=""
143.                       />
144.            <figcaption>
145.            <p>Photo by <a href="https://unsplash.com/@anniespratt">Annie Spratt</a> on <a href="https://unsplash.com/photos/gray-wooden-welcome-to-the-beach-signage-YopBL6zM7F8">Unsplash</a></p>
146.        </figcaption>
147.    </figure>
148.                <div class="component component--text">
149.                    <p>Continuing the <a href="/blog/tags/ceo/">series</a> that puts the emphasis on the key areas that help ensure that the Web works, for everyone, this month I am diving into Web security. It is one of the key areas that we call “horizontals” and that shape every W3C work package because they involve approaches that are common to all work groups. Our horizontals are <a href="https://www.w3.org/mission/accessibility/">Web accessibility</a>, <a href="https://www.w3.org/mission/internationalization/">internationalization</a>, <a href="https://www.w3.org/mission/security/">security</a> and <a href="https://www.w3.org/mission/privacy/">privacy</a>.&nbsp;</p><h2>The imperative</h2><p>Creating a more trustworthy web and protecting user privacy is fundamental to creating a web that works, for everyone.</p><p>Privacy, along with Security, are integral to <a href="https://www.un.org/en/about-us/universal-declaration-of-human-rights">human rights</a> and <a href="https://www.ohchr.org/en/instruments-mechanisms/instruments/international-covenant-civil-and-political-rights">civil liberties</a>, and are essential to the success of the web platform. Today, so many of the features of the web and its usage involve information about people and their communications that privacy must be considered consistently across the design of the entire platform. The human factors and the sociotechnical aspects add additional complexity.</p><p>To affirmatively realize the privacy of people using the web and address privacy threats that have already arisen requires us to operate in an interdisciplinary and global space, and to develop dedicated privacy features.</p><h2>How W3C approaches privacy on the web</h2><p>Following the mid-2000s W3C work on <a href="https://www.w3.org/P3P/">Platform for Privacy Preferences (P3P)</a>, the W3C Team in 2011 identified the need to strengthen the foundations of trust on the web for communities large and small to access and share data, and made it an area of <a href="https://www.w3.org/2011/01/w3c2011.html#social">focus in 2011</a>. The evolution then trended toward significantly more intense collection, processing, and publication of personal data.</p><p>We follow a recipe that is simple but which details are of importance:</p><ul><li>Review the privacy of web standards</li><li>Advise W3C groups developing standards to mitigate privacy issues</li><li>Develop some private technology standards</li></ul><p>Horizontal reviews are conducted for privacy of proposals and specifications under development by other W3C Working Groups and Community Groups, and of charters for other W3C groups. Related to that is advising groups developing standards on how to avoid and mitigate privacy issues with web technologies.</p><p>The other main component is the standardization of new technical mechanisms that improve privacy on the web, including work moving from incubation when there is a basic technical design, significant implementer interest and activity.</p><p>The <a href="https://www.w3.org/groups/wg/privacy/">W3C Privacy Working Group</a> undertakes the former and a lot of the latter. The rest of the privacy-focused features specific to technical work covered by another Working Group are typically best developed in those Working Groups, alongside related technical features.</p><h2>In focus: Global Privacy Control, Private Advertising</h2><p><a href="https://www.w3.org/TR/gpc/">Global Privacy Control (GPC)</a> defines a signal, transmitted over HTTP and through the DOM, that conveys a person's request to websites and services to not sell or share their personal information with third parties. This standard is intended to work with existing and upcoming legal frameworks that render such requests enforceable.</p><p>W3C launched the <a href="https://www.w3.org/groups/wg/pat/">Private Advertising Working Group</a></p><p><a href="https://www.w3.org/groups/wg/pat/">in late 2024, motivated by the </a><a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles W3C Statement</a>, to specify web features and APIs that support advertising while acting in the interests of users, in particular providing strong privacy assurances using predominantly technical means.</p><p>If you wish to know more about ongoing work, I suggest you take 8 minutes to watch the <a href="https://www.youtube.com/watch?v=SxOKYBnqqXc">Privacy talk</a> my colleague Tara Whalen, W3C Privacy Lead, gave early April 2025.</p><h2>W3C Statement: Privacy Principles</h2><p>The <a href="https://www.w3.org/TR/privacy-principles/">Privacy Principles</a> were elevated in May 2025 to W3C Statement, which means that although the document is informative and not a formal standard in nature, it creates a stable reference that has received formal review and endorsement from W3C Members.</p><p>The document provides definitions for privacy that are applicable worldwide as well as a set of privacy principles that aim to guide the development of the web as a trustworthy platform.</p><p>You can read more in Tara Whalen’s <a href="https://www.w3.org/blog/2025/new-privacy-principles-for-a-more-trustworthy-web/">blog post</a> on the W3C Statement: New Privacy Principles for a more trustworthy web.</p>
150.            </div>
151.    ]]></content:encoded>
152.      <slash:comments>0</slash:comments>
153.    </item>
154.    <item>
155.      <title>New Privacy Principles for a more trustworthy web</title>
156.      <description><![CDATA[Protecting user privacy is fundamental to creating a web that works for everyone. Last week, W3C published its Statement on Privacy Principles, which provides definitions for privacy concepts plus privacy principles to guide web development. Learn more about this guide and how it can help us all to create a more trustworthy web for users around the world by “levelling up” privacy.]]></description>
157.      <pubDate>Thu, 22 May 2025 09:58:00 +0000</pubDate>
158.      <link>https://www.w3.org/blog/2025/new-privacy-principles-for-a-more-trustworthy-web/</link>
159.      <guid>https://www.w3.org/blog/2025/new-privacy-principles-for-a-more-trustworthy-web/</guid>
160.      <author>Tara Whalen, W3C Privacy Lead</author>
161.      <comments>https://www.w3.org/blog/2025/new-privacy-principles-for-a-more-trustworthy-web/#comments</comments>
162.      <category><![CDATA[privacy]]></category>
163.      <category><![CDATA[blogs]]></category>
164.      <dc:creator>Tara Whalen, W3C Privacy Lead</dc:creator>
165.      <content:encoded><![CDATA[            <figure class="component component--image">
166.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/privacy-lock-by-rob-pongsajapan.jpeg" extension="jpeg"             sizes="100vw"
167.            loading="lazy"
168.                            alt=""
169.                       />
170.            <figcaption>
171.            <p><a href="https://www.flickr.com/photos/15131913@N00/2404940312">"Privacy"</a> by Rob Pongsajapan, licensed under CC BY 2.0</p>
172.        </figcaption>
173.    </figure>
174.                <div class="component component--text">
175.                    <p>
176. Protecting user privacy is fundamental to creating a web that works for everyone. Last week, W3C published its Statement on <a href="https://www.w3.org/TR/privacy-principles/">Privacy Principles</a>, in support of furthering this goal. This document defines some foundational privacy concepts and provides a set of privacy principles to guide web development. We hope this guide will enhance the community’s understanding of privacy, illustrate ways of realizing it in practice, and inspire a vision of the trustworthy web that we can create and sustain together.
177. </p>
178.  
179. <p>
180. Last December, W3C published its first ever Statement, on <a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a>. The Privacy Principles Statement continues this series, focusing specifically on the considerations required for creating a web that <a href="https://www.w3.org/TR/ethical-web-principles/#privacy">respects people’s privacy</a>. This milestone is significant: <a href="https://www.w3.org/standards/types/#x2-5-3-statements">W3C Statements</a> are documents that have been formally reviewed and endorsed by W3C's membership as a whole. The Privacy Principles document was developed over three years and incorporated feedback and contributions from the W3C community, and is now accepted as a W3C Statement to indicate our collective stance on the fundamental importance of web privacy and how to achieve it in practice.
181. </p>
182.  
183. <p>
184. I first started working on privacy with W3C in 2012 (as one of the <a href="https://www.w3.org/news/2012/w3c-launches-privacy-interest-group/">original co-chairs of the Privacy Interest Group</a>) and I have seen first-hand how users’ online privacy has evolved over the years, both in terms of new opportunities as well as new challenges. During this time, a lot of helpful privacy material has been produced, such as a guide on <a href="https://www.w3.org/TR/fingerprinting-guidance/">mitigating browser fingerprinting</a> (to reduce the risk of user tracking) and a <a href="https://www.w3.org/TR/security-privacy-questionnaire/">questionnaire</a> to assist specification authors and reviewers in improving the level of privacy and security of their designs. The Privacy Principles Statement complements this body of work by providing a more general document that includes core privacy concepts as well as overarching guidance that ensures privacy is built into the foundations of web technologies.
185. </p>
186.  
187. <p>
188. Privacy is a very broad topic. In order to reason about privacy on the web, and therefore provide actionable guidance, it’s first necessary to define what we mean by privacy in the context of the web. That’s why this document begins with an introduction to privacy on the web, covering topics like data governance, individual autonomy, deceptive patterns, consent, opt-out and privacy labor, as well as the role that browsers (user agents) play in safeguarding web users. This provides context for the actionable principles, each of which is marked with the audiences that it's most relevant to: websites, user agents or API (web technology) designers.
189. </p>
190.  
191. <p>
192. It’s also important to consider how web technologies interact with social and policy aspects in the privacy realm. The regulatory environment, for example, is constantly evolving and has significant implications for the data protection of users around the world. One of the goals of the Privacy Principles Statement is to support online privacy regulations; the document is written to address both technological and policy considerations and hopefully help achieve some alignment between different regulatory regimes. Because the discussions around online data can sometimes become complex, the document includes several short, concrete examples to illustrate privacy risks and possible mitigations – for example, handling geolocation information or managing children’s services.
193. </p>
194.  
195. <p>
196. It’s taken a lot of work from many members of the W3C community to get these Privacy Principles to this stage, and I want to acknowledge their hard work and dedication. This document is the result of sustained effort by the <a href="https://github.com/w3ctag/privacy-principles">Privacy Principles Task Force</a> (a group representing a wide range of web stakeholders, convened by the W3C Technical Architecture Group), with particular credit to its Chair Daniel Appelquist and to the document editors, Robin Berjon and Jeffrey Yasskin. Additional thanks are due to all of the people who constructively engaged in discussions about web privacy–some of them over several years!–that were instrumental in producing a Statement that accurately reflects our collective privacy vision for the web.
197. </p>
198.  
199. <p>
200. While we’re taking a moment to celebrate the publication of this document, we acknowledge that the work is far from over. We’re eager to hear feedback about the Privacy Principles, which we can use to improve and expand our future documentation. And of course we encourage you to put the principles into practice as we build a better web!
201. </p>
202.            </div>
203.    ]]></content:encoded>
204.      <slash:comments>0</slash:comments>
205.    </item>
206.    <item>
207.      <title>Educational and Cultural Exchange on Digital Accessibility — Highlights from Hong Kong</title>
208.      <description><![CDATA[Shawn Henry shares her thoughts about a recent trip as part of the Educational and Cultural Affairs Exchange Program in Hong Kong on Digital Accessibility]]></description>
209.      <pubDate>Thu, 15 May 2025 08:30:00 +0000</pubDate>
210.      <link>https://www.w3.org/blog/2025/educational-and-cultural-exchange-on-digital-accessibility-highlights-from-hong-kong/</link>
211.      <guid>https://www.w3.org/blog/2025/educational-and-cultural-exchange-on-digital-accessibility-highlights-from-hong-kong/</guid>
212.      <author>Shawn Henry</author>
213.      <comments>https://www.w3.org/blog/2025/educational-and-cultural-exchange-on-digital-accessibility-highlights-from-hong-kong/#comments</comments>
214.      <category><![CDATA[accessibility]]></category>
215.      <category><![CDATA[blogs]]></category>
216.      <dc:creator>Shawn Henry</dc:creator>
217.      <slash:comments>0</slash:comments>
218.    </item>
219.    <item>
220.      <title>EPUB3.3 Recommendations published, work begins on new features</title>
221.      <description><![CDATA[The Publishing Maintenance Working Group (PMWG) has finalized the EPUB 3.3 specification, clarifying language and aligning it with related specifications. The group is now working on the next major revision, EPUB 3.4. This revision will include new features such as dark mode support and standardized footnote/endnote practices. Additionally, new task forces are exploring digital comics support and EPUB annotations.]]></description>
222.      <pubDate>Wed, 23 Apr 2025 15:03:00 +0000</pubDate>
223.      <link>https://www.w3.org/blog/2025/epub3-3-recommendations-published-work-begins-on-new-features/</link>
224.      <guid>https://www.w3.org/blog/2025/epub3-3-recommendations-published-work-begins-on-new-features/</guid>
225.      <author>Susan Neuhaus, co-Chair of the Publishing Maintenance Working Group</author>
226.      <comments>https://www.w3.org/blog/2025/epub3-3-recommendations-published-work-begins-on-new-features/#comments</comments>
227.      <category><![CDATA[blogs]]></category>
228.      <dc:creator>Susan Neuhaus, co-Chair of the Publishing Maintenance Working Group</dc:creator>
229.      <content:encoded><![CDATA[            <div class="component component--text">
230.                    <p>The <a href="https://www.w3.org/groups/wg/pm/">Publishing Maintenance Working Group</a> (PMWG) is pleased to announce the final update of the W3C Recommendation for <a href="https://www.w3.org/TR/epub-overview-33/">EPUB® 3.3</a>.</p><p>The publishing community has thoroughly tested these Recommendations. When presented for publication, support was unanimous among responding W3C Members. It is encouraging that several reviewers indicated that they produce or plan to produce products that use this specification.</p><h2 id="corrections">Corrections made to EPUB Recommendations</h2><p>This update introduces no new features. The changes clarify the language and bring it in line with related specifications. The PMWG reports:</p><ul><li>We fixed the epub:type attribute not allowed on links in <abbr title="Scalable Vector Graphics">SVG</abbr>;</li><li>We clarified the requirements for SVG embedded by inclusion and by reference; and</li><li>We fixed our white space definition for the fixed layout viewport meta tag. This disallowed form feed, avoiding potential rendering issues.</li></ul><h2 id="next">What’s next for EPUB3?</h2><p>The PMWG’s work continues with the next major revision to the EPUB 3 family of Recommendations. This upcoming version will add new normative features to the specifications. For more information, please refer to the <a href="https://www.w3.org/2025/02/pmwg-charter.html">Publishing Maintenance Working Group Charter</a>.</p><p>The WG will take on these tasks:</p><ul><li>Ensuring a good experience when reading in dark mode</li><li>Considering adding support for HTML in the EPUB package, and</li><li>Standardizing practices for content like footnotes &amp; endnotes.</li></ul><h2 id="tfs">New Task Forces: Digital Comics, and EPUB Annotations</h2><p>The Digital Comics Task Force will explore how EPUB can better support comics creators and readers. This would include webtoons, manga, graphic novels, and similar content. Digital comics are often read as a continuous scroll on mobile devices. They are not usually separated into pages like a typical ebook. The TF will develop scrolling specifications for both ebook producers and ebook reading systems. Another important feature of manga and webtoons is serialization. Digital comics need new metadata so that people can find the next installment of their favorite manga.</p><p>Currently, people can annotate EPUBs within a reading system. But the annotation remains with the platform, not the publication. There are use cases for annotations stored within an EPUB package. Researchers could access their notes from multiple devices, and potentially export the annotations. Teachers would be able to share their perspective with students. Annotations are valuable in legal documents, too. Ebook reading platforms could benefit from making it easier for people to switch accounts. An EPUB Annotations Task Force will look into adding this long-requested feature to EPUB.</p><h2 id="accessibility">Accessibility in EPUB</h2><p>The Accessibility Task Force and the Fixed Layout (FXL) Accessibility Task Force will continue their work. The FXL Accessibility Task Force is developing a techniques document. It will include specific models and examples. Since the current FXL EPUBS cannot be fully accessible, the TF will incubate ways around this with new technology. Additionally, they are tasked with bridging EPUB metadata to library and other publication data systems. This will ensure that people can find an ebook that suits their reading needs.</p><p>The Accessibility Task Force topics include moving from WCAG 2.0 to 2.1 or 2.2 as the floor specification. They will also look at metadata. New metadata is needed to identify publisher contacts for accessibility issues. The TF intends to develop a way to deterministically identify content by type. With that in place, people will know if they can access an ebook’s content.</p><p>Contact the <a href="mailto:group-pm-wg-chairs@w3.org">group's co-chairs</a> if you have an interest in one of these TFs and would like to contribute to the new EPUB specifications.</p><h2 id="epub34">EPUB 3.4 working drafts</h2><p>The Working Group has published the first working drafts of the EPUB 3.4 specification below. At this moment, the initial Working Drafts are essentially identical to the 3.3 versions, but the Working Group plans to evolve these documents to a standard in about two years.</p><ul><li><a href="https://www.w3.org/TR/epub-34">EPUB 3.4</a></li><li><a href="https://www.w3.org/TR/epub-rs-34">EPUB Reading Systems 3.4</a></li><li><a href="https://www.w3.org/TR/epub-a11y-111">EPUB Accessibility 1.1.1</a></li></ul><p>Congratulations to Matt Garrish, main editor; co-chairs Wendy Reid, Shinya Takami; co-editor and W3C staff contact Ivan Herman; and the entire Publishing Maintenance Working Group for this update.</p>
231.            </div>
232.    ]]></content:encoded>
233.      <slash:comments>0</slash:comments>
234.    </item>
235.    <item>
236.      <title>Join the W3C Exploration Interest Group: where standards start</title>
237.      <description><![CDATA[The goal of the Exploration Interest Group is to provide a platform to help W3C investigating emerging technology trends, analyzing their impacts on the evolution of Web technologies, and proposing ways for W3C to collaborate shaping the trends for the benefit of the Web users.]]></description>
238.      <pubDate>Tue, 22 Apr 2025 10:23:00 +0000</pubDate>
239.      <link>https://www.w3.org/blog/2025/join-the-w3c-exploration-interest-group-where-standards-start/</link>
240.      <guid>https://www.w3.org/blog/2025/join-the-w3c-exploration-interest-group-where-standards-start/</guid>
241.      <author>Heather Flanagan, co-chair of the Exploration Interest Group, Jet Ding, co-chair of the Exploration Interest Group</author>
242.      <comments>https://www.w3.org/blog/2025/join-the-w3c-exploration-interest-group-where-standards-start/#comments</comments>
243.      <category><![CDATA[blogs]]></category>
244.      <dc:creator>Heather Flanagan, co-chair of the Exploration Interest Group, Jet Ding, co-chair of the Exploration Interest Group</dc:creator>
245.      <content:encoded><![CDATA[            <div class="component component--text">
246.                    <p>You know the feeling. You’re in a product meeting, skimming GitHub issues, or catching up on another EU regulatory proposal, and you realize there’s something missing in how we’re building for the web. Maybe it’s a technical shortfall, maybe it’s a user experience no one’s nailed yet, or maybe it’s a whole category of use case the current standards aren’t touching with a ten-foot pole.</p><p>That’s where the <a href="https://www.w3.org/groups/ig/exploration/">W3C Exploration Interest Group</a> (IG) comes in.</p><p>We’re not a working group. We’re not here to define normative specs. We’re here to connect the dots between the real world and the standards world and to ask better questions before jumping to answers. Think of us as the early R&amp;D lab for identity, authentication, and trust on the web.</p><h3>Why this group, and why now?</h3><p>If you’re building for the web, navigating its policy landscape, or just trying to make something interoperable, this group’s for you. Why? Because web identity is in flux. Cookies are on the way out. Federated login flows are being rebuilt. Browsers are experimenting with new APIs. And regulators? They're not exactly standing still either.</p><p>If we want a web that works for real users, across real use cases, we need more people at the table who can say:</p><p><i>“Here’s what’s happening in production, and here’s what we still don’t understand.”</i></p><p>That’s what the Exploration IG is here for: to find the gaps, to make space for disagreement, to spotlight use cases that standards groups haven’t prioritized yet, and to build the bridges that <i>might</i> become working group charters down the line.</p><h3>What we’re exploring?</h3><p>We don’t have a single-track agenda—but here’s the kind of stuff that gets us talking:</p><ul><li>Technical gaps between browser implementations and web specs</li><li>Emerging wallet models, identity credentials, and federation flows</li><li>Use cases that span trust frameworks, sectors, or jurisdictions</li><li>Fragmentation risks when multiple standards solve the same problem differently</li><li>Regulatory signals that need a better technical response</li></ul><h3>Contribute your ideas!</h3><p>Our <a href="https://github.com/w3c/exploration-ig">GitHub repo</a> is public, and we actively welcome ideas and discussion there; this is an open forum, and everyone is welcome to contribute their ideas. If you see something in the wild that standards groups should be thinking about, bring it to us. Whether you’re an implementer, a researcher, a policymaker, or someone with a stubborn browser bug and a vision, open an issue. We want to hear from you. And if it turns into a recurring collaboration, we’d be delighted to have you <a href="https://www.w3.org/groups/ig/exploration/join/">join the group</a>.</p><h3>Some of the best conversations start with “I’m not sure this fits anywhere else."</h3><p>And that’s exactly the kind of conversation we want to have. So if you’ve ever felt like there’s something important that doesn’t quite have a home in the <a href="https://www.w3.org/standards/">standards process</a> yet, maybe it belongs with us.</p><p>We meet every other week and organize sessions around topics raised by the community. Join us. Listen in. Bring your questions. Or just open an issue and see what happens.</p><p><a href="https://www.w3.org/groups/ig/exploration/">Learn more about the Exploration Interest Group</a>.</p>
247.            </div>
248.    ]]></content:encoded>
249.      <slash:comments>0</slash:comments>
250.    </item>
251.    <item>
252.      <title>First catalog of web features completed by the WebDX Community Group</title>
253.      <description><![CDATA[The WebDX Community Group has completed a first nearly complete catalog of web features targeted at web developers, along with support data across main browsers. The catalog already powers MDN, Can I Use, and is now being integrated in tools and libraries. Feedback welcome!]]></description>
254.      <pubDate>Thu, 13 Mar 2025 11:58:00 +0000</pubDate>
255.      <link>https://www.w3.org/blog/2025/first-catalog-of-web-features-completed-by-the-webdx-community-group/</link>
256.      <guid>https://www.w3.org/blog/2025/first-catalog-of-web-features-completed-by-the-webdx-community-group/</guid>
257.      <author>Patrick Brosset, co-chair of the WebDX Community Group, François Daoust, co-chair of the WebDX Community Group</author>
258.      <comments>https://www.w3.org/blog/2025/first-catalog-of-web-features-completed-by-the-webdx-community-group/#comments</comments>
259.      <category><![CDATA[developers]]></category>
260.      <category><![CDATA[blogs]]></category>
261.      <dc:creator>Patrick Brosset, co-chair of the WebDX Community Group, François Daoust, co-chair of the WebDX Community Group</dc:creator>
262.      <content:encoded><![CDATA[            <div class="component component--text">
263.                    <p>The WebDX Community Group <a href="https://www.w3.org/blog/2022/webdx-improving-the-experience-for-web-developers/">started work in 2022</a> to <strong>make it easier for developers to track the list of features that are widely available and those that are under development</strong>.</p><p>Since then, the Community Group has been busy developing the open-source <a href="https://github.com/web-platform-dx/web-features"><code>web-features</code> project</a>, a shared catalog of features of the web platform, and the <a href="https://web-platform-dx.github.io/web-features/">Baseline</a> status to give developers clear information about which of these features work across a core browser set. Baseline badges have now been integrated in <a href="https://caniuse.com/">Can I Use</a>, <a href="https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility">MDN</a>, <a href="https://rumarchive.com/insights/#baseline">RUM Archive Insights</a>, <a href="https://www.rumvision.com/help-center/monitoring/dashboard/baseline/">RUMvision</a> and others. Watch the <a href="https://www.w3.org/2024/09/TPAC/demo-baseline.html">Baseline web features for the win</a> video (September 2024) for a quick dive into the <code>web-features</code> project.</p><p>Today, we are happy to announce that the WebDX Community Group has reached a new milestone: most keys defined in the <a href="https://github.com/mdn/browser-compat-data"><code>@mdn/browser-compat-data</code> project</a> (BCD), which powers support tables in MDN pages and contains the most complete set of fine-grained features defined in web specifications, have been mapped to 1000+ higher-level features in the <code>web-features</code> project. This provides a first nearly complete <strong>catalog of web features</strong>, along with their Baseline status. The catalog is available through the <a href="https://www.npmjs.com/package/web-features"><code>web-features</code> package</a> in the npm registry.</p><p>This effort would not have been possible without significant contributions from, and collaboration with, organizations such as <a href="https://openwebdocs.org/">Open Web Docs</a>, <a href="https://developer.mozilla.org/en-US/">MDN</a>, browser vendors, and many others! Many thanks to them and to organizations that provided support in the background so that group participants could do the work.</p><p>Plotting browser support data in the catalog shows the evolution of the web platform in terms of number of features and Baseline status within browsers from the first release of Safari in June 2003 (95 features) to the end of February 2025 (1006 features), and the relative split between features that are implemented somewhere (328 as of February 2025), Baseline Newly Available (150 as of February 2025), and Baseline Widely Available (528 as of February 2025). Please keep in mind that the support data only covers browsers of the core browser set (Chrome, Edge, Firefox, Safari) and that the notion of Baseline only becomes meaningful once all these browsers have shipped a first version (after July 2015 for the Baseline Newly Available status, after January 2018 for the Baseline Widely Available status).</p>
264.            </div>
265.                <figure class="component component--image">
266.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/web-features-evolution.png" extension="png"             sizes="100vw"
267.            loading="lazy"
268.                            alt="Stacked area chart illustrating the evolution of the web platform in terms of number of features in core browsers (2003-2025)"
269.                       />
270.            <figcaption>
271.            <p>Evolution of the web platform in terms of number of features implemented in browsers</p>
272.        </figcaption>
273.    </figure>
274.                <div class="component component--text">
275.                    <p>The list of features will of course keep growing as new features get discussed, standardized and implemented across web browsers. The group also expects to refine existing mappings, to further improve tooling (including the <a href="https://github.com/web-platform-dx/baseline-status"><code>&lt;baseline-status&gt;</code> web component</a> to display the Baseline status of a web feature), and to work with browser vendors, maintainers of libraries, documentation and services to integrate web-features where it matters for web developers.</p><p>If you want to learn more about the project and provide feedback, you are welcome to attend the <a href="https://github.com/w3c/breakouts-day-2025/issues/8">breakout session about web-features</a> that Patrick Brosset, co-chair of the WebDX Community Group, will lead during <a href="https://www.w3.org/2025/03/breakouts-day-2025/">Breakouts Day 2025</a> on 26 March 2025 (time still to be defined).</p><p>If you want to contribute and improve the developer experience of the web platform, please join the <a href="https://www.w3.org/community/webdx/">WebDX Community Group</a> or bring your input to the <a href="https://github.com/web-platform-dx/web-features"><code>web-platform-dx/web-features</code> GitHub repository</a>.</p>
276.            </div>
277.    ]]></content:encoded>
278.      <slash:comments>0</slash:comments>
279.    </item>
280.    <item>
281.      <title>How to protect your Web applications from XSS</title>
282.      <description><![CDATA[The W3C SWAG (Security Web Application Guidelines) Community Group, launched in June 2024, aims to simplify security features in web app development. SWAG's mission is to enhance web app security by creating best practices for developers and fostering collaboration. A key output includes videos on configuring CSP and Trusted Types, which mitigate XSS. Based on Google’s adoption experience, these resources offer tools to help developers securely configure these protections with minimal effort.]]></description>
283.      <pubDate>Thu, 06 Mar 2025 19:16:00 +0000</pubDate>
284.      <link>https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/</link>
285.      <guid>https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/</guid>
286.      <author>Simone Onofri, W3C Security Lead, Daniel Appelquist, W3C SWAG CG Chair</author>
287.      <comments>https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/#comments</comments>
288.      <category><![CDATA[security]]></category>
289.      <category><![CDATA[blogs]]></category>
290.      <dc:creator>Simone Onofri, W3C Security Lead, Daniel Appelquist, W3C SWAG CG Chair</dc:creator>
291.      <content:encoded><![CDATA[            <div class="component component--text">
292.                    <p>The <a href="/groups/cg/swag/">W3C Security Web Application Guidelines (SWAG) Community Group</a> seeks to make it easier for developers to leverage security features that are often complex in their application development.</p><p>SWAG launched in June 2024 after the <a href="https://www.w3.org/2023/03/secure-the-web-forward/">W3C Workshop "Secure the Web Forward"</a>. One of the workshop’s findings, and some accompanying developer research presented there, is that web developers are generally unsure about security and their role in ensuring that web apps are secure. This group’s mission, therefore, is “to increase the overall security of web application development by writing security best practices for web developers and providing a platform for stakeholder collaboration.” In the same manner as that workshop, SWAG is intended to be connected to other organizations that share a similar mission, such as the <abbr title="Open Source Security Foundation">OpenSSF</abbr> Best Practices Group, OpenJS Foundation, and <abbr title="Open Web Application Security Project">OWASP</abbr>.</p><p><strong>One of the first results of SWAG’s efforts is a set of videos addressing the complexities of Content Security Policy and Trusted Types.</strong> These two features can be used as effective <abbr title="cross site scripting">XSS</abbr> mitigations but, unfortunately, are difficult to configure due to the breadth of the threats they mitigate and the fact that they are time-consuming to debug.</p><p>Six talks introduce open-source tooling developed from Google’s large-scale <abbr title="Content Security Policy">CSP</abbr> and Trusted Types adoption work. These tools, which serve as a natural interface between developers and the specifications, provide <strong>actionable help in a tight feedback loop during the development cycle to reduce the uncertainty and complexity of configuring these best-in-class web security mitigations against XSS</strong>. The experience of Google engineers who have shipped strict CSP and Trusted Types to hundreds of web applications is distilled into tools that provide best practices and gentle guidance toward a more secure codebase.</p><p>SWAG meets every week and those talks were recorded during the meeting of 11 November 2024. The 6 videos are available via the "<a href="https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr">Security at W3C" playlist</a> on W3C's YouTube channel.</p>
293.            </div>
294.    ]]></content:encoded>
295.      <slash:comments>0</slash:comments>
296.    </item>
297.    <item>
298.      <title>International standards and World Economic Forum (WEF)</title>
299.      <description><![CDATA[In this blog post, W3C CEO Seth Dobbs shares impressions from representing W3C for the first time at the World Economic Forum, and illustrates how our distinctive human-centric focus in the world of Standards Development Organizations positions W3C to be helping to shape the future of the web.]]></description>
300.      <pubDate>Mon, 24 Feb 2025 17:29:00 +0000</pubDate>
301.      <link>https://www.w3.org/blog/2025/international-standards-and-world-economic-forum-wef/</link>
302.      <guid>https://www.w3.org/blog/2025/international-standards-and-world-economic-forum-wef/</guid>
303.      <author>Seth Dobbs, W3C CEO and President</author>
304.      <comments>https://www.w3.org/blog/2025/international-standards-and-world-economic-forum-wef/#comments</comments>
305.      <category><![CDATA[corporate]]></category>
306.      <category><![CDATA[blogs]]></category>
307.      <dc:creator>Seth Dobbs, W3C CEO and President</dc:creator>
308.      <content:encoded><![CDATA[            <div class="component component--text">
309.                    <p>I recently had the pleasure of speaking at several events during the World Economic Forum in Davos, Switzerland. This was a great opportunity to represent W3C and the <strong>power of international standards</strong>, particularly since the theme this year was “Collaboration for the Intelligent Age”.&nbsp;</p><p><strong>W3C’s 30 year history of global collaboration to build open, free, interoperable standards for a single world wide web is a great example of the kind of collaboration our world continues to need in rapidly changing times</strong>. As such, it was good to see how much interest there is in interoperable international standards in general and in W3C’s participation in such conversations in particular. It was great to have the opportunity to talk about the <strong>positive and at times life-changing impacts that international standards can have</strong>, and to hear others outside of the standards community express their interest, support, and even the very need for international interoperable standards.</p><p>Key points:</p><ol><li><strong>Interoperability</strong>: Alain Labrique (World Health Organization) expressed how interoperable standards for health information can save lives by enabling the exchange of critical information in a crisis. Earlier in the week I shared the importance of interoperable standards around validating the provenance of critical information during disaster relief efforts.</li><li><strong>Trust</strong>: there was much discussion throughout these sessions of the need to increase trust in the digital infrastructure and how openness, be it open source development or an open and royalty-free standards process such as we have at W3C, serves as a foundation for trust.</li><li><strong>Privacy</strong>: I don’t believe you can discuss identity, security, and trust without talking about privacy. In our privacy principles, W3C emphasizes the importance of individual autonomy and the need for user agents to adhere to privacy principles in order to ensure a trustworthy web.</li></ol><p>Ultimately, <strong>international standards can enable trustworthy solutions that support local control and security while providing a framework for global trust</strong>.</p><p>We at W3C play a critical role in making this happen. Because of our long standing focus on enabling one web for all, and our current composition representing industry leaders, big and small, from around the world, we have the potential to influence global discussions involving the web. Because the web is embedded in many different aspects of society throughout much of the world, there are many conversations outside of W3C that can impact how the web is used and even how the web is shaped. This was the first time W3C was formally represented at an event during the World Economic Forum and the opportunities that these conversations bring to us are invaluable.</p><p>It’s important for W3C to be involved in those conversations, in large part because of our knowledge and that <strong>we are a hub for major and minor implementers around the world</strong>. It’s also important that our values are represented in these discussions. The web is more than just technology - it’s technology with the fundamental purpose of interconnecting humanity. <strong>Our human-centric focus is distinct in the world of Standards Development Organizations and as such we need to be helping to shape the future of the web wherever we can.</strong></p><p>I made important contacts and already see opportunities for W3C to further step up, because If we don’t, there are plenty of other organizations, public and private, ready to fill the void to keep work needed by the world moving, but without the same dedication to our mission.</p>
310.            </div>
311.                <figure class="component component--image">
312.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/2025-01-seth-dobbs-davos.jpg" extension="jpg"             sizes="100vw"
313.            loading="lazy"
314.                            alt=""
315.                       />
316.            <figcaption>
317.            <p>Seth Dobbs posing in front of a House of Switzerland backdrop, WEF, Davos, January 2025</p>
318.        </figcaption>
319.    </figure>
320.    ]]></content:encoded>
321.      <slash:comments>0</slash:comments>
322.    </item>
323.    <item>
324.      <title>Collaborating across W3C and Ecma for web-interoperable server runtimes through WinterTC</title>
325.      <description><![CDATA[The W3C Web Interoperable Runtimes Community Group ("WinterCG") and Ecma International (the organization which standardizes ECMAScript, also known as JavaScript) have collaborated to create a new Ecma Technical Committee,TC55 – Web-interoperable server runtimes, dubbed "WinterTC", for the development of a common web-aligned API surface for server-side JavaScript runtimes like Node.js, Deno and Cloudflare Workers.]]></description>
326.      <pubDate>Fri, 10 Jan 2025 15:27:00 +0000</pubDate>
327.      <link>https://www.w3.org/blog/2025/collaborating-across-w3c-and-ecma-for-web-interoperable-server-runtimes-through-wintertc/</link>
328.      <guid>https://www.w3.org/blog/2025/collaborating-across-w3c-and-ecma-for-web-interoperable-server-runtimes-through-wintertc/</guid>
329.      <author>Luca Casonato (Deno, WinterCG co-chair, Ecma TC55 co-chair), Mike Smith (W3C staff, liaison to Ecma), Daniel Ehrenberg (Bloomberg, Ecma President)</author>
330.      <comments>https://www.w3.org/blog/2025/collaborating-across-w3c-and-ecma-for-web-interoperable-server-runtimes-through-wintertc/#comments</comments>
331.      <category><![CDATA[blogs]]></category>
332.      <dc:creator>Luca Casonato (Deno, WinterCG co-chair, Ecma TC55 co-chair), Mike Smith (W3C staff, liaison to Ecma), Daniel Ehrenberg (Bloomberg, Ecma President)</dc:creator>
333.      <content:encoded><![CDATA[            <div class="component component--text">
334.                    <p>The <a href="https://www.w3.org/community/wintercg/">W3C Web Interoperable Runtimes Community Group</a> ("WinterCG") and <a href="https://ecma-international.org">Ecma International </a>(the organization which standardizes ECMAScript, also known as JavaScript) have collaborated to create a new <a href="https://ecma-international.org/technical-committees/tc55/">Ecma Technical Committee</a>,<strong> TC55 – Web-interoperable server runtimes</strong>, dubbed "WinterTC", for the development of a common web-aligned API surface for server-side JavaScript runtimes like Node.js, Deno and Cloudflare Workers.</p><p>Developers these days are increasingly working “full-stack”, writing code for the client side (often web browsers) and the server side (often based on JavaScript). Reusing web platform APIs reduces developers’ cognitive load and allows some logic to be shared between client and server, or easily migrated from one to the other. This sharing is increasingly employed in technologies like server-side rendering (SSR) and server actions.</p><p>For the past two years, the W3C Web Interoperable Runtimes Community Group (“WinterCG”) has been working to strengthen the convergence of server JavaScript runtimes with the web platform by defining a common base for JavaScript in web-interoperable server environments.</p><p>WinterCG’s most prominent work item is the “<a href="https://github.com/wintercg/proposal-common-minimum-api">minimum common API</a>", which defines the subset of the web platform to be supported across all web-interoperable server environments. Further, WinterCG drives development on the web platform itself, as implemented in browsers, e.g., <a href="https://fetch.spec.whatwg.org/#ref-for-dom-response-json①">Response.json</a> and <a href="https://github.com/tc39/proposal-async-context/">AsyncContext</a>. WinterCG serves as a place to gather requirements from server environments, to be solved for and standardized in other existing standards venues, including Ecma International’s <a href="https://tc39.es">TC39</a>, <a href="https://whatwg.org">WHATWG</a> and various W3C Working Groups, when server and browser needs to align.</p><p>After incubating the “minimum common API” in WinterCG, the <strong>WinterCG participants decided to charter an Ecma Technical Committee, TC55 – Web-interoperable server runtimes</strong>, ("WinterTC"), which will host the effort to standardize this API. The cooperation between venues builds off of decades of experience collaborating between W3C and Ecma International on ECMAScript (a.k.a. JavaScript) and the web platform.</p><p>Once Ecma TC55/WinterTC is set up fully, all WinterCG work will move there and the existing community group will close. WinterTC's work with W3C is not over though: "<i>We still have a lot of work to do</i>", says Luca Casonato, previously co-chair of WinterCG and now co-chair of Ecma TC55/WinterTC. "<i>W3C is very central to the web platform, and a lot of the work from WinterCG touches existing web platform APIs. This means that Ecma TC55 participants and W3C will continue to work together closely.</i>"</p><p>Luca continues: "<i>The W3C Community Group programme enabled us to start work on unifying server side and web browser JavaScript very quickly. It is a great programme that I can recommend to anyone in a similar position to ours. We are very grateful to W3C for providing us with such an excellent home over the last couple years.</i>"</p><p>We encourage participation between W3C members and Ecma TC55 to further the development of a unified “full-stack” platform incorporating JavaScript and web technologies, across web servers and clients.</p><p>“<i>We are glad to see this work proceed from a W3C Community Group,</i>” said Philippe Le Hégaret, W3C Strategy and Project Lead. “<i>Congratulations to the Winter Community Group on chartering Ecma Technical Committee, TC55. We look forward to future collaborations with the W3C WebAppSec (WebCrypto API), WebApps (FileAPI), WebPerf (HR-TIME) and WebAssembly (WASM-*) Working Groups, to effectively address and meet the needs of the community</i>.”</p><p>"<i>Ecma is pleased to announce the formation of TC55 (Web-interoperable server runtimes), a collaborative effort with W3C that reflects our commitment to serving the community,</i>” said Samina Husain, Ecma International Secretary General. “<i>I commend W3C WinterCG for their dedication and foundational contributions, which have laid the groundwork for this important new technical committee in Ecma.</i>”</p><p>Learn more about <a href="https://wintertc.org">WinterTC</a> and Ecma's <a href="https://ecma-international.org/technical-committees/tc55/">TC55 website</a>, as well as announcements from <a href="https://ecma-international.org/news/collaborating-across-w3c-and-ecma-for-web-interoperable-server-runtimes-through-wintertc/">Ecma</a>, <a href=" https://igalia.com/2025/01/10/WinterCG-becomes-Ecma's-WinterTC.html">Igalia</a> and <a href="https://deno.com/blog/wintertc">Deno</a>.</p>
335.            </div>
336.    ]]></content:encoded>
337.      <slash:comments>0</slash:comments>
338.    </item>
339.    <item>
340.      <title>Happy holidays from the World Wide Web Consortium</title>
341.      <description><![CDATA[Discover the World Wide Web Consortium’s 30th anniversary year animated holiday card and read about some of the highlights of the year 2024 in W3C’s CEO Seth Dobbs’ blog post.]]></description>
342.      <pubDate>Wed, 18 Dec 2024 19:45:00 +0000</pubDate>
343.      <link>https://www.w3.org/blog/2024/happy-holidays-from-the-world-wide-web-consortium/</link>
344.      <guid>https://www.w3.org/blog/2024/happy-holidays-from-the-world-wide-web-consortium/</guid>
345.      <author>Seth Dobbs, W3C CEO and President</author>
346.      <comments>https://www.w3.org/blog/2024/happy-holidays-from-the-world-wide-web-consortium/#comments</comments>
347.      <category><![CDATA[corporate]]></category>
348.      <category><![CDATA[blogs]]></category>
349.      <dc:creator>Seth Dobbs, W3C CEO and President</dc:creator>
350.      <content:encoded><![CDATA[            <figure class="component component--video">
351.    <div class="l-frame l-frame--16-9">
352.                                                    <iframe src="https://www.w3.org/2024/12/EOY2024-anim.en.html?"></iframe>
353.                        </div>
354.    </figure>
355.                <div class="component component--text">
356.                    <p>As the year 2024 comes to an end, the Web Consortium presents our 30th anniversary year holiday card (click the still image for the animation) to once more express our gratitude:</p><blockquote><p>“With you, our W3C community, we have achieved a lot in the past 30 years and we look forward to many more opportunities to work together and continue to build a web that works, for everyone”</p></blockquote><p>Our card is available in the following languages, thanks to <a href="https://chapters.w3.org/">W3C Chapters</a> and our Team:</p><ul><li><a href="https://www.w3.org/2024/12/EOY2024-anim.en.html">English</a></li><li><a href="https://www.w3.org/2024/12/EOY2024-anim.ar-ma.html">Arabic</a></li><li><a href="https://www.w3.org/2024/12/EOY2024-anim.it.html">Italian</a></li><li><a href="https://www.w3.org/2024/12/EOY2024-anim.ja.html">Japanese</a></li><li><a href="https://www.w3.org/2024/12/EOY2024-anim.pt-br.html">Brazilian Portuguese</a></li><li><a href="https://www.w3.org/2024/12/EOY2024-anim.zh-hans.html">Simplified Chinese</a></li><li><a href="https://www.w3.org/2024/12/EOY2024-anim.zh-hant.html">Traditional Chinese</a></li></ul>
357.            </div>
358.                <figure class="component component--image">
359.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/EOY2024-still-en.png" extension="png"             sizes="100vw"
360.            loading="lazy"
361.                            alt=""
362.                       />
363.    </figure>
364.                <div class="component component--text">
365.                    <p>It has been nearly two years since W3C <a href="https://www.w3.org/press-releases/2023/w3c-le-launched/">re-launched</a> as a public-interest non-profit organization, and almost a year since I <a href="https://www.w3.org/press-releases/2023/w3c-welcomes-seth-dobbs-as-new-ceo/">joined as CEO</a> and President. As I pause to reflect, I wanted to share some of W3C’s notable highlights from 2024. As you’ll see, we demonstrated a lot of the “what” of W3C in really important ways, but the “who" was also a big focus as well as “for whom”.</p><h2>W3C 30th anniversary</h2><p>On the occasion of our 30th anniversary, we released a <a href="https://www.youtube.com/watch?v=0TfUBuIZkmQ">short animation</a> (clip <a href="https://www.youtube.com/watch?v=AA8EP5UPa-k&amp;t=0s">with audio description</a>) with select milestones for W3C and the Internet between 1989-2024. At W3C@30 we celebrated three decades of W3C and of advances in the web, by <a href="https://www.w3.org/2024/09/TPAC/w3c-30.html#memento">lining up a few speakers</a> who shared stories about the incredible impact of W3C standards on themselves or the world, and enjoyed ourselves during an authentic evening that culminated with a gala that was nice and cozy (as much as can be for several hundreds people). <a href="https://www.w3.org/2024/09/TPAC/w3c-30-gallery.html">Photos</a> are available.</p><h2>Expanding the W3C Team</h2><p>2024 was a big year as far as increasing the capability of the <a href="https://www.w3.org/2024/09/w3cteam.html">W3C Team</a>. The W3C Staff has remained consistently relatively small over the years but this year we hired 10 new persons and managed to fill a number of important roles, and to create new positions that are in line with the work we need to be doing for a web that better serves humanity.</p><ul><li>Ken Troshinsky (USA), hired in February as Chief Financial Officer</li><li>Simone Onofri (Spain), hired in February as Security Lead</li><li>Ken Franqueiro (USA), hired in May as accessibility technical specialist</li><li>Tamsin Ewing (New Zealand), hired in July as accessibility content specialist</li><li>Tara Whalen (Portugal), hired in July as Privacy Lead</li><li>Emma Fraser (USA), hired in July as Board enablement specialist</li><li>Tzviya Siegman (USA), hired in September to spearhead our work in Sustainability, and to handle Member relations in North America</li><li>Sylvia Cadena (Australia), hired in September as Chief Development Officer</li><li>Christine Gefaell (USA), hired in October as Director of Legal &amp; Compliance</li><li>Catrina Ahlbach (USA), hired in November as manager of the Office of the CEO</li></ul><p>I am proud in particular that we welcomed so many women to the Team this year and that we expanded even more the geographic and cultural diversity of our global Team.</p><p>Today the W3C Team operates primarily remotely and includes engineers and experts who work from 11 countries and across 12 time zones (Pacific/Auckland, Australia/Brisbane, Asia/Tokyo, Asia/Shanghai, Indian/Reunion, Europe/Athens, Europe/Madrid+Paris+Lisbon, Europe/London, America/New York, America/Chicago, America/Denver, America/Vancouver).</p><h2>Principles and goals for the web</h2><p>2024 was a year where W3C began to surface more of our guiding principles and goals for the web, with emphasis on the human impact of our work.</p><ul><li>Just last week we published as our first ever W3C Statement the <a href="https://www.w3.org/blog/tags/ewp/">Ethical Web Principles</a> which are as much a guide in ethical thinking for our work in the W3C community as they are across the web industry.</li><li>The document <a href="https://www.w3.org/news/2024/group-note-vision-for-w3c/">Vision for W3C</a> articulates W3C’s mission, what it does and why that matters, and the values and principles by which it operates and makes decisions.</li><li>W3C Team Member Dominique Hazaël-Massieux published a white paper on managing the impact of AI &amp; Machine Learning on the Web (<a href="https://www.w3.org/blog/2024/managing-the-impact-of-ai-machine-learning-on-the-web/">blog</a>)</li><li>W3C Team Member Simone Onofri wrote a white paper on the societal, ethical, and technical impacts of digital identities (<a href="https://www.w3.org/blog/2024/societal-ethical-and-technical-impacts-of-digital-identities/">blog</a>)</li><li>W3C Members chartered the S<a href="https://www.w3.org/blog/2023/introducing-web-sustainability-guidelines/">ustainable Web Interest Group</a> with a goal to improve digital sustainability so that the Web works better for all people and the planet.</li></ul><h2>Philanthropic external funding</h2><p>Further underscoring the importance of our impact on humanity, W3C was the recipient of a <a href="https://www.w3.org/press-releases/2024/w3c-web-accessibility-work-boosted-by-ford-foundation-core-funding/">major grant from the Ford Foundation</a> “as an investment in a more inclusive future.” This funding will go towards development of web accessibility standards, guidelines, and implementation resources to support access for people with disabilities.</p><p>Not only will this strengthen the foundations for our work in accessibility to continue and thrive in the long term, but it is also a boost to our development efforts as this is the first grant that we received since becoming a US public-interest non-profit organization.</p><h2>Vitality of the Consortium</h2><p>Finally, I want to share the following 2024 key figures:</p><ul><li>493 specifications are being actively developed, of which 284 are on the W3C Recommendation track (<a href="https://w3c.github.io/spec-dashboard/report.html">dashboard</a>)</li><li>W3C has 46 <a href="https://www.w3.org/groups/wg/">open working groups</a> and 11 <a href="https://www.w3.org/groups/ig/">open interest groups</a></li><li>To date, 1,955 <a href="https://www.w3.org/standards/stats/?startdate=2024-01-01&amp;enddate=2024-12-18">Technical Reports</a> have been published since 1 January 2024. Of those, 29 reached the status of W3C Recommendation, or, in other words became web standards. The first number is so big because about 1,800 of them were published as “draft”</li></ul><p>All in all, we’ve accomplished a lot together in 2024. At the same time we have laid the groundwork to face some of the challenges in front of us as we move into the new year and to create an even bigger impact on the world.</p>
366.            </div>
367.    ]]></content:encoded>
368.      <slash:comments>0</slash:comments>
369.    </item>
370.    <item>
371.      <title>W3C seeking community input for TAG appointment</title>
372.      <description><![CDATA[W3C is seeking community input between December 17 and January 5 for appointment to the W3C Technical Architecture Group (TAG), to complement the TAG election by actively seeking candidate appointees in order to support a diverse and well-balanced TAG, including diversity of technical background, knowledge, and skill sets.]]></description>
373.      <pubDate>Tue, 17 Dec 2024 00:00:00 +0000</pubDate>
374.      <link>https://www.w3.org/blog/2024/w3c-seeking-community-input-for-tag-appointment/</link>
375.      <guid>https://www.w3.org/blog/2024/w3c-seeking-community-input-for-tag-appointment/</guid>
376.      <author>Yves Lafon, W3C Team contact for the TAG, Coralie Mercier, Head of W3C Communications</author>
377.      <comments>https://www.w3.org/blog/2024/w3c-seeking-community-input-for-tag-appointment/#comments</comments>
378.      <category><![CDATA[corporate]]></category>
379.      <category><![CDATA[blogs]]></category>
380.      <dc:creator>Yves Lafon, W3C Team contact for the TAG, Coralie Mercier, Head of W3C Communications</dc:creator>
381.      <content:encoded><![CDATA[            <div class="component component--text">
382.                    <p>W3C is seeking input from the wider community for appointment to the <a href="https://www.w3.org/groups/other/tag/">W3C Technical Architecture Group</a> (TAG), having just released the <a href="https://www.w3.org/news/2024/w3c-advisory-committee-elects-technical-architecture-group/">election results</a>. Please, do share this post within your organization or with friends and colleagues who might be interested.&nbsp;</p><h2>Call to action</h2><p>Following the W3C Process Document's <a href="https://www.w3.org/2023/Process-20230612/#TAG-appointments">rules for the TAG appointees</a>, the W3C Team must complement the TAG election with actively seeking candidates for appointment to the TAG in order to support a <strong>diverse and well-balanced TAG, including diversity of technical background, knowledge, and skill sets</strong>.</p><p>This time, the W3C Team must appoint one individual. The term follows this election cycle and starts at appointment until 31 January 2027.</p><p>We have opened a mail address for an internal list that you can use to make suggestions for us to consider.&nbsp;</p><p>Please write <strong>by January 5, 2025 </strong>to our internal mailing list at <a href="mailto:nomination@w3.org">nomination@w3.org</a> to make suggestions, and tell us why. You may self-nominate or suggest other people. Please, be as specific but also as brief as you can.</p><p>Please, note two important aspects:</p><ul><li>The Process <a href="https://www.w3.org/policies/process/20231103/#AB-TAG-constraints">limits</a> participation in the TAG to no more than one individual with a primary affiliation to a given organization. Affiliations of the individuals on the TAG are: Apple, Samsung, Alibaba, Google, Huawei and Mozilla.</li><li>Appointees secure their own funding for TAG work, including travel.</li></ul><h3>Timeline</h3><p>During the window spanning 17 December 2024 - 1 February 2025, suggestions are made to –and assessed by– the W3C Team (including seeking willingness and financial ability to serve from individuals), and the W3C Team's choice is then subject to ratification by secret ballots by both the W3C Advisory Board and the TAG itself.</p><h2>Roles of the W3C TAG</h2><p>The <a href="https://www.w3.org/policies/process/20231103/#tag-role">TAG</a> was created in 2001 as a special W3C working group, chartered to steward the Web architecture. To do so, it fulfills 3 missions:</p><ul><li>to document and build consensus around principles of web architecture and to interpret and clarify these principles when necessary;</li><li>to resolve issues involving general web architecture brought to the TAG;</li><li>to help coordinate cross-technology architecture developments inside and outside W3C.</li></ul><p>The TAG is part of the <a href="https://www.w3.org/Guide/documentreview/">Horizontal Review Process</a> and reviews a large number of specifications done at W3C and outside, even during their early stage.</p><p>The TAG and the <a href="https://www.w3.org/groups/other/ab/">W3C Advisory Board</a> are also part of the <a href="https://www.w3.org/about/council/">W3C Council</a> to help resolve objections on specifications.</p><p>To be successful in these roles, the TAG needs to be well-balanced in its composition and individuals's complementary skills are highly valued. Effective work on the TAG is done because people demonstrate particular skills and interests in the following areas: understanding of web architecture, design review, diplomacy, chairing skills, cultural/social diversity, technical writing and copy editing, deep/broad technical knowledge.</p><h2>Participating as a TAG member</h2><p>Individuals elected or appointed to TAG act in their personal capacity, to serve the needs of the W3C membership as a whole, and the Web community. Whether they are Member representatives or Invited Experts, their activities in those roles are separate and distinct from their activities on the TAG. The TAG participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user. The participation commitment for the TAG includes:</p><ol><li>one teleconference per week,</li><li>three to four in-person meetings per year,</li><li>participation in TAG mailing list discussions,</li><li>participation at the two Advisory Committee meetings each year (encouraged, but not required).</li></ol>
383.            </div>
384.                <figure class="component component--image">
385.        <img src="https://www.w3.org/cms-uploads/imported-assets/news/_580xAUTO_crop_center-center_none/w3c-tag-new.png" extension="png"             sizes="100vw"
386.            loading="lazy"
387.                            alt=""
388.                       />
389.    </figure>
390.    ]]></content:encoded>
391.      <slash:comments>0</slash:comments>
392.    </item>
393.    <item>
394.      <title>Ethical Web Principles: Building a better web</title>
395.      <description><![CDATA[The Ethical Web Principles are a manifesto of W3C’s core values and principles. In this post, W3C Technical Architecture co-chair Dan Appelquist outlines how to go from words to action.]]></description>
396.      <pubDate>Mon, 16 Dec 2024 21:42:00 +0000</pubDate>
397.      <link>https://www.w3.org/blog/2024/ethical-web-principles-building-a-better-web/</link>
398.      <guid>https://www.w3.org/blog/2024/ethical-web-principles-building-a-better-web/</guid>
399.      <author>Daniel Appelquist, TAG co-chair</author>
400.      <comments>https://www.w3.org/blog/2024/ethical-web-principles-building-a-better-web/#comments</comments>
401.      <category><![CDATA[web-architecture]]></category>
402.      <category><![CDATA[blogs]]></category>
403.      <dc:creator>Daniel Appelquist, TAG co-chair</dc:creator>
404.      <content:encoded><![CDATA[            <div class="component component--text">
405.                    <p>The web has transformed our lives, connecting people, ideas, and communities across the globe. But the web can also cause harm. The way we design web features and technologies can either mitigate or enable that harm. Technology is not ethically or morally neutral. Our technical design choices are ethical choices, whether we like it or not. That’s why the W3C’s <a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a> are so important. I've been working on these principles <a href="https://www.torgo.com/blog/2019/03/we-need-a-more-ethical-web.html">since 2019</a> when I was inspired to start thinking about how we could apply an ethical framework to the way we develop web specifications. W3C published them last week as their <a href="https://www.w3.org/blog/2024/w3c-statement-on-ethical-web-principles-guides-the-community-to-build-a-better-web/">first W3C Statement</a>.</p><p>But principles alone aren’t enough. How do we make sure these ideals translate into real-world impact? At W3C, this happens through rigorous review processes—specifically wide review and <a href="https://github.com/w3ctag/design-reviews/">design review</a>.</p><h2>From words to action: How review processes enforce ethics</h2><p>Simply putting out a document with ethical principles can’t be the end of it. That is a route to “ethics washing”. Ethics washing refers to the practice of presenting ethical principles, commitments, or guidelines without implementing or enforcing them effectively, often to enhance public image or avoid criticism without making substantive changes. This concept is discussed critically in literature such as Elettra Bietti's paper, "<a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3513182">From Ethics Washing to Ethics Bashing: A View on Tech Ethics from Within Moral Philosophy</a>," published in the Proceedings of the ACM Conference on Fairness, Accountability, and Transparency (FAT* 2020). Elettra quite rightly calls out ethics washing (“shallow appearances of ethical behavior”) as a bad practice.</p><p>So how can we ensure that with the publication of the W3C Ethical Web Principles we are not falling into that trap? How can we embed these principles into the processes that shape the Web’s architecture?</p><p>Firstly, we need to recognize that the Ethical Web Principles were not created from nowhere. Hadley Beeman <a href="https://www.w3.org/blog/2019/our-ethics-drive-the-architecture-of-the-web/">pointed out in her 2019 post</a> on their first publication, these principles are reflecting how we already work. They are a reflection of the culture of the W3C community. The process of documenting them in simple, accessible language is a way to restate our assumptions, to recommit to the principles we already hold dear, and do so in one easily referenceable place.</p><p>Secondly, we need to infuse these principles into <a href="https://www.w3.org/Guide/documentreview/">wide review</a>. In W3C, we have both a culture and a process for wide review – the practice of ensuring work is reviewed across different web community stakeholders. W3C is a consensus-based organization, and you can’t achieve consensus without sharing your work with others, getting their feedback, and allowing that feedback to shape your work.</p><p>Within wide review, the Technical Architecture Group (TAG) performs <a href="https://github.com/w3ctag/design-reviews/">design review</a>, where groups come to us for architectural and design guidance. Along with providing technical design guidance, the TAG measures proposals against our core values like privacy, security, and accessibility—all of which are grounded in the Ethical Web Principles. If something doesn't look right, the TAG can—and often does—send it back to be reworked.</p><h2>Connecting principles to practice: Privacy and web platform design principles</h2><p>The Ethical Web Principles also inspire other guidance documents that provide more actionable advice, like the <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a> and <a href="https://www.w3.org/TR/privacy-principles/">Privacy Principles</a>. These documents translate the higher level principles into concrete advice for specification authors. Our first design principle, the priority of constituencies, states “put user needs first.” That guidance refers back to the Ethical Web Principles on not causing harm to society and enhancing individuals’ control and power.</p><p>This kind of practical guidance bridges the gap between ethics and execution, ensuring that our standards serve real-world needs without compromising core values.</p><h2>Centering human rights</h2><p>Ethics in web standards isn’t just about avoiding harm. It’s about actively building a web that works for everyone, grounded in respect for human rights. The W3C’s processes—wide review, design review, and actionable guidance—ensure the web remains a force for good. In a world where technology often undermines rights, the web can and must do better.</p><h2>A call to action for web developers and advocates</h2><p>The Ethical Web Principles are as much a guide in ethical thinking for our work in the W3C community as they are across the web industry. This isn’t a one-and-done effort. And we can’t do this alone. We need your help. If the Ethical Web Principles resonates with you, let it (and other relevant documents such as our <a href="https://www.w3.org/TR/privacy-principles/">privacy principles</a>) guide how you design web products and services. And while you’re at it, please get involved in web standards. Join a group. Comment on an issue. Add your voice. And call us out when it seems we’re not living up to our goals.</p>
406.            </div>
407.                <figure class="component component--image">
408.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/compass-map-denise-jans-IJy2ZUex0-Y-unsplash.jpg" extension="jpg"             sizes="100vw"
409.            loading="lazy"
410.                            alt=""
411.                       />
412.            <figcaption>
413.            <p>Photo by <a href="https://unsplash.com/@dmjdenise">Denise Jans</a> on <a href="https://unsplash.com/photos/round-brass-colored-compass-on-map-IJy2ZUex0-Y">Unsplash</a></p>
414.        </figcaption>
415.    </figure>
416.    ]]></content:encoded>
417.      <slash:comments>0</slash:comments>
418.    </item>
419.    <item>
420.      <title>W3C Statement on Ethical Web Principles guides the community to build a better web</title>
421.      <description><![CDATA[The Ethical Web Principles, which build on W3C’s core values and principles in the web and its architecture, are a call to action for the web industry and for W3C itself, aiming to deliver positive social outcomes. As we expand the web platform, we must consider the consequences of our work. As members of the web community, we each play a part in shaping its future.]]></description>
422.      <pubDate>Thu, 12 Dec 2024 07:23:00 +0000</pubDate>
423.      <link>https://www.w3.org/blog/2024/w3c-statement-on-ethical-web-principles-guides-the-community-to-build-a-better-web/</link>
424.      <guid>https://www.w3.org/blog/2024/w3c-statement-on-ethical-web-principles-guides-the-community-to-build-a-better-web/</guid>
425.      <author>Daniel Appelquist, TAG co-chair, Yves Lafon, W3C Team contact for the TAG</author>
426.      <comments>https://www.w3.org/blog/2024/w3c-statement-on-ethical-web-principles-guides-the-community-to-build-a-better-web/#comments</comments>
427.      <category><![CDATA[web-architecture]]></category>
428.      <category><![CDATA[blogs]]></category>
429.      <dc:creator>Daniel Appelquist, TAG co-chair, Yves Lafon, W3C Team contact for the TAG</dc:creator>
430.      <content:encoded><![CDATA[            <div class="component component--text">
431.                    <p>
432.    The web is a fundamental part of our lives, shaping how we work, connect, and learn. We understand that with this profound impact comes the responsibility to ensure that the web serves as a platform that benefits people and delivers positive social outcomes. As we continue to advance the web platform, we must therefore consider the consequences of our work.
433. </p>
434. <p>
435.    In response to this need, the W3C Technical Architecture Group (TAG) has published the <a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a> as a W3C Statement. This is the first <a href="https://www.w3.org/policies/process/#statement">W3C Statement</a> being published since the W3C Process Document introduced them in November 2021. W3C Statements provide a stable reference for documents not intended to be formal standards, but have been formally reviewed and are endorsed by W3C.
436. </p>
437. <p>
438.    The Ethical Web Principles are as much a guide in ethical thinking across the web industry as they are a guide for the work of the W3C community by providing a concise set of principles to assist spec developers, authors, and reviewers in their work. In particular, the purpose of this document is to inform the wide review of new charters, new specifications, candidate additions to published recommendations, and the development of actionable technical guidelines such as the <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a> and <a href="https://www.w3.org/TR/privacy-principles/">Privacy Principles</a>. Furthermore, the document outlines how we, as an organization, define the power and purpose of the web, from an ethical standpoint.
439. </p>
440. <p>
441.    These principles are not merely theoretical; they constitute a call to action. They encourage everyone involved in the web's evolution to assess their contributions' societal and environmental impacts. We can create a web that truly benefits everyone by adhering to these principles:
442. </p>
443. <ul>
444.    <li>
445.        There is one web
446.    </li>
447.    <li>
448.        The web does not cause harm to society
449.    </li>
450.    <li>
451.        The web supports healthy community and debate
452.    </li>
453.    <li>
454.        The web is for all people
455.    </li>
456.    <li>
457.        The web is secure and respects people's privacy
458.    </li>
459.    <li>
460.        The web enables freedom of expression
461.    </li>
462.    <li>
463.        The web makes it possible to verify information
464.    </li>
465.    <li>
466.        The web enhances individuals' control and power
467.    </li>
468.    <li>
469.        The web is an environmentally sustainable platform
470.    </li>
471.    <li>
472.        The web is transparent
473.    </li>
474.    <li>
475.        The web is multi-browser, multi-OS, and multi-device
476.    </li>
477.    <li>
478.        The web can be consumed in any way that people choose
479.    </li>
480. </ul>
481. <p>
482.    W3C has a long history that embeds its core values and principles in the web’s architecture. As members of the web community, we each play a part in shaping its future. The Ethical Web Principles remind us that the web extends beyond technology—it’s a reflection of the values we hold as a global society. Let us adopt this guide to enhance a web that connects and empowers us all.
483. </p>
484.            </div>
485.                <figure class="component component--image">
486.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/compass-map-denise-jans-IJy2ZUex0-Y-unsplash.jpg" extension="jpg"             sizes="100vw"
487.            loading="lazy"
488.                            alt=""
489.                       />
490.            <figcaption>
491.            <p>Photo by <a href="https://unsplash.com/@dmjdenise">Denise Jans</a> on <a href="https://unsplash.com/photos/round-brass-colored-compass-on-map-IJy2ZUex0-Y">Unsplash</a></p>
492.        </figcaption>
493.    </figure>
494.    ]]></content:encoded>
495.      <slash:comments>0</slash:comments>
496.    </item>
497.    <item>
498.      <title>AIOTI Workshop on Semantic Interoperability for Digital Twins at ERCIM</title>
499.      <description><![CDATA[the workshop will discuss Semantic interoperability - key to open ecosystems on the Web]]></description>
500.      <pubDate>Thu, 14 Nov 2024 08:00:00 +0000</pubDate>
501.      <link>https://www.w3.org/blog/2024/semantic-interoperability-key-to-open-ecosystems-on-the-web/</link>
502.      <guid>https://www.w3.org/blog/2024/semantic-interoperability-key-to-open-ecosystems-on-the-web/</guid>
503.      <author>Dave Raggett</author>
504.      <comments>https://www.w3.org/blog/2024/semantic-interoperability-key-to-open-ecosystems-on-the-web/#comments</comments>
505.      <category><![CDATA[workshop]]></category>
506.      <category><![CDATA[blogs]]></category>
507.      <dc:creator>Dave Raggett</dc:creator>
508.      <slash:comments>0</slash:comments>
509.    </item>
510.    <item>
511.      <title>Sustainable Web Interest Group is formed</title>
512.      <description><![CDATA[Announcement of the formation of the W3C Sustainable Web Interest Group.]]></description>
513.      <pubDate>Mon, 04 Nov 2024 14:26:00 +0000</pubDate>
514.      <link>https://www.w3.org/blog/2024/sustainable-web-interest-group-is-formed/</link>
515.      <guid>https://www.w3.org/blog/2024/sustainable-web-interest-group-is-formed/</guid>
516.      <author>Tzviya Siegman</author>
517.      <comments>https://www.w3.org/blog/2024/sustainable-web-interest-group-is-formed/#comments</comments>
518.      <category><![CDATA[sustainability]]></category>
519.      <category><![CDATA[blogs]]></category>
520.      <dc:creator>Tzviya Siegman</dc:creator>
521.      <slash:comments>0</slash:comments>
522.    </item>
523.    <item>
524.      <title>W3C 30th anniversary &amp; impressions on my first TPAC</title>
525.      <description><![CDATA[In this blog post, W3C CEO Seth Dobbs describes W3C’s 30th anniversary event, and shares his impressions after attending for the first time a W3C TPAC which attracts in a week several hundreds from the W3C community in order to coordinate solutions to web problems.]]></description>
526.      <pubDate>Wed, 23 Oct 2024 21:38:00 +0000</pubDate>
527.      <link>https://www.w3.org/blog/2024/w3c-30th-anniversary-impressions-on-my-first-tpac/</link>
528.      <guid>https://www.w3.org/blog/2024/w3c-30th-anniversary-impressions-on-my-first-tpac/</guid>
529.      <author>Seth Dobbs</author>
530.      <comments>https://www.w3.org/blog/2024/w3c-30th-anniversary-impressions-on-my-first-tpac/#comments</comments>
531.      <category><![CDATA[corporate]]></category>
532.      <category><![CDATA[blogs]]></category>
533.      <dc:creator>Seth Dobbs</dc:creator>
534.      <content:encoded><![CDATA[            <figure class="component component--image">
535.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/IMGP7100-cake-by-atsushi-medium.jpeg" extension="jpeg"             sizes="100vw"
536.            loading="lazy"
537.                            alt=""
538.                       />
539.            <figcaption>
540.            <p>W3C 30th anniversary cake. Photo by Atsushi Shimono, W3C</p>
541.        </figcaption>
542.    </figure>
543.                <div class="component component--text">
544.                    <p>I returned from my first W3C TPAC week energized and thoroughly impressed by the drive and the strong sense of community.</p><p>TPAC is our annual, now-hybrid meeting, where most W3C work groups meet amongst themselves or jointly, to coordinate solutions and resolve challenging technical and social issues that the Web faces. <a href="https://www.w3.org/2024/09/TPAC/">TPAC 2024</a> was the 24th edition of that popular and well-attended yearly event. 845 attended in total, with 549 at the in-person hub in Anaheim, California (USA) and 296 remotely. We used 15 to 17 separate meeting rooms each day at once and held a total of 191 meetings that week. 87 of them were part of the Breakouts day on Wednesday, dedicated to sessions organized by TPAC participants themselves.</p><p>I wish to come back to the incredible spirit of community that I felt throughout the week but one moment stood out. Our event was disrupted on day 2 by a two-hour power outage that affected the entire block. Rather than being upset, one of several paths were followed - some people in our group helped ensure others were safe and accounted for (in particular those in wheelchairs), some found spaces to continue working, some took it as a salutary break. One of our attendees who had arrived that day saw the room he was in get dark just as he plugged his computer and thought he had caused it. Others joked that the power cut was a radical way to pause the jack-hammering that was taking place as part of the hotel renovation - another unfortunate source of disruption in some meeting rooms.</p><p>I had a lot of conversations with members via zoom and in person, in the hallways, during breaks and meals. While some concerns about our future and the future of the web were voiced, there is a clear expression of optimism across our community, and genuine commitment to making the web work for everyone.</p><p>Another highlight of the week was the celebration of the 30th anniversary of W3C (the actual anniversary falls on the first day of October). We carved out time at the end of Wednesday for inspirational talks and a gala. It was a great celebration. After kick-starting the Talks with a <a href="https://www.w3.org/2024/09/TPAC/w3c-30.html#memento">short anniversary video</a> spanning 1989-2024 with milestones for W3C and the Internet, I spoke about the challenges we’ve overcome to bring the web to where it is today and the challenges in front of us. We’ve changed the world and will continue to.</p><p>I really enjoyed the other <a href="https://www.w3.org/2024/09/TPAC/w3c-30.html#program">speakers</a> covering the past, present, and future. We focused on celebrating our community, and on our impact on humanity.</p><p>The gala dinner gave members an opportunity to make a toast, or share their gratitude to the community. Food and company was excellent and the atmosphere was friendly and relaxed. The cake arrived. It was splendid and delicious, it turned out. I asked to be joined for the cutting by Tatsuya Igarashi, the representative from Sony (one of the few organizations to be a Member since W3C’s founding in 1994), and by David Singer of Apple, the outgoing Chair of the W3C Board of Directors whose last W3C event it was now that he is retiring. And like any good party, most stayed late and the hotel staff had to kick us out of the veranda lest we kept the hotel guests from sleeping.</p>
545.            </div>
546.                <figure class="component component--image">
547.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/IMGP7131-cutting-cake-by-atsushi-medium.jpeg" extension="jpeg"             sizes="100vw"
548.            loading="lazy"
549.                            alt=""
550.                       />
551.            <figcaption>
552.            <p>Tatsuya Igarashi (Sony), David W. Singer (Apple), Seth Dobbs (W3C) cutting the cake. Photo by Atsushi Shimono, W3C</p>
553.        </figcaption>
554.    </figure>
555.                <div class="component component--text">
556.                    <p>The week also saw us have our first W3C Team Day in over a decade. We used the opportunity that so many of our staff were present for TPAC to spend an extra day with <a href="https://www.w3.org/2024/09/w3cteam.html">each other</a>. And we were able to include during most of our activities and via video conferencing all the Team members who had not been able to attend in person. For many of us, not just new folks like myself, this was the first time that people were meeting each other in person. It was a great opportunity to connect / reconnect and build the bonds needed to do the challenging but captivating work that we’re involved in.</p><p>All in all I returned home exhausted but energized and confident in our consortium’s collective ability to face whatever comes next.</p>
557.            </div>
558.    ]]></content:encoded>
559.      <slash:comments>0</slash:comments>
560.    </item>
561.    <item>
562.      <title>Reflections on TPAC 2024 Breakouts</title>
563.      <description><![CDATA[In this post, the staff who organize TPAC breakout sessions share thoughts on the topics covered this year and some feedback received so far.]]></description>
564.      <pubDate>Wed, 16 Oct 2024 14:49:00 +0000</pubDate>
565.      <link>https://www.w3.org/blog/2024/reflections-on-tpac-2024-breakouts/</link>
566.      <guid>https://www.w3.org/blog/2024/reflections-on-tpac-2024-breakouts/</guid>
567.      <author>Ian Jacobs, François Daoust</author>
568.      <comments>https://www.w3.org/blog/2024/reflections-on-tpac-2024-breakouts/#comments</comments>
569.      <category><![CDATA[blogs]]></category>
570.      <dc:creator>Ian Jacobs, François Daoust</dc:creator>
571.      <content:encoded><![CDATA[            <div class="component component--text">
572.                    <p>At <a href="https://www.w3.org/2024/09/TPAC/">TPAC 2024</a>, this year's edition of W3C’s big annual meeting, attendees proposed a <a href="https://www.w3.org/2024/09/TPAC/breakouts.html#America/Los_Angeles">record number of breakouts (87)</a> compared to 69 in 2023. We identified some prominent themes among the sessions:</p><ul><li>AI</li><li>Identity</li><li>Wallets</li><li>Web Apps</li><li>Web Components</li><li>Feature lifecycle</li><li>Permissions</li><li>Real-time Web</li></ul><p>There were many other sessions on both technical topics and ideas for improving incubation and standardization at W3C. We invite you to check out the agendas, minutes, and slide decks available from the <a href="https://www.w3.org/2024/09/TPAC/breakouts.html">breakouts page</a>.</p><p>As is the custom, we survey TPAC attendees and have already heard both enthusiasm for this year's breakouts and ideas to improve them. Here's a sample of support:</p><ul><li>"At first I was overwhelmed by the many breakout sessions, but it didn't take me long to determine which I wanted to attend. These were excellent, and a great way to get people to mix together and discuss a broad range of things. I particularly loved the Web on the Moon session in the afternoon."</li><li>"The breakouts are the best part of TPAC and I wish there was more space for them."</li><li>"Very dense, very useful, many conflicts to manage because of many interesting sessions."</li><li>"Breakouts were great, and there was only one instance where two sessions I wanted to attend conflicted."</li></ul><p>It is easy to detect in these encouraging comments (hand-selected for this post, yes, but also representative) a recurring theme: the number of sessions in parallel created conflicts. We wrestled with that issue in the planning phases. We anticipated over 500 attendees (which came true) and chose to allocate enough breakout rooms to accommodate them. We ended up with 15 sessions in parallel during each time slot, which created ample choice for some and conflicts for others.</p><p>We have some ideas for improving the situation. For example, we want to enable all TPAC attendees to participate in breakouts, but we recognize that, in practice, not all of them do. We think we can improve our strategy so that we schedule fewer sessions during a given time slot without overcrowding rooms or turning people away.</p><p>Several people have suggested that we add more breakout sessions to other days of the week, which would help, but involves other tradeoffs because traditionally groups want enough time for their meetings on other days.</p><p>After TPAC 2023, we also heard feedback about attendee conflicts, so we organized our first <a href="https://www.w3.org/2024/03/breakouts-day-2024/">fully remote, non-TPAC Breakouts Day</a> in March 2024 to handle some of the overflow; see the <a href="https://www.w3.org/blog/2024/breakouts-day-2024-recap/">related blog post</a>. We anticipate organizing a similar event in early 2025.</p><p>Beyond scheduling considerations, we have also received (and continue to receive) suggestions for other enhancements, including making time for follow-up discussions for some of the breakouts later in the week, making it easier to organize one's breakouts day experience, and providing more guidance to session chairs. We look forward to hearing other suggestions (<a href="https://github.com/w3c/tpac-breakouts/issues">via GitHub issues</a>) to improve breakouts for attendees and encourage topics that are most relevant to the community.</p>
573.            </div>
574.    ]]></content:encoded>
575.      <slash:comments>0</slash:comments>
576.    </item>
577.    <item>
578.      <title>On the 55th World Standards Day, my history of the Web and relationship with W3C</title>
579.      <description><![CDATA[In this blog post, W3C's Head of Marketing and Communications Coralie Mercier shares a recent filmed interview for W3C Member Igalia on the history of the Web, and reflects on the importance of standards and how they are done in the very long run.]]></description>
580.      <pubDate>Mon, 14 Oct 2024 13:25:00 +0000</pubDate>
581.      <link>https://www.w3.org/blog/2024/on-the-55th-world-standards-day-my-history-of-the-web-and-relationship-with-w3c/</link>
582.      <guid>https://www.w3.org/blog/2024/on-the-55th-world-standards-day-my-history-of-the-web-and-relationship-with-w3c/</guid>
583.      <author>Coralie Mercier</author>
584.      <comments>https://www.w3.org/blog/2024/on-the-55th-world-standards-day-my-history-of-the-web-and-relationship-with-w3c/#comments</comments>
585.      <category><![CDATA[blogs]]></category>
586.      <dc:creator>Coralie Mercier</dc:creator>
587.      <content:encoded><![CDATA[            <div class="component component--text">
588.                    <p>Today is the 55th <a href="https://en.wikipedia.org/wiki/World_Standards_Day">World Standards Day</a>. The first one was declared in 1970. It is still relevant today and worthy to honor the efforts of the many individuals and organizations who develop voluntary standards. Standards are blueprints for systems and technology to operate as seamlessly as possible.<br>Standards are instrumental globally both at the social and economic levels. Standardization is the development by consensus of technologies, techniques, systems and processes which aim to maximize compatibility, interoperability, safety, repeatability, or quality.</p><p>W3C is a standards development organization (SDO) which launched in 1994 -- 30 years ago. We celebrated <a href="https://www.w3.org/2024/09/TPAC/w3c-30.html">W3C's 30th anniversary</a> a week in advance this year, taking advantage of our community gathering for our yearly conference, TPAC 2024, where our work groups coordinate solutions and resolve challenging technical and social issues that the Web faces.</p><p>In <a href="https://www.w3.org/standards/stats/?startdate=1994-10-01&amp;enddate=2024-10-14">30 years W3C published</a> 14254 technical reports for 518 web standards. The rest is standards-to-be all at different milestones of maturity, notes which are informational documents, registries or superseded documents because all technologies evolve and improve.</p><p>In 1946 when 25 countries decided to form the International Organization for Standardization (ISO) my parents were toddlers. In 1970 when the first World Standards Day was celebrated I wasn't yet born. In 1994 when W3C was launched by Web inventor Tim Berners-Lee I was a student. I joined W3C in 1999 and its mission and values shaped the person I became.&nbsp;</p><p>My point is that standardization is in-depth work that is done in the very long run. Standards are everywhere, ubiquitous, almost like utilities. They are so low-level that for the most part people are made aware of them only when they are controversial, fragmented or do not work. Part of my job in the W3C Communications Team is to ensure that key parties are aware of the Web standards work of the Web Consortium so that they can participate.</p><p>A few weeks ago, I was asked to talk about (my) history of the web and my relationship with the World Wide Web Consortium. Brian Kardell on behalf of W3C Member Igalia hosted and filmed the <a href="https://www.igalia.com/chats/coralie ">interview</a> which aired late last week. I was delighted by the favorable timing which would see this "Igalia Chat" released the same month W3C celebrates its 30th anniversary.</p><p>I hesitated to accept the invitation because I didn't think I had a lot to contribute, given that I joined W3C only thanks to my good fortune, and given that unlike so many in the Web and Internet community I took a non-traditional discovery path. But Brian being an excellent host, he coaxed out of me a lot more than I was aware I knew. So many memories resurfaced! For example did you know the 1998 soccer World Cup was streamed live, in ASCII, over Telnet? I watched it!</p><p>Parts of the interview are a bit personal, but I shared with Brian some of my favorite thoughts and hopes for W3C.</p><p>My history of the Web starts at the discovery of a URL in 1995 on the back of a Sony Music CD, at making friends over IRC in 1996, then learning LaTeX in 1998 before learning HTML in the early 2000s while at W3C to work on and for the Web.</p><p>My relationship with W3C started in late 1998 at a job interview that I had not prepared for because I had little hope to be hired, but which turned out to be massively interesting. I got the job in January 1999 and today, 25 years after, I've held many roles within the organization and today still I continue to advocate internally about the things I care about for the Web and what as a public-interest organization the Web Consortium must do to better connect humanity.</p><p>Of my early "W3C years", we talked about Napster, Netscape Composer, Blogger, My.Opera, Blosxom, MovableType, WordPress, CSS, W3C's annual conference TPAC which I helped organize for many years, Social media and Mastodon, Identi.ca, a few pivotal moments for W3C, including the creation of Community Groups to significantly expand how web features could be incubated and put on the "fast track" for standardization. We took a trip back to 1994 to explain why W3C was set up the way it was, and then Brian and I could reminisce on why we had met in the first place 10 years ago: attempting to create a Membership tier with a reasonable fee allowing individuals to become W3C Members without paying the same fee as a small organization. Fast forward to 2023, W3C incorporated as a 501(c)(3) in the US, becoming officially the public-interest non-profit organization that it's always been. This is where I'm treading a bit of uncharted waters: after being a vocal proponent internally of doing more for Web sustainability and human rights, it would seem like there are opportunities for W3C's meaningful work to be complemented which may be coming to fruition in the near term.</p><p>If you watch/listen I hope you learn something!<br>&nbsp;</p>
589.            </div>
590.                <figure class="component component--video">
591.    <div class="l-frame l-frame--16-9">
592.                                                    <iframe width="200" height="113" src="https://www.youtube-nocookie.com/embed/5sCmpE_v9aA?feature=oembed"  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen="" title="History&#x20;of&#x20;Web&#x20;BlinkOn&#x20;19&#x3A;&#x20;Coralie&#x20;Mercier"></iframe>
593.                        </div>
594.            <figcaption>
595.                            <p>Igalia's Brian Kardell chats with the Head of W3C Marketing & Communications, Coralie Mercier about the her history and relationship with the Web and the W3C.</p>
596.                                        <a href="https://www.igalia.com/chats/coralie">Read transcript <span class="visuallyhidden">for History of Web BlinkOn 19: Coralie Mercier</span></a>
597.                    </figcaption>
598.    </figure>
599.    ]]></content:encoded>
600.      <slash:comments>0</slash:comments>
601.    </item>
602.    <item>
603.      <title>Accessibility education and outreach: Another milestone in W3C's 30-year history and evolution</title>
604.      <description><![CDATA[As W3C celebrates 30 years, we also celebrate the success of the Accessibility Education and Outreach Working Group (EOWG), share news of its closure, and look forward to a new chapter in W3C accessibility work.]]></description>
605.      <pubDate>Thu, 19 Sep 2024 19:02:00 +0000</pubDate>
606.      <link>https://www.w3.org/blog/2024/accessibility-education-and-outreach-another-milestone-in-w3cs-30-year-history-and-evolution/</link>
607.      <guid>https://www.w3.org/blog/2024/accessibility-education-and-outreach-another-milestone-in-w3cs-30-year-history-and-evolution/</guid>
608.      <author>Shawn Lawton Henry</author>
609.      <comments>https://www.w3.org/blog/2024/accessibility-education-and-outreach-another-milestone-in-w3cs-30-year-history-and-evolution/#comments</comments>
610.      <category><![CDATA[accessibility]]></category>
611.      <category><![CDATA[blogs]]></category>
612.      <dc:creator>Shawn Lawton Henry</dc:creator>
613.      <content:encoded><![CDATA[            <div class="component component--text">
614.                    <p>As W3C celebrates 30 years, we also celebrate the success of the Accessibility Education and Outreach Working Group (EOWG), share news of its closure, and look forward to a new chapter in W3C accessibility work.</p><h2 id="impact">EOWG impact</h2><p>When W3C launched the <a href="https://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a> way back in 1997, the web community had little awareness of accessibility. In 1998, W3C chartered the Education and Outreach Working Group (EOWG) with a mission to develop strategies and materials to increase awareness of the need for web accessibility, and educate the community on web accessibility solutions. EOWG's mission evolved over the years to develop strategies and resources to promote awareness, understanding, implementation, and conformance testing for W3C accessibility standards; and to support the accessibility work of other W3C Groups.</p><p>It's now 25 years later and accessibility is an integral part of the web. EOWG was part of that evolution.</p><p>EOWG crafted a body of resources that fill a vital role in understanding the need for accessibility, in the adoption of W3C's accessibility standards around the world, and in accessibility implementation throughout a wide range of environments. To highlight a few:</p><ul><li><a href="https://www.w3.org/WAI/people-use-web/">How people with disabilities use the web</a></li><li><a href="https://www.w3.org/WAI/tips/">Tips for getting started designing, writing, and developing for accessibility</a></li><li><a href="https://www.w3.org/WAI/tutorials/">Tutorials</a> covering page structure, menus, images, tables, carousels, and forms</li><li><a href="https://www.w3.org/WAI/media/av/">Making audio and video media accessible</a></li><li><a href="https://www.w3.org/WAI/planning-and-managing/">Planning and managing web accessibility</a></li><li><a href="https://www.w3.org/WAI/test-evaluate/preliminary/">Easy checks – a first review of web accessibility</a></li><li>those listed in <a href="https://www.w3.org/WAI/fundamentals/">Accessibility fundamentals overview</a> and <a href="https://www.w3.org/WAI/roles/">Resources for roles</a> including for managers, testers, policy makers, and educators</li></ul><p>EOWG has also:</p><ul><li>Supported the accessibility work of other W3C Groups, for example, significantly contributing to the approach and content design of the <a href="https://www.w3.org/WAI/test-evaluate/conformance/wcag-em/">Website Accessibility Conformance Evaluation Methodology (WCAG-EM)</a></li><li>Developed tools such as the <a href="https://www.w3.org/WAI/WCAG22/quickref/">How to Meet WCAG (Quick Reference)</a>, <a href="https://www.w3.org/WAI/eval/report-tool/">WCAG-EM Report Tool: Website Accessibility Evaluation Report Generator</a>, and <a href="https://www.w3.org/WAI/planning/statements/">Accessibility Statement Generator</a></li><li>Supported W3C-wide accessibility, for example, developing <a href="https://www.w3.org/WAI/teach-advocate/accessible-presentations/">Making Events Accessible: Checklist for meetings, conferences, training, and presentations that are remote/virtual, in-person, or hybrid</a></li></ul><p>EOWG resources have been viewed millions of times and are used in a wide range of contexts, including governments, universities, and industry. EOWG resources have been <a href="https://www.w3.org/WAI/translations/">translated into multiple languages</a>.</p><h2 id="structure">Structure for W3C's accessibility education and outreach work</h2><p>Web accessibility has evolved and W3C's options for group work have evolved. While most W3C Members strongly support W3C's continued work on accessibility education and outreach, there is insufficient Membership support for the work in a Working Group.</p><p>After much deliberation, we made the difficult decision not to propose re-chartering the Working Group in 2024 and we will be closing EOWG. Several former EOWG participants are already contributing through other WAI Working Groups and Task Forces.</p><p><strong>Be assured that W3C's accessibility education and outreach work will continue!</strong></p><ul><li>Existing and new WAI staff, including a full-time <a href="https://www.w3.org/staff/#tamsin">accessibility content specialist</a>, will update and develop accessibility resources and expand outreach. This staff work is funded by a grant and non-Member funds.</li><li>We will encourage collaboration and vetting through the new <a href="https://www.w3.org/groups/cg/adva11yresources/">Advancing Accessibility Resources Community Group</a>. The W3C Community Group model has several advantages, including that participation is open to anyone. You can join!</li><li>We will seek input through GitHub, through user studies, and through the existing <a href="https://www.w3.org/WAI/about/groups/waiig/">WAI Interest Group (IG)</a> mailing lists. You can subscribe to the Announcements list to learn about drafts for review.</li></ul><h2 id="thanks">Thank you EO</h2><p>As an Invited Expert, Chair, W3C Team Contact, and Editor for EOWG over nearly 23 years, I (<a href="https://www.w3.org/People/Shawn/">Shawn</a>) am proud of all that the Group accomplished. Please join me in heartfelt thanks to:</p><ul><li>Co-Chairs: Sharron Rush, Brent Bakken, Kris Anne Kinney, Brian Elton; and the first Chair: Judy Brewer</li><li>Editors: Shadi Abou-Zahra, Eric Eggert, Kevin White, Daniel Montalvo, Andrew Arch, Hidde de Vries, Sharron Rush, and others listed in the footer of each resource</li><li><a href="https://www.w3.org/groups/wg/eowg/former-participants/">EOWG participants</a> who contributed their valuable time, knowledge, and perspectives</li></ul><p>EOWG has been a positive, supportive group with plenty of laughs along the way. Among the many resources the group developed collaboratively are videos that illustrate:</p><ul><li><a href="https://www.w3.org/WAI/perspective-videos/">Accessibility: Essential for some, useful for all</a></li><li><a href="https://www.w3.org/WAI/people-use-web/user-stories/">Accessibility: It's about people</a></li><li><a href="https://www.w3.org/WAI/planning/involving-users/#video">The importance of involving users in web projects</a></li></ul><h2 id="next">EO next</h2><p>W3C's accessibility education and outreach work continues. We look forward to this next chapter in the evolution to support W3C's mission that humanity can experience all that the web has to offer. We will continue working to make the web and related technologies accessible so that people with disabilities around the globe can participate equally in the digital world.</p><p>We invite you to learn more about all of W3C's accessibility work and how you can contribute:</p><ul><li>Read <a href="https://www.w3.org/WAI/update/">What We're Working On - Accessibility Activities and Publications</a></li><li>Subscribe to <a href="https://www.w3.org/WAI/news/subscribe/">Get WAI News</a></li></ul><p><strong>Onward!</strong></p>
615.            </div>
616.    ]]></content:encoded>
617.      <slash:comments>0</slash:comments>
618.    </item>
619.    <item>
620.      <title>Web Security: shaping the secure Web</title>
621.      <description><![CDATA[In this blog post, W3C CEO Seth Dobbs explains why and how Web Security as a requirement for humanity is central to W3C’s mission, mentions digital identities and credentials as a high-stake current focus, and invites all to participate.]]></description>
622.      <pubDate>Wed, 21 Aug 2024 12:14:00 +0000</pubDate>
623.      <link>https://www.w3.org/blog/2024/web-security-shaping-the-secure-web/</link>
624.      <guid>https://www.w3.org/blog/2024/web-security-shaping-the-secure-web/</guid>
625.      <author>Seth Dobbs</author>
626.      <comments>https://www.w3.org/blog/2024/web-security-shaping-the-secure-web/#comments</comments>
627.      <category><![CDATA[privacy-and-security]]></category>
628.      <category><![CDATA[blogs]]></category>
629.      <dc:creator>Seth Dobbs</dc:creator>
630.      <content:encoded><![CDATA[            <figure class="component component--image">
631.        <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/shutterstock_2414670395-woman-hands-smartphone-idcard-overlay-1920px.jpg" extension="jpg"             sizes="100vw"
632.            loading="lazy"
633.                            alt=""
634.                       />
635.    </figure>
636.                <div class="component component--text">
637.                    <p>Continuing the <a href="/blog/tags/ceo/">series</a> that puts the emphasis on the key areas that help ensure that the Web works, for everyone, this month I am diving into Web security. It is one of the key areas that we call “horizontals” and that shape every W3C work package because they involve approaches that are common to all work groups. Our horizontals are <a href="https://www.w3.org/mission/accessibility/">Web accessibility</a>, <a href="https://www.w3.org/mission/internationalization/">internationalization</a>, <a href="https://www.w3.org/mission/security/">security</a> and <a href="https://www.w3.org/mission/privacy/">privacy</a>.&nbsp;</p><h2>The imperative</h2><p>A technology isn’t truly beneficial to humanity if it isn’t safe, and security standards are an essential aspect of ensuring the Web is safe.</p><p>Security, along with Privacy, are integral to <a href="https://www.un.org/en/about-us/universal-declaration-of-human-rights">human rights</a> and <a href="https://www.ohchr.org/en/instruments-mechanisms/instruments/international-covenant-civil-and-political-rights">civil liberties</a> and have long been important in the World Wide Web Consortium's agenda. W3C has a long history of improving Web security and our work has been instrumental through the development of authentication technologies that can replace weak passwords and help mitigate threats from phishing and similar attacks.</p><p>Security is essential to our digital lives as appropriate measures can create trust between people, organizations, businesses, and governments, and while advances on the web make it easier for people to interconnect, this results in a wider attack surface for servers. In other words, the more ways you allow people to interact with your site and products, the more ways bad actors have of attacking.<br>As users we want to engage with what we trust. We want to ensure our information, our money, and other resources aren’t stolen. We want to make sure we are interacting with who we really think we’re interacting with. As a provider of information, service, or product on the web we want to ensure that we reduce risks and costs, and that we increase trust and strengthen our reputation.</p><h2>How W3C approaches Security</h2><p>We follow a recipe that is simple but which details are of importance:</p><ol><li>Develop security technology standards</li><li>Review the security of web standards</li><li>Guide Web Developers to design and develop in a secure manner</li></ol><p>At the heart of developing the right security standards is threat modeling, which enables the creation of living documents that identify cross-areas threats and mitigations and provide information on residual risks, and in turn frame and guide technical specifications.</p><p>We are in the process of elevating the conduct of reviews from a pool of volunteers to a chartered group, called the <a href="https://github.com/w3c/strategy/issues/449">Security Interest Group (SING)</a> whose charter the W3C Members are currently assessing as part of approving the group. With a mission to improve Security on the Web by advising groups developing standards on how to avoid and mitigate security issues with their technologies, the Security Interest Group would also suggest changes to existing standards and technologies to improve the security of existing systems.</p><p>Last February, we welcomed to the W3C Team our new Security Lead, <a href="https://www.w3.org/staff/#sonofri">Simone Onofri</a>. Among the many projects he set into place, he helped launch a cross-organization group, called the <a href="https://www.w3.org/groups/cg/swag/">Security Web Application Guidelines (SWAG) Community Group</a>, to guide Web developers and ensure a holistic approach to security through the edition of web creators security best practices and providing a platform for stakeholder collaboration (e.g., OpenSSF, OWASP, Open Web Docs, etc.)</p><h2>In focus: Digital Identities</h2><p>In recent years we've seen the emergence of the paradigm of decentralized identity and credentials, where users have a digital wallet and control over their identity. All sectors, from social networks and education to enterprises and governments worldwide are considering becoming providers and consumers, with the intention to have digital credentials that are more secure and privacy-preserving than physical ones.</p><p>Given the societal, ethical, and technical impacts, Simone and the W3C Team wrote a paper on Digital Identities on the Web. "Identity &amp; the Web" analyzes through different use cases the systemic impact on both the market side and the human side, as well as the role that Web standardization may play in managing that impact. We <a href="https://www.w3.org/blog/2024/societal-ethical-and-technical-impacts-of-digital-identities/">published the report</a> this month and are looking forward to charting a credible and safe path to strengthen the position of the Web during this rapid evolution phase of the information ecosystem.</p><h2>Key players</h2><p>I want to conclude by emphasizing that as a horizontal area, Web Security matters to most and that most can be key players. Whether you are an independent developer or work for an organization that develops products or services, or are a user, your participation in <a href="https://www.w3.org/mission/security/">Web Security</a> can make a difference and will be meaningful: contributing to a Web that works for all humanity.</p>
638.            </div>
639.    ]]></content:encoded>
640.      <slash:comments>0</slash:comments>
641.    </item>
642.  </channel>
643. </rss>
644.  

Home · About · News · Docs · Terms