@w3c invites implementations of "Decentralized Identifiers (DIDs) v1.1". DIDs enable verifiable digital #identity without relying on central authorities. #timetoimplement
▶️ https://www.w3.org/TR/did-1.1/

A DID is a simple text string consisting of three parts: 1) the 'did' URI scheme identifier, 2) the identifier for the DID method and 3) the DID method-specific identifier.

Feedback welcome: https://github.com/w3c/did/issues

The @w3c Web Machine Learning #WorkingGroup invites implementations of an updated #CandidateRecommendation Snapshot of the WebNN #API. Most notable additions include a third wave of operators for enhanced transformers support, the MLTensor API for buffer sharing, and a new abstract device selection mechanism #timetoimplement #MachineLearning

▶️ https://www.w3.org/TR/webnn/

Explainer: https://github.com/webmachinelearning/webnn/blob/main/explainer.md

Feedback wlc: https://github.com/webmachinelearning/webnn/issues/

Web Neural Network API

Web Authentication defines an #API for creating and using securely and smoothly public key-based credentials in Web #browsers.
This 3rd level adds client features that make passkeys easier to use and help transition from passwords via conditional mediation (learn more at https://passkeys.dev). It also enables cross-origin iframe support for use cases like federated identity and payments #WebAuthn

▶️ https://www.w3.org/TR/webauthn-3 #timetoimplement

Feedback wlc: https://github.com/w3c/webauthn/issues

RE: https://w3c.social/@w3cdevs/114896204993494333

We now invite implementations of "IMSC Text Profile 1.3"! This specification defines a text-only profile of TTML2 intended for subtitle and caption delivery applications worldwide #a11y #timetoimplement

▶️ https://www.w3.org/TR/ttml-imsc1.3/

Feedback also welcome: https://github.com/w3c/imsc/issues/

Web Fonts let pages use fonts on demand without local installation. The @w3c Incremental Font Transfer (IFT) speeds up #font loading and cuts data use by sending only needed parts in multiple requests #timetoimplement
▶️ https://www.w3.org/TR/IFT/

IFT avoids layout issues (ligatures, etc.), enabling efficient, fine-grained font loading, even for complex scripts like Indic or Arabic.

Demo: https://garretrieger.github.io/ift-demo/
Explainer: https://github.com/w3c/IFT/blob/main/IFT-Explainer.md

Feedback welcome! https://github.com/w3c/IFT/issues

The @w3c MathML Core specification, now at #CandidateRecommendation status, defines a core subset of the #MathML 3 specification designed for reliable, interoperable web browser support. It focuses on mathematical notation rendering, tightly integrating with #HTML, #CSS, and DOM standards to ensure consistency, testability, and minimal implementation complexity. #timetoimplement
▶️ https://www.w3.org/TR/mathml-core/

Feedback welcome: https://github.com/w3c/mathml-core/issues/

Explainer: https://github.com/w3c/mathml-core/blob/main/docs/explainer.md

@w3c has released "Pointer Events Level 3" as #CandidateRecommendation #timetoimplement
▶️ https://www.w3.org/TR/pointerevents3/

This specification aims to simplify development across diverse input devices like mouse, pen, and touchscreens. Along with expanded #CSS touch-action values, new features include altitudeAngle and azimuthAngle properties for detailed stylus input.

Feedback welcome: https://github.com/w3c/pointerevents/

Pointer Events

The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen. For compatibility with existing mouse-based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.

The @w3c Compute Pressure #API specification defines a set of pressure states (e.g. high CPU load) delivered to a #WebApp to signal when adaptation of the workload is appropriate to ensure consistent quality of service. #timetoimplement
▶️ https://www.w3.org/TR/compute-pressure/

The document defines 3 concepts: processing units (such as the CPU), supported sources (such as #GPU), sampling and reporting rates.

Key usage scenarios are described in this explainer: https://github.com/w3c/compute-pressure#readme

Compute Pressure Level 1

The Compute Pressure API provides a way for websites to react to changes in the CPU pressure of the target device, such that websites can trade off resources for an improved user experience.

The @w3c Timed Text #WorkingGroup invites implementations of the "Dubbing and Audio Description Profiles of TTML2 (DAPT)" specification for exchanging timed text content in #dubbing and #audio description workflows #timetoimplement

▶️ https://www.w3.org/TR/dapt/

DAPT enables scripting, voicing, and mixing for dubbing and audio descriptions, supporting video #localization and #accessibility.

Feedback welcome in https://github.com/w3c/dapt/

Dubbing and Audio description Profiles of TTML2

@w3c invites implementations of Controlled Identifiers (CIDs) v1.0

CIDs generalizes the mechanism used to prove control of an identifier in Decentralized Identifiers (#DID), making it also applicable to non-decentralized identifiers and systems (e.g. HTTPS URLs). They can be used with Verifiable Credentials, e.g. to authenticate the subject of such a credential
#timetoimplement
▶️ https://www.w3.org/TR/cid-1.0/

Bring input and feedback on the #GitHub repo: https://github.com/w3c/cid/

Controlled Identifiers v1.0

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.