A MathML for CSS profile

W3C Working Draft 14 December 2007

This version:
Latest version:
Previous versions:
Bert Bos, W3C
David Carlisle, NAG
George Chavchanidze, Opera Software
Patrick D. F. Ion, Mathematical Reviews, American Mathematical Society
Bruce R. Miller, National Institute of Standards and Technology


This document describes a profile of MathML 3.0 that admits formatting with Cascading Style Sheets.

Status of this Document

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

This document is a W3C Public Working Draft produced by the W3C Math Working Group as part of W3C Math Activity. The goals of the W3C Math Working Group are discussed in the W3C Math WG Charter. The authors of this document are the W3C Math Working Group members.

Publication as a Working Draft does not imply endorsement by the W3C Membership. 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 Working Draft specifies a profile of a specification, MathML 3.0 [mathml], which is itself under development, and is intended to accord with current CSS [css], which is also under active development. The Math WG hopes this draft will permit informed feedback on this part of its work. There is also a short description of some considerations underlying this work in the W3C Math WG's public Roadmap [roadmap]. Feedback should be sent to the Public W3C Math mailing list (list archives).

This document was produced by a group operating under the 5 February 2004 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.

Table of Contents

1 Introduction
    1.1 Differences in formatting models
2 Math Elements
    2.1 Root element
    2.2 Token elements and layout schemata
    2.3 Required Arguments
    2.4 Common attributes
3 Token Elements
    3.1 Identifier (mi)
    3.2 Number (mn)
    3.3 Operator (mo)
    3.4 Text (mtext)
    3.5 Space (mspace)
    3.6 String Literal (ms)
4 General Layout Schemata
    4.1 Horizontally Group Sub-Expressions (mrow)
    4.2 Fractions (mfrac)
    4.3 Radicals (msqrt, mroot)
    4.4 Error Message (merror)
    4.5 Making Sub-Expressions Invisible (mphantom)
    4.6 Expression Inside Pair of Fences (mfenced)
    4.7 Enclose Expression Inside Notation (menclose)
5 Script and Limit Schemata
    5.1 Subscript (msub)
    5.2 Superscript (msup)
    5.3 Subscript-superscript Pair (msubsup)
    5.4 Underscript (munder)
    5.5 Overscript (mover)
    5.6 Underscript-overscript Pair (munderover)
    5.7 Prescripts (mmultiscripts)
6 Tables and Matrices
    6.1 Table or Matrix (mtable)
    6.2 Row in a Table or Matrix (mtr)
    6.3 Entry in a Table or Matrix (mtd)
7 Annotations
    7.1 Bind Action to a Sub-Expression (maction)
    7.2 Add semantic mapping (semantics)
8 Extensibility and Conformance
    8.1 Extensibility
    8.2 Conformance
9 Differences between MathML presentational markup and present profile
10 Document Type Definition
11 Default CSS style sheet
12 References

1 Introduction

The current profile is intended to be subset of MathML 3.0 [mathml] that could be used to capture structure of mathematical formulae in the way suitable for further CSS formatting. This profile is expected to facilitate adoption of MathML in web browsers and CSS formatters, allowing them to reuse existing CSS [css] visual formatting model, enhanced with a few mathematics-oriented extensions, for rendering of the layout schemata of presentational MathML. Development of the CSS profile is assumed to be coordinated with ongoing work on CSS. As specified in this a restricted part of MathML3 properly used should render well with currently implemented CSS up to CSS 2.1. Some descriptions are offered of what might be done better were a limited set of new properties to be added to CSS3 modules.

It may be useful to note, in connection with the need for this profile, that the CSS2 specification [css2] was developed and refined at about the same time as the first MathML specification [mathml1]. Now new versions of both MathML and CSS are being created. This profile is thus part of the ongoing effort to realize the synergy that W3C Recommendations offer to the Web.

1.1 Differences in formatting models

The Math Working Group has identified the following issues, which are considered to be the main obstacles delaying fully consistent MathML/CSS integration.

  • Insufficient control over vertical alignment of complex inline expressions such as inline tables with multiple rows.

  • Lack of a mechanism to control stretching of glyphs, or any equivalent functionality, that could be used for sizing of mathematical delimiters and stretchy operators.

  • Limited scope in the use of selectors and generation of content, which makes it difficult to apply complex formatting to basic structural markup.

  • The order of children in presentational elements such as mover, munderover, mmultiscripts and mroot does not match their in-flow positions; this makes formatting of such elements more difficult.

  • Handling of operators, delimiters and accents governed by an operator dictionary (that is by element content rather than attribute values) rather than by explicit markup makes matching of such operators using CSS selectors impossible.

  • Usage of some presentational elements such as mpadded, mspace, mstyle might conflict with corresponding CSS formatting properties.

2 Math Elements

2.1 Root element

