The Verifiable Claims Working Group invites implementations of an updated Candidate Recommendation of Verifiable Credentials Data Model 1.0. 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.
Thursday, July 25, 2019
First Public Working Draft: Timing Entry Names Registry
The Web Performance Working Group has published a First Public Working Draft of Timing Entry Names Registry. This document provides a registry of
PerformanceEntry.entryType used in Performance Timeline [PERFORMANCE-TIMELINE-2].W3C Invites Implementations of Three WebAssembly Candidate Recommendations
The WebAssembly Working Group invites implementations of three Candidate Recommendations published today:
- WebAssembly Core Specification describes version 1.0 of the core WebAssembly standard, a safe, portable, low-level code format designed for efficient execution and compact representation.
- WebAssembly JavaScript Interface provides an explicit JavaScript API for interacting with WebAssembly.
- WebAssembly Web API describes the integration of WebAssembly with the broader web platform.
Wednesday, July 10, 2019
W3C Invites Implementations of Media Capture and Streams
The Web Real-Time Communication Working Group has published an updated Candidate Recommendation of Media Capture and Streams. This document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform.
Wednesday, July 3, 2019
First Public Working Draft: Fetch Metadata Request Headers
The Web Application Security Working Group has published a First Public Working Draft of Fetch Metadata Request Headers. This document defines a set of Fetch metadata request headers that aim to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used.
Updated: Inaccessibility of CAPTCHA, alternatives to Visual Turing Tests on the Web
The Accessible Platform Architectures (APA) Working Group, with support from the Research Questions Task Force, has published an updated Working Draft of Inaccessibility of CAPTCHA, alternatives to Visual Turing Tests on the Web. This update includes changes that address the substantial comments received since the May 2019 version, which have helped us improve our analysis of the state of the art in telling human users apart from their robotic impersonators. Comments are requested by 26 July 2019. Please, read more in a dedicated blog post by Janina Sajka, Chair Accessible Platform Architectures (APA) Working Group, and learn more about the Web Accessibility Initiative (WAI).
First Public Working Draft: CSS Animation Worklet API
The CSS Working Group has published a First Public Working Draft of CSS Animation Worklet API. The Animation Worklet API provides a method to create scripted animations that control a set of animation effects. The API is designed to make it possible for user agents to run such animations in their own dedicated thread to provide a degree of performance isolation from main thread.
First Public Working Draft: Audiobook Profile for Web Publications
The Publishing Working Group has published a First Public Working Draft of Audiobook Profile for Web Publications. This profile, derived from the structure laid out in the Web Publications specification, has been developed to address a major gap in the publishing ecosystem. Unlike the ebooks industry which predominantly uses the EPUB standard, Audiobooks never developed a common specification. This has created a distribution model where content creators create many different files for their distributors or retailers, leaving users behind.
Our profile is focused on bringing a common, single manifest format to the industry. The manifest centers on providing a simple way for content creators to include identifying metadata, a reading order, and additional resources. Identifying metadata includes information like title, author, narrator, identifier, and duration. The reading order is designed to provide user agents with a single source of truth on the presentation order of the audio files, should no other user input occur. The resources section of the manifest is reserved for any additional files that are important to the content but are not part of the reading order. This can include a cover image, supplemental content like images or data, the table of contents, and synchronized media files. We hope that this specification will bring common ground to the industry, as well as pave the way for a standard way of including supplemental content, tables of contents, and accessibility in the format. We look forward to the publication of the first draft, and any feedback it will bring. Please offer your input on GitHub
Subscribe to:
Posts (Atom)