forked from w3c/charter-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmath-2023.html
More file actions
640 lines (544 loc) · 31.9 KB
/
math-2023.html
File metadata and controls
640 lines (544 loc) · 31.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>Math Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">PROPOSED Math Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->
<p class="mission">The <strong>mission</strong> of the <a href="">Math Working Group</a> is to promote the inclusion of mathematics on the Web so that it is a first class citizen of the web that displays well and is accessible.</p>
<div class="noprint">
<p class="join todo"><a href="https://www.w3.org/2004/01/pp-impl/#####/join">Join the Math Working Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <i class="todo"><a href="https://github.com/w3c/charter-drafts/">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues">issues</a></i>.
</p>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
TBD
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
TBD + 2 years
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Brian Kardell (Igalia), Neil Soiffer (Talking Cat Software)
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:bert@w3.org">[Bert Bos]</a> <i class="todo">(0.05 <abbr title="Full-Time Equivalent">FTE</abbr>)</i>
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> two 1-hour calls working on different aspects of MathML to be held weekly to monthly to resolve issues as needed.
<br>
<strong>Face-to-face:</strong> 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.
</td>
</tr>
</table>
</section>
<section id="background">
<h2>Background and Motivation</h2>
<p>
<a href="https://www.w3.org/Math/">MathML </a>
is a markup language for encoding and communicating mathematics.The need for
mathematical rendering on the web was evident from the
<a href="https://www.w3.org/MarkUp/HTMLPlus/htmlplus_45.html">earliest days of the Web at CERN</a>,
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.
At the start of 2023, Chromium support of MathML Core was enabled by default so that all major browsers now support MathML without the need of third party libraries.
MathML Core is a subset of the full MathML recommendation. Additional work is needed to expand MathML Core to encompass more features used in mathematical layout and to resolve some open issues which were put off to a future time such as links in MathML.
</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>
The existing WG plans to move MathML Core to CR in the very near future and expects to move MathML 4 in the fall. The continuation of this group will move these and the XML entities to recommendation status.
The goals of these recommendations are:
</p>
<ul>
<li>
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.
</li>
<li>
Increased accessibility of Presentation MathML for
mathematical notation 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.
</li>
</ul>
<p>
The Working Group will begin by providing a thorough review and refinement of MathML Core Level 1’s
rendering, including integration with current CSS and basic DOM, and providing tests and opening bugs.
</p>
<p>
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.
</p>
<p>
The scope of the Math Working Group includes the following:
</p>
<ul>
<li>
Development of Recommendations as outlined above.
</li>
<li>
Development of a test suite to check conformance of implementations.
</li>
<li>
Clarifications to the current use of Web Platform technologies, such as supported JavaScript APIs and CSS modules.
</li>
<li>
Enhancements and improvements to internationalization/localization in consultation with a broad international community.
</li>
<li>
Continued integration of errata and bug fixes.
</li>
<li>
Integration of new and existing Web Platform technologies, including, but not limited to:
<ul>
<li>Hyperlinks</li>
<li>DOM APIs</li>
<li>Shadow DOM and Custom Elements</li>
<li>CSS</li>
</ul>
</li>
<li>Integration with tools above and beyond browsers.</li>
<li>Refinements to the MathML markup and processing model that enhance accessibility.</li>
<li>Depreciating elements and attributes from MathML that have had minimal adoption.</li>
</ul>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<ul>
<li>Changes that would cause legacy MathML that has significant usage to stop working on the Web Platform or elsewhere.</li>
<li>Significant changes in MathML 4 to Content MathML beyond those useful for accessibility.
Larger changes will be considered for MathML 5 after gaining experience and feedback from proposed additions to Presentation MathML and MathML Core.</li>
</ul>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/wiki/MathML/PubStatus">group publication status page</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="mathml-core1" class="spec"><a href="#">MathML Core Level 1</a></dt>
<dd>
<p>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).</p>
<p class="draft-status"><b>Working Draft:</b> <a href="https://www.w3.org/TR/mathml-core/">
Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> TBD + 9 months</p>
</dd>
<dt id="mathml-core2" class="spec"><a href="#">MathML Core Level 2</a></dt>
<dd>
<p>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.
</p>
<p>The MathML Core specifications are intended to define those parts of MathML that are, or will be, implemented by all major browser engines.</p>
<p class="draft-status"><b>Draft state:</b> No draft </p>
<p class="milestone"><b>Working Draft:</b> TBD + 18 months</p>
</dd>
<dt id="mathml4" class="spec"><a href="#">MathML 4</a></dt>
<dd>
<p>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.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://w3c.github.io/mathml//">Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> TBD + 20 months</p>
</dd>
<dt id="mathml5" class="spec"><a href="#">MathML 5</a></dt>
<dd>
<p>Collect requirements for MathML 5 based on deferred issues.
This includes potential work around content MathML which was excluded from the previous charter.</p>
<p class="draft-status"><b>Draft state:</b> No draft</p>
<p class="milestone"><b>Working Draft:</b> TBD + 24 months</p>
</dd>
</dl>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Test suites and implementation reports for the specification.</li>
<li>Analysis of mathematical notation usage in world-wide writing systems, including but not limited to non-LTR writing systems.</li>
<li>MathML Accessibility Technique Notes.</li>
<li>Guides on annotating Presentation MathML for accessibility.</li>
<li>A repository for intent values and properties beyond those defined in a MathML 4 recommendation.</li>
<li>At least one open-source (example code) MathML-to-speech/MathML-to-braille implementation that makes use of accessibility annotations.</li>
<li>At least one TeX-to-MathML converter that incorporates accessibility annotations in its MathML output.
<li>Code to convert Content MathML to Presentation MathML with accessibility annotations.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<p>These dates are not meant as deadlines; work may need to continue after these dates to ensure the quality of the deliverables.</p>
<ul>
<li>TBD: First teleconference</li>
<li>TBD + 3 months: Candidate Recommendation, MathML Core</li>
<li>TBD + 5 months: Candidate Recommendation, MathML 4</li>
<li>TBD + 5 months: An implementation of MathML-to-speech/braille that makes use of accessibility annotations</li>
<li>TBD + 9 months: Proposed Recommendation, MathML Core</li>
<li>Sept 2024: First face-to-face meeting (TPAC)</li>
<li>TBD + 18 months: First Public Working Draft, MathML Core Level 2</li>
<li>TBD + 20 months: Proposed Recommendation MathML 4</li>
<li>Sept 2025: Second face-to-face meeting (TPAC)</li>
<li>TBD + 24 months: First Public Working Draft, MathM 5</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>In order to advance to
<a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have
<a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent interoperable
implementations</a> of every feature defined in the specification, where
interoperability can be verified by passing open test suites, and two or
more implementations interoperating with each other. In order to advance to
Proposed Recommendation, each normative specification must have an open
test suite of every feature defined in the specification.</p>
<p>The larger Web Platform ecosystem shows signs of movement toward creating and using new MathML content,
including direct use of core features and direct use of new accessibility features by authoring tools that create MathML content.
Additionally, at least two assistive technology products make use of the accessibility features when they are present in MathML content.
</p>
<p>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).
</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>To promote interoperability, all changes made to specifications
in Candidate Recommendation
or to features that have deployed implementations
should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
Testing efforts should be conducted via the <a href="https://github.com/web-platform-tests/wpt">Web Platform Tests</a> project.</p>
<!-- Horizontal review -->
<p>Each specification should contain sections detailing
security and privacy implications for implementers,
Web authors, and end users,
as well as recommendations for mitigations.
There should be a clear description of the residual risk
to the user or operator of that protocol
after threat mitigation has been deployed.</p>
<p>Each specification should contain a section on accessibility that describes the benefits and impacts,
including ways specification features can be used to address them, and
recommendations for maximizing accessibility in implementations.</p>
<p>The Math Working Group expects to follow the TAG Web Platform Design Principles.</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">horizontal review</a> for
accessibility, internationalization, performance, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. 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
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/Style/CSS/">CSS Working Group</a></dt>
<dd>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.</dd>
<dt><a href="https://www.w3.org/community/wicg/">Web Incubator Community Group (WICG)</a></dt>
<dd>The Web Platform Incubator Community Group
(<a href="https://www.w3.org/community/wicg/">WICG</a>)
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
<a href="https://www.w3.org/community/wicg">WICG</a>
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.
</dd>
<dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a></dt>
<dd>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.</dd>
<dt><a href="https://www.w3.org/WAI/ARIA/">ARIA Working Group</a></dt>
<dd>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
<a href="">MathML AAM</a>
and continue to improve the accessibility of that which is part of MathML.
</dd>
<dt><a href="https://www.w3.org/publishing/groups/epub-wg/">EPUB Working Group</a></dt>
<dd>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.</dd>
<dt><a href="https://www.w3.org/Graphics/SVG/">SVG Working Group</a></dt>
<dd>The SVG Working Group is responsible for the development of
<a href="https://www.w3.org/TR/SVG11/">SVG</a>.
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
<a href="https://html.spec.whatwg.org/multipage/dom.html%23embedded-content-category">embedded content</a>.
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
<a href="https://www.w3.org/community/svgcg/">SVG CG</a>).
</dd>
<dt><a href="https://www.w3.org/community/chem-web-pub/">Chemistry for the Web and Publishing Community Group</a> (Chem CG)</dt>
<dd>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.</dd>
<dt><a href="https://www.w3.org/community/publishingcg/">Publishing Community Group</a></dt>
<dd>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.</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="https://whatwg.org/">WHATWG</a></dt>
<dd>The
<a href="https://whatwg.org/">WHATWG</a>
is responsible for the development of
<a href="https://html.spec.whatwg.org/multipage/">HTML</a>
and
<a href="https://dom.spec.whatwg.org/">DOM</a>.
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
<a href="https://www.w3.org/community/wicg/">WICG</a>).
</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
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.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: 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.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/Math">Math Working Group home page.</a>
</p>
<p>
Most Math Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on <a id="public-github" href="https://github.com/mathml-refresh/mathml/issues">GitHub issues</a>.
The public is invited to review, discuss and contribute to this work.
</p>
<p>
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.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 3.3</a>). 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.</p>
<p>
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.
</p>
<p>
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.
</p>
<p>
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.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (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 <a href="https://www.w3.org/groups/wg/[shortname]/ipr">licensing information</a>. </p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. 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.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p> The Math Working group was first chartered in 1998 and has produced three versions of MathML since then.
After the MathML 3 spec was released, the Working Group decided that a pause was needed and the group's charter
ended in 2016. The <a href="https://www.w3.org/community/mathml4/">MathML refresh community group</a> was formed form in 2019 to consider ideas for how to expand browser implementation of MathML and modernize the recommendation to be more in align with current the web platform. This eventually lead to the charter history shown below.
</p>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 4.3, Advisory Committee Review of a Charter)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a>Initial Charter</a>
</th>
<td>
1 April, 2021
</td>
<td>
31 May, 2023
</td>
<td>
</td>
</tr>
<tr>
<th>
<a>Charter Extension</a>
</th>
<td>
1 June, 2023
</td>
<td>
21 August, 2023
</td>
<td>
</td>
</tr>
</tbody>
</table>
</section>
<section id="changelog">
<h3>Change log</h3>
<p>Changes to this document are documented in this section.</p>
<dl id='changes'>
<dt>2021-05-20</dt>
<dd>Brian Kardell appointed as group co-chair</dd>
</dl>
</section>
</section>
</main>
<hr>
<footer>
<address>
<i class="todo"><a href="mailto:bert@w3.org">[Bert Bos]</a></i>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©2023
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="https://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<hr>
<p><a href="https://github.com/w3c/charter-drafts">Yes, it's on GitHub!</a>.</p>
</footer>
</body>
</html>