MathML specifies a single top-level or root math element, which encapsulates each instance of MathML markup within a document. All other MathML markup must be contained in a math element, which must always be the outermost element of a MathML expression and can contain an arbitrary number of children. The math element carries the display attribute that specifies whether the enclosed MathML expression should be rendered in a display style or an in-line style. Allowed values are "block" and "inline" (default). It also accepts altimg and alttext attributes that provide fall-back for User Applications (UAs) that do not support MathML layout schemata. The values of altimg and alttext attributes are URI and CDATA respectively. All MathML elements should be in the MathML namespace http://www.w3.org/1998/Math/MathML [rec-xmlns]. This can be ensured by adding a default namespace declaration to math elements, or by using namespace prefixes bound to the MathML namespace.

2.2 Token elements and layout schemata

MathML elements included in the current profile can be divided into two classes. Token elements represent individual symbols, names, numbers, labels, etc. In general, tokens can have only character data as content. Layout schemata build expressions out of parts, and can only have elements as content except for whitespace, which they ignore. There are also a few empty elements used only in conjunction with specific layout schemata.

All individual "symbols" in a mathematical expression should be represented by MathML token elements. The primary MathML token element types are identifiers (e.g. variables or function names), numbers, and operators (including fences, such as parentheses, and separators, such as commas). There are also token elements for representing text or whitespace that has more aesthetic than mathematical significance, and for representing "string literals" for compatibility with computer algebra systems. Note that although a token element represents a single meaningful "symbol" (name, number, label, mathematical symbol, etc.), such symbols may be comprised of more than one character. For example sin and 24 are represented by the single tokens <mi>sin</mi> and <mn>24</mn> respectively.

Token elements included in the current profile are summarized in the table below.

mooperator, fence or separator
msstring literal

In traditional mathematical notation, expressions are recursively constructed out of smaller expressions, and ultimately out of single symbols, with the parts grouped and positioned using one of a small set of notational structures, which can be thought of as "expression constructors". In MathML, expressions are constructed in the same way, with the layout schemata playing the role of the expression constructors. The layout schemata specify the way in which sub-expressions are built into larger expressions. The terminology derives from the fact that each layout schema corresponds to a different way of "laying out" its sub-expressions to form a larger expression in traditional mathematical typesetting.

Basic expression constructions included in the current profile are listed in the table below.

mrowgroups any number of sub-expressions horizontally
mfracforms a fraction from two sub-expressions
msqrtforms a square root (radical without an index)
mrootforms a radical with specified index
merrorencloses a syntax error message from a preprocessor
mphantommakes content invisible but preserve its size
mfencedsurrounds content with a pair of fences
mencloseencloses content with a stretching symbol
msubattaches a subscript to a base
msupattaches a superscript to a base
msubsupattaches a subscript-superscript pair to a base
munderattaches an underscript to a base
moverattaches an overscript to a base
munderoverattaches an underscript-overscript pair to a base
mmultiscriptsattaches prescripts to a base
mtablemarks a table or matrix
mtrmarks a row in a table or matrix
mtdmarks a one entry in a table or matrix
mactionbinds actions to a sub-expression

2.3 Required Arguments

Some layout schemata require a specific number of arguments, for example mfrac is supposed to have two child elements representing numerator and denominator. In the current profile, layout schemata with fixed number of required arguments accept only elements mrow, maction, merror, mphantom and tokens mi, mn, mo, ms, mtext as child elements. This restrictions is imposed to ensure that each part of layout schemata has its own containing block and is uniquely represented in the document object model. For example nested fractions where the numerator or denominator are themselves fractions


are not allowed in the MathML for CSS profile, although they are allowed in MathML 3.0. It is easy to meet the profile requirements by wrapping nested fractions in mrow elements:


The number of arguments required by a particular layout schemata element is specified in the table below. Note that in the current profile, the content model of mfenced and maction is stricter compared to what is allowed by MathML 3.0 specification.

ElementRequired argument countArgument roles (when these differ by position)
mfrac2numerator denominator
mroot2base index
msub2base subscript
msup2base superscript
msubsup3base subscript superscript
munder2base underscript
mover2base overscript
munderover3base underscript overscript
mmultiscripts4base mprescripts presubscript presuperscript
maction2base tooltip

The elements mrow, msqrt, merror, mphantom, menclose, mtable, mtr, mtd and math admit any number of arguments and accept any layout schemata or token elements from current profile as children.

2.4 Common attributes

The attributes xml:id, class and style can be used on any element included in the current profile: xml:id provides a mechanism for annotating elements with unique identifiers [rec-xmlid], class assigns one or more class names to an element and style specifies style information for the current element. The attribute mathvariant is allowed on nonempty token elements, attribute is included in the profile for interoperability reasons to ensure that font changes are transparent for CSS unaware UAs.

The following table lists common attributes, their values and the elements on which they can be used.

Namevaluesdefaultvalid on
xml:idIDall elements
classNMTOKENSall elements
styleCDATAall elements
mathvariantnormal  | bold | italic | bold‑italic | sans-serif | bold‑sans‑serif | sans‑serif‑italic | sans‑serif‑bold‑italic | monospacenormalmn, mo, ms, mtext
mathvariantnormal  | bold | italic | bold‑italic | sans-serif | bold‑sans‑serif | sans‑serif‑italic | sans‑serif‑bold‑italic | monospaceitalicmi

