First Public Working Draft: Mathematical Markup Language (MathML) Version 4.0

Mathematical Markup Language (MathML) Version 4.0

https://www.w3.org/TR/2022/WD-mathml4-20220908/

Published by
 Math Working Group

Abstract

This specification defines the Mathematical Markup Language, or MathML. MathML is a markup language for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as [HTML] has enabled this functionality for text. 

This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. 

MathML can be used to encode both mathematical notation and mathematical content. About thirty-eight of the MathML tags describe abstract notational structures, while another about one hundred and seventy provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of special characters used for mathematics, their handling in MathML, their presence in Unicode, and their relation to fonts. 

While MathML is human-readable, authors typically will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools exist, both freely available software and commercial products, and more are under development. 

MathML was originally specified as an XML application and most of the examples in this specification assume that syntax. Other syntaxes are possible, most notably [HTML] specifies the syntax for MathML in HTML. Unless explicitly noted, the examples in this specification are also valid HTML syntax.

Status of the Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/. 

Public discussion of MathML and issues of support through the W3C for mathematics on the Web takes place on the public mailing list of the Math Working Group (list archives). To subscribe send an email to www-math-request@w3.org with the word subscribe in the subject line. Alternatively, report an issue at this specification's GitHub repository. 

A fuller discussion of the document's evolution can be found in I. Changes. 

Some sections are collapsed and may be expanded to reveal more details. The following button may be used to expand all such sections. Expand All Sections 

This document was published by the Math Working Group as a First Public Working Draft using the Recommendation track.

Publication as a First Public Working Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 2 November 2021 W3C Process Document.



Issue summary 

  * Issue 304: Potential presentation MathML items to deprecate in MathML 4
  * Issue 180: "decimalpoint" value definition
  * Issue 284: Make the sample presentation of Strict Content use intent
  * Issue 257: Intent "alias" capability
  * Issue 255: Are intents needed in intent-core for "self-describing" things?
  * Issue 254: Need a scheme/philosophy/plan for unifying/breaking apart "level 0" names
  * Issue 253: n-ary Intent discussion
  * Issue 410: Intent: location/arrangement of names
  * Issue 337: Intent for "mtable" constructs
  * Issue 402: sibling intent references
  * Issue 267: Chapter: Interactions with the Host Environment updates
  * Issue 247: Spec should specify what char to use for accents/lines
  * Issue 178: Make MathML attributes ASCII case-insensitive
  * Issue 361: structuring common attributes

-- 
This report was automatically generated using https://github.com/w3c/transition-notifier

Received on Thursday, 8 September 2022 16:38:32 UTC