W3C

The Math Working Group has published the First Public Working Draft of MathML Core.

The MathML Core specification tries to address several issues related to implementing MathML in browsers. The MathML3 specification has been difficult to implement for browsers, because it is big and does not contain very precise rules for rendering math formulas. MathML also has several parts that are not useful in browsers. The MathML Core specification tries to define an appropriate subset of MathML, describe its rendering in detail (using rules from the TeXBook and the Open Font Format as basis) and clarify the interactions of MathML with other parts of HTML and the Open Web Platform.

The Math Working Group is also working on the rest of MathML. It is defining MathML4, the fourth version of MathML. The features included in MathML Core may evolve, or a second version of MathML Core may be defined, depending on how MathML4 develops.

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 Proposed Recommendation. DOM defines a platform-neutral model for events, aborting activities, and node trees. We invite the community to provide feedback until 2 September 2021.

The EPUB 3 Working Group has just published a Working Group Note of EPUB 3 Text-to-Speech Enhancements 1.0. This document describes authoring features and reading system support for improving the voicing of EPUB 3 publications.

The EPUB Working Group of the International Digital Publishing Forum (IDPF) first defined a means of integrating the Synthetic Speech Markup Language and pronunciation lexicons in EPUB 3.0 so that EPUB Creators could improve the rendering quality of text-to-speech (TTS) playback in Reading Systems. The ability to include cascading style sheets also allowed EPUB Creators to access the in-development speech properties of the CSS Speech module. However, although there has been some authoring uptake of these technologies, support in Reading Systems has yet to materialize to a level where these technologies are considered stable. Consequently, these technologies are now published as a W3C Working Group Note.

The Automotive Working Group has published two Public Working Drafts for VISS version 2, Core and Transport.

This specification describes a second version of VISS which has been implemented and deployed on production vehicles. It adds major new capabilities and improvements to the earlier version. The first version of VISS only supported WebSocket as a transport protocol, the second version is generalized to work across different protocols as some are better suited for different use cases. HTTP is now supported with additional protocols used within the automotive industry being evaluated for inclusion. Subscription capabilities have been improved and access control has been added.

There are two parts to this specification, Core and Transport.

• VISS version 2 – Core describes the VISSv2 messaging layer. The companion specifications for the VISSv2 transport protocols detail the mapping of the messaging layer to selected transports. The ontologies based on the VISSv2 core specification are defined in documents for each specific domain (e.g. navigation, media, vehicle data).
• VISS version 2-Transport describes the VISSv2 transport protocols, and the mapping of the message layer on these transports. The companion specification VISSv2 CORE describes the messaging layer.

To those in the world who are from a group that is under-represented in the web community, who can and want to join us in making Web standards, but would otherwise be unable to without financial help, please apply to become a beneficiary of the TPAC 2021 Inclusion Fund, by August 15. (Note: being designed for people who would like to participate in our standards work or who already do, the form requires applicants to have a W3C account. Request one here.)

We wish to make it easier for underrepresented communities to contribute to our important work: making the Web work, for everyone. The Web standards that we create need to reflect the diversity of the whole world. More background, more use cases, more edge cases, do eventually bring higher quality results, and lead to a more inclusive design and a better Web.

For a few years now, we have developed methods to improve diversity at the World Wide Web Consortium. One such means is to be in a position to welcome more contributors at our annual conference: TPAC (“Technical Plenary / Advisory Committee”). Because during that event, the W3C work groups gather, network, and work to resolve challenging technical or social issues, it is one of the most important rendez-vous for the Web community. We recently released a short video introducing TPAC.

This year’s fund is sponsored by W3C, Adobe, Samsung Electronics, Coil, Charles Nevile, Microsoft, TetraLogical, Siteimprove, and an anonymous donor. We recognize and thank donors for this important gesture.

You may be interested in reading on the topic of diversity and inclusion at W3C. Our CEO Jeff Jaffe published a 2021 update last month.

W3C announced today that as part of our growing concern for inclusion, all W3C workshops will now include the following standard accessibility accommodations:

• English captions available on all pre recorded presentations, before the live sessions
• Real-time English captions available during the live sessions
• American Sign language and other services will depend on participant requests

W3C organizes Workshops to promote early involvement in the development of W3C activities from Members and the public. The goal of a workshop is usually either to convene experts and other interested parties for an exchange of ideas about a technology or policy, or to address the pressing concerns of W3C Members.