3 Token Elements

Token elements in presentation markup are, broadly speaking, intended to represent the smallest units of mathematical notation which carry meaning. Tokens are roughly analogous to words in text. However, because of the precise, symbolic nature of mathematical notation, the various categories and properties of token elements figure prominently in MathML markup. By contrast, in textual data, individual words rarely need to be marked up or styled specially.

Frequently tokens consist of a single character denoting a mathematical symbol. Other cases, e.g., function names, involve multi-character tokens. Further, because traditional mathematical notation makes extensive use of symbols distinguished by their typographical properties, care must be taken to ensure that styling mechanisms respect typographical properties which carry meaning. Consequently, characters, tokens, and typographical properties of symbols are closely related to one another in MathML.

3.1 Identifier (mi)

An mi element represents a mathematical identifier; its rendering consists of the text content displayed in a typeface corresponding to the mathvariant attribute. Since the typeface used can distinguish similar identifiers, it often serves an important semantic function.

In MathML 3.0, the default value of mathvariant depends on the content of the element, it is "italic" for single character content (e.g., <mi>x</mi>) and "normal" otherwise (e.g., <mi>sin</mi>). Such behavior does not fit well in the scope of CSS, therefore in current profile "italic" is the default value regardless of the element content and mathematical identifiers for which a non-italic typeface is desired (e.g., multi-character identifiers), must explicitly specify the mathvariant attribute.

3.2 Number (mn)

An mn element represents a "numeric literal" or other data that should be rendered as a numeric literal. Generally speaking, a numeric literal is a sequence of digits, perhaps including a decimal point, representing an unsigned integer or real number.

A typical graphical renderer would render an mn element as the characters of its content, with no extra spacing around them (except spacing from neighboring elements such as mo).

3.3 Operator (mo)

An mo element represents an operator or anything that should be rendered as an operator. In MathML the list of things that should "render as an operator" is widely inclusive. Besides ordinary operators with infix, prefix, or postfix forms, fence characters such as braces, parentheses, and separators such as comma and semicolon are included. In the current profile the mo element is not expected to produce vertically stretchable delimiters; instead the mfenced element should be used for vertically stretchy delimiters such as stretchy brackets, braces, parentheses and vertical bars.

Note also that this profile does not rely on an operator dictionary, but instead it is recommended to mark fences, separators and large operators explicitly using fence, separator and largeop attributes. In addition, prefix, infix and postfix operators may be distinguished using the form attribute. In the present profile, the default value of this attribute is "prefix" if the mo element is the first child of a parent element that has many children, and "postfix" if mo element is the last child of a parent with multiple children; the value is "infix" in all other cases. Those mo tokens that represent fences such as brackets, braces, parens and vertical bars should be marked using the fence attribute, separators such as comma and semicolon should be marked using the separator attribute, while large operators such as sums, products and integrals may be labeled using the largeop attribute. UAs may rely on these attribute to infer default spacing around operators.

In the present profile stretchy operators are defined by the stretchar attribute's specifying a stretchy character to replaces the content of an mo element. The specified character is supposed to stretch to fill the available space (height of line box in case of vertically stretchy delimiters and the available width in case of horizontally stretchy delimiters). UAs that do not recognize a character specified by an stretchar attribute as stretchy should ignore the attribute and display the content of the mo element instead.

formprefix | infix | postfixdepends on position of mo element, see exact rules above
fencetrue | falsefalse
separatortrue | falsefalse
largeoptrue | falsefalse

3.4 Text (mtext)

An mtext element is intended to denote commentary text.

3.5 Space (mspace)

An mspace empty element represents a blank space of any desired size, as set by its attributes. It can also be used to make linebreaking suggestions to a visual renderer.

widthverythinmathspace | thinmathspace | mediummathspace | thickmathspace | verythickmathspace0
linebreakauto | newline | goodbreakauto

The width attribute defines the width of the space produced by an mspace element. The default value is zero. Named values are described in table below.

Named spacevalue (em)

The linebreak attribute is used to give a linebreaking hint to a visual renderer. Attribute values are defined in table below.

autodefault linebreaking algorithm (implementation dependent)
newlinestart a new line
goodbreakif a linebreak is needed on the line, here is a good spot

In the case when both the width attribute and the linebreak attribute are set, the linebreak attribute is ignored.

3.6 String Literal (ms)

The ms element is used to represent "string literals" in expressions meant to be interpreted by computer algebra systems or other systems containing "programming languages". By default, string literals are displayed surrounded by double quotes.

In visual renderers, the content of an ms element is typically rendered with no extra spacing added around the string, and quote characters at the beginning and the end of the string. By default, the left and right quote characters are both the standard double quote character ". However, these characters can be changed with the lquote and rquote attributes defined below.


4 General Layout Schemata

