News

W3C Launches Initiative to Improve the Web for Merchants

21 October 2020 | Archive

megaphoneW3C today launched the Merchant Business Group, an open forum to address challenges for customer experiences and business needs using Web technologies. Merchants, integrators, platform providers, and others will discuss how emerging Web technologies could help address customer experience challenges, and what additional Web capabilities may be necessary. The group offers participants an opportunity to learn directly from the organizations building Web experiences about how Web standards trends can affect (and improve) e-commerce. W3C Members Worldpay from FIS, Fiserv, Coles Supermarket Group and Connexus are the first organizations to join the new group, whose first meeting will take place on October 26, 2020.

A W3C Business Group gives innovators wanting to have an impact on the development of the Web in the near-term, a vendor-neutral forum for collaborating with like-minded stakeholders, including W3C Members and non-Members who can participate in the Business Group without full W3C Membership. Please read more in our press release.

W3C community convenes online for TPAC 2020

12 October 2020 | Archive

TPAC 2020 logoToday marks the start of TPAC 2020, our 20th Technical Plenary and Advisory Committee meetings week!

The W3C Community convenes remotely for our annual all-groups meetings which is online and virtual for the first time since 2001, and will span at least three weeks. The event focuses on collaborative meetings to create momentum and collective brainstorming, and brings together W3C technical groups, the W3C Advisory Board, TAG and Advisory Committee. Because TPAC is a way to meet with others, discuss and share ideas, our attendees can hang out in the virtual TPAC lounge and open meeting rooms at any time.

This week is dedicated to joint meetings (12-16 October) of W3C work groups, which have self-organized their own meetings as early as late September. Next week will host the semi-annual member-only W3C Advisory Committee meeting (20 October). And the following week is dedicated to the TPAC breakout week (26-30 October), most of which will be open the public for the first time, aiming to ensure the fullest range of users and perspectives is represented and encoded in Web standards.

Breakouts are proposed by the community on a variety of topics relating to W3C activities. TPAC attendees may suggest breakout sessions until October 19th via the wiki. Breakout participants contribute to discussions and connect with people working on ideas that may not fall within their usual areas of activity.

First Public Working Draft: WebXR Hand Input Module — Level 1

22 October 2020 | Archive

The Immersive Web Working Group has published a First Public Working Draft of WebXR Hand Input Module – Level 1. The WebXR Hand Input module expands the WebXR Device API with the functionality to track articulated hand poses.

First Public Working Draft: CSS Custom Highlight API Module Level 1

22 October 2020 | Archive

The CSS Working Group has published a First Public Working Draft of CSS Custom Highlight API Module Level 1. This CSS module describes a mechanism for styling arbitrary ranges of a document identified by script.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.

First Public Working Draft: Propagation format for distributed trace context: Baggage

20 October 2020 | Archive

The Distributed Tracing Working Group has published a First Public Working Draft of Propagation format for distributed trace context: Baggage. Distributed tracing is a set of tools and practices to monitor the health and reliability of a distributed application. A distributed application is an application that consists of multiple components that are deployed and operated separately. It is also known as micro-service.

The main concept behind distributed tracing is event correlation. Event correlation is a way to correlate events from one component to the events from another. It allows to find the cause-and-effect relationship between these events. For instance – find which user action in a browser caused a failure in the business logic layer.

To correlate events between components, these components need to exchange and store a piece of information called context. Typically context consists of an originating event identifier, an originating component identity and other event properties. Context has two parts. The first part is a trace context. Trace context consists of properties crucial for event correlation. The second part is baggage. Baggage carries user-defined properties. These properties may be helpful for correlation scenarios. But they are not required and components may choose to not carry or store them.

Unifying the format of distributed tracing context as well as aligning on semantic meaning of the values is the main objective of this working group. The goal is to share this with the community so that various tracing and diagnostics products can operate together.

Working Group Note: Progressive Font Enrichment: Evaluation Report

15 October 2020 | Archive

The WebFonts Working Group has published a First Public Working Group Note of Progressive Font Enrichment: Evaluation Report. The success of WebFonts is unevenly distributed. This study evaluates solutions which would allow WebFonts to be used where slow networks, very large fonts, or complex subsetting requirements currently preclude their use. Comments on this report are welcome by 15 December 2020.

Call for Review: Publication Manifest and Audiobooks are W3C Proposed Recommendations

1 October 2020 | Archive

The Publishing Working Group has published two Proposed Recommendations:

  • Publication Manifest defines a general manifest format for expressing information about a digital publication. It uses schema.org metadata augmented to include various structural properties about publications, serialized in JSON-LD, to enable interoperability between publishing formats while accommodating variances in the information that needs to be expressed.
  • Audiobooks describes the requirements for the creation of audiobooks, using a profile of the Publication Manifest specification.

Comments on the Proposed Recommendations are welcome through 03:59 UTC/GMT on 2020-10-31 (23:59 Boston time on 2020-10-30).

New version of the Roadmap of Web Applications on Mobile

25 September 2020 | Archive

Icon representing mobile life-cycleW3C has published a new version of its Roadmap of Web Applications on Mobile, an overview of the various technologies developed in W3C that increase the capabilities of Web applications, and how they apply more specifically to the mobile context.

The September 2020 snapshot refreshes the list of technologies under incubation in Community Groups or on the standardization track in Working Groups. See the Change history since November 2019 for details. Standardization proposals that have emerged since last publication include:

  • various proposals focused on privacy (such as the Storage Access API, the Trust Token API, Private Click Measurement, TURTLEDOVE, or the isLoggedIn proposal), described in Security and Privacy;
  • exploration of standards needed for so-called MiniApps, see Application Lifecycle;
  • main thread scheduling APIs to improve scheduling primitives, see Performance and Tuning;
  • Web Monetization to enable continuous and small payments facilitated by the browser, see Payment and Services;

Former proposals under incubation in Community Groups have moved to the standardization track since November 2019. For instance, the WebTransport API is now in scope of the recently created WebTransport Working Group (see Network and Communications). The GPU for the Web Working Group has also been recently created to standardize the WebGPU and WebGPU Shading Language specifications, incubated in the GPU for the Web Community Group (see Graphics and Layout).

Implementation info for all features has been updated. A number of features that were previously in development, under consideration, or simply not implemented have now shipped in the new version of Edge, based on Chromium. Main technologies behind Web Components, which allow applications to encapsulate their logic in re-usable components, are now available across browsers (see Device Adaptation). Similarly, Web Animations, which allow application to manage animations via scripting, are available across main browsers (see Graphics and Layout).

Last but not least, a new groups page summarizes groups mentioned throughout the roadmap’s pages, along with the name of the specifications and features that these groups are (or were) responsible for.

Sponsored by Beihang University, this project is part of a set of roadmaps under development in a GitHub repository to document existing standards, highlight ongoing standardization efforts, point out topics under incubation, and discuss technical gaps that may need to be addressed in the future. New versions are published as needed depending on progress of key technologies of the Web platform. We encourage the community to review them and raise comments, or suggest new ones, in the repository’s issue tracker.

More news… RSS Atom

Events Header link