From 71f3e32d9e6507d25f09cf65fcd0c33fd81c6498 Mon Sep 17 00:00:00 2001
From: Bert Bos
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).
- -Working Draft: - Working Draft
-Expected completion: TBD + 9 months
+Draft state: + Working Draft
+Expected completion: (Proposed Recommendation) Start date + 9 months
+Adopted draft: 2022-05-04
+Exclusion Draft: https://www.w3.org/TR/2021/WD-mathml-core-20210810/
+Exclusion Draft charter: https://www.w3.org/Math/Documents/Charter2021.html
Draft state: No draft
-Working Draft: TBD + 18 months
+Expected completion: (First Public Working Draft) start date + 18 months
-This specification overhauls the existing MathML 3 specification, rebasing it on MathML Core Level 1. It deprecates, make obsoletes, and drop features that are not used and likely will not be used. It adds attributes allows specification of mathematical intent on Presentation MathML elements to enhance accessibility of math.
-Draft state: Working Draft
-Expected completion: TBD + 20 months
+Draft state: Working Draft
+Expected completion: (Proposed Recommendation) Start date + 20 months
+Adopted draft: 2022-09-08
+Exclusion Draft: https://www.w3.org/TR/2022/WD-mathml4-20220908/
+Exclusion Draft charter: https://www.w3.org/Math/Documents/Charter2021.html
Draft state: No draft
-Working Draft: TBD + 24 months
+Expected completion: (First Public Working Draft) Start date + 24 months
These dates are not meant as deadlines; work may need to continue after these dates to ensure the quality of the deliverables.
In order to advance to - Proposed Recommendation, each normative specification is expected to have +
In order to advance to + Proposed Recommendation, each normative specification is expected to have at least two independent interoperable implementations of every feature defined in the specification, where interoperability can be verified by passing open test suites, and two or @@ -369,8 +376,8 @@
For all specifications, this Working Group will seek horizontal review for - accessibility, internationalization, performance, privacy, and security with the relevant Working and +
For all specifications, this Working Group will seek horizontal review for + accessibility, internationalization, 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 @@ -405,12 +412,12 @@
- 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. + 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 in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however.
@@ -497,7 +504,7 @@
- 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.
+ This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus). 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.
@@ -512,7 +519,7 @@- 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 charter is written in accordance with the W3C Process Document (Section 5.2.3, Deciding by Vote) 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 Web specifications 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 licensing information.
+ For more information about disclosure obligations for this group, please see the licensing information.The following table lists details of all changes from the initial charter, per the W3C Process Document (section 4.3, Advisory Committee Review of a Charter):
-
@@ -574,41 +581,214 @@ | |||
---|---|---|---|
- Initial Charter - | -- 1 April, 2021 - | -- 31 May, 2023 - | -- | -
- Charter Extension + Initial Charter | - 1 June, 2023 + April 1997 | - 21 August, 2023 + June 1998 | + MathML 1.0, character entities |
Changes to this document are documented in this section.
+