Besides tokens there are several families of MathML presentation elements. One family of elements deals with various "scripting" notations, such as subscript and superscript. Another family is concerned with matrices and tables. The remainder of the elements, discussed in this section, describe other basic notations such as fractions and radicals, or deal with general functions such as action binding and error handling.

4.1 Horizontally Group Sub-Expressions (mrow)

An mrow element is used to group together any number of sub-expressions, usually consisting of one or more mo elements acting as "operators" on one or more other expressions that are their "operands".

4.2 Fractions (mfrac)

The mfrac element is used for fractions. It can also be used to mark up the presentation of fraction-like objects such as binomial coefficients and Legendre symbols. The syntax for mfrac is:

<mfrac> numerator denominator </mfrac>

In addition to common attributes, mfrac has additional attributes that could be used to control horizontal alignment of numerator and denominator and thickness of fraction bar.

linethickness0 | 1 | 2 | medium | thick1
numalignleft | center | rightcenter
denomalignleft | center | rightcenter

The linethickness attribute indicates the thickness of the horizontal "fraction bar", or "rule", typically used to render fractions. Value "0" indicates that no bar should be rendered, value "1" (the same as "medium") refers to default width of fraction bar and "2" ("thick") produces bold fraction bar.

The numalign and denomalign attributes control the horizontal alignment of the numerator and denominator, respectively. Typically, numerators and denominators are centered.

4.3 Radicals (msqrt, mroot)

These elements construct radicals. The msqrt element is used for square roots, while the mroot element is used to draw radicals with indices, e.g., a cube root. The syntax for these elements is:

<msqrt> base </msqrt>
<mroot> base index </mroot>

The mroot element requires exactly 2 arguments. However, msqrt accepts any number of arguments.

4.4 Error Message (merror)

The merror element displays its contents as an "error message". The contents can be any expression or expression sequence.

4.5 Making Sub-Expressions Invisible (mphantom)

The mphantom element renders its content as invisible, but with the same size and other dimensions, including baseline position, that its contents would have if they were rendered normally; mphantom can be used to align parts of an expression by invisibly duplicating sub-expressions.

4.6 Expression Inside Pair of Fences (mfenced)

The mfenced element provides a convenient way of expressing common constructs involving fences (i.e., braces, brackets, and parentheses). The size of the fences depends on the size of the expression enclosed by the fence element. Opening and closing fences are specified using the open and close attributes defined below. This profile does not allow an mfenced element to have multiple children; authors are encouraged to group multiple children into one mrow element if this can be done.


4.7 Enclose Expression Inside Notation (menclose)

The menclose element renders its content inside the enclosing notation specified by its notation attribute, menclose accepts any number of arguments.

The values allowed for notation are open-ended. Conforming renderers may ignore any value they do not handle, although renderers are supposed to recognize at least the values listed below.

notationbox | left | right | top | bottom | horizontalstrike

The value "box" can be used to enclose content of the element in a frame. The values "left", "right", "top" and "bottom" should result in lines drawn on the corresponding sides of the contents, "horizontalstrike" should result in strikeout lines being superimposed over the content of the menclose.

5 Script and Limit Schemata

The elements described in this section position one or more scripts around a base. In addition to subscript and superscript elements, MathML has overscript and underscript elements that place scripts above and below the base.

Because presentation elements should be used to describe the abstract notational structure of expressions, it is important that the base expression in all "scripting" elements (i.e., the first argument expression) should be the entire expression that is being scripted, not just, as has been common, the rightmost character.

5.1 Subscript (msub)

The syntax for the msub element is:

 <msub> base subscript </msub>

The element is used to attach a subscript to a base.

5.2 Superscript (msup)

The syntax for the msup element is:

<msup> base superscript </msup>

The element is used to attach a superscript to a base.

5.3 Subscript-superscript Pair (msubsup)

The msubsup element is used to attach both a subscript and a superscript to a base expression.

The syntax for the msubsup element is:

<msubsup> base subscript superscript </msubsup>

5.4 Underscript (munder)

The syntax for the munder element is:

<munder> base underscript </munder>

The element is used to attach an underscript below a base.

5.5 Overscript (mover)

The syntax for the mover element is:

<mover> base overscript </mover>

The element is used to attach an overscript over a base.

5.6 Underscript-overscript Pair (munderover)

The syntax for the munderover element is:

 <munderover> base underscript overscript</munderover>

The element is used to attach both an underscript and an overscript to a base.

5.7 Prescripts (mmultiscripts)

In the current profile the syntax for the mmultiscripts element is:

<mmultiscripts> base <prescripts/> presubscript presuperscript</mmultiscripts>

This element allows adding pairs of prescripts to one base expression. Missing scripts can be represented by the empty element none.

The argument sequence consists of the base followed by an empty element mprescripts and a pair of, vertically aligned, a presubscript and a presuperscript.

6 Tables and Matrices

Matrices, arrays and other table-like mathematical notation are marked up using mtable, mtr, and mtd elements. These elements are similar to the table, tr and td elements of XHTML.

6.1 Table or Matrix (mtable)

