Minutes: MathML Full Meeting, 20 March 2025

The minutes are brief this week because we didn't have the services of
Louis this week...Attendees:

   - David Carlisle
   - Stella Vouthsina
   - Paul Libbrecht
   - Bruce Miller
   - Neil Soiffer
   - Deyan Ginev
   - Neil Soiffer

<https://cryptpad.fr/#cp-md-0-regrets>Regrets

   - Louis Maher

<https://cryptpad.fr/#cp-md-0-agenda>Agenda
<https://cryptpad.fr/#cp-md-0-1-announcements-updates-progress-reports>1.
Announcements/Updates/Progress reports

DG: have most of the infrastructure in place for concept submission UI,
demo expected in a couple of weeks.

PL: On sanitizer we need to warn people which elements are affected. We
need to decide whether to close issue
https://github.com/w3c/mathml-core/issues/227 mathml-core which jumps to
[Sanitizer's #103](https://github.com/WICG/sanitizer-api/issues/103

DC: Message from Brian re MathML Core meeting this month, feeling we could
cancel and raise any Core issues on any Thursday Meeting.
<https://cryptpad.fr/#cp-md-0-2-a-href-https-github-com-w3c-mathml-issues-181-181-mathml-4-extensions-for-alignment-and-possible-deprecation-of-maligngroup-and-malignmark-a->2.
#181: MathML 4 extensions for alignment and possible deprecation of
(maligngroup/) and (malignmark/) <https://github.com/w3c/mathml/issues/181>

Action DC: to make a PR amending the spec as outlined in the comments in
the issue.
<https://cryptpad.fr/#cp-md-0-3-a-href-https-github-com-w3c-mathml-issues-385-385-comments-on-chapter-3-a->3.
#385: comments on chapter 3 <https://github.com/w3c/mathml/issues/385>

(updates/new thoughts on how to handle examples?)

I think the intended issue was
#284 Make the sample presentation of Strict Content use intent
<https://github.com/w3c/mathml/issues/284> and PR 550
<https://github.com/w3c/mathml/pull/530>

DC: This PR adds simple core intents to two of the blocks of examples
including showing |x| distinguished as absolute value and cardinality, and
is probably enough to close the issue. Other intents could be added later
if good cases come up.
<https://cryptpad.fr/#cp-md-0-4-a-href-https-github-com-w3c-mathml-issues-120-120-remove-deprecate-simplify-the-ms-element-a->4:
#120: Remove/deprecate/simplify the ms element
<https://github.com/w3c/mathml/issues/120>

(both core and full -- where are we on this?)

This item was accidentally skipped
<https://cryptpad.fr/#cp-md-0-5-a-href-https-github-com-w3c-mathml-issues-433-433-include-or-not-a-sample-set-of-default-conversion-from-plain-mathml-to-mathml-with-intent-a->5.
#433 include (or not) a sample-set of default conversion from plain-MathML
to MathML-with-intent <https://github.com/w3c/mathml/issues/433>

(discuss need for "Common" for "intent-default") -- any progress?

DC: There was some discussion between all participants on this, ending in
consensus to ad :legacy which will be an explicit system-specific set of
rules, and define that the behaviour if no such property is specified that
this is :legacy

BM: suggested we may need a property meaning "use as much inference as
possible so more than :common and perhaps more like mathcat, but we agreed
to defer decision on that until later, after the current proposal merged."
<https://cryptpad.fr/#cp-md-0-6-a-href-https-github-com-w3c-mathml-issues-523-523-missing-property-to-indicate-needed-grouping-a->6
#523: Missing property to indicate needed grouping?
<https://github.com/w3c/mathml/issues/523>

This item was skipped, due to Neil being unwell.
<https://cryptpad.fr/#cp-md-0-7-a-href-https-github-com-w3c-mathml-issues-1-1-simplification-of-the-mstyle-element-a->7
#1 Simplification of the mstyle element
<https://github.com/w3c/mathml/issues/1>

DC: described the current state with one existing PR to move scriptlevel
and displaystyle to be a common presentation attriute, annd that left just
4 non-core attributes unique to mstyle. Proposal accepted that should make
a second PR that moves the remaoning attributes which woul dthen leave
mstyle being identical to mrow, as in core.