◇◆
<mml:math> Math (MathML Tag Set)
Use documentation for the Mathematical Markup Language (MathML) Tag Set (https://www.w3.org/TR/MathML3/ or https://www.w3.org/TR/MathML2/).
Usage/Remarks
<mml:math>
The top-level element for math tagged according to the MathML Tag Set.
MathML 2.0 or MathML 3.0
While MathML 3.0 is the preferred
MathML version for new material, NISO STS recognizes that many organizations have
existing material in MathML 2.0, so MathML 2.0 will also be supported in this version
of NISO STS.
There are two NISO STS Tag Sets in four distinct variants: one each for Interchange
and Extended in MathML 3.0 (preferred) and one each for Interchange and Extended in
MathML 2.0.
Changes to MathML
With one exception, the various
elements and attributes of MathML used inside <mml:math> are not documented here, and the reader should refer
to online documentation from the W3C and Design Science. The one exception is the
<mml:annotation-xml> element. The content model for the
<mml:annotation-xml> has been limited to one or more paragraphs: (p+).
MathML Namespacing
The majority of organizations using this Tag Set use the DTDs as their primary (or
only) model, so this Tag Set is maintained to ensure that using DTDs and DTD-based
tools will work well. Because DTDs do not “play well” with namespaces, and most DTD-based
tools are not namespace aware, the MathML namespace has been hardcoded to the prefix
“mml” in the DTDs. This means that the element name, in the DTDs, really is <mml:math>. While this was the usual prefix when this Tag Set was originally established, the
more frequently seen MathML prefix is now “m”. Since XSD and RNG use “real” namespaces, this makes no difference to them, as to
a namespace-aware processor a namespace prefix is only a placeholder. For DTD users,
the element names in the MathML will need to be “mml” (for example, <mml:mfrac>), but tools can be set to provide that prefix and the essence of namespaces is that
prefixes do not matter, so no harm is done.
Some current MathML viewers cannot handle MathML elements that are prefixed (using
the tag
<mml:msub> rather than the tag <msub>) unless the MathML namespace pseudo-attribute has been placed directly on the <mml:math> element (<mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML">); the presence of the namespace on the top-level element is not good enough. By default
in this Tag Set, the namespace has been established as a #FIXED attribute on the <mml:math> element, but processors not using a DTD/schema cannot see defaulted or #FIXED attributes. For such processors, the MathML namespace attribute must be placed directly
on all <mml:math> elements in the instance document.
Attributes
The attributes for <mml:math> (with the exception of the namespace pseudo-attribute) are not listed below, because
they are not defined by or
under the control of NISO STS.
Attribute
Namespaces
xmlns:mml (fixed value = http://www.w3.org/1998/Math/MathML)
Models and Context
May be contained in
<ack>, <alternatives>, <alt-title>, <app>, <app-group>, <article-title>, <attrib>, <bio>, <body>, <bold>, <boxed-text>, <chapter-title>, <chem-struct>, <comment>, <compl>, <def-head>, <disp-formula>, <disp-quote>, <fixed-case>, <full>, <glossary>, <index>, <index-div>, <index-group>, <inline-formula>, <intro>, <italic>, <license-p>, <main>, <meta-value>, <monospace>, <named-content>, <non-normative-example>, <non-normative-note>, <normative-example>, <normative-note>, <notes>, <overline>, <p>, <part-title>, <ref-list>, <related-term>, <roman>, <sans-serif>, <sc>, <sec>, <see>, <see-also>, <see-also-entry>, <see-entry>, <source>, <strike>, <styled-content>, <sub>, <subtitle>, <sup>, <tbx:crossReference>, <tbx:definition>, <tbx:entailedTerm>, <tbx:example>, <tbx:externalCrossReference>, <tbx:note>, <tbx:pronunciation>, <tbx:see>, <tbx:source>, <tbx:term>, <tbx:usageNote>, <td>, <term>, <term-display>, <term-display-string>, <term-head>, <term-sec>, <textual-form>, <th>, <title>, <trans-source>, <trans-subtitle>, <trans-title>, <underline>
Tagged Samples
In display formula
...
<p>In the case of dollies of diameter 20 mm, the
breaking strength, in megapascals, is given by
<xref ref-type="disp-formula" rid="formula_2">Formula
(2)</xref>
<disp-formula id="formula_2"
><mml:math display="block"
id="mml_m2"
xmlns:mml="http://www.w3.org/1998/Math/MathML" >
<mml:mrow>
<mml:mi>s</mml:mi><mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>4</mml:mn><mml:mi>F</mml:mi></mml:mrow>
<mml:mrow>
<mml:mn>400</mml:mn><mml:mi>p</mml:mi></mml:mrow>
</mml:mfrac>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mi>F</mml:mi>
<mml:mrow>
<mml:mn>314</mml:mn></mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(2)</label>
</disp-formula>
</p>
...
Inline
...
<p>In Example 1 (one-sided paired test), the data were as
follows: <italic>n</italic> = 30, <italic>x</italic> = 21,
<italic>a</italic> = 0,05. From these data, the analyst
calculates</p>
<list list-type="bullet">
<list-item>
<label>—</label>
<p><italic>p</italic><sub>c</sub> =
<italic>x</italic>/<italic>n</italic> = 21/30 = 0,7,</p>
</list-item>
<list-item>
<label>—</label>
<p><inline-formula
><mml:math display="inline" id="mml_m1">
<mml:mrow>
<mml:msub>
<mml:mover accent="true">
<mml:mi>p</mml:mi>
<mml:mo>^</mml:mo>
</mml:mover>
<mml:mtext>d</mml:mtext>
</mml:msub>
</mml:mrow>
</mml:math></inline-formula> (proportion of distinguishers) ...</p>
</list-item>
...
</list>
...