A matrix or table is specified using the mtable element.

The following attributes may be used to specify alignment and to add frames and rules to the table.

rowaligntop | bottom | center | baselinebaseline
columnalignleft | center | rightcenter
rowlinesnone | solid | dashednone
columnlinesnone | solid | dashednone
framenone | solid | dashednone

Note that the default value for each of rowlines, columnlines and frame is the literal string none, meaning that the default is to render no lines, rather than that there is no default.

The rowalign attribute specifies how the entries in each row should be aligned. For example, "top" means that the tops of each entry in each row should be aligned with the tops of the other entries in that row. The columnalign attribute specifies how the entries in each column should be aligned.

6.2 Row in a Table or Matrix (mtr)

An mtr element represents one row in a table or matrix. An mtr element is only allowed as a direct sub-expression of an mtable element, and specifies that its contents should form one row of the table. Each argument of mtr is placed in a different column of the table, starting at the leftmost column.

The following attributes may be used to specify alignment

rowaligntop | bottom | center | baselineinherited
columnalignleft | center | rightinherited

The rowalign and columnalign attributes allow a specific row to override the alignment specified by the same attributes in the surrounding mtable element.

6.3 Entry in a Table or Matrix (mtd)

An mtd element represents one entry, or cell, in a table or matrix. An mtd element is only allowed as a direct sub-expression of an mtr.

The following attributes may be used to specify alignment

rowaligntop | bottom | center | baselineinherited
columnalignleft | center | rightinherited

The rowalign and columnalign attributes allow a specific matrix element to override the alignment specified by a surrounding mtable or mtr element.

7 Annotations

7.1 Bind Action to a Sub-Expression (maction)

To provide a mechanism for binding actions to expressions, MathML provides the maction element. The action type is specified by the actiontype attribute. Current profile defines only "tooltip" actiontype.

actiontypetooltip(required attribute, no default value)

<maction actiontype="tooltip"> base tooltip </maction>

When a mouse cursor is placed over an expression UAs that support this action type should display the content of the second child in a "tooltip" box.

7.2 Add semantic mapping (semantics)

The current profile deals with layout schemata that reflect the visual structure of mathematical formulae. To attach extra semantic information that describes the content of formulae or provide an alternative encoding of a mathematical expression one can use the Content MathML semantics element. In current profile content model of semantics element is limited to presentational MathML followed by annotation and/or annotation-xml elements.

8 Extensibility and Conformance

8.1 Extensibility

Since the current profile is designed to be suitable for use in an XML/CSS environment, it is relatively easy to extend it by adding new elements or attributes [rec-xml] to a DTD and specifying the default formatting in a style sheet. However any new elements should be placed in their own namespace and any new attributes added to existing MathML elements should have a namespace prefix; authors and implementers are strongly encouraged to use standard markup whenever possible. Similarly, maintainers of documents employing MathML extension mechanisms are encouraged to monitor relevant standards activity and to update documents to use more standardized markup as it becomes available.

8.2 Conformance

Documents that conform to this MathML for CSS profile should be conformant MathML 3.0 documents and should use only those MathML elements and attributes included in the current profile. The content of layout schemata with a fixed number of arguments should match the content model specified in the list of required arguments and the profile's DTD.

UAs that conform to the MathML for CSS profile should support all MathML elements and attributes included in profile. When a conformant UA encounters an element that it does not recognize it may ignore that element, but should process its content. UAs that support the standard DOM are encouraged to expose such elements through generic DOM Element interface. UAs that support style sheets are encouraged to apply formatting specified in style sheets to such elements.

9 Differences between MathML presentational markup and present profile

The MathML for CSS profile differs from full MathML presentational markup in a number of ways. The present section is intended to highlight the main differences.

10 Document Type Definition

The DTD included in the present working draft does not follow the conventions specified in [xhtml-modularization]; it will be changed appropriately in time for the Last Call WD

<!ENTITY % common "class NMTOKENS #IMPLIED xml:id ID #IMPLIED style CDATA #IMPLIED">
<!ENTITY % math "(maction | menclose | merror | mfenced | mfrac | mi | mmultiscripts | mn | mo | 
		mover | mphantom | mroot | mrow | ms | mspace | msqrt | msub | msubsup | msup |
		mtable | mtext | munder | munderover | semantics)+">
<!ENTITY % mrow "(mi | mn | mo | mphantom | maction | merror | mrow | ms | mtext)">
<!ATTLIST maction actiontype (tooltip) #REQUIRED %common;>
<!ELEMENT maction (%mrow;,%mrow;)>
<!ATTLIST math display (block | inline) #IMPLIED xmlns CDATA #REQUIRED
		alttext CDATA #IMPLIED altimage CDATA #IMPLIED %common;>
