Minutes: MathML Full Meeting, 6 Aug, 2026

 Attendees:

   - Neil Soiffer
   - Louis Maher
   - David Carlisle
   - Deyan Ginev
   - Paul Libbrecht
   - Bruce Miller

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

1.1 Polyfills Security Update (FastURI) David reported a Dependabot alert
regarding the FastURI node library used in the polyfills. A security
advisory requires updating the dependency to ≥ 3.15. Paul agreed to perform
the update.

1.2 MathML Security Review (Intent) A horizontal security review was issued
for MathML intent. Concerns relate to potential system limits when
expanding intents. Neil will read the review before next week’s meeting.

“There’s a security review on MathML about intent… they want us to put some
wording about… expanding intents.”

1.3 #582 review MUST/MAY/SHOULD <https://github.com/w3c/mathml/issues/582>
update

Neil used AI to scan the spec for capitalization correctness of normative
keywords. Some chapters clearly required uppercase SHOULD/MUST; others were
ambiguous. The group agreed changes may be appropriate but must be manually
reviewed.

“Really should have been ‘should’ in lowercase… others could go either
way.” Neil also noted AI performance has significantly improved in reading
complex documents such as Braille specs.
<https://cryptpad.fr/#cp-md-0-2-continuation-of-a-href-https-dginev-github-io-mathml-intent-open-editor-open-intent-editor-a-discussion-appropriate-keys-in-yaml->2.
Continuation of open intent editor
<https://dginev.github.io/mathml-intent-open-editor/> discussion
(appropriate keys in YAML)

Deyan presented a fully populated example YAML entry for rising factorial,
showing all currently used keys. “This is an example with all the keys
used… the only mandatory key is concept.”
<https://cryptpad.fr/#cp-md-0-2-1-current-keys-discussed>2.1 Current Keys
Discussed

   - concept (mandatory)
   - speech (languages nested under this)
   - property (likely should be plural: properties)
   - area (suggested rename: subject area)
   - alias
   - URLs (definition links)
   - notations (with tex and mathml fields)

<https://cryptpad.fr/#cp-md-0-2-2-intent-vs-arity>2.2 Intent vs Arity

Consensus:

   - Replace arity with intent, containing the full intent expression with
   named parameters.
   - Named parameters (e.g., $base, $power) must be included to determine
   argument order. “Given that you’re using names, that has to be mandatory…
   otherwise you have no idea what the order is.”

<https://cryptpad.fr/#cp-md-0-2-3-speech-model>2.3 Speech Model

Discussion focused on:

   - Mandatory vs optional speech strings
   - Support for verbose and terse variants
   - Conditional speech (e.g., square root special cases)
   - Multiple speech variants per language

Deyan proposed a unified structure:

   - speech:
      - language:
         - condition:
         - verbose:
         - terse:
         - (additional variants allowed)

Paul emphasized that verbose/terse should be encouraged but not required.
<https://cryptpad.fr/#cp-md-0-2-4-comments-field>2.4 Comments Field

Neil proposed adding a comments field for explanatory notes not covered by
other keys. “A catch all field of comments… explanations, differences,
general ideas.”
<https://cryptpad.fr/#cp-md-0-2-5-alignment-with-core-yaml>2.5 Alignment
with Core YAML

David noted the existing core YAML already includes:

   - conditional speech
   - verbose/terse variants

comments The group agreed the open editor schema should align with the core
Schema.
3. Action Items

Update FastURI dependency in polyfills to ≥ 3.15 Paul Libbrecht In
progress; may require more time.

Review MathML intent security issue Neil Soiffe.r To be discussed next week.

Continue refining YAML key schema for open intent editor. Deyan Ginev. Will
iterate and return next week.

Review AI suggested MUST/MAY/SHOULD changes. Entire group. Manual
verification required.