Friday, January 17, 2020

Updated Candidate Recommendation: Identifiers for WebRTC’s Statistics API

The Web Real-Time Communications Working Group invites implementation of its updated Candidate Recommendation of Identifiers for WebRTC’s Statistics API. This document defines a set of WebIDL objects that allow access to the statistical information about a RTCPeerConnection. These objects are returned from the getStats API that is specified in [WEBRTC].

Upcoming: W3C Workshop on Web & Machine Learning

W3C Web & Machine Learning Workshop page banner imageW3C announced today a Workshop on Web & Machine Learning, 24-25 March 2020, in Berlin, Germany. The event is hosted by Microsoft.
The primary goal of the workshop is to bring together providers of Machine Learning tools and frameworks with Web platform practitioners to enrich the Open Web Platform with better foundations for machine learning.
The secondary goals of the workshop are as follows:
  • Understand how machine learning fits into the Web technology stack,
  • Understand how browser-based machine learning fits into the machine learning ecosystem,
  • Explore the impact of machine learning technologies on Web browsers and Web applications,
  • Evaluate the opportunities for standardization around machine learning APIs and formats.
Expected topics of discussion include:
  • Dedicated machine learning APIs for browsers as explored by the Machine Learning for the Web Community Group
  • Integration of browser-provided data sources in machine learning workflows
  • Layering and interoperability of machine learning APIs with other computing APIs (e.g. WebGPU, WebAssembly)
  • Domain-specific machine learning APIs
  • Interchange format for machine learning models on the Web
  • Client- and cloud-based machine learning interactions
  • On-device machine learning training in browsers
  • Risks and benefits of browser-based machine learning on privacy, security, accessibility
  • Using machine learning primitives to help improve accessibility of Web pages and applications
  • Machine learning frameworks for the Web
  • Machine learning hardware accelerators
Attendance is free for all invited participants and is open to the public, whether or not W3C members. For more information on the workshop, please see the workshop details and submission instructions.
Registration is available online due by 21 February 2020.

Monday, January 13, 2020

W3C Advisory Committee Elects Technical Architecture Group

W3C TAG logoThe W3C Advisory Committee has elected the following people to the W3C Technical Architecture Group (TAG): Rossen Atanassov (Microsoft Corporation), David Baron (Mozilla Foundation) and Kenneth Rohde Christiansen (Intel Corporation). They join co-Chair Tim Berners-Lee and continuing participants, Daniel Appelquist (Samsung Electronics; co-Chair), Hadley Beeman (W3C Invited Expert), Alice Boxhall (Google), Peter Linss (W3C Invited Expert; co-Chair), Sangwhan Moon (Odd Concepts), and Theresa O’Connor (Apple, Inc.). Yves Lafon continues as staff contact. Many thanks to Lukasz Olejnik (W3C Invited Expert) whose term ends at the end of this month.
The TAG is a special group within the W3C, chartered under the W3C Process Document, with stewardship of the Web architecture. The mission of the TAG is to build consensus around principles of Web architecture and to interpret and clarify these principles when necessary, to resolve issues involving general Web architecture brought to the TAG, and to help coordinate cross-technology architecture developments inside and outside W3C. The elected Members of the TAG participate as individual contributors and not representatives of their organizations. TAG participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user. Learn more about the TAG.

First Public Working Draft: Web Share API

The Web Applications Working Group has published a First Public Working Draft of Web Share API. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.