W3C News

Updated Candidate Recommendation: Decentralized Identifiers (DIDs) v1.0

The Decentralized Identifier Working Group has just published a second Candidate Recommendation Snapshot for the Decentralized Identifiers (DIDs) v1.0.

This document defines Decentralized identifiers (DIDs), a new type of identifier that enables verifiable, decentralized digital identity. A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject. Each DID document can express cryptographic material, verification methods, or services, which provide a set of mechanisms enabling a DID controller to prove control of the DID.

Candidate Recommendation means that the Working Group considers the technical design to be complete, and is seeking implementation feedback on the document. The group is keen to get comments and implementation experiences on this specification as issues raised in the document’s Github repository.

The group expects to satisfy the implementation goals (i.e., at least two, independent implementations for each of the test cases) by July 17, 2021.

DOM Review Draft 15 June 2020 Endorsed as a W3C Candidate Recommendation

As part of working with the WHATWG together on HTML and DOM, W3C selected today to endorse the DOM Review Draft — Published 15 June 2020 as a W3C Candidate Recommendation. DOM defines a platform-neutral model for events, aborting activities, and node trees. This document is published for purposes of patent review by WHATWG Workstream Participants and as a W3C Candidate Recommendation. We invite the community to provide feedback until 6 July 2021.

W3C Advisory Committee Elects Advisory Board

Logo for the W3C Advisory BoardThe W3C Advisory Committee has elected the following people to fill six seats on the W3C Advisory Board starting 1 July 2021: Heejin Chung (Samsung Electronics), Avneesh Singh (DAISY Consortium), Eric Siow (Intel), Léonie Watson (TetraLogical), Chris Wilson (Google) and Hongru (Judy) Zhu (Alibaba) will join continuing participants Tantek Çelik (Mozilla), Tatsuya Igarashi (Sony), Florian Rivoal (W3C Invited Expert), Tzviya Siegman (Wiley) and David Singer (Apple). Many thanks to the 7 candidates, and to Elika J Etemad (W3C Invited Expert) whose term ends this month.

Created in March 1998, the Advisory Board provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution. The Advisory Board manages the evolution of the Process Document. The elected Members of the Advisory Board participate as individual contributors and not representatives of their organizations. Advisory Board participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user. Read more about the Advisory Board and its work.

First Public Working Draft of Geolocation API

The Devices and Sensors Working Group has re-published the Geolocation API as a First Public Working Draft. The Geolocation API provides access to geographical location information associated with the hosting device.

The specification has been updated to reflect numerous privacy and security improvements made by implementers since last publication in 2016. The specification includes a list of substantive changes since last publication.

The Working Group welcomes comments via the GitHub repository issues.

Working Group Note: RTC Accessibility User Requirements (RAUR)

The Accessible Platform Architectures (APA) Working Group has published RTC Accessibility User Requirements (RAUR) as a Working Group Note.

Real-time communication (RTC) provides real-time peer-to-peer audio, video, and data exchange directly between supported user agents. This enables instantaneous applications for video and audio calls, text chat, file exchange, screen sharing, and gaming.

RAUR describes various accessibility related user needs, requirements, and scenarios for real-time communication (RTC) applications. These user needs should drive accessibility requirements in various related specifications and the overall architecture that enables RTC.

First Public Working Draft: Specification for Spoken Presentation in HTML

The Accessible Platform Architectures (APA) Working Group has published a First Public Working Draft of Specification for Spoken Presentation in HTML from the Pronunciation Task Force. This document is part of W3C work on pronunciation to provide normative specifications and best practices guidance so that text-to-speech (TTS) synthesis can properly pronounce HTML content. TTS has long been used by screen readers (and other assistive technologies) for people with disabilities. It is now also widely used in popular applications such as voice assistants. Yet today there is no way for content creators to markup HTML content that will correctly and consistently present TTS generated output across all commonly used TTS engines and operating environments. This specification is intended to fill this critical gap.

This First Public Working Draft specification describes two possible technical approaches for author-controlled pronunciation of HTML content, using Speech Synthesis Markup Language (SSML).

Either approach will satisfy our accessibility requirements. However, we seek to establish a widely applicable approach. W3C is therefore seeking more input on these approaches, particularly from content authors and implementors who would convert the authoring techniques described into aural presentation. Please send comments by 18 June 2021.

W3C Invites Implementations of Page Visibility Level 2

The Web Performance Working Group has published the Page Visibility Level 2 as a W3C Candidate Recommendation Snapshot. This specification defines a means to programmatically determine the visibility state of a document. This can aid in the development of resource efficient web applications.

The document was previously published as a Proposed Recommendation and now returns to Candidate Recommendation status to allow better integration with the HTML specification. Further, this snapshot has been updated so that dependent specifications can better integrate with its various defined concepts and algorithms.

The Working Group welcomes comments via the GitHub repository issues by 18 June 2021.

First Public Working Drafts: WebGPU and WebGPU Shading Language

The GPU for the Web Working Group has published the following two First Public Working Drafts:

  • WebGPU: WebGPU exposes an API for performing operations, such as rendering and computation, on a Graphics Processing Unit.
  • WebGPU Shading Language: WebGPU Shader Language (WGSL) is the shader language for WebGPU. That is, an application using the WebGPU API uses WGSL to express the programs, known as shaders, that run on the GPU.