<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"> <channel> <language>en</language> <title>W3C - News</title> <description>W3C News</description> <pubDate>Mon, 07 Apr 2025 06:13:20 +0000</pubDate> <generator>Laminas_Feed_Writer 2 (https://getlaminas.org)</generator> <link>https://www.w3.org/news/</link> <atom:link rel="self" type="application/rss+xml" href="https://www.w3.org/news/feed/"/> <item> <title>Draft Note: RDF 1.2 Primer</title> <description><![CDATA[This primer is designed to provide the reader with the basic knowledge required to effectively use RDF.]]></description> <pubDate>Thu, 03 Apr 2025 05:30:00 +0000</pubDate> <link>https://www.w3.org/news/2025/draft-note-rdf-1-2-primer/</link> <guid>https://www.w3.org/news/2025/draft-note-rdf-1-2-primer/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/rdf-star/">RDF-star Working Group</a> has published a first <a href="https://www.w3.org/standards/types/#DNOTE">Draft Note</a> of <a href="https://www.w3.org/TR/2025/DNOTE-rdf12-primer-20250403/">RDF 1.2 Primer</a>. This primer is designed to provide the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and shows concrete examples of the use of RDF. Secs. 3-5 can be used as a minimalist introduction into the key elements of RDF. Changes between RDF 1.1 and RDF 1.2 are summarized in a separate document: <a href="https://w3c.github.io/rdf-new/spec/">What’s New in RDF 1.2</a>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Authorized Translation of WCAG 2.2 in Brazilian Portuguese</title> <description><![CDATA[W3C published the Authorized Brazilian Portuguese Translation of Web Content Accessibility Guidelines (WCAG) 2.2, Diretrizes de Acessibilidade para Conteúdo Web (WCAG) 2.2.]]></description> <pubDate>Thu, 27 Mar 2025 07:18:00 +0000</pubDate> <link>https://www.w3.org/news/2025/authorized-translation-of-wcag-2-2-in-brazilian-portuguese/</link> <guid>https://www.w3.org/news/2025/authorized-translation-of-wcag-2-2-in-brazilian-portuguese/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <figure class="component component--image"> <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/wcag-intro-social.png" extension="png" sizes="100vw" loading="lazy" alt="Screenshot showing the w3c logo and the title of the W3C WCAG 2 Web Content Accessibility Guidelines" /> </figure> <div class="component component--text"> <p>The World Wide Web Consortium (W3C) published the Authorized Brazilian Portuguese Translation of Web Content Accessibility Guidelines (WCAG) 2.2, <a href="https://www.w3.org/Translations/WCAG22-pt-BR/">Diretrizes de Acessibilidade para Conteúdo Web (WCAG) 2.2</a>. The Lead Translation Organization for this Authorized Translation was <a href="https://ceweb.br">Ceweb.br</a>.</p><p>Other translations of accessibility resources — including non-technical and educational resources — are listed in <a href="https://www.w3.org/WAI/translations/">All WAI Translations</a>.</p><p>W3C Web Accessibility Initiative (<a href="https://www.w3.org/WAI/">WAI</a>) particularly encourages the development of Authorized Translations of WCAG 2.2 and other technical specifications to facilitate their adoption and implementation internationally. For information on developing an Authorized Translation, please see <a href="https://www.w3.org/2005/02/TranslationPolicy">Policy for Authorized W3C Translations</a>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Updated W3C Recommendation: EPUB 3.3</title> <description><![CDATA[This specification defines the authoring requirements for EPUB 3 publications and represents the third major revision of the standard.]]></description> <pubDate>Thu, 27 Mar 2025 06:50:00 +0000</pubDate> <link>https://www.w3.org/news/2025/updated-w3c-recommendation-epub-3-3/</link> <guid>https://www.w3.org/news/2025/updated-w3c-recommendation-epub-3-3/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/pm/">Publishing Maintenance Working Group</a> has published an updated <a href="https://www.w3.org/TR/2025/REC-epub-33-20250327/">EPUB 3.3 Recommendation</a>. EPUB® 3 defines a distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file container. This specification defines the authoring requirements for EPUB 3 publications and represents the third major revision of the standard. The update includes a number of minor changes, primarily to clarify some details on the conformance requirements of EPUB 3 documents.</p><p>The Working Group has also published three First Public Working Drafts: <a href="https://www.w3.org/TR/2025/WD-epub-34-20250327/">EPUB 3.4</a>, <a href="https://www.w3.org/TR/2025/WD-epub-rs-34-20250327/">EPUB Reading Systems 3.4</a>, and <a href="http://www.w3.org/TR/2025/WD-epub-a11y-111-20250327/">EPUB Accessibility 1.1.1</a>. These drafts will eventually evolve into the next major version of the EPUB 3 standard (EPUB 3.4). 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> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>First Public Working Draft: CSS Form Control Styling Level 1</title> <description><![CDATA[This CSS Module defines various ways of styling form controls and their different parts.]]></description> <pubDate>Tue, 25 Mar 2025 07:31:00 +0000</pubDate> <link>https://www.w3.org/news/2025/first-public-working-draft-css-form-control-styling-level-1/</link> <guid>https://www.w3.org/news/2025/first-public-working-draft-css-form-control-styling-level-1/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/css/">CSS Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2025/WD-css-forms-1-20250325/">CSS Form Control Styling Level 1</a>. This CSS Module defines various ways of styling form controls and their different parts.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>First Public Working Draft: ContentEditable</title> <description><![CDATA[This specification defines allowed values and expected behaviors for the contentEditable attribute. This specification builds on HTML.]]></description> <pubDate>Tue, 25 Mar 2025 07:30:00 +0000</pubDate> <link>https://www.w3.org/news/2025/first-public-working-draft-contenteditable/</link> <guid>https://www.w3.org/news/2025/first-public-working-draft-contenteditable/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/webediting/">Web Editing Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2025/WD-content-editable-20250325/">ContentEditable</a>, a collection of proposals developed by the group. Some of these proposals are further defined in <a href="https://www.w3.org/TR/edit-context/">EditContext API</a>, which supersedes this document. The Working Group ceased work on this specification in 2022 prior to publishing a First Public Working Draft (FPWD). This FPWD is intended to archive the prior work. Following the publication of this FPWD the Working Group intends to publish this document as a <a href="https://www.w3.org/policies/process/#discontinuedREC">Discontinued Draft</a> and cease further work on it. This does not affect the definition of <code>contenteditable=true</code>, <code>contenteditable=false</code> and <code>contenteditable=plaintext-only</code> as they can be found in [<a href="https://html.spec.whatwg.org/multipage/" title="HTML Standard">HTML</a>]. Nor does it affect <code>execCommand</code> which is described in <a href="https://w3c.github.io/editing/docs/execCommand/">another unofficial draft document</a>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Seven Proposed Recommendations published by the Verifiable Credentials Working Group</title> <description><![CDATA[The Verifiable Credentials Working Group published Verifiable Credentials Data Model v2.0, Verifiable Credential Data Integrity 1.0, Data Integrity EdDSA Cryptosuites v1.0, Data Integrity ECDSA Cryptosuites v1.0, Securing Verifiable Credentials using JOSE and COSE, Controlled Identifiers v1.0 and Bitstring Status List v1.0 as W3C Proposed Recommendations.]]></description> <pubDate>Thu, 20 Mar 2025 07:33:00 +0000</pubDate> <link>https://www.w3.org/news/2025/seven-proposed-recommendations-published-by-the-verifiable-credentials-working-group/</link> <guid>https://www.w3.org/news/2025/seven-proposed-recommendations-published-by-the-verifiable-credentials-working-group/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>Today the <a href="https://www.w3.org/groups/wg/vc/">Verifiable Credentials Working Group</a> published the following seven documents as W3C Proposed Recommendations:</p><ul><li><a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/">Verifiable Credentials Data Model v2.0</a>: A <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-verifiable-credential">verifiable credential</a> is a specific way to express a set of <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-claims">claims</a> made by an <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-issuers">issuer</a>, such as a driver's license or an education certificate. This specification describes the extensible data model for <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-verifiable-credential">verifiable credentials</a>, how they can be secured from tampering, and a three-party ecosystem for the exchange of these credentials that is composed of <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-issuers">issuers</a>, <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-holders">holders</a>, and <a href="https://www.w3.org/TR/2025/PR-vc-data-model-2.0-20250320/#dfn-verifier">verifiers</a>. This document also covers a variety of security, privacy, internationalization, and accessibility considerations for ecosystems that use the technologies described in this specification.</li><li><a href="https://www.w3.org/TR/2025/PR-vc-data-integrity-20250320/">Verifiable Credential Data Integrity 1.0</a>: This specification describes mechanisms for ensuring the authenticity and integrity of <a href="https://www.w3.org/TR/vc-data-model-2.0/#dfn-verifiable-credential">verifiable credentials</a> and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.</li><li><a href="https://www.w3.org/TR/2025/PR-vc-di-eddsa-20250320/">Data Integrity EdDSA Cryptosuites v1.0</a>: This specification describes Data Integrity cryptographic suites for use when creating or verifying a digital signature using the Ed25519 instantiation of the Edwards-Curve Digital Signature Algorithm (EdDSA).</li><li><a href="https://www.w3.org/TR/2025/PR-vc-di-ecdsa-20250320/">Data Integrity ECDSA Cryptosuites v1.0</a>: This specification describes Data Integrity cryptosuites for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA).</li><li><a href="https://www.w3.org/TR/2025/PR-vc-jose-cose-20250320/">Securing Verifiable Credentials using JOSE and COSE</a>: This specification defines how to secure credentials and presentations conforming to the <a href="https://www.w3.org/TR/vc-data-model-2.0/">Verifiable Credential data model</a> with <a href="https://datatracker.ietf.org/wg/jose/about/">JSON Object Signing and Encryption</a>, <a href="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-selective-disclosure-jwt">Selective Disclosure for JWTs</a>, and <a href="https://www.rfc-editor.org/rfc/rfc9052">CBOR Object Signing and Encryption (COSE)</a>. This enables the Verifiable Credential data model [VC-DATA-MODEL-2.0] to be implemented with standards for signing and encryption that are widely adopted.</li><li><a href="https://www.w3.org/TR/2025/PR-cid-1.0-20250320/">Controlled Identifiers v1.0</a>: A controlled identifier document contains cryptographic material and lists service endpoints for the purposes of verifying cryptographic proofs from, and interacting with, the controller of an identifier.</li><li><a href="https://www.w3.org/TR/2025/PR-vc-bitstring-status-list-20250320/">Bitstring Status List v1.0</a>: This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials through use of bitstrings.</li></ul> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>First Public Working Drafts: SHACL 1.2 Core and SHACL 1.2 SPARQL Extensions</title> <description><![CDATA[SHACL 1.2 Core defines the Core of the SHACL Shapes Constraint Language. SHACL 1.2 SPARQL Extensions defines SPARQL-related extensions of the SHACL Shapes Constraint Language.]]></description> <pubDate>Tue, 18 Mar 2025 07:46:00 +0000</pubDate> <link>https://www.w3.org/news/2025/first-public-working-drafts-shacl-1-2-core-and-shacl-1-2-sparql-extensions/</link> <guid>https://www.w3.org/news/2025/first-public-working-drafts-shacl-1-2-core-and-shacl-1-2-sparql-extensions/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/data-shapes/">Data Shapes Working Group</a> has published the following two First Public Working Drafts:</p><ul><li><a href="https://www.w3.org/TR/2025/WD-shacl12-core-20250318/">SHACL 1.2 Core</a>: This document defines the Core of the SHACL Shapes Constraint Language. SHACL is a language for validating RDF graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph. RDF graphs that are used in this manner are called "shapes graphs" in SHACL and the RDF graphs that are validated against a shapes graph are called "data graphs". As SHACL shape graphs are used to validate that data graphs satisfy a set of conditions they can also be viewed as a description of the data graphs that do satisfy these conditions. Such descriptions may be used for a variety of purposes beside validation, including user interface building, code generation and data integration.</li><li><a href="https://www.w3.org/TR/2025/WD-shacl12-sparql-20250318/">SHACL 1.2 SPARQL Extensions</a>: This document defines SPARQL-related extensions of the SHACL Shapes Constraint Language. While the Core part of SHACL defines the basic syntax of shapes and the most common constraint components supported by SHACL, the SPARQL-related extensions cover features that extend the expressiveness of Core by means of SPARQL. In particular, this document defines how constraints and constraint components can be defined using SPARQL.</li></ul> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>DPub-ARIA 1.1 and DPub-AAM 1.1 are W3C Proposed Recommendations</title> <description><![CDATA[Today the Accessible Rich Internet Applications Working Group published Digital Publishing WAI-ARIA Module 1.1 and Digital Publishing Accessibility API Mappings 1.1 as W3C Proposed Recommendations.]]></description> <pubDate>Tue, 18 Mar 2025 07:14:00 +0000</pubDate> <link>https://www.w3.org/news/2025/dpub-aria-1-1-and-dpub-aam-1-1-are-w3c-proposed-recommendations/</link> <guid>https://www.w3.org/news/2025/dpub-aria-1-1-and-dpub-aam-1-1-are-w3c-proposed-recommendations/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>Today the <a href="https://www.w3.org/groups/wg/aria/">Accessible Rich Internet Applications Working Group</a> published the following two documents as W3C Proposed Recommendations:</p><ul><li><a href="https://www.w3.org/TR/2025/PR-dpub-aria-1.1-20250318/">Digital Publishing WAI-ARIA Module 1.1</a>: Enabling users of assistive technologies to find their way through web content requires embedding semantic metadata about web document structural divisions. This is particularly important for structural divisions of long-form documents and goes along with embedding semantic metadata about web-application widgets and behaviors for assistive technologies. This specification defines a set of WAI-ARIA roles specific to helping users of assistive technologies navigate through such long-form documents. This document is part of the WAI-ARIA suite described in the <a href="https://www.w3.org/WAI/standards-guidelines/aria/">WAI-ARIA Overview</a>.</li><li><a href="https://www.w3.org/TR/2025/PR-dpub-aam-1.1-20250318/">Digital Publishing Accessibility API Mappings 1.1</a> defines how <a href="https://infra.spec.whatwg.org/#user-agent">user agents</a> map the <a href="https://www.w3.org/TR/dpub-aria-1.1/">Digital Publishing WAI-ARIA Module</a> markup to platform <a href="https://www.w3.org/TR/wai-aria/#dfn-accessibility-api">accessibility APIs</a>. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.</li></ul> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Authorized Translation of WCAG 2.2 in French</title> <description><![CDATA[W3C published the Authorized French Translation of Web Content Accessibility Guidelines (WCAG) 2.2, Règles pour l’accessibilité des contenus Web (WCAG) 2.2.]]></description> <pubDate>Mon, 17 Mar 2025 07:16:00 +0000</pubDate> <link>https://www.w3.org/news/2025/authorized-translation-of-wcag-2-2-in-french/</link> <guid>https://www.w3.org/news/2025/authorized-translation-of-wcag-2-2-in-french/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <figure class="component component--image"> <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/wcag-intro-social.png" extension="png" sizes="100vw" loading="lazy" alt="Screenshot showing the w3c logo and the title of the W3C WCAG 2 Web Content Accessibility Guidelines" /> </figure> <div class="component component--text"> <p>The World Wide Web Consortium (W3C) published the Authorized French Translation of Web Content Accessibility Guidelines (WCAG) 2.2, <a href="https://www.w3.org/Translations/WCAG22-fr/">Règles pour l’accessibilité des contenus Web (WCAG) 2.2</a>. The Lead Translation Organization for this Authorized Translation was <a href="https://access42.net">Access42</a>.&nbsp;</p><p>Other translations of accessibility resources — including non-technical and educational resources — are listed in <a href="https://www.w3.org/WAI/translations/">All WAI Translations</a>.&nbsp;</p><p>W3C Web Accessibility Initiative (<a href="https://www.w3.org/WAI/">WAI</a>) particularly encourages the development of Authorized Translations of WCAG 2.2 and other technical specifications to facilitate their adoption and implementation internationally. For information on developing an Authorized Translation, please see <a href="https://www.w3.org/2005/02/TranslationPolicy">Policy for Authorized W3C Translations</a>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Updated W3C Recommendation: WebRTC: Real-Time Communication in Browsers</title> <description><![CDATA[The WebRTC API allows media and generic application data to be sent to and received from another browser or device implementing the appropriate set of real-time protocols.]]></description> <pubDate>Thu, 13 Mar 2025 07:21:00 +0000</pubDate> <link>https://www.w3.org/news/2025/updated-w3c-recommendation-webrtc-real-time-communication-in-browsers/</link> <guid>https://www.w3.org/news/2025/updated-w3c-recommendation-webrtc-real-time-communication-in-browsers/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/webrtc/">Web Real-Time Communications Working Group</a> has published <a href="https://www.w3.org/TR/2025/REC-webrtc-20250313/">WebRTC: Real-Time Communication in Browsers</a> as an updated W3C Recommendation. This document defines a set of ECMAScript APIs in WebIDL to allow media and generic application data to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Updated Candidate Recommendation: Portable Network Graphics (PNG) Specification (Third Edition)</title> <description><![CDATA[This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of static and animated raster images.]]></description> <pubDate>Thu, 13 Mar 2025 07:08:00 +0000</pubDate> <link>https://www.w3.org/news/2025/updated-candidate-recommendation-portable-network-graphics-png-specification-third-edition/</link> <guid>https://www.w3.org/news/2025/updated-candidate-recommendation-portable-network-graphics-png-specification-third-edition/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/png/">Portable Network Graphics (PNG) Working Group</a> invites implementations of an updated Candidate Recommendation Snapshot of <a href="https://www.w3.org/TR/2025/CR-png-3-20250313/">Portable Network Graphics (PNG) Specification (Third Edition)</a>. This document describes PNG (Portable Network Graphics), an extensible file format for the <a href="https://www.w3.org/TR/2025/CR-png-3-20250313/#dfn-lossless">lossless</a>, portable, well-compressed storage of static and animated raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. <a href="https://www.w3.org/TR/2025/CR-png-3-20250313/#3indexedColour">Indexed-color</a>, <a href="https://www.w3.org/TR/2025/CR-png-3-20250313/#dfn-greyscale">greyscale</a>, and <a href="https://www.w3.org/TR/2025/CR-png-3-20250313/#3truecolour">truecolor</a> images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits.</p><p>PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store color space data for improved color matching on heterogeneous platforms.</p><p>This specification defines two Internet Media Types, image/png and image/apng.</p><p>Comments are welcome via the <a href="https://github.com/w3c/png/">GitHub issues</a> by <strong>13 May 2025</strong>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>W3C invites implementations of Dubbing and Audio description Profiles of TTML2</title> <description><![CDATA[This specification defines DAPT, a TTML-based file format for the exchange of timed text content in dubbing and audio description workflows.]]></description> <pubDate>Tue, 11 Mar 2025 09:25:00 +0000</pubDate> <link>https://www.w3.org/news/2025/w3c-invites-implementations-of-dubbing-and-audio-description-profiles-of-ttml2/</link> <guid>https://www.w3.org/news/2025/w3c-invites-implementations-of-dubbing-and-audio-description-profiles-of-ttml2/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/timed-text/">Timed Text Working Group</a> has published <a href="https://www.w3.org/TR/2025/CR-dapt-20250311/">Dubbing and Audio description Profiles of TTML2</a> as a W3C Candidate Recommendation. This document defines DAPT, a TTML-based file format for the exchange of timed text content in dubbing and audio description workflows.&nbsp;</p><p>Comments are welcome via <a href="https://github.com/w3c/dapt/issues">GitHub issues</a> by <strong>8 April 2025</strong>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>For Review: Accessibility Roles and Responsibilities Mapping (ARRM)</title> <pubDate>Thu, 06 Mar 2025 19:48:00 +0000</pubDate> <link>https://www.w3.org/news/2025/for-review-accessibility-roles-and-responsibilities-mapping-arrm/</link> <guid>https://www.w3.org/news/2025/for-review-accessibility-roles-and-responsibilities-mapping-arrm/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p><a href="https://www.w3.org/WAI/planning/arrm/">Accessibility Roles and Responsibilities Mapping (ARRM)</a> is published as a first draft Web Accessibility Initiative (WAI) resource. ARRM helps your team create more accessible digital products and services. ARRM provides an approach for defining roles, tasks, and responsibilities for meeting Web Content Accessibility Guidelines (<a href="https://www.w3.org/WAI/standards-guidelines/wcag/">WCAG</a>). If you would like to be involved in developing ARRM, we encourage you to join the <a href="/community/arrm/">ARRM Community Group</a>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>CSS Snapshot 2024 Published as W3C Group Note</title> <description><![CDATA[This document collects together into one definition all the specifications that together form the current state of Cascading Style Sheets (CSS) as of 2024.]]></description> <pubDate>Tue, 25 Feb 2025 07:40:00 +0000</pubDate> <link>https://www.w3.org/news/2025/css-snapshot-2024-published-as-w3c-group-note/</link> <guid>https://www.w3.org/news/2025/css-snapshot-2024-published-as-w3c-group-note/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/css/">CSS Working Group</a> published the <a href="https://www.w3.org/TR/2025/NOTE-css-2024-20250225/">CSS Snapshot 2024</a> as a Group Note. This document collects together into one definition all the specifications that together form the current state of Cascading Style Sheets (CSS) as of 2024. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.&nbsp;</p><p>When the first CSS specification was published, all of CSS was contained in one document that defined CSS Level 1. CSS Level 2 was defined also by a single, multi-chapter document. However for CSS beyond Level 2, the CSS Working Group chose to adopt a modular approach, where each module defines a part of CSS, rather than to define a single monolithic specification. This breaks the specification into more manageable chunks and allows more immediate, incremental improvement to CSS.&nbsp;</p><p>Since different CSS modules are at different levels of stability, the CSS Working Group has chosen to publish this profile to define the current scope and state of Cascading Style Sheets as of 2024.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Upcoming: Authentic Web mini-workshop series - session 1</title> <description><![CDATA[W3C is working on a deconstructed mini-workshop series to review proposals to combat misinformation on the web.]]></description> <pubDate>Thu, 20 Feb 2025 07:19:00 +0000</pubDate> <link>https://www.w3.org/news/2025/upcoming-authentic-web-mini-workshop-series-session-1/</link> <guid>https://www.w3.org/news/2025/upcoming-authentic-web-mini-workshop-series-session-1/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>W3C is working on a deconstructed mini-workshop series to review proposals aimed at combating misinformation on the web. Based on discussions at TPAC 2024 (<a href="https://github.com/w3c/tpac2024-breakouts/issues/90">Originator Profile</a> and <a href="https://github.com/w3c/tpac2024-breakouts/issues/70">Content Authenticity</a>) and in the <a href="https://github.com/w3c/strategy/issues/483">W3C Strategy Team</a>, there is clear interest in investigating how several proposals in this space can contribute and what standardization support they might need.&nbsp;</p><p>The <a href="https://www.w3.org/community/credibility/">Credible Web Community Group</a> will host this deconstructed mini-workshop series to discuss a project framework for assessing tooling in the authentic web ecosystem. The first session, scheduled for <strong>12 March 2025</strong>, will review the framework and discuss how to move proposals to interoperable standards to combat misinformation on the web.&nbsp;</p><p>Attendance is free for all participants and is open to the public, whether or not W3C members.</p><p>Visit <a href="https://www.w3.org/events/workshops/2025/authentic-web-workshop/">here</a> for more details.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>W3C Team appointment to the TAG ratified</title> <description><![CDATA[Lola Odelola is appointed as new TAG member by the W3C Team]]></description> <pubDate>Thu, 30 Jan 2025 16:49:00 +0000</pubDate> <link>https://www.w3.org/news/2025/w3c-team-appointment-to-the-tag-ratified/</link> <guid>https://www.w3.org/news/2025/w3c-team-appointment-to-the-tag-ratified/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <figure class="component component--image"> <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/w3c-tag-new.png" extension="png" sizes="100vw" loading="lazy" alt="" /> </figure> <div class="component component--text"> <p>Following the <a href="https://www.w3.org/2001/tag/">W3C Technical Architecture Group</a> (TAG)'s election <a href="https://www.w3.org/news/2024/w3c-advisory-committee-elects-technical-architecture-group/">results</a>, the W3C Team has chosen and the Advisory Board and Technical Architecture Group have ratified the following appointment to the TAG for the 2025-2027 term:<br><strong>Lola Odelola (unaffiliated W3C Invited Expert)</strong></p><p>Among the individuals the W3C Team considered, Lola particularly stands out due to her connections with the developer community and her involvement in making web development available to under-represented parts of the community. Lola also has experience in W3C Working Groups and is an open source contributor.</p><p>Per W3C Process Document regarding <a href="https://www.w3.org/policies/process/20231103/#TAG-appointments">TAG appointments</a>, this procedure follows a <a href="https://www.w3.org/blog/2024/w3c-seeking-community-input-for-tag-appointment/">public call for nominations</a> which together with nominations from the W3C Team and Members surfaced a list of several traditional and non-traditional candidates. The Team considered what each on the list would bring to the TAG. In addition to the aspects mentioned in Process, the Team considered cultural diversity and gender diversity.</p><p>The Team is confident Lola Odelola brings robust complementary skills to the TAG and thanks her for offering her time to do the important TAG work of stewarding the Web architecture.</p><h3>About the W3C TAG</h3><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/2002/ab/">W3C Advisory Board</a> are also part of the <a href="https://www.w3.org/policies/process/20231103/#council">W3C Council</a> to help resolve objections on specifications.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>W3C invites implementations of Controlled Identifiers (CIDs) v1.0</title> <description><![CDATA[A controlled identifier document contains cryptographic material and lists service endpoints for the purposes of verifying cryptographic proofs from, and interacting with, the controller of an identifier.]]></description> <pubDate>Thu, 30 Jan 2025 08:04:00 +0000</pubDate> <link>https://www.w3.org/news/2025/w3c-invites-implementations-of-controlled-identifiers-cids-v1-0/</link> <guid>https://www.w3.org/news/2025/w3c-invites-implementations-of-controlled-identifiers-cids-v1-0/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/vc">Verifiable Credentials Working Group</a> invites implementations of the following Candidate Recommendation Snapshot: <a href="https://www.w3.org/TR/2025/CR-cid-1.0-20250130/">Controlled Identifiers (CIDs) v1.0</a>.</p><p>A controlled identifier document contains cryptographic material and lists service endpoints for the purposes of verifying cryptographic proofs from, and interacting with, the controller of an identifier.</p><p>Comments are welcome via <a href="https://github.com/w3c/cid/issues/">GitHub issues</a> by 28 February 2025.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>First Public Working Draft: Decentralized Identifiers (DIDs) v1.1</title> <description><![CDATA[This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent.]]></description> <pubDate>Tue, 28 Jan 2025 08:42:00 +0000</pubDate> <link>https://www.w3.org/news/2025/first-public-working-draft-decentralized-identifiers-dids-v1-1/</link> <guid>https://www.w3.org/news/2025/first-public-working-draft-decentralized-identifiers-dids-v1-1/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p> The <a href="https://www.w3.org/groups/wg/did">Decentralized Identifier Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2025/WD-did-1.1-20250128/">Decentralized Identifiers (DIDs) v1.1</a>. This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent. </p> <p> Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. They may refer to any subject and have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities, so as to enable the controller of a DID to prove control over it without requiring permission from any other party. </p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Collaboration Tools Accessibility User Requirements Published as W3C Group Note</title> <description><![CDATA[The document covers accessibility user needs, requirements, and scenarios for collaborative content creation and development tools.]]></description> <pubDate>Tue, 21 Jan 2025 06:03:00 +0000</pubDate> <link>https://www.w3.org/news/2025/collaboration-tools-accessibility-user-requirements-published-as-w3c-group-note/</link> <guid>https://www.w3.org/news/2025/collaboration-tools-accessibility-user-requirements-published-as-w3c-group-note/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The Accessible Platform Architectures (<a href="https://www.w3.org/groups/wg/apa/">APA</a>) Research Questions Task Force (<a href="https://www.w3.org/groups/tf/rqtf/">RQTF</a>) published <a href="https://www.w3.org/TR/ctaur/">Collaboration Tools Accessibility User Requirements</a> as a W3C Group Note. The document covers accessibility user needs, requirements, and scenarios for collaborative content creation and development tools. The solutions identified in this document are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are also relevant to software developers who contribute to developing the collaborative experience.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Draft Note: String Searching</title> <description><![CDATA[This document describes string searching operations on the Web in order to allow greater interoperability.]]></description> <pubDate>Tue, 07 Jan 2025 07:26:00 +0000</pubDate> <link>https://www.w3.org/news/2025/draft-note-string-searching/</link> <guid>https://www.w3.org/news/2025/draft-note-string-searching/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/i18n-core/">Internationalization Working Group</a> has published a first Draft Note of <a href="https://www.w3.org/TR/2025/DNOTE-string-search-20250107/">String Searching</a>. This document describes string searching operations on the Web in order to allow greater interoperability. String searching refers to natural language string matching such as the "find" command in a Web browser. This document builds upon the concepts found in <a href="https://www.w3.org/TR/charmod/">Character Model for the World Wide Web 1.0: Fundamentals</a> and <a href="https://www.w3.org/TR/charmod-norm/">Character Model for the World Wide Web 1.0: String Matching</a> to provide authors of specifications, software developers, and content developers the information they need to describe and implement search features suitable for global audiences.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Last Call for Review of Proposed Corrections to EPUB 3.3</title> <description><![CDATA[This specification defines the authoring requirements for EPUB publications and represents the third major revision of the standard.]]></description> <pubDate>Tue, 07 Jan 2025 07:14:00 +0000</pubDate> <link>https://www.w3.org/news/2025/last-call-for-review-of-proposed-corrections-to-epub-3-3/</link> <guid>https://www.w3.org/news/2025/last-call-for-review-of-proposed-corrections-to-epub-3-3/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/pm/">Publishing Maintenance Working Group</a> has proposed corrections to the W3C Recommendation of <a href="https://www.w3.org/TR/2025/REC-epub-33-20250107/">EPUB 3.3</a>. EPUB® 3 defines a distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file container. This specification defines the authoring requirements for <a href="https://www.w3.org/TR/2025/REC-epub-33-20250107/#dfn-epub-publication">EPUB publications</a> and represents the third major revision of the standard.</p><p>Proposed corrections are marked in the document. Comments, including implementation experience, are welcome via <a href="https://github.com/w3c/epub-specs/issues/">GitHub</a> through <strong>10 March 2025</strong>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>W3C Invites Implementations of WebGPU</title> <description><![CDATA[The GPU for the Web Working Group invites implementations of the first Candidate Recommendation Snapshots for WebGPU and WebGPU Shading Language.]]></description> <pubDate>Thu, 19 Dec 2024 09:02:00 +0000</pubDate> <link>https://www.w3.org/news/2024/w3c-invites-implementations-of-webgpu/</link> <guid>https://www.w3.org/news/2024/w3c-invites-implementations-of-webgpu/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/gpu/">GPU for the Web Working Group</a> invites implementations of the first Candidate Recommendation Snapshots for the following documents:</p><ul><li><a href="https://www.w3.org/TR/2024/CR-webgpu-20241219/">WebGPU</a>: Graphics Processing Units, or GPUs for short, have been essential in enabling rich rendering and computational applications in personal computing. WebGPU is an API that exposes the capabilities of GPU hardware for the Web. The API is designed from the ground up to efficiently map to (post-2014) native GPU APIs.</li><li><a href="https://www.w3.org/TR/2024/CR-WGSL-20241219/">WebGPU Shading Language</a>, also known as WGSL for short: An application using the WebGPU API uses WGSL to express the programs, known as shaders, that run on the GPU. The shading language is tailored for parallel execution and usage on the Web.</li></ul><p>Comments are welcome via <a href="https://github.com/gpuweb/gpuweb/issues">GitHub issues</a> by <strong>28 February 2025</strong>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>First Public Working Draft: CSS Display Module Level 4</title> <description><![CDATA[This module describes how the CSS formatting box tree is generated from the document element tree and defines the 'display' property that controls it.]]></description> <pubDate>Thu, 19 Dec 2024 06:13:00 +0000</pubDate> <link>https://www.w3.org/news/2024/first-public-working-draft-css-display-module-level-4/</link> <guid>https://www.w3.org/news/2024/first-public-working-draft-css-display-module-level-4/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/css/">CSS Working Group</a> has published the First Public Working Draft of <a href="https://www.w3.org/TR/2024/WD-css-display-4-20241219/">CSS Display Module Level 4</a>. This module describes how the CSS formatting box tree is generated from the document element tree and defines the <a class="property css" href="https://www.w3.org/TR/2024/WD-css-display-4-20241219/#propdef-display">display</a> property that controls it.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>First Public Working Draft: CSS Multi-column Layout Module Level 2</title> <description><![CDATA[This specification describes multi-column layouts in CSS, a style sheet language for the web.]]></description> <pubDate>Thu, 19 Dec 2024 06:12:00 +0000</pubDate> <link>https://www.w3.org/news/2024/first-public-working-draft-css-multi-column-layout-module-level-2/</link> <guid>https://www.w3.org/news/2024/first-public-working-draft-css-multi-column-layout-module-level-2/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/css/">CSS Working Group</a> has published the First Public Working Draft of <a href="https://www.w3.org/TR/2024/WD-css-multicol-2-20241219/">CSS Multi-column Layout Module Level 2</a>. This specification describes multi-column layouts in CSS, a style sheet language for the web. Using functionality described in the specification, content can be flowed into multiple columns with a gap and a rule between them.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> <item> <title>Five Candidate Recommendation Snapshots Published by the Verifiable Credentials Working Group</title> <description><![CDATA[The Verifiable Credentials Working Group invites implementations of the five updated Candidate Recommendation Snapshots: Verifiable Credentials Data Model v2.0, Verifiable Credential Data Integrity 1.0, Data Integrity EdDSA Cryptosuites v1.0, Data Integrity ECDSA Cryptosuites v1.0, and Securing Verifiable Credentials using JOSE and COSE.]]></description> <pubDate>Thu, 19 Dec 2024 06:06:00 +0000</pubDate> <link>https://www.w3.org/news/2024/five-candidate-recommendation-snapshots-published-by-the-verifiable-credentials-working-group/</link> <guid>https://www.w3.org/news/2024/five-candidate-recommendation-snapshots-published-by-the-verifiable-credentials-working-group/</guid> <category><![CDATA[news]]></category> <content:encoded><![CDATA[ <div class="component component--text"> <p>The <a href="https://www.w3.org/groups/wg/vc/">Verifiable Credentials Working Group</a> invites implementations of the second Candidate Recommendation Snapshots for the following documents:</p><ul><li><a href="https://www.w3.org/TR/2024/CR-vc-data-model-2.0-20241219/">Verifiable Credentials Data Model v2.0</a>: Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.</li><li><a href="https://www.w3.org/TR/2024/CR-vc-data-integrity-20241219/">Verifiable Credential Data Integrity 1.0</a>: This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.</li><li><a href="https://www.w3.org/TR/2024/CR-vc-di-eddsa-20241219/">Data Integrity EdDSA Cryptosuites v1.0</a>: This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).</li><li><a href="https://www.w3.org/TR/2024/CR-vc-di-ecdsa-20241219/">Data Integrity ECDSA Cryptosuites v1.0</a>: This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA).</li><li><a href="https://www.w3.org/TR/2024/CR-vc-jose-cose-20241219/">Securing Verifiable Credentials using JOSE and COSE</a>: This specification defines how to secure credentials and presentations conforming to the Verifiable Credential data model with JSON Object Signing and Encryption (JOSE), Selective Disclosure for JWTs, and CBOR Object Signing and Encryption (COSE) [RFC9052]. This enables the Verifiable Credential data model to be implemented with standards for signing and encryption that are widely adopted.</li></ul><p>Comments are welcome via the GitHub issues by <strong>19 January 2025</strong>.</p> </div> ]]></content:encoded> <slash:comments>0</slash:comments> </item> </channel> </rss>