<!ELEMENT math %math;>
<!ATTLIST menclose notation (bottom | box | left | right | top | horizontalstrike) #REQUIRED %common;>
<!ELEMENT menclose %math;>
<!ATTLIST merror %common;>
<!ELEMENT merror %math;>
<!ATTLIST mfenced open CDATA #IMPLIED close CDATA #IMPLIED %common;>
<!ELEMENT mfenced %mrow;>
<!ATTLIST mfrac linethickness (0 | 1 | 2 | medium | thick) #IMPLIED 
		numalign (center | left | right) #IMPLIED denalign (center | left | right) #IMPLIED %common;>
<!ELEMENT mfrac (%mrow;,%mrow;)>
<!ATTLIST mi mathvariant (normal | bold | italic | bold-italic | sans-serif | bold-sans-serif | 
		sans-serif-italic | sans-serif-bold-italic | monospace) #IMPLIED %common;>
<!ATTLIST mmultiscripts %common;>
<!ELEMENT mmultiscripts (%mrow;,mprescripts,((none,%mrow;)|(%mrow;,(none|%mrow;))))>
<!ATTLIST mn mathvariant (normal | bold | italic | bold-italic | sans-serif | bold-sans-serif | 
		sans-serif-italic | sans-serif-bold-italic | monospace) #IMPLIED %common;>
<!ATTLIST mo largeop (true | false) #IMPLIED separator (true | false) #IMPLIED fence (true | false) #IMPLIED
		form (prefix | infix | postfix) #IMPLIED stretchar CDATA #IMPLIED
		mathvariant (normal | bold | italic | bold-italic | sans-serif | 
		bold-sans-serif | sans-serif-italic | sans-serif-bold-italic | monospace) #IMPLIED %common;>
<!ATTLIST mover %common;>
<!ELEMENT mover (%mrow;,%mrow;)>
<!ATTLIST mphantom %common;>
<!ELEMENT mphantom %math;>
<!ATTLIST mprescripts %common;>
<!ELEMENT mprescripts EMPTY>
<!ATTLIST mroot %common;>
<!ELEMENT mroot (%mrow;,%mrow;)>
<!ATTLIST mrow %common;>
<!ELEMENT mrow %math;>
<!ATTLIST ms lquote CDATA #IMPLIED rquote CDATA #IMPLIED %common;>
<!ATTLIST msqrt %common;>
<!ELEMENT msqrt %math;>
<!ATTLIST msub %common;>
<!ELEMENT msub (%mrow;,%mrow;)>
<!ATTLIST msubsup %common;>
<!ELEMENT msubsup (%mrow;,%mrow;,%mrow;)>
<!ATTLIST msup %common;>
<!ELEMENT msup (%mrow;,%mrow;)>
<!ATTLIST mtable 
	rowalign (top | bottom | center | baseline) #IMPLIED
	columnalign (left | center | right) #IMPLIED
	rowlines (none | solid | dashed) #IMPLIED
	columnlines (none | solid | dashed) #IMPLIED
	frame (none | solid | dashed) #IMPLIED %common;>
<!ELEMENT mtable (mtr+)>
<!ATTLIST mtd 
	rowalign (top | bottom | center | baseline) #IMPLIED
	columnalign (left | center | right) #IMPLIED %common;>
<!ELEMENT mtd %math;>
<!ATTLIST mtext mathvariant (normal | bold | italic | bold-italic | sans-serif | bold-sans-serif | 
		sans-serif-italic | sans-serif-bold-italic | monospace) #IMPLIED %common;>
<!ELEMENT mtext (#PCDATA)>
<!ATTLIST mtr 
	rowalign (top | bottom | center | baseline) #IMPLIED 
	columnalign (left | center | right) #IMPLIED %common;>
<!ELEMENT mtr (mtd+)>
<!ATTLIST munder %common;>
<!ELEMENT munder (%mrow;,%mrow;)>
<!ATTLIST munderover %common;>
<!ELEMENT munderover (%mrow;,%mrow;,%mrow;)>
<!ATTLIST mspace width (verythinmathspace | thinmathspace | mediummathspace | thickmathspace | verythickmathspace) #IMPLIED 
		linebreak (auto | newline | goodbreak) #IMPLIED %common;>
<!ATTLIST none %common;>
<!ELEMENT semantics (%math;,(annotation|annotation-xml)*)>
<!ATTLIST annotation definitionURL CDATA #IMPLIED encoding CDATA #REQUIRED>
<!ELEMENT annotation (#PCDATA)>
<!ATTLIST annotation-xml definitionURL CDATA #IMPLIED encoding CDATA #REQUIRED>
<!ELEMENT annotation-xml ANY>

11 Default CSS style sheet

(this section is non normative)

This profile admits a default CSS style sheet that could be used to render MathML in CSS aware UAs. In the long term perspective it would be appropriate to extend CSS3 with a few math specific properties, until then one can use style sheet enclosed below for formatting of MathML defined in the current profile.

@namespace "http://www.w3.org/1998/Math/MathML";
	margin:0 2px;
mfrac > *
mfrac > *:first-child
mfrac > * + *
	{border-top:solid thin;
mfrac[linethickness="0"] > * + *
mfrac[linethickness="2"] > * + *, mfrac[linethickness="thick"] > * + *
	{border-top:solid medium;}
mfrac[numalign="left"] > *:first-child, mfrac[denalign="left"] > * + *
mfrac[numalign="right"] > *:first-child, mfrac[denalign="right"] > * + *
msub, msup, msubsup, mmultiscripts
msubsup, msup, mmultiscripts
msubsup, msub, mmultiscripts
msubsup, msup
msub > *
msubsup > *, msup > *
mmultiscripts > *
mmultiscripts > *:first-child, mmultiscripts > mprescripts + *
mmultiscripts > mprescripts + * + *
msub > *:first-child:after, msub > * + *:before, 
msubsup > *:first-child:before, msup > *:first-child:before,
mmultiscripts > *:first-child:before
msubsup > * + * + *, msup > * + *
msub > * + *, msup > * + *, msubsup > * + *, munder > * + *, mover > * + *, munderover > * + *,
mmultiscripts > * + *
munder, munderover, mover
munder > *, munderover > *, mover > *
mover > * + *, munderover > * + * + *
mover, munderover
	margin:1px 0 1px 22px;
	border-top:solid 1px;
	border-left:groove 2px;
	padding:2px 5px 0 0;}
	margin:0 3px 0 -22px;}
msqrt:before, mroot > * + *:after
mroot > *
mroot > *:first-child
	{border-top:solid 1px;
	border-left:groove 2px;
	padding:2px 5px 0 3px;}
mroot > * + *
mroot > * + *:after
	border-spacing:0.2ex 0;
mfenced > *:first-child
mfenced > * + *
mfenced > *:before, mfenced > *:after
	background-size:100% 100%;}
