PROPOSED Math Working Group Charter
The mission of the Math Working Group is to promote the inclusion of mathematics on the Web so that it is a first class citizen of the web that displays well, is accessible, and is searchable.
|Chairs||Neil Soiffer (Talking Cat Software)|
|Team Contacts||[Bert Bos] (0.05 FTE)|
Teleconferences: two 1-hour calls working on different aspects of MathML to be held weekly to resolve issues as needed.
Face-to-face: we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than one additional meeting per year.
Background and Motivation
MathML is a markup language for encoding and communicating mathematics.The need for mathematical rendering on the web was evident from the earliest days of the Web at CERN, and MathML was among the first specifications taken up and developed by the W3C in the mid to late 1990's XML/XHTML era. It received much attention and has created a vibrant ecosystem of implementations and integration outside of web browsers. It advanced on the Web itself becoming integrated, along with SVG, into the HTML Parser and the HTML Specification in the mid 2000's. Since then, much has happened. While MathML has much success with making math accessible and has had wide adoption in the tools used to generate and consume math, browser adoption is not universal. The MathML 3 specification does not match some current Web realities; it does not contain precise enough requirements for interoperability with the now changed Web Platform; indeed, some features are either incompatible with, or subsumed by, new features added to the Web Platform outside MathML.
The MathML Refresh Community Group (CG) was formed to begin revision of MathML to address perceived difficulties in the MathML 3 spec. The Math Working Group will advance, refine, and clarify the work begun by the MathML Refresh Community Group and ensure MathML’s relevance continues to evolve, grow and improve. In particular, there are three goals the Math WG will work toward:
- Wide adoption by browsers of a core set of presentational elements so that authors can be assured that mathematics will be displayed similarly in all browsers, without having to rely on external libraries to do the display.
- Increased accessibility of Presentation MathML for both mathematics and chemical formulas achieved by allowing a means of specifying relevant mathematical intent, as well as by providing guidelines for interpreting Presentation MathML in the absence of additional information.
- Ensuring that mathematical formulations are better searchable.
The Working Group will begin by providing a thorough review and refinement of MathML Core Level 1, a restricted form of MathML created by the MathML Refresh Community Group, which has done the initial hard work of largely aligning with features of the current Web platform and precisely defining MathML's rendering, including integration with current CSS and basic DOM, and providing tests and opening bugs.
The Working Group will take up new work, such as problems the CG identified as requiring better solutions in order to move MathML in the Web Platform forward, in proposing a MathML Core Level 2.
The Working Group will also overhaul MathML 3 by building upon these fundamentals and experience with needs for accessibility, and on many years of practical experience and use (or lack thereof), to create a path forward to a MathML 4.
The scope of the Math Working Group includes the following:
- Development of Recommendations as outlined above.
- Development of a test suite to check conformance of implementations.
- Enhancements and improvements to internationalization.
- Continued integration of errata and bug fixes.
Integration of new and existing Web Platform technologies, including, but not limited to:
- DOM APIs
- Shadow DOM and Custom Elements
- Integration with tools above and beyond browsers.
- Improvements to the MathML markup and processing model to enhance accessibility and searchability.
- Identification of normative requirements needed to ensure accessibility.
- Removing elements and attributes from MathML that have had minimal adoption.
Out of Scope
- Adding new elements for use exclusively outside the Web Platform
- Changes that would cause legacy MathML that has significant usage to stop working on the Web Platform or elsewhere.
- Significant changes to Content MathML. These will be considered at a later time after gaining experience and feedback from proposed additions to enhance accessibility and searchability in Presentation MathML.
More detailed milestones and updated publication schedules are available on the group publication status page.
Draft state indicates the state of the deliverable at the time of the charter approval. Expected completion indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.
The Working Group will deliver the following W3C normative specifications:
- MathML Core Level 1
This specification provides an initial integration into the Web Platform with increased implementation details, focusing on a subset of MathML 3 which has had wide implementation and fits well with the platform. It details and relies on automated Web Platform tests to improve MathML interoperability. It provides the core layer of MathML support upon which MathML 4 can build. Authors can implement remaining features, or more generally extend MathML Core, using modern web technologies (e.g., by polyfills).
Draft state: Final Community Group Editors' Draft
Expected completion: Q1 2022
- MathML Core Level 2
This specification will address some features left out of Level 1 due to time and implementation constraints. It will provide guidance on improving MathML within the evolving Web Platform and enhancing the descriptions of generally polyfilling or extending MathML, using technologies such as a Shadow DOM, Custom Elements, the CSS Layout API or other Houdini APIs. It will also address questions such as linking and accessibility through suggested accessibility mappings of elements and attributes.
The MathML Core specifications are intended to define only those parts of MathML that are, or will be, implemented by all major browser engines.
Draft state: No draft
- MathML 4
This specification will overhaul the existing MathML 3 specification, rebasing it on MathML Core Level 1. It will deprecate, make obsolete, or drop features that are not used and likely will not be used. It will add attributes that allow specification of mathematical intent on Presentation MathML elements to enhance accessibility and searchability of math.
Draft state: Community Group's Initial Revision of MathML 3
Expected completion: Q4 2022
Adopt Draft: Mathematical Markup Language (MathML) Version 3.0 2nd Edition
Other non-normative documents may be created such as:
- Test suites and implementation reports for the specification.
- Analysis of mathematical notation usage in non LTR writing systems.
- MathML Accessibility Technique Notes.
- Guides on annotating Presentation MathML for accessibility and search.
- A living catalog for annotations beyond those defined in a MathML 4 recommendation.
- Sample code that converts default "intent" values to explicit "intent" values in Presentation MathML.
- At least one TeX-to-MathML converter that incorporates accessibility/searchability annotations in its MathML output.
- Code to convert Content MathML to Presentation MathML with accessibility and searchability annotations.
- Sample code for conversion of annotated Presentation MathML to an external form such as speech and/or Content MathML
These dates are not meant as deadlines; work may need to continue after these dates to ensure the quality of the deliverables.
- February 2021: First teleconference
- October 2021: First (virtual?) face-to-face meeting (TPAC)
- March 2021: FPWD, MathML Core Level 1
- June 2021: FPWD, MathML 4
- November 2021: MathML Core Test Suites
- November 2021: Implementation Report
- November 2021: Candidate Recommendation, MathML Core Level 1
- January 2022: Sample code that adds annotations making defaults explicit
- February 2022: Code that converts Content MathML to annotated Presentation MathML
- March 2022: FPWD, MathML Core Level 2
- May 2022: Sample code that uses annotated Presentation MathML to create Speech and/or Content MathML
- June 2022: Prototype TeX-to-annotated MathML implementation
- October 2022: Living catalog established for extended Presentation annotations
- November 2022: Candidate Recommendation, MathML 4
The Math Working Group’s work is considered a success if:
- There are independent, interoperable native implementations of MathML Core Level 1 that are widely used.
- The larger Web Platform ecosystem shows signs of movement toward creating and using new MathML content, including direct use of core features aimed at improving accessibility by authoring tools and MathML converters.
- There is proven advancement and interest by implementers in MathML Core Level 2, exploring linking, better alignment with how the larger Web Platform evolves (Shadow DOM, Custom Elements, CSS).
- A MathML Full (MathML 4) specification, based on Core.
- Each specification contains a section detailing all known security and privacy implications for implementers, Web authors, and end users.
- There are significant testing plans, and all testable changes have tests.
- There is an AAM (Accessibility API Mapping) for MathML Core and there are considerations of the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.
For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition, including FPWD. The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.
Additional technical coordination with the following Groups will be made, per the W3C Process Document:
- CSS Working Group
- The Math Working Group will contribute to and coordinate work with the CSS Working Group related to aligning the development and testing of new and existing CSS functionalities that are of interest to the MathML community. The group will designate liaisons to work with the CSS Working Group on issues as needed. Liaisons will ideally be participants of both groups.
- Web Incubator Community Group (WICG)
- The Web Platform Incubator Community Group (WICG) provides a lightweight venue for proposing and discussing new web platform features, like new HTML features or Web Platform APIs. Also, new technical features arising during the development of MathML may have relevance for the Web Platform in general, or ideas developing for the Web Platform in general might be developing in WICG which could be relevant to MathML. The MathML WG will make an effort to make sure these are explored further together within incubations in the Web Platform Incubator Community Group where appropriate.
- Accessible Platform Architectures Working Group
- The APA WG provides horizontal review of potential accessibility issues in the architecture, including knowledge domains for STEM accessibility, as well as of the accessibility impact of a specification. The MathML WG will request reviews and coordinate, and may nominate liaisons to ensure that these groups are aligned and working in concert toward accessible mathematics.
- ARIA Working Group
- The ARIA Working Group is responsible for the development of ARIA and related Accessibility Mappings. The MathML WG will appoint a liaison and coordinate with the ARIA Working Group to provide the MathML AAM and continue to improve the accessibility of that which is part of MathML.
- EPUB Working Group
- MathML is used in EPUB documents for the display of math. Accessibility of all of the contents of an EPUB document is a priority of the group, and math accessibility has been a challenge for them due to uneven support of MathML in various reading systems. The MathML WG will work with the EPUB WG to ensure their needs are met with updates to the MathML recommendations.
- SVG Working Group
- The SVG Working Group is responsible for the development of SVG. While largely non-overlapping technically, SVG and MathML share similar origin stories and are both special in their integration with the HTML Parser specification and integration as embedded content. As such they have many similar challenges and efforts to align with the larger Web Platform and share common interests in providing common developer experiences and expectations. The Math Working Group will attempt to coordinate furthering these efforts with the SVG Working Group (and the SVG CG).
- Chemistry for the Web and Publishing Community Group (Chem CG)
- Chemical Formulas make use of mathematical notations. The Chem CG is concerned about the accessibility challenges of using math notations and having them spoken and brailed appropriately. The MathML Refresh CG has worked with the Chem CG to ensure appropriate access to chemical formulas and the Math WG will continue this effort.
- Publishing Community Group
- The Publishing Community Group is an incubation zone for digital publishing ideas. MathML has been a topic of discussion for them. Working with this group may lead to inclusion of support for new ideas in MathML.
- The WHATWG is responsible for the development of HTML and DOM. This may have an influence on the future evolution of MathML. Efforts to align MathML Core with the Web Platform may lead to alignment requirements (issues might arise from a new IDL, focusability, support for ideas like Shadow DOM, support for attributes, etc.), in which case these should be explored further together with the WHATWG (and the WICG).
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the W3C Patent Policy.
Participants in the group are required (by the W3C Process) to follow the W3C Code of Ethics and Professional Conduct.
Technical discussions for this Working Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted using documents that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository and may permit direct public contribution requests. The meetings themselves are not open to public participation, however.
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Math Working Group home page.
Most Math Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
This group primarily conducts its technical work on GitHub issues. The public is invited to review, discuss and contribute to this work.
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from 10 to 20 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.
This charter is written in accordance with the W3C Process Document (Section 3.4, Votes) and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This Working Group will use the W3C Software and Document license for all its deliverables.
About this Charter
This charter has been created according to section 5.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
The following table lists details of all changes from the initial charter, per the W3C Process Document (section 5.2.3):
|Charter Period||Start Date||End Date||Changes|
|Initial Charter||4 January, 2021||28 February, 2023|