mfenced > *:before
mfenced > *:after
mfenced[open="["] > *:before
	border-width:1px 0 1px 1px;
mfenced[close="]"] > *:after
	border-width:1px 1px 1px 0;
mfenced[open="\2016"] > *:before
	border-width:0 0 0 3px;
mfenced[close="\2016"] > *:after
	border-width:0 3px 0 0;
mfenced[open="\27e6"] > *:before
	border-width:2px 0 2px 3px;
mfenced[close="\27e7"] > *:after
	border-width:2px 3px 2px 0;
mfenced[open="|"] > *:before
	border-width:0 0 0 1px;
mfenced[close="|"] > *:after
	border-width:0 1px 0 0;
mfenced[open="\230a"] > *:before
	border-width:0 0 1px 1px;
mfenced[close="\230b"] > *:after
	border-width:0 1px 1px 0;
mfenced[open="\2308"] > *:before
	border-width:1px 0 0 1px;
mfenced[close="\2309"] > *:after
	border-width:1px 1px 0 0;
mfenced[open="{"] > *:before
mfenced[close="}"] > *:after
mfenced[open="\27e8"] > *:before, mfenced[open="\2329"] > *:before
mfenced[close="\27e9"] > *:after, mfenced[close="\232A"] > *:after
mfenced[open=""] > *:before, mfenced[close=""] > *:after
mover > * + mo[fence="true"], munder > * + mo[fence="true"]
	background-size:100% 100%;
munder > * + mo[fence="true"]
	border-spacing:0.4ex 0;}
	{border-top:solid thin;}
	{border-bottom:solid thin;}
	{border-right:solid thin;}
	{border-left:solid thin;}
	{border:solid thin;}
	padding:0 0.5ex;}
mtable[columnalign="left"], mtr[columnalign="left"], mtd[columnalign="left"]
mtable[columnalign="right"], mtr[columnalign="right"], mtd[columnalign="right"]
mtable[rowalign="top"] mtd, mtable mtr[rowalign="top"] mtd, 
math mtable mtr mtd[rowalign="top"]
mtable[rowalign="bottom"] mtd, mtable mtr[rowalign="bottom"] mtd, 
math mtable mtr mtd[rowalign="bottom"]
mtable[rowalign="center"] mtd, mtable mtr[rowalign="center"] mtd, 
math mtable mtr mtd[rowalign="center"]
	{border:solid thin;}
	{border:dashed thin;}
mtable[rowlines="solid"], mtable[rowlines="dashed"], 
mtable[columnlines="solid"], mtable[columnlines="dashed"]
mtable[rowlines="solid"] > mtr + mtr
	{border-top:solid thin;}
mtable[rowlines="dashed"] > mtr + mtr
	{border-top:dashed thin;}
mtable[columnlines="solid"] > mtr > mtd + mtd
	{border-left:solid thin;}
mtable[columnlines="dashed"] > mtr > mtd + mtd
	{border-left:dashed thin;}
mspace[linebreak="newline"]:before, mspace[linebreak="indentingnewline"]:before 
	{padding:0 0.05em;}
	{padding:0 0.08em;}
	{padding:0 0.11em;}
	{padding:0 0.14em;}
	{padding:0 0.17em;}
mo[form="infix"], * + mo
	{padding:0 0.3ex;}
	{padding:0 0 0 0.5ex;}
	{padding:0 0.5ex 0 0;}
mo[fence="true"], mo[separator="true"]
mi[mathvariant="bold"], mi[mathvariant="bold-italic"], mi[mathvariant="bold-sans-serif"], 
mi[mathvariant="sans-serif-bold-italic"],mn[mathvariant="bold"], mn[mathvariant="bold-italic"], 
mn[mathvariant="bold-sans-serif"], mn[mathvariant="sans-serif-bold-italic"],mo[mathvariant="bold"], 
mo[mathvariant="bold-italic"], mo[mathvariant="bold-sans-serif"], mo[mathvariant="sans-serif-bold-italic"],
ms[mathvariant="bold"], ms[mathvariant="bold-italic"], ms[mathvariant="bold-sans-serif"], 
ms[mathvariant="sans-serif-bold-italic"],mtext[mathvariant="bold"], mtext[mathvariant="bold-italic"], 
mtext[mathvariant="bold-sans-serif"], mtext[mathvariant="sans-serif-bold-italic"]
mi[mathvariant="monospace"], mn[mathvariant="monospace"],mo[mathvariant="monospace"], 
mi[mathvariant="sans-serif"], mi[mathvariant="bold-sans-serif"], mi[mathvariant="bold-sans-serif"], 
mi[mathvariant="sans-serif-italic"], mi[mathvariant="sans-serif-bold-italic"],mn[mathvariant="bold-sans-serif"],
mn[mathvariant="sans-serif"], mn[mathvariant="bold-sans-serif"], mn[mathvariant="sans-serif-italic"],
mn[mathvariant="sans-serif-bold-italic"], mo[mathvariant="sans-serif"], mo[mathvariant="bold-sans-serif"], 
mo[mathvariant="bold-sans-serif"], mo[mathvariant="sans-serif-italic"], mo[mathvariant="sans-serif-bold-italic"], 
ms[mathvariant="sans-serif"], ms[mathvariant="bold-sans-serif"], ms[mathvariant="bold-sans-serif"], 
ms[mathvariant="sans-serif-italic"], ms[mathvariant="sans-serif-bold-italic"], mtext[mathvariant="sans-serif"], 
mtext[mathvariant="bold-sans-serif"], mtext[mathvariant="bold-sans-serif"], mtext[mathvariant="sans-serif-italic"], 
mi, mi[mathvariant="italic"], mi[mathvariant="bold-italic"],mi[mathvariant="sans-serif-italic"], 
mi[mathvariant="sans-serif-bold-italic"],mn[mathvariant="italic"], mn[mathvariant="bold-italic"],
mn[mathvariant="sans-serif-italic"], mn[mathvariant="sans-serif-bold-italic"],mo[mathvariant="italic"], 
mo[mathvariant="bold-italic"],mo[mathvariant="sans-serif-italic"], mo[mathvariant="sans-serif-bold-italic"],
ms[mathvariant="italic"], ms[mathvariant="bold-italic"],ms[mathvariant="sans-serif-italic"], 
ms[mathvariant="sans-serif-bold-italic"],mtext[mathvariant="italic"], mtext[mathvariant="bold-italic"],
mtext[mathvariant="sans-serif-italic"], mtext[mathvariant="sans-serif-bold-italic"]
mi[mathvariant="normal"], mn[mathvariant="normal"], mo[mathvariant="normal"], 
ms[mathvariant="normal"], mtext[mathvariant="normal"]
ms:before, ms:after 
	{outline:solid thin red}
	{content:"Error: "}
maction > * + *
maction[actiontype="tooltip"]:focus > * + *,
maction[actiontype="tooltip"]:hover > * + *
	border:solid 1px;}
annotation, annotation-xml

12 References

Cascading Style Sheets, level 2 revision 1, Bert Bos, Tantek Çelik, Ian Hickson, Håkon Wium Lie. W3C Candidate Recommendation 19 July 2007.
Cascading Style Sheets, level 2 CSS2 Specification, Bert Bos, Håkon Wium Lie, Chris Lilley, Ian Jacobs. May 1998.
Extensible Markup Language (XML) 1.0 (Fourth Edition), Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, et. al. editors. W3C Recommendation 16 August 2006.
Namespaces in XML 1.0 (Second Edition), Tim Bray, Dave Hollander, Andrew Layman, Richard Tobin. W3C Recommendation 16 August 2006.
Mathematical Markup Language (MathML) Version 3.0, David Carlisle, Patrick Ion, Robert Miner. W3C Working Draft 5 October 2007.
Mathematical Markup Language (MathML) 1.0 Specification, Patrick Ion, Robert Miner. April 1998.
Math Working Group Roadmap 2007/8, Patrick Ion, Robert Miner. March 2007, document subject to update. [See especially 2.2.1]
XHTML™ Modularization 1.1, Daniel Austin, Subramanian Peruvemba, Shane McCarron, Masayasu Ishikawa, W3C Proposed Recommendation 13 February 2006.
xml:id Version 1.0, Jonathan Marsh, Daniel Veillard, Norman Walsh. W3C Recommendation 9 September 2005.