Tables (103)

Table p. 28.0 — 7×3, 0 spanning cell(s)
languageMathMLOpenMath
byW3C Math WGOpenMath society
originmath for HTMLintegration of CAS
coveragecontent + presentation; K14content; extensible
statusVersion 2.2e (VI 2003)Version 2 (VI 2004)
activitymaintenancemaintenance
Infohttp://w3c.org/Math/http://www.openmath.org/

columns: language | MathML | OpenMath

Table p. 41.1 — 4×2, 0 spanning cell(s)
Level of RepresentationOMDoc Example
\begin{tabular}[t]{l} Theory Level: Development Graph \begin{itemize} \item[-] Inheritance via symbol-mapping \item[-] Theory inclusion via proofobligations \item[-] Local (one-step) vs. global links \end{itemize} \end{tabular}![](https://cdn.mathpix.com/cropped/1b348de5-ed54-4a9a-aba0-06a9a89f7dc6-041.jpg?height=192\&width=504\&top_left_y=539\&top_left_x=762)
\begin{tabular}[t]{l} Statement Level: \begin{itemize} \item[-] Axiom, definition, theorem, proof, example,... \item[-] Structure explicit in statement forms and references \end{itemize} \end{tabular}\begin{tabular}[t]{l} \begin{itemize} \item[] <definition for="\#plus" type="recursive"> \item[] <CMP>Addition is defined by recursion on the second argument \item[] </CMP> \item[] <FMP> \(X+0=0</ \mathrm{FMP}>\) \item[] \(<\mathrm{FMP}>X+s(Y)=s(X+Y)</ \mathrm{FMP}>\) \end{itemize} \\ </definition> \end{tabular}
\begin{tabular}[t]{l} Object Level: OpenMath/MathML \begin{itemize} \item[-] Objects as logical formulae \item[-] Semantics by pointing to theory level \end{itemize} \end{tabular}\begin{tabular}[t]{l} \begin{itemize} \item[] <OMA> \item[] <OMS cd="arith1" name="plus"/> \item[] <OMV name="X"/> \item[] <OMS cd="nat" name="zero"/> \end{itemize} \\ </OMA> \end{tabular}

columns: Level of Representation | OMDoc Example

Table p. 50.2 — 2×3, 0 spanning cell(s)
lineDescriptionref.
1This document is an XML 1.0 file that is encoded in the UTF-8 encoding.

columns: line | Description | ref.

Table p. 51.3 — 16×3, 0 spanning cell(s)
2,3The parser is told to use a document type definition for validation. The string omdoc specifies the name of the root element, the identifier PUBLIC specifies that the DTD (we use the "OMDoc basic" DTD; see Subsection 22.3.1), which can be identified by the public identifier in the first string and looked up in an XML catalog or (if that fails) can be found at the URL specified in the second string. A DTD declaration is not strictly needed for an OMDoc document, but is recommended, since the DTD supplies default values for some attributes.24.1 p. 228
4In general, XML files can contain as much whitespace as they want between elements, here we have used it for structuring the document.
5Start tag of the root element of the document. It declares the version (OMDoc 1.2) via the version, and an identifier of the document using the xml:id attribute. The optional modules specifies the sub-language used in this document. This is used when no DTD is present (see Subsection 22.3.1).11.1 p. 90
6,7the namespace prefix declarations for the Dublin Core, Creative Commons, and OpenMath namespaces. They declare the prefixes dc:, cc:, and om:, and bind them to the specified URIs. We will need the OpenMath namespace only in the third markup step described in Section 4.3 but spurious namespace prefix declarations are not a problem in the XML world.\begin{tabular}[t]{l} 10 \\ 10 p. 83 p. 83 \end{tabular}
8the namespace declaration for the document; if not prefixed, all elements live in the OMDoc namespace.10.1 p. 83
9-29The metadata for the whole document in Dublin Core format11.2 p. 92
10The title of the document12.1 p. 98
11The document creator, here in the role of a translator12.2 p. 101
12The date and time of first creation of the document in ISO 8601 norm format.12.1 p. 99
13The date and time of the last update to the document in ISO 8601 norm format.12.1 p. 99
14-16A short description of the contents of the document12.1 p. 99
17-19Here we acknowledge that the OMDoc document is just a translation from an earlier work.12.1 p. 100
20The type of the document, this can be Dataset (un-ordered mathematical knowledge) or Text (arranged for human consumption).12.1 p. 100
21The format/MIME type [FB96] of the document, for OMDoc, this is application/omdoc+xml.12.1 p. 100
22The copyright resides with the creator of the OMDoc document12.1 p. 100
23-28The creator licenses the document to the world under certain conditions as specified in the Creative Commons license specified in this element.12.3 p. 102

columns: 2,3 | The parser is told to use a document type definition for validation. The string omdoc specifies the name of the root element, the identifier PUBLIC specifies that the DTD (we use the "OMDoc basic" DTD; see Subsection 22.3.1), which can be identified by the public identifier in the first string and looked up in an XML catalog or (if that fails) can be found at the URL specified in the second string. A DTD declaration is not strictly needed for an OMDoc document, but is recommended, since the DTD supplies default values for some attributes. | 24.1 p. 228

Table p. 52.4 — 7×3, 0 spanning cell(s)
24,25The cc:permissions element gives the world the permission to reproduce and distribute it freely. Furthermore the license grants the public the right to make derivative works under certain conditions.12.3 p. 103
26The cc:prohibitions can be used to prohibit certain uses of the document, but this one is unencumbered.12.3 p. 103
27The cc:requirements states conditions under which the license is granted. In our case the licensee is required to keep the copyright notice and license notices intact during distribution, to give credit to the copyright holder, and that any derivative works derived from this document must be licensed under the same terms as this document (the copyleft clause).12.3 p. 103
31-37The omtext element is used to mark up text fragments. Here, we have simply used a single omtext to classify the whole text in the fragment as unspecific "text".14.3 p. 124
32-36The CMP element holds the actual text in a multilingual group. Its xml:lang specifies the language. If the document is used with a DTD or an XML schema (as we are) this attribute is redundant, since the default value given by the DTD or schema is en. More keywords in other languages can be given by adding more CMP elements.14.1 p. 122
33-35The text of the \(\mathrm{APT}_{\mathrm{E}} \mathrm{X}\) fragment we are migrating. For simplicity we do not change the text, and leave that to later stages of the migration.
38The closing tag of the root omdoc element. There may not be text after this in the file.11.1 p. 90

columns: 24,25 | The cc:permissions element gives the world the permission to reproduce and distribute it freely. Furthermore the license grants the public the right to make derivative works under certain conditions. | 12.3 p. 103

Table p. 53.5 — 7×3, 0 spanning cell(s)
lineDescriptionref.
1The omtext element classifies the text fragment as a definition, other types for mathematical statements include axiom, example, theorem, and lemma. Note that the numbering of the original text is lost, but can be re-created in the text presentation process. The optional xml:id attribute specifies a document-unique identifier that can be used for reference later.14.3 p. 124
2A multilingual group of CMP elements that hold the text (in our case, there is only the English default). Here the \(\mathrm{T}_{\mathrm{E}} \mathrm{X}\) formulae have been marked up with legacy elements characterizing them as such. This might simplify a later automatic transformation to OpenMath or Content-MathML.13.5 p. 120
4-13We have classified every paragraph in the original as a separate omtext element, which does not carry a type since it does not fit any other mathematical category at the moment.14.3 p. 124
15The three examples in the original in Figure 4.1 are grouped into an enumeration. We use the OMDoc omgroup element for this. The optional attribute xml:id can be used for referencing later. We have chosen enumeration for the type attribute to specify the numbering of the examples in the original.11.4 p. 93
16We can use the metadata of the omgroup element to accommodate the title "Examples" in the original. We could enter more metadata at this level.14.1 p. 122
18The type attribute of this omtext element classifies this text fragment as an example.14.3 p. 124

columns: line | Description | ref.

Table p. 55.6 — 8×3, 0 spanning cell(s)
lineDescriptionref.
1-4\begin{tabular}[t]{l} The omdoc-basic document type definition is no longer sufficient for our purposes, since we introduce new symbols that can be used in other documents. The DTD for OMDoc content dictionaries (see Chapter 5), which allows this. Correspondingly, we would specify the value cd for the attribute module. \\ The part in line 4 is the internal subset of the DTD, which sets a parameter entity for the modularized DTD to instruct it to accept OpenMath elements in their namespace prefixed form. Of course a suitable namespace prefix declaration is needed as well. \end{tabular}22.3.2 p. 218
5The start tag of a theory. We need this, since symbols and definitions can only appear inside theory elements.15.6 p. 149
6,7We need to import the theory products to be able to use symbols from it in the definition below. The value of the from is a relative URI reference to a theory element much like the one in line 5. The other imports element imports the theory relation1 from the OpenMath standard content dictionaries \({ }^{1}\). Note that we do not need to import the theory sets here, since this is already imported by the theory products.15.6.1 p. 150
9-11A symbol declaration: For every definition, OMDoc requires the declaration of one or more symbol elements for the concept that is to be defined. The name attribute is used to identify it. The dc:description element allows to supply a multilingual (via the xml:lang attribute) group of keywords for the declared symbol15.2.1 p. 136
12Upon closer inspection it turns out that the definition in Listing 4.4 actually defines three concepts: "law of composition", "composition", and "magma". Note that "composition" is just another name for the value under the law of composition, therefore we do not need to declare a symbol for this. Thus we only declare one for "law of composition".15.2.1 p. 136
14A definition: the definition element carries a name attribute for reference within the theory. We need to reference the two symbols defined here in the for attribute of the definition element; it takes a whitespace-separated list of name attributes of symbol elements in the same theory as values.15.2.4 p. 139
16We use an OpenMath object for the set \(E\). It is an om:OMOBJ element with an om:OMV daughter, whose name attribute specifies the object to be a variable with name \(E\). We have chosen to represent the set \(E\) as a variable instead of a constant (via an om:OMS element) in the theory, since it seems to be local to the definition. We will discuss this further in the next section, where we talk about formalization.13.1.1 p. 108

columns: line | Description | ref.

Table p. 56.7 — 5×3, 0 spanning cell(s)
17-21This om:0M0BJ represents the Cartesian product \(E \times E\) of the set \(E\) with itself. It is an application (via an om:0MA element) of the symbol for the binary Cartesian product relation to \(E\).13.1.1 p. 108
18The symbol for the Cartesian product constructor is represented as an om:0MS element. The cd attribute specifies the theory that defines the symbol, and the name points to the symbol element in it that declares this symbol. The value of the cd attribute is a theory identifier. Note that this theory has to be imported into the current theory, to be legally used.13.1.1 p. 108
22We use the term element to characterize the defined terms in the text of the definition. Its role attribute can used to mark the text fragment as a definiens, i.e. a concept that is under definition.14.5 p. 128
24-28This object stands for \(f(x, y)\)
30-39This object represents \((x, y) \in E \times E\). Note that we make use of the symbol for the elementhood relation from the OpenMath core content dictionary set1 and of the pairconstructor from the theory of products from the Bourbaki collection there.

columns: 17-21 | This om:0M0BJ represents the Cartesian product \(E \times E\) of the set \(E\) with itself. It is an application (via an om:0MA element) of the symbol for the binary Cartesian product relation to \(E\). | 13.1.1 p. 108

Table p. 93.8 — 29×4, 17 spanning cell(s) ⚠ overlap at (2,0); overlap at (2,1); overlap at (2,2); overlap at (2,3); overlap at (14,0)
ModuleTitleRequired?Chapter
MOBJMathematical ObjectsyesChapter 13
![](https://cdn.mathpix.com/cropped/1b348de5-ed54-4a9a-aba0-06a9a89f7dc6-093.jpg?height=98\&width=1056\&top_left_y=305\&top_left_x=200)Formulae are a central part of mathematical documents; this module integrates the content-oriented representation formats OpenMath and MathML into OMDoc
MTXTMathematical TextyesChapter 14
Mathematical vernacular, i.e. natural language with embedded formulae
DOCDocument InfrastructureyesChapter 11
A basic infrastructure for assembling pieces of mathematical knowledge into functional documents and referencing their parts
DCDublin Core MetadatayesSections 12.1 and 12.2
Contains bibliographical "data about data", which can be used to annotate many OMDoc elements by descriptive and administrative information that facilitates navigation and organization
CCCreative Commons MetadatayesSection 12.3
Licenses for text use
RTRich Text StructurenoSection 14.6
Rich text structure in mathematical vernacular (lists, paragraphs, tables, ...)
STMathematical StatementsnoChapter 15
![](https://cdn.mathpix.com/cropped/1b348de5-ed54-4a9a-aba0-06a9a89f7dc6-093.jpg?height=132\&width=1061\&top_left_y=980\&top_left_x=200)Markup for mathematical forms like theorems, axioms, definitions, and examples that can be used to specify or define properties of given mathematical objects and theories to group mathematical statements and provide a notion of context.
PFProofs and proof objectsnoChapter 17
![](https://cdn.mathpix.com/cropped/1b348de5-ed54-4a9a-aba0-06a9a89f7dc6-093.jpg?height=70\&width=1058\&top_left_y=1165\&top_left_x=200)Structure of proofs and argumentations at various levels of details and formality
ADTAbstract Data TypesnoChapter 16
Definition schemata for sets that are built up inductively from constructor symbols
CTHComplex TheoriesnoChapter 18
Theory morphisms; they can be used to structure mathematical theories
DGDevelopment GraphsnoSection 18.5
Infrastructure for managing theory inclusions, change management
EXTApplets, Code, and DatanoChapter 20
Markup for applets, program code, and data (e.g. images, measurements, ...)
PRESPresentation InformationnoChapter 19
Limited functionality for specifying presentation and notation information for local typographic conventions that cannot be determined by general principles alone
QUIZInfrastructure for AssessmentsnoChapter 21
Markup for exercises integrated into the OMDoc document model

columns: Module | Title | Required? | Chapter

Table p. 94.9 — 6×3, 1 spanning cell(s)
Formatnamespace URIsee
Dublin Corehttp://purl.org/dc/elements/1.1/ http://creativecommons.org/ns http://www.w3.org/1998/Math/MathML http://www.openmath.org/OpenMath http://www.w3.org/1999/XSL/TransformSections 12.1 and 12.2
Section 12.3
MathMLSection 13.2
OpenMathSection 13.1
XSLTChapter 19

columns: Format | namespace URI | see

Table p. 99.10 — 8×5, 2 spanning cell(s)
ElementAttributesDContent
RequiredOptionalC
omdocversion, xmlnsxml:id,type,class,style, version,modules+(《top-level》)*
omgroupxml:id,modules,type,class, style+(《top-level》)*
metadataxml:id,inherits,class,style-《(MDelt)*
refxreftype,class,style-
ignoretype,comment-ANY
where 《 top-level》 stands for top-level OMDoc elements,and « \(\langle\) MDelt \(\rangle\) for those introduced in Chapter 12

columns: Element | Attributes Required | Attributes Optional | D C | Content

Table p. 105.11 — 17×4, 2 spanning cell(s)
ElementAttributesContent
Req.Optional
dc:creatorxml:id,class,style,roleANY
dc:contributorxml:id,class,style,roleANY
dc:titlexml:lang《 math vernacular 》
dc:subjectxml:lang《math vernacular》
dc:descriptionxml:lang《 math vernacular 》
dc:publisherxml:id,class,styleANY
dc:dateaction,whoISO 8601
dc:typefixed:"Dataset"or"Text"
dc:formatfixed:"application/omdoc+xml"
dc:identifierschemeANY
dc:sourceANY
dc:languageISO 639
dc:relationANY
dc:rightsANY
for 《 math vernacular》 see Section 14.1

columns: Element | Attributes Req. | Attributes Optional | Content

Table p. 111.12 — 6×4, 1 spanning cell(s)
ElementAttributesContent
Req.Optional
cc:licensejurisdictionpermissions, prohibitions, requirements
cc:permissionsreproduction, distribution, derivative_worksEMPTY
cc:prohibitionscommercial_useEMPTY
cc:requirementsnotice, copyleft, attributionEMPTY

columns: Element | Attributes Req. | Attributes Optional | Content

Table p. 111.13 — 4×3, 0 spanning cell(s)
AttributePermissionDefault
reproductionthe work may be reproducedpermitted
distributionthe work may be distributed, publicly displayed, and publicly performedpermitted
derivative_worksderivative works may be created and reproducedpermitted

columns: Attribute | Permission | Default

Table p. 111.14 — 2×3, 0 spanning cell(s)
AttributeProhibitionDefault
commercial_usestating that rights may be exercised for commercial purposes.permitted

columns: Attribute | Prohibition | Default

Table p. 111.15 — 4×3, 0 spanning cell(s)
AttributeRequirementDefault
noticecopyright and license notices must be kept intactrequired
attributioncredit must be given to copyright holder and/or authorrequired
copyleftderivative works, if authorized, must be licensed under the same terms as the workrequired

columns: Attribute | Requirement | Default

Table p. 114.16 — 5×4, 1 spanning cell(s)
ElementAttributesContent
RequiredOptional
OMOBJidclass, styleSee Figure 13.2
m:mathid, xlink:hrefSee Figure 13.8
legacyformatxml:id, formalism\#PCDATA

columns: Element | Attributes Required | Attributes Optional | Content

Table p. 115.17 — 17×4, 2 spanning cell(s)
ElementAttributesContent
RequiredOptional
OMOBJid,cdbase,class,style《(OMel》)?
OMScd,nameid,cdbase,class,styleEMPTY
OMVnameid,class,styleEMPTY
OMAid,cdbase,class,style《(OMel》*
OMBINDid,cdbase,class,style《OMel》,OMBVAR,《OMel》
OMBVARid,class,style(OMV|OMATTR)+
OMFOREIGNid,cdbase,class,styleANY
OMATTRid,cdbase,class,style《OMel》
OMATPid,cdbase,class,style(OMS,(《OMel》|OMFOREIGN))+
OMIid,class,style[0-9]*
OMBid,class,style#PCDATA
OMFid,class,style,dec,hex#PCDATA
OMEid,class,style《OMel》 ?
OMRhref《OMel》?
where 《OMel》 is(OMS|OMV|OMI|OMB|OMSTR|OMF|OMA|OMBIND|OME|OMATTR)

columns: Element | Attributes Required | Attributes Optional | Content

Table p. 120.18 — 2×2, 0 spanning cell(s)
SharedExploded
\begin{tabular}[t]{l} \begin{itemize} \item[] <OMOBJ> <OMA> <OMS cd="nat" name="plus" /> <OMA id="t1"> <OMS cd="nat" name="plus" /> <OMA id="t11"> <OMS cd="nat" name="plus" /> <OMI>1</OMI> <OMI>1</OMI> </OMA> <OMR href="\#t11"/> \item[] </OMA> <OMR href="\#t1"/> \item[] </OMA> </OMOBJ> \end{itemize} \end{tabular}\begin{tabular}[t]{l} \begin{itemize} \item[] <OMOBJ> <OMA> \begin{itemize} \item[] <OMS cd="nat" name="plus" /> <OMA> \begin{itemize} \item[] <OMS cd="nat" name="plus"/> <OMA> \item[] <OMS cd="nat" name="plus"/> <OMI>1</OMI> \item[] <OMI>1</OMI> \item[] </OMA> \item[] <OMA> \item[] <OMS cd="nat" name="plus"/> <OMI>1</OMI> \begin{itemize} \item[] <OMI>1</OMI> \end{itemize} \item[] </OMA> \item[] </OMA> <OMA> \begin{itemize} \item[] <OMS cd="nat" name="plus"/> <OMA> \item[] <OMS cd="nat" name="plus" /> <OMI>1</OMI> <OMI>1</OMI> \item[] </OMA> <OMA> \item[] <OMS cd="nat" name="plus" /> <OMI>1</OMI> <OMI>1</OMI> \item[] </OMA> \item[] </OMA> \end{itemize} \item[] </OMA> \end{itemize} \item[] </OMOBJ> \end{itemize} \end{itemize} \end{tabular}

columns: Shared | Exploded

Table p. 121.19 — 1×2, 0 spanning cell(s)
\begin{itemize} \item[] <OMOBJ> \begin{itemize} \item[] <OMA id="bar"> \begin{itemize} \item[] <OMS cd="nat" name="plus" /> \item[] <OMI>1</OMI> \item[] <OMR href="\#baz"/> \end{itemize} \item[] </OMA> \end{itemize} \item[] </OMOBJ> \end{itemize}\begin{itemize} \item[] <OMOBJ> \begin{itemize} \item[] <OMA id="baz"> \begin{itemize} \item[] <OMS cd="nat" name="plus" /> \item[] <OMI>1</OMI> \item[] <OMR href="\#bar"/> \item[] </OMA> \end{itemize} \end{itemize} \item[] </OMOBJ> \end{itemize}

columns: \begin{itemize} \item[] <OMOBJ> \begin{itemize} \item[] <OMA id="bar"> \begin{itemize} \item[] <OMS cd="nat" name="plus" /> \item[] <OMI>1</OMI> \item[] <OMR href="\#baz"/> \end{itemize} \item[] </OMA> \end{itemize} \item[] </OMOBJ> \end{itemize} | \begin{itemize} \item[] <OMOBJ> \begin{itemize} \item[] <OMA id="baz"> \begin{itemize} \item[] <OMS cd="nat" name="plus" /> \item[] <OMI>1</OMI> \item[] <OMR href="\#bar"/> \item[] </OMA> \end{itemize} \end{itemize} \item[] </OMOBJ> \end{itemize}

Table p. 122.20 — 12×4, 1 spanning cell(s)
ElementAttributesContent
RequiredOptional
m:mathid,xlink:href《CMel》+
m:applyid,xlink:hrefm:bvar?,《 CMel》*
m:csymboldefinitionURLid,xlink:hrefm:EMPTY
m:ciid,xlink:href#PCDATA
m:cnid,xlink:href([0-9]|,|.)(*|e([0-9]|,|.)*)?
m:bvarid,xlink:hrefm:ci|m:semantics
m:semanticsid,xlink:href, definitionURL《CMel》,(m:annotation| m:annotation-xml)*
m:annotationdefinitionURL, encoding#PCDATA
m:annotation-xmldefinitionURL, encodingANY
where 《CMel》 is m:apply|m:csymbol|m:ci|m:cn|m:semantics

columns: Element | Attributes | | Content

Table p. 128.21 — 9×5, 1 spanning cell(s)
ElementAttributesDContent
RequiredOptionalC
CMPxml:lang,id-《math vernacular》
FMPxml:id,logic-(assumption*,conclusion*)| OMOBJ|m:math|legacy
assumptionxml:id,inductive, class,style+(OMOBJ|m:math|legacy)
conclusionxml:id,class,style+(OMOBJ|m:math|legacy)
phrasexml:id,class,style, index,verbalizes, type-《math vernacular》
termcd,namerole,xml:id,class, style-《math vernacular》
omtextxml:id,type, for,class,style, verbalizes+CMP+,FMP*

columns: Element | Attributes Required | Attributes Optional | D C | Content

Table p. 129.22 — 6×4, 0 spanning cell(s)
ModuleElementsCommentsee
MOBJom:0M0BJ, m:math, legacymathematical Objectsp. 107
MTXTphrase, termphrase-level markupbelow
DOCref, ignoredocument structurep. 89
RTp, ol, ul, dl, table, link, note, idxrich text structurep. 128
EXTomletfor applets, images, ...p. 205

columns: Module | Elements | Comment | see

Table p. 136.23 — 19×4, 0 spanning cell(s)
ElementOptional AttributesDCContent
pxml:id,style,class,index,verbalizes+《math vernacular》
olxml:id,style,class,index,verbalizes+li*
ulxml:id,style,class,index,verbalizes+li*
lixml:id,style,class,index,verbalizes+《math vernacular》
dlxml:id,style,class,index,verbalizes+di*
dixml:id,style,class,index,verbalizes+dt*,dd*
dtxml:id,style,class,index,verbalizes+《math vernacular》
ddxml:id,style,class,index,verbalizes+《math vernacular》
idx(xml:id|xref)-idt?,ide+
ideindex,sort-by,see,seealso,links-idp*
idtstyle,class-《math vernacular》
idpsort-by,see,seealso,links-《math vernacular》
tablexml:id,style,class,index,verbalizes+tr*
trxml:id,style,class,index,verbalizes+td*
tdxml:id,style,class,index,verbalizes+《math vernacular》
thxml:id,style,class,index,verbalizes+《math vernacular》
linkxml:id,style,class,index,verbalizes-《math vernacular》
notetype,xml:id,style,class,index,verbalizes+《math vernacular》

columns: Element | Optional Attributes | DC | Content

Table p. 141.24 — 4×3, 0 spanning cell(s)
DefiniendumDefiniensType
The number 1\(1:=s(0)\) (1 is the successor of 0)simple
The exponential function \(e^{\cdot}\)The exponential function \(e\) is the solution to the differential equation \(\partial f=f[\) where \(f(0)=1]\).implicit
The addition function +Addition on the natural numbers is defined by the equations \(x+0=x\) and \(x+s(y)=s(x+y)\).recursive

columns: Definiendum | Definiens | Type

Table p. 142.25 — 10×5, 2 spanning cell(s)
ElementAttributesDContent
RequiredOptionalC
symbolnamexml:id,role,scope,style, class+type*
typexml:id,system,style, class-CMP*,\(\langle\langle\) mobj \(\rangle\rangle\)
axiomxml:id,for,type,style, class+CMP*,FMP*
definitionforxml:id,type,style,class, uniqueness,existence, consistency,exhaustivity+CMP*,(FMP*|requation+ |《(mobj》)?,measure?, ordering?
requationxml:id,style,class-《 \(\langle\) mobj \(\rangle\) ,《 \(\langle\) mobj \(\rangle\)
measurexml:id,style,class-《(mobj》
orderingxml:id,style,class-《(mobj》)
where 《 mobj》 is(OMOBJ|m:math|legacy)

columns: Element | Attributes Required | Attributes Optional | D C | Content

Table p. 148.26 — 7×5, 2 spanning cell(s)
ElementAttributesDContent
RequiredOptionalC
assertionxml:id,for,type, theory,class,style, status,just-by+CMP*,FMP*
typesystemxml:id,for,just-by, theory,class,style-CMP*,《 \(\langle\) mobj \(\rangle\) ,〈 \(\langle\) mobj \(\rangle\) 〉
exampleforxml:id,type, assertion,theory, class,style+CMP*|\(\langle\langle\) mobj \(\rangle\rangle *\)
alternativefor,theory, entailed-by, entails, entailed-by-thm, entails-thmxml:id,type,theory, class,style+CMP*,(FMP*| requation*|《(mobj》))
where 《 mobj》 is(OMOBJ|m:math|legacy)

columns: Element | Attributes Required | Attributes Optional | D C | Content

Table p. 149.27 — 15×2, 7 spanning cell(s)
ValueExplanation
theorem, propositionan important assertion with a proof
Note that the meaning of the type (in this case the existence of a proof) is not enforced by OMDoc applications. It can be appropriate to give an assertion the type theorem, if the author knows of a proof (e.g. in the literature), but has not formalized it in OMDoc yet.
lemmaa less important assertion with a proof
The difference of importance specified in this type is even softer than the other ones, since e.g. reusing a mathematical paper as a chapter in a larger monograph, may make it necessary to downgrade a theorem (e.g. the main theorem of the paper) and give it the status of a lemma in the overall work.
corollarya simple consequence
An assertion is sometimes marked as a corollary to some other statement, if the proof is considered simple. This is often the case for important theorems that are simple to get from technical lemmata.
postulate, conjecturean assertion without proof or counter-example
Conjectures are assertions, whose semantic value is not yet decided, but which the author considers likely to be true. In particular, there is no proof or counterexample (see Section 15.4).
false-conjecturean assertion with a counter-example
A conjecture that has proven to be false, i.e. it has a counter-example. Such assertions are often kept for illustration and historical purposes.
obligation, assumptionan assertion on which the proof of another depends
These kinds of assertions are convenient during the exploration of a mathematical theory. They can be used and proven later (or assumed as an axiom).
formulaif everything else fails
This type is the catch-all if none of the others applies.

columns: Value | Explanation

Table p. 150.28 — 26×2, 13 spanning cell(s)
statusjust-by points to
tautologyProof of \(\mathcal{F}\)
All \(\mathcal{T}\)-interpretations satisfy \(\mathcal{A}\) and some \(\mathcal{C}_{i}\)
tautologous-conclusionProof of \(\mathcal{F}_{c}\).
All \(\mathcal{T}\)-interpretations satisfy some \(\mathcal{C}_{j}\)
equivalentProofs of \(\mathcal{F}\) and \(\mathcal{F}^{-1}\)
\(\mathcal{A}\) and \(\mathcal{C}\) have the same \(\mathcal{T}\)-models (and there are some)
theoremProof of \(\mathcal{F}\)
All \(\mathcal{T}\)-models of \(\mathcal{A}\) (and there are some) satisfy some \(\mathcal{C}_{i}\)
satisfiableModel of \(\mathcal{A}\) and some \(\mathcal{C}_{i}\)
Some \(\mathcal{T}\)-models of \(\mathcal{A}\) (and there are some) satisfy some \(\mathcal{C}_{i}\)
contradictory-axiomsRefutation of \(\mathcal{A}\)
There are no \(\mathcal{T}\)-models of \(\mathcal{A}\)
no-consequence\(\mathcal{T}\)-model of \(\mathcal{A}\) and some \(\mathcal{C}_{i}, \mathcal{T}\)-model of \(\mathcal{A} \cup \overline{\mathcal{C}}\).
Some \(\mathcal{T}\)-models of \(\mathcal{A}\) (and there are some) satisfy some \(\mathcal{C}_{i}\), some satisfy \(\overline{\mathcal{C}}\)
counter-satisfiableModel of \(\mathcal{A} \cup \overline{\mathcal{C}}\)
Some \(\mathcal{T}\)-models of \(\mathcal{A}\) (and there are some) satisfy \(\overline{\mathcal{C}}\)
counter-theoremProof of \(\overline{\mathcal{C}}\) from \(\mathcal{A}\)
All \(\mathcal{T}\)-models of \(\mathcal{A}\) (and there are some) satisfy \(\overline{\mathcal{C}}\)
counter-equivalentProof of \(\overline{\mathcal{C}}\) from \(\mathcal{A}\) and proof of \(\mathcal{A}\) from \(\overline{\mathcal{C}}\)
\(\mathcal{A}\) and \(\overline{\mathcal{C}}\) have the same \(\mathcal{T}\)-models (and there are some)
unsatisfiable-conclusionProof of \(\overline{\mathcal{C}}\)
All \(\mathcal{T}\)-interpretations satisfy \(\overline{\mathcal{C}}\)
unsatisfiableProof of \(\neg \mathcal{F}\)
All \(\mathcal{T}\)-interpretations satisfy \(\mathcal{A}\) and \(\overline{\mathcal{C}}\)
Where \(\mathcal{F}\) is an assertion whose FMP has assumption elements \(\mathcal{A}_{1}, \ldots, \mathcal{A}_{n}\) and conclusion elements \(\mathcal{C}_{1}, \ldots, \mathcal{C}_{m}\). Furthermore, let \(\mathcal{A}:=\left\{\mathcal{A}_{1}, \ldots, \mathcal{A}_{n}\right\}\) and \(\mathcal{C}:=\left\{\mathcal{C}_{1}, \ldots, \mathcal{C}_{m}\right\}\), and \(\mathcal{F}^{-1}\) be the sequent that has the \(\mathcal{C}_{i}\) as assumptions and the \(\mathcal{A}_{i}\) as conclusions. Finally, let \(\overline{\mathcal{C}}:=\left\{\overline{\mathcal{C}_{1}}, \ldots, \overline{\mathcal{C}_{m}}\right\}\), where \(\overline{\mathcal{C}_{i}}\) is a negation of \(\mathcal{C}_{i}\).

columns: status | just-by points to

Table p. 156.29 — 6×5, 2 spanning cell(s)
ElementAttributesDContent
Req.OptionalC
theoryxml:id,class,style,cdbase,cdversion, cdrevision,cdstatus,cdurl,cdreviewdate+(《top+thc》| imports)*
importsfromid,type,class,style+
tgroupxml:id,modules,type,class,style+\((\langle\langle t o p+t h c\rangle\rangle) *\)
where 《 top+thc》 stands for top-level and theory-constitutive elements

columns: Element | Attributes Req. | Attributes Optional | D C | Content

Table p. 162.30 — 9×5, 1 spanning cell(s)
ElementAttributesDContent
Req.OptionalC
adtxml:id,class,style, parameters+sortdef+
sortdefnametype,role,scope,class, style+(constructor| insort)*,recognizer?
constructornametype,scope,class,style+argument*
argument+type,selector?
insortfor-
selectornametype,scope,role,total, class,style+EMPTY
recognizernametype,scope,role,class, style+

columns: Element | Attributes Req. | Attributes Optional | D C | Content

Table p. 168.31 — 8×5, 1 spanning cell(s)
ElementAttributesDContent
Req.OptionalC
prooffortheory, xml:id, class, style+(omtext | derive | hypothesis | symbol | definition)*
proofobjectxml:id, for, class, style, theory+CMP*, (OMOBJ |m:math |legacy)
hypothesisxml:id, class, style, inductive-CMP*, FMP*
derivexml:id, class, style, type-CMP*, FMP*, method?
methodxref-(OMOBJ |m:math |legacy | premise | proof | proofobject)*
premisexref-EMPTY

columns: Element | Attributes Req. | Attributes Optional | D C | Content

Table p. 178.32 — 8×5, 1 spanning cell(s)
ElementAttributesDContent
RequiredOptionalC
theoryxml:id, class, style+(《top-level》| imports | inclusion)*
importsfromxml:id, type, class, style, conservativity, conservativity-just+morphism?
morphismxml:id, base, class, style, type, hiding, consistency, exhaustivity-requation*, measure?, ordering?
inclusionviaxml:id, conservativity, conservativity-just-EMPTY
theory-inclusionfrom, toxml:id, class, style, conservativity, conservativity-just+(CMP*,FMP*, morphism, obligation*)
axiom-inclusionfrom, toxml:id, class, style, conservativity, conservativity-just+morphism?, obligation*

columns: Element | Attributes Required | Attributes Optional | D C | Content

Table p. 189.33 — 6×5, 1 spanning cell(s)
ElementAttributesDContent
RequiredOptionalC
decompositionlinks-EMPTY
path-justlocal, globalsfor-EMPTY
theory-inclusionfrom, to, byxml:id, class, style+(CMP*,FMP*, morphism, (decomposition* | obligation*))
axiom-inclusionfrom, toxml:id, class, style+morphism?, (path-just* | obligation*)

columns: Element | Attributes Required | Attributes Optional | D C | Content

Table p. 192.34 — 6×4, 1 spanning cell(s)
ElementAttributesContent
RequiredOptional
omstyleelementfor, xml:id, xref, class, style(style|xslt)*
presentationforxml:id, xref, fixity, role, lbrack, rbrack, separator, bracket-style, class, style, precedence, crossref-symbol(use | xslt | style)*
xsltformatxml:lang, requires, xrefXSLT fragment
useformatxml:lang, requires, fixity, lbrack, rbrack, separator, element, attributes, crossref-symbol(element | text | recurse | map | value-of)*

columns: Element | Attributes Required | Attributes Optional | Content

Table p. 195.35 — 10×4, 0 spanning cell(s)
ElementAttributesContent
RequiredOptional
styleformatxml:lang, requires, xref(element | text | recurse | map | value-of)*
elementnamecrid, cr, ns(attribute | element | text | value-of | recurse | map)*
attributename(value-of | text)*
text(\#PCDATA)
value-ofselectEMPTY
recurseselectEMPTY
mapselectseparator?, (element | text | recurse | map)
separator(element | text | recurse | map)

columns: Element | Attributes | | Content

Table p. 201.36 — 7×3, 0 spanning cell(s)
PrecedenceOperatorsComment
200+,-unary
200-exponentiation
400\(*, \wedge, \cap\)multiplicative
500+, -, V, Uadditive
600/fraction
700\(=, \neq, \leq,<,>, \geq\)relation

columns: Precedence | Operators | Comment

Table p. 201.37 — 6×4, 1 spanning cell(s)
fixitybracket-styleseparatoryields
prefixlisp" "(f123)
postfixlisp" "(123f)
prefixmath","f(1, 2, 3)
postfixmath","(1,2,3)f
assuming lbrack="(" and rbrack=")"

columns: fixity | bracket-style | separator | yields

Table p. 202.38 — 3×2, 1 spanning cell(s)
Notation specificationExample
\begin{lstlisting}[mathescape=true] <presentation for=" #forall" role="binding" separator = ". " \(>\) <use format="TeX"> forall</use> <use format="html">&#8704;</use> </presentation> \end{lstlisting}\begin{lstlisting}[mathescape=true] <OMBIND> <OMS cd="quant1" name="forall"/> <OMBVAR> <OMV name="X"/> </OMBVAR> <OMS cd="logic1" name="true"/> </OMBIND> \end{lstlisting}
\begin{tabular}[t]{l} Using XSLT templates induced from the presentation element on the OpenMath expression yields \(\forall X\).true, where the glyph \(\forall\) carries a hyperlink \({ }^{\varnothing}\) to it definition, as the crossref-symbol on the presentation element has the default value yes. Internally, the hyperlinks are format-dependent, we have: \\ LATEX: \begin{lstlisting} \href{../ocd/logic1.ps#true}{\forall}X. \href{../ocd/logic1.ps#true}{{\sf true}} HTML: <a href="../ocd/logic1.html#forall">&#8704;</a> X. <a href="../ocd/logic1.html#true"><b>true</b></a> \end{lstlisting} \end{tabular}

columns: Notation specification | Example

Table p. 206.39 — 8×5, 1 spanning cell(s)
ElementAttributesDContent
Req.OptionalC
privatexml:id, for, theory, requires, type, reformulates, class, style+CMP*, data+
codexml:id, for, theory, requires, type, class, style+CMP*, input?, output?, effect?, data+
inputxml:id, style, class+CMP*, FMP*
outputxml:id, style, class+CMP*, FMP*
effectxml:id, style, class+CMP*, FMP*
dataformat, href, size, original, pto, pto-version-<![CDATA[...]]>

columns: Element | Attributes Req. | Attributes Optional | D C | Content

Table p. 210.40 — 4×5, 1 spanning cell(s)
ElementAttributesDContent
Req.OptionalC
omletdata,xml:id, action, show, actuate, class, style+(《CMP content》 | param)*,data*
paramnamevalue, valuetype-EMPTY

columns: Element | Attributes Req. | Attributes Optional | D C | Content

Table p. 214.41 — 8×5, 1 spanning cell(s)
ElementAttributesDContent
Req.OptionalC
exercisexml:id, class, style+CMP*,FMP*,hint?,(solution*|mc*)
hintxml:id, class, style+CMP*, FMP*
solutionxml:id, for, class, style+《top-level element》
mcxml:id, for, class, style-choice, hint?, answer
choicexml:id, class, style+CMP*, FMP*
answerverdictxml:id, class, style+CMP*, FMP*

columns: Element | Attributes Req. | Attributes Optional | D C | Content

Table p. 220.42 — 5×4, 0 spanning cell(s)
\#Rulecommentelements
1unordere dThe order of children of this element is irrelevant (as far as permitted by the content model). For instance only the order of obligation elements in the axiom-inclusion element is arbitrary, since the others must precede them in the content model.adt axiom-inclusion metadata symbol code private presentation omstyle
2multigroupThe order between siblings elements does not matter, as long as the values of the key attributes differ.CMP FMP requation dc:description sortdef data dc:title solution
3DAG encodingDirected acyclic graphs built up using om:OMR elements are equal, iff their tree expansions are equal.om:OMR ref
4DatasetIf the content of the dc:type element is Dataset, then the order of the siblings of the parent metadata element is irrelevant.dc:type

columns: \# | Rule | comment | elements

Table p. 227.43 — 7×2, 0 spanning cell(s)
directoriescontent
bin, lib, oz, thirdPartyprograms and third-party software used in the administration and examples
css, xslstyle sheets for displaying OMDoc documents on the web, see Chapter 25 for a discussion.
docThe OMDoc documentation, including the specification, papers about a the OMDoc format and tools.
dtd, rncThe OMDoc document type definition and the RelaxNG schemata for OMDoc
examplesVarious example documents in OMDoc format.
projectsvarious contributed developments for OMDoc. Documentation is usually in their doc sub-directory

columns: directories | content

Table p. 233.44 — 7×3, 0 spanning cell(s)
languagenamespaceprefix
MathMLhttp://www.w3.org/1998/Math/MathMLm:
OpenMathhttp://www.openmath.org/OpenMathom:
XSLThttp://www.w3.org/1999/XSL/Transformxsl:
Dublin Corehttp://purl.org/dc/elements/1.1/dc:
Creative Commonshttp://creativecommons.org/nscc:
OMDochttp://www.mathweb.org/omdocomdoc:

columns: language | namespace | prefix

Table p. 245.45 — 2×2, 0 spanning cell(s)
Project Homehttp://www.matracas.org/qmath/index.en.html
AuthorsAlberto González Palomo Toledo, Spain \({ }^{2}\)

columns: Project Home | http://www.matracas.org/qmath/index.en.html

Table p. 248.46 — 2×2, 0 spanning cell(s)
Project Homehttp://www.matracas.org/sentido/index.en.html
AuthorsAlberto González Palomo Toledo, Spain \({ }^{4}\)

columns: Project Home | http://www.matracas.org/sentido/index.en.html

Table p. 253.47 — 2×2, 0 spanning cell(s)
Project Homehttp://www.mathweb.org/mbase
AuthorsAndreas Franke \({ }^{1}\), Michael Kohlhase \({ }^{2}\) \begin{itemize} \item[] \({ }^{1}\) Computer Science, Saarland University \item[] \({ }^{2}\) School of Engineering and Science, International \end{itemize} University Bremen

columns: Project Home | http://www.mathweb.org/mbase

Table p. 255.48 — 2×2, 0 spanning cell(s)
Project Homehttp://search.mathweb.org/
AuthorsIoan Sucan, Michael Kohlhase Computer Science, International University Bremen

columns: Project Home | http://search.mathweb.org/

Table p. 259.49 — 2×2, 0 spanning cell(s)
Project Homehttp://www.mmiss.de
AuthorsBernd Krieg-Brückner, Achim Mahnke Computer Science, University of Bremen, Germany

columns: Project Home | http://www.mmiss.de

Table p. 263.50 — 2×2, 0 spanning cell(s)
Project Homehttp://www.mathdox.org
AuthorsA.M. Cohen, H. Cuypers, E. Reinaldo Barreiro Department of Mathematics and Computer Science, Eindhoven University of Technology

columns: Project Home | http://www.mathdox.org

Table p. 267.51 — 2×2, 0 spanning cell(s)
Project Homehttp://www.activemath.org/
AuthorsThe ActiveMath group: Erica Melis, Giorgi Goguadse, Alberto Gonzales-Palomo, Adrian Frischauf, Martin Homik, Paul Libbrecht, Carsten Ullrich DFKI GmbH and Universität des Saarlandes

columns: Project Home | http://www.activemath.org/

Table p. 273.52 — 2×2, 0 spanning cell(s)
Project Homehttp://www.activemath.org/projects/jEdit0QMath
AuthorsPaul Libbrecht DFKI GmbH and Universität des Saarlandes

columns: Project Home | http://www.activemath.org/projects/jEdit0QMath

Table p. 275.53 — 2×2, 0 spanning cell(s)
Project Homehttp://kwarc.eecs.iu-bremen.de/projects/swim
AuthorsChristoph Lange, Michael Kohlhase Computer Science, International University Bremen

columns: Project Home | http://kwarc.eecs.iu-bremen.de/projects/swim

Table p. 279.54 — 2×2, 0 spanning cell(s)
Project Homehttp://www.cs.nott.ac.uk/ \({ }^{\sim}\) lad/research/ challenges/challenge_manager.html
AuthorsThomas D. Attfield, Monica C. Duarte, Lin Li, HoYing Mak, Adam M. Neal, Lewis M. Toft, Zixuan Wang, Louise A. Dennis School of Computer Science and Information Technology, University of Nottingham

columns: Project Home | http://www.cs.nott.ac.uk/ \({ }^{\sim}\) lad/research/ challenges/challenge_manager.html

Table p. 282.55 — 2×2, 0 spanning cell(s)
Project Homewww.dfki.de/ \({ }^{\sim}\) inka/maya.html
AuthorsSerge Autexier \({ }^{1}\), Dieter Hutter \({ }^{1}\), Till Mossakowski \({ }^{2}\), Axel Schairer \({ }^{1} { }^{1}\) DKFI GmbH, Stuhlsatzenhausweg 3, D 66123 Saarbrücken \({ }^{2}\) Computer Science, University of Bremen, Germany

columns: Project Home | www.dfki.de/ \({ }^{\sim}\) inka/maya.html

Table p. 287.56 — 2×2, 0 spanning cell(s)
Project Homewww.tzi.de/cofi/hets
AuthorsTill Mossakowski, Christian Maeder, Klaus Lüttich Computer Science, University of Bremen, Germany

columns: Project Home | www.tzi.de/cofi/hets

Table p. 291.57 — 2×2, 0 spanning cell(s)
Project Homehttp://kwarc.eecs.iu-bremen.de/software/CPoint/
Authors\begin{tabular}[t]{l} Andrea Kohlhase \\ Digital Media in Education (DiMeB), Dept. of Mathematics and Computer Science, University Bremen \end{tabular}

columns: Project Home | http://kwarc.eecs.iu-bremen.de/software/CPoint/

Table p. 295.58 — 2×2, 0 spanning cell(s)
Project Homehttp://kwarc.iu-bremen.de/projects/stex/
AuthorsMichael Kohlhase Computer Science, International University Bremen

columns: Project Home | http://kwarc.iu-bremen.de/projects/stex/

Table p. 299.59 — 2×2, 0 spanning cell(s)
Project Homehttp://www.cs.cmu.edu/ \({ }^{\sim}\) ccaps
AuthorsPeter Jansen School of Computer Science, Carnegie Mellon University

columns: Project Home | http://www.cs.cmu.edu/ \({ }^{\sim}\) ccaps

Table p. 302.60 — 2×2, 0 spanning cell(s)
Project Homehttp://www.cs.cmu.edu/ \({ }^{\sim}\) ccaps
AuthorsKlaus Sutner School of Computer Science, Carnegie Mellon University

columns: Project Home | http://www.cs.cmu.edu/ \({ }^{\sim}\) ccaps

Table p. 305.61 — 2×2, 0 spanning cell(s)
Project Homehttp://www.mathweb.org/omdoc/examples/logics
AuthorsMichael Kohlhase Computer Science, International University Bremen

columns: Project Home | http://www.mathweb.org/omdoc/examples/logics

Table p. 306.62 — 14×4, 0 spanning cell(s)
PVS\(\Omega\) MEGAPVS\(\Omega_{\text {MEGA }}\)
setsubset?subset
memberinsubset2
empty?emptystrict_subset?proper-subset
emptysetemptysetsuperset
nonempty?not-emptyunionunion
full?union2
fullsetunion-over-collection
singleton?singletonintersectionintersection
singletonintersection-over-coll.
complementset-complementdisjoint?misses
differencesetminusmeets
symmetric_differenceaddadd-one
exclunionremove

columns: PVS | \(\Omega\) MEGA | PVS | \(\Omega_{\text {MEGA }}\)

Table p. 310.63 — 2×2, 0 spanning cell(s)
Project Homehttp://www.ags.uni-sb.de/~omega/projects/ verimathdoc
AuthorsSerge Autexier, Christoph Benzmüller, Armin Fiedler, and Henri Lesourd Computer Science, Saarland University, Saarbrücken, Germany

columns: Project Home | http://www.ags.uni-sb.de/~omega/projects/ verimathdoc

Table p. 314.64 — 2×2, 0 spanning cell(s)
Project Homehttp://www.verifun.de/
AuthorsNormen Müller School of Engineering and Science, International University Bremen

columns: Project Home | http://www.verifun.de/

Table p. 320.65 — 4×4, 0 spanning cell(s)
elementstatecommentscf.
alternativeaugThis element can now have theory, generated-from, and generated-via attributes.145
argumentchaThe sort has been replaced by a type child, so that higher-order sorts can be specified.156
assertionaugthe assertion element now has an optional for attribute. Furthermore, an optional attribute generated-via has been added to allow generation via a theory morphism. Finally, two new attributes status and just-by have been added to mark up the deductive status of the assertion.142

columns: element | state | comments | cf.

Table p. 321.66 — 10×4, 0 spanning cell(s)
assumptionchaThis element can now have an attribute inductive for inductive assumptions. The natural langauge description in the optional CMP element is no longer allowed, use a phrase element in a CMP that is a sibling to the FMP instead.145
adtaugthe adt loses the CMP and commonname children, use the Dublin Core metadata elements dc:description and dc:subject instead. The type attribute is now on the sortdef element. Furthermore, an optionala attribute generated-via has been added to allow generation via a theory morphism. Finally, an attribute parameters has been added to allow for parametric ADTs.156
answerchathe answer element does not allow symbol children any more, if these are needed, the exercise should have its own theory.210
attributeaugthe attribute element now has a optional ns attribute for the namespace URI of the generated attribute node and an attribute select for an XPath expression that specifies the value of the generated attribute.191
axiomaugthe axiom element now has an optional for attribute which can point to a list of symbols. Furthermore, an optional attribute generated-via has been added to allow generation via a theory morphism and an attribute type is now also allowed.138
axiom-inclusionlibthe axiom-inclusion element can now contain multiple path-just children to record multiple justifications. Furthermore, it can now have theory, generated-from, and generated-via attributes. New optional attributes conservativity and conservativity-just for stating and justifying conservativity.180
cataloguedepthe catalogue mechanism has been eliminated.
choicechathe choice element does not allow symbol children any more, if these are needed, the exercise should have its own theory210
codechaAttributes classid and codebase are deprecated. The attributes pto and pto-version have moved to the data element. The attribute type has been removed and optional attributes theory, generated-from, and generated-via have been added.202
commonnamedepThis element is deprecated in favor of a metadata/dc:subject element.

columns: assumption | cha | This element can now have an attribute inductive for inductive assumptions. The natural langauge description in the optional CMP element is no longer allowed, use a phrase element in a CMP that is a sibling to the FMP instead. | 145

Table p. 322.67 — 11×4, 0 spanning cell(s)
conclusionchaThe natural langauge description in the optional CMP element is no longer allowed, use a phrase element in a CMP that is a sibling to the FMP instead.124
constructorchaThe role attribute is now fixed to object. The commonname child has been replaced by an initial metadata element.156
dataaugnew optional attributes original to specify whether the external resource referenced by the href attribute (value external) or the data content is the original (value local). The data element has acquired attributes pto and pto-version from the code and private elements.203
dc:*augAll Dublin Core tags have been lowercased to synchronize with the tag syntax recommended by the Dublin Core Initiative. The tags were capitalized in OMDoc1.1. Furthermore, dc:contributor, dc:creator, dc:publisher have received an optional xml:id attribute, so that they can be crossreferenced by the new who of the dc : date element.98
decompositionaugThe for attribute is now optional, it need not be given, if the element is a child of a theory-inclusion element. Furthermore, it can now have a theory, generated-from, and generated-via attributes.184
dc:descriptionaugThe dc:description can now have the optional xml:id, and CSS attributes99
definitionaugThe definition element can now have the type pattern for pattern-defined functions. This is a degenerate case of the type inductive. Furthermore, an optional attribute generated-via has been added to allow generation via a theory morphism.139
effectaugallows an optional xml:id attribute204
exampleaugThe example element now has the optional theory attribute that specifies the home theory. Furthermore, it can now have attributes theory, generated-from, and generated-via.146
exercisechathe exercise element does not allow symbol children any more, if these are needed, the exercise should have its own theory. Furthermore, it can now have a theory, generated-from, and generated-via attributes.209
extradatachaThe content of the old extradata element can now be directly in the metadata/dc:subject element.

columns: conclusion | cha | The natural langauge description in the optional CMP element is no longer allowed, use a phrase element in a CMP that is a sibling to the FMP instead. | 124

Table p. 323.68 — 13×4, 0 spanning cell(s)
elementaugThe element element now allows the map and separator elements in the body. Furthermore, it carries the optional attributes crid for parallel markup, cr for cross-references, and ns for specifying the namespace.190
hintaugthe hint element can now appear on toplevel and has a for attribute. It does not allow symbol children any more, if these are needed, the exercise should have its own theory. Furthermore, the exercise can now have a theory, generated-from, and generated-via attributes.209
hypothesischathe discharged-in attribute has been eliminated. Scoping is now specified in terms of the enclosing proof element. Furthermore, the symbol child is no longer allowed inside the element. A sibling symbol should be used.162
inclusionaugallows optional attributes xml:id, conservativity, and conservativity-just for stating and justifying conservativity.179
importslibthe xml:id is now optional. New optional attributes conservativity and conservativity-just for stating and justifying conservativity.150
inputaugallows an optional xml:id attribute204
legacynewAn element for encapsulating legacy mathematics, can be used wherever m:math and om:OMOBJ are allowed.120
locdepThe catalogue mechanism has been eliminated.
m:mathnewContent-MathML is now allowed wherever OpenMath objects were allowed before.114
mapnewthis element allows to map its style directives over a list of e.g. arguments191
mcaugthe mc element can now have a for attribute. It does not allow symbol children any more, if these are needed, the dominating exercise element should have its own theory. Furthermore, the mc element can now have a theory, generated-from, and generated-via attributes.210
measureaugallows an optional xml:id attribute141
metacommentdepThis element is superseded by the omtext element.124

columns: element | aug | The element element now allows the map and separator elements in the body. Furthermore, it carries the optional attributes crid for parallel markup, cr for cross-references, and ns for specifying the namespace. | 190

Table p. 324.69 — 11×4, 0 spanning cell(s)
morphismaugThe morphism element now carries the optional attributes consistency, exhaustivity, hiding, and type. Furthermore the content model allows optional elements measure and ordering after the requation children to specify termination information like in definition.92
obligationaugallows an optional xml:id attribute178
omdocaugThis element can now have a theory, generated-from, and generated-via attributes.90
omgroupchaThe values dataset and labeled-dataset are deprecated in Version 1.2 of OMDoc, since we provide tables in module RT; see Section 14.6 for details. Furthermore, the element can now have the attributes, modules, theory, generated-from, and generated-via.93
omletchaomlet can no longer occur at top-level (it just does not make sense). The data model for this element has been totally reworked, inspired by the xhtml:object element.205
omstyleaugThis element can now have generated-from, and generated-via attributes. New attribute xref that allows to inherit the information from another omstyle element.188
om:*augwith OpenMath2, the OpenMath elements carry an optional id attribute for structure sharing via the om:OMR element. Furthermore, in OMDoc, they carry cref attributes for parallel markup with crossreferences.108
om: OMFOREIGNnewThe om:OMFOREIGN element can be used to encapsulate arbitrary XML data in OpenMath attributions.110
om: 0MRnewIn the OpenMath2 standard, this element is the main vehicle of the structure sharing representation.112
omtextaugthe type attribute can now also have the values axiom, definition, theorem, proposition, lemma, corollary, postulate, conjecture, false-conjecture, obligation, assumption, and formula. Furthermore, omtext can now have theory, generated-from, and generated-via and verbalizes attributes.124
orderingaugNow allows the optional xml:id and terminating attributes. The latter points to a termination assertion.141

columns: morphism | aug | The morphism element now carries the optional attributes consistency, exhaustivity, hiding, and type. Furthermore the content model allows optional elements measure and ordering after the requation children to specify termination information like in definition. | 92

Table p. 325.70 — 12×4, 0 spanning cell(s)
outputaugallows an optional xml:id attribute204
patternaugthis element is no longer used, the pattern of a recursive equation is determined by the position as the first child.
path-justaugThe element can now appear as a toplevel element, if it does, the attribute for must point to the axiom-inclusion element it justifies. It also now allows an optional xml:id attribute184
phrasenewused to mark up phrases in CMPs and supply them with identifiers and links to context that can be used for presentation and referencing.126
presentationchaThe theory is not allowed any more, to refer to a symbol outside its theory use its xml:id attribute. The element now also allows a mutilingual CMP group, so that it can be used as a notation definition element in mathematical vernacular.192
privatechaThe replaces attribute is now called reformulates. The attributes pto and pto-version have moved to the data element. The attribute type has been removed and optional attributes theory, generated-from, and generated-via have been added.202
prooflibThe for attribute is now optional to allow for proofs as objects of mathematical discourse. Furthermore, it can now have generated-from and generated-via attributes.161
proofobjectlibThe for attribute is now optional to allow for proofs as objects of mathematical discourse. Furthermore, it can now have generated-from and generated-via attributes.169
recognizerchaThe role attribute was fixed to object. The commonname child has been replaced by an initial metadata element.157
refaugref now has an optional xml:id attribute that identifies it.94
selectorchaThe role attribute was fixed to object. The commonname child has been replaced by an initial metadata element.157
solutionchathe solution element now allows arbitrary OMDoc top-level elements as children. Furthermore, it can now have a theory, generated-from, and generated-via attributes.209

columns: output | aug | allows an optional xml:id attribute | 204

Table p. 326.71 — 8×4, 0 spanning cell(s)
sortdefchaThe role attribute was fixed to sort. The type from the adt element is now on the sortdef element. The commonname child has been replaced by an initial metadata element.156
dc:subjectaugThe dc:subject can now have the optional dc:id, and CSS attributes99
styleaugThe style element now allows a map element in the body189
symbolchamay no longer contain selector, since it only makes sense for constructors in data types. The kind attribute has been renamed to role for compatibility with OpenMath2 and can have the additional values binder, attribution, semantic-attribution, and error corresponding to the OpenMath 2 roles. Furthermore, an optional attribute generated-via has been added to allow generation via a theory morphism.136
termnewthe term element can appear in mathematical text and contain it. It is used to link technical terms to symbols defined in content dictionaries via its cd and name attributes.128
theorychathe theory element loses the CMP and commonname children, use the Dublin Core metadata elements dc:description and dc:subject instead. The theory element also gains the optional cdbase attribute to specify the disambiguating string prescribed for content dictionaries by the OpenMath2 standard. The xml:id is now optional, it only needs to be specified, if the theory has constitutive elements. Finally, the element has gained the optional attributes cdurl, cdbase, cdreviewdate, cdversion, cdrevision, and cdstatus attributes for encoding the management metadata of OpenMath content dictionaries.149
dc:titleaugThe dc:title can now have the optional dc:id, and CSS attributes.98
tgroupnewThe tgroup can be used to structure theories like documents.149

columns: sortdef | cha | The role attribute was fixed to sort. The type from the adt element is now on the sortdef element. The commonname child has been replaced by an initial metadata element. | 156

Table p. 327.72 — 7×4, 0 spanning cell(s)
typeaug\begin{tabular}[t]{l} the type element now has the optional just-by and theory attribute. The first one points to an assertion or axiom that justifies the type judgment, the second specifies the home theory. The system attribute is now optional. \\ Furthermore, the type element can have two math objects as children. If it does, then it is a term declaration, i.e. the first element is interpreted as a mathematical object and the second one is interpreted as its type. \\ Finally, it can now have generated-from and generated-via attributes. \end{tabular}139
theory-inclusionaugthe theory-inclusion element can now have obligation and decomposition children that justify it. Furthermore, it can now have a theory, generated-from, and generated-via attributes. New optional attributes conservativity and conservativity-just for stating and justifying conservativity.178
theoryaugthe theory element can now be nested.149
usechacan now contain element, text, recurse, map, and value-of to specify XML content. We have deprecated the larg-group and rarg-group attributes, since they were never used.194
valueaugthis element is no longer used, the value of a recursive equation is determined by the position as the second child.
withrenthe role of this element is now taken by the phrase element.126
xsltchathe content of this element need not be escaped any more, it is now a valid XSLT fragment.189

columns: type | aug | \begin{tabular}[t]{l} the type element now has the optional just-by and theory attribute. The first one points to an assertion or axiom that justifies the type judgment, the second specifies the home theory. The system attribute is now optional. \\ Furthermore, the type element can have two math objects as children. If it does, then it is a term declaration, i.e. the first element is interpreted as a mathematical object and the second one is interpreted as its type. \\ Finally, it can now have generated-from and generated-via attributes. \end{tabular} | 139

Table p. 328.73 — 14×4, 0 spanning cell(s)
elementstatecommentscf.
attributenewpresentation of attributes for XML elements191
alternativechanew form of the alternative-def element, it can now also used as an alternative to axiom. Compared to alternative-def it has a new optional attribute generated-by to show that an assertion is generated by expanding a some other element like adt.145
alternative-defdepnew form is alternative, since there can be alternative axioms too.
argumentchaattribute sort is now of type IDREF, since it must be local in the definition.156
assertionaugmore values for the type attribute, new optional attribute generated-by to show that an assertion is generated by expanding a definition or an adt. New optional attribute proofs.142
assertion-justdepthis is now obligation
axiomaugnew optional attribute generated-by to show that an axiom is generated by expanding a definition.138
axiom-inclusionchanow allows a CMP group for descriptive text, includes a set of obligation elements instead of an assertion-just. The timestamp attribute is deprecated, use dc:date with appropriate action instead180
CMPchathe attribute format is now deprecated, it makes no sense, since we are more strict and consistent about CMP content. CMP now allows an optional id attribute.122
codechaAttributes width and height now in omlet, got attributes classid and codebase from private. Attribute format moved to data children. The multilingual group of CMP elements for description is deprecated, use metadata/dc:description instead. Child element data may appear multiple times (with different values of the format).202
constructoraugnew optional child recognizer for a recognizer predicate156
Coveragedepthis Dublin Core element specifies the place or time which the publication's contents addresses. This does not seem appropriate for the mathematical content of OMDoc.
dataaugnew optional attributes size to specify the size of the data file that is referenced by the href attribute and format for the format the data is in.203

columns: element | state | comments | cf.

Table p. 329.74 — 16×4, 0 spanning cell(s)
dc:dateaugnew optional who attribute that can be used to specify who did the action on this date.99
Translatordepthis element is not part of Dublin Core, it got into OMDoc by mistake, we use dc:contributor with role=trl for this.98
decompositionaughas a new required id attribute. It is no longer a child of theory-inclusion, but specifies which theory-inclusion it justifies by the new required attribute for.184
definitionaugnew optional children measure and ordering to specify termination of recursive definitions. New optional attribute generated-by to show that it is generated by expanding a definition.139
elementnewpresentation of XML elements190
FMPaugnow allows multiple conclusion elements, to represent general Gentzen-type sequents (not only natural deduction.) FMP now allows an optional id attribute.123
hypothesischanew required attribute discharged-in to specify the derive element that discharges this hypothesis.162
measurenewspecifies a measure function (as an OMOBJ)141
metadataaugnew optional attribute inherits that allows to inherit metadata from other declarations92
methodchafirst child that used to be an om:OMSTR or ref element is now moved into a required xref attribute that holds an URI that points to the element that defines the method. The om:OMOBJ content of the other children (they were parameter elements) is now directly included in the method element.164
obligationnewtakes over the role of assertion-just.
omgroupaugalso allows the elements that can only appear in theory elements, so that omgroups can also be used for grouping inside theory elements. The type attribute is now restrained to one of narrative, sequence, alternative, contrast.93
omletaugobtained attributes width and height from private. New optional attributes action for the action to be taken when activated, and data a URIref to data in a private element. New optional attribute type for the type of the applet.205
omstylenewfor specifying the style of OMDoc elements188
omtextchathe from is deprecated, we only leave the for attribute, to specify the referential character of the type.124
orderingnewspecifies a well-founded ordering (as an OMOBJ)141

columns: dc:date | aug | new optional who attribute that can be used to specify who did the action on this date. | 99

Table p. 330.75 — 13×4, 0 spanning cell(s)
parameterdepthe om:OMOBJ element child is now directly a child of method
patternchathe child can be an arbitraryOpenMath element.
premisechanew optional attribute rank for the importance in the inference rule. The old href attribute is renamed to xref to be consistent with other cross-referencing.
presentationaug\begin{tabular}[t]{l} New attribute xref that allows to inherit the information from another presentation element. New attribute theory to specify the theory the symbol is from; without this, referencing in OMDoc is not unique. \\ The parent attribute has been renamed to role and now takes the values applied, binding, and key, since we want to be less OpenMath-centric \end{tabular}192
privatecha\begin{tabular}[t]{l} new optional attribute for to point to an OMDoc element it provides data for. As a consequence, private elements are no longer allowed in other OMDoc elements, only on top-level. New attribute replaces as a pointer to the OMDoc elements that are replaced by the system-specific information in this element. Old attributes width and height now in omlet. Attribute format moved to data children. \\ The descriptive CMP elements are deprecated, use metadata/dc:description instead. \\ Child element data may appear multiple times (with different values of the format). The attributes classid and codebase are deprecated, since they only make sense on the code element. \end{tabular}q 202
proofchaattribute theory is now optional, since the element can appear inside a theory element.161
proofobjectchaattribute theory is now optional, since the element can appear inside a theory element.161
recognizernewspecifies the recognizer predicate of a sort.157
recursenewrecursive calls to presentation in style.191
refchaattribute kind renamed to type.94
selectorchathe old type attribute (had values total and partial) is deprecated, its duty is now carried by an attribute total (values yes and no).157
signaturedepfor the moment
sortdefchahas a mandatory name attribute, otherwise the defined symbol has no name.156

columns: parameter | dep | the om:OMOBJ element child is now directly a child of method |

Table p. 331.76 — 9×4, 0 spanning cell(s)
stylenewallows to specify style information in presentation and omstyle elements using a simplified OMDoc-internalized version of XSLT.189
symbolaugnew optional attribute generated-by to show that it is generated by expanding a definition.136
textnewpresentation of text in omstyle.190
theory-inclusionchanow allows CMP group for descriptive text, no longer has a decomposition child, this is now attached by its for attribute. The timestamp attribute is deprecated, use dc:date with appropriate action instead.178
typeaugcan now also appear on top-level. Has an optional id attribute for identification, and an optional for attribute to point to a symbol element it declares type information for.139
useaugNew attribute element allows to specify that the content should be encased in an XML element with the attribute-value pairs specified in the string specified in the attribute attributes.194
value-ofnewpresentation of values in style.190
withnewused to supply fragments of text in CMPs with style and id attributes that can be used for presentation and referencing.126
xsltnewallows to embed XSLT into presentation and omstyle elements.189

columns: style | new | allows to specify style information in presentation and omstyle elements using a simplified OMDoc-internalized version of XSLT. | 189

Table p. 332.77 — 2×7, 0 spanning cell(s)
Elementp.Mod.RequiredOptionalDContent
AttribsAttribsC

columns: Element | p. | Mod. | Required | Optional | D | Content

Table p. 332.78 — 10×7, 0 spanning cell(s)
adt156ADTxml:id, type, style, class, theory, generated-from, generated-via+sortdef+
alternative145STfor, entailed-by, entails, entailed-by-thm, entails-thmxml:id, type, theory, generated-from, generated-via, uniqueness, exhaustivity, consistency, existence, style, class+CMP*, (FMP| requation*| (OMOBJ |m:math |legacy)*)
answer210QUIZverdictxml:id, style, class+CMP*, FMP*
m:apply115MMLid, xlink:href-bvar?, 《CMel》*
argument156ADTsort+selector?
assertion142STxml:id, type, theory, generated-from, generated-via, style, class+CMP*, FMP*
assumption124MTXTxml:id, inductive, style, class+CMP*, (OMOBJ |m:math |legacy)?
attribute191PRESname-(value-of| text)*
axiom138STnamexml:id, type, generated-from, generated-via, style, class+CMP*, FMP*
axiom-inclusion180CTHfrom, toxml:id, style, class, theory, generated-from, generated-via+morphism?, (path-just| obligation*)

columns: adt | 156 | ADT | | xml:id, type, style, class, theory, generated-from, generated-via | + | sortdef+

Table p. 332.79 — 4×6, 0 spanning cell(s)
m:bvar115MMLid, xlink:href-ci*
m:ci115MMLid, xlink:href-PCDATA
m : cn115MMLid, xlink:href-\[ \begin{aligned} & ([0-9]|,| .) \\ & (* \mid \mathrm{e}([0-9]|,| .) *) ? \end{aligned} \]
choice210QUIZxml:id, style, class+CMP*, FMP*

columns: m:bvar | 115 | MML | id, xlink:href | - | ci*

Table p. 333.80 — 6×7, 0 spanning cell(s)
CMP122MTXTxml:lang,xml:id-(text|OMOBJ|m:math |legacy|with|term |omlet)*
code202EXTxml:id, for,theory, generated-from, generated-via, requires,style, class+input?,output?, effect?,data+
conclusion124MTXTxml:id,style, class+CMP*,(OMOBJ|m:math |legacy)?
constructor156ADTnametype,scope, style,class, theory, generated-from, generated-via+argument*,recognizer?
dc:contributor98DCxml:id,role, style,class-《text》
dc:creator98DCxml:id,role, style,class-《text》

columns: CMP | 122 | MTXT | | xml:lang,xml:id | - | (text|OMOBJ|m:math |legacy|with|term |omlet)*

Table p. 333.81 — 11×7, 0 spanning cell(s)
m:csymbol115MMLdefinitionURLid,xlink:href-EMPTY
data203EXTformat,href, size,original-<![CDATA[...]]>
dc:date99DCaction,who-ISO 8601 norm
dd130RTxml:id,style, class,index, verbalizes+CMPcontent
di130RTxml:id,style, class,index, verbalizes+dt+,dd*
dl130RTxml:id,style, class,index, verbalizes+li*
dt130RTxml:id,style, class,index, verbalizes+CMPcontent
decomposition184DGlinkstheory, generated-from, generated-via-EMPTY
definition139STxml:id,foruniqueness, existence, consistency, exhaustivity, type, generated-from, generated-via, style,class+CMP*,(FMP| requation+|OMOBJ |m:math|legacy)?, measure?,ordering?
dc:description99DCxml:lang-CMPcontent
derive162PFxml:id,style, class-CMP*,FMP?,method?

columns: m:csymbol | 115 | MML | definitionURL | id,xlink:href | - | EMPTY

Table p. 333.82 — 3×7, 0 spanning cell(s)
effect204EXTxml:id,style, class-CMP*,FMP*
element190PRESnamexml:id,cr,ns-(attribute|element| text|recurse)*
example146STforxml:id,type, assertion, proof,style, class,theory, generated-from, generated-via+CMP*|(OMOBJ|m:math |legacy)?

columns: effect | 204 | EXT | | xml:id,style, class | - | CMP*,FMP*

Table p. 334.83 — 3×7, 0 spanning cell(s)
exercise209QUIZxml:id, type, for, from, style, class, theory, generated-from, generated-via+CMP*, FMP*, hint?, (solution*|mc*)
FMP123MTXTlogic, xml:id-(assumption*, conclusion*) |OMOBJ |m:math |legacy
dc:format100DC-fixed: "application/omdoc+xml"

columns: exercise | 209 | QUIZ | | xml:id, type, for, from, style, class, theory, generated-from, generated-via | + | CMP*, FMP*, hint?, (solution*|mc*)

Table p. 334.84 — 2×7, 0 spanning cell(s)
hint209QUIZxml:id, style, class, theory, generated-from, generated-via+CMP*, FMP*
hypothesis162PFxml:id, style, class, inductive-CMP*, FMP*

columns: hint | 209 | QUIZ | | xml:id, style, class, theory, generated-from, generated-via | + | CMP*, FMP*

Table p. 334.85 — 10×7, 0 spanning cell(s)
dc:identifier100DCscheme-ANY
ide130RTindexxml:id,sort-by,see seealso, links, style, class-idp*
idp130RTxml:id,sort-by,see seealso, links, style, class-CMPcontent
idt130RTstyle, class-CMPcontent
idx130RTxml:id,sort-by,see seealso, links, style, class-idt?,idp+
ignore92DOCtype, comment-ANY
imports150CTHfromxml:id, type, style, class+morphism?
inclusion179CTHforxml:id-
input204EXTxml:id, style, class-CMP* , FMP*
insort156ADTfor-

columns: dc:identifier | 100 | DC | | scheme | - | ANY

Table p. 334.86 — 2×7, 0 spanning cell(s)
dc:language100DC-ISO 8601 norm
li130RTxml:id, style, class, index, verbalizes-Math Vernacular

columns: dc:language | 100 | DC | | | - | ISO 8601 norm

Table p. 334.87 — 8×7, 0 spanning cell(s)
cc:license102CCjurisdiction-permissions, prohibitions, requirements
link130RTxml:id, style, class, index, verbalizes-Math Vernacular
m:math114MMLid, xlink:href-《CMel》+
mc210QUIZxml:id, style, class, theory, generated-from, generated-via-choice, hint?, answer
measure141STxml:id-OMOBJ |m:math |legacy
metadata92DCinherits-(dc-element) *
method164PFxref-(OMOBJ |m:math |legacy| premise | proof | proofobject)*
morphism175CTHxml:id, base, consistency, exhaustivity, type, hiding, style, class-requation*, measure?, ordering?

columns: cc:license | 102 | CC | | jurisdiction | - | permissions, prohibitions, requirements

Table p. 334.88 — 1×7, 0 spanning cell(s)
note131RTtype,xml:id, style, class, index, verbalizes-Math Vernacular

columns: note | 131 | RT | | type,xml:id, style, class, index, verbalizes | - | Math Vernacular

Table p. 335.89 — 23×7, 0 spanning cell(s)
obligation178CTHinduced-by, assertionxml:id-EMPTY
om:0MA108OMid,cdbase-《OMel》*
om:OMATTR110OMid,cdbase-《OMel》
om:OMATP110OMcdbase-(OMS,(《OMel》)I om:OMFOREIGN))+
om :0MB111OMid,class,style, class-#PCDATA
om:OMBIND109OMid,cdbase-《OMel》,om:OMBVAR,《OMel》 ?
om :OMBVAR109OM-(om:OMV|om:OMATTR)+
om:OMFOREIGN110OMid,cdbase-ANY
omdoc90DOCxml:id,type, version, style,class, xmlns,theory, generated-from, generated-via+(top-level element)*
om:0ME111OMxml:id-(《OMel》))?
om:0MR112OMhref-
om :0MF111OMid,dec,hex-#PCDATA
omgroup93DOCxml:id,type, style,class, modules,theory, generated-from, generated-via+top-level element*
ol130RTxml:id,style, class,index, verbalizes—li*
om:0MI111OMid,class,style-[0-9]*
omlet205EXTid,argstr,type, function,action, data,style, class+ANY
om:0M0BJ108OMid,cdbase, class,style-《(OMel)〉?
omstyle188PRESelementfor,xml:id, xref,style, class-(style|xslt)*
om:0MS108OMcd,nameclass,style-EMPTY
omtext124MTXTxml:id,type, for,from, style,theory, generated-from, generated-via+CMP+,FMP?
om:0MV108OMnameclass,style-EMPTY
ordering141STxml:id-OMOBJ|m:math|legacy
output204EXTxml:id,style, class-CMP*,FMP*

columns: obligation | 178 | CTH | induced-by, assertion | xml:id | - | EMPTY

Table p. 335.90 — 5×7, 0 spanning cell(s)
p130RTxml:id,style, class,index, verbalizes-Math Vernacular
param207EXTnamevalue,valuetype-EMPTY
path-just184DGlocal,globalsfor,xml:id-EMPTY
cc:permissions103CCreproduction, distribution, derivative_works-EMPTY
premise164PFxref-EMPTY

columns: p | 130 | RT | | xml:id,style, class,index, verbalizes | - | Math Vernacular

Table p. 336.91 — 6×7, 0 spanning cell(s)
presentation192PRESforxml:id, xref, fixity, role, lbrack, rbrack, separator, bracket-style, style, class, precedence, crossref-symbol-(use | xslt | style)*
private202EXTxml:id, for, theory, generated-from, generated-via, requires, reformulates, style, class+data+
cc:prohibitions103CCcommercial_use-EMPTY
proof161PFxml:id, for,theory, generated-from, generated-via, style, class+(symbol | definition | omtext | derive | hypothesis)*
proofobject169PFxml:id, for, theory, generated-from, generated-via, style, class+CMP*, (OMOBJ |m:math |legacy)
dc:publisher99DCxml:id, style, class-ANY

columns: presentation | 192 | PRES | for | xml:id, xref, fixity, role, lbrack, rbrack, separator, bracket-style, style, class, precedence, crossref-symbol | - | (use | xslt | style)*

Table p. 336.92 — 7×7, 0 spanning cell(s)
ref94DOCxref, type-ANY
recognizer157ADTnametype, scope, role, style, class+
recurse191PRESselect-EMPTY
dc:relation100DC-ANY
requation140STxml:id, style, class—(OMOBJ |m:math |legacy), (OMOBJ |m:math |legacy)
cc:requirements103CCnotice, copyleft, attribution—EMPTY
dc:rights100DC-ANY

columns: ref | 94 | DOC | | xref, type | - | ANY

Table p. 336.93 — 7×7, 0 spanning cell(s)
selector157ADTnametype, scope, role, total, style, class+
solution209QUIZxml:id, for, style, class, theory, generated-from, generated-via+(CMP*, FMP*) | proof
sortdef156ADTnamerole, scope, style, class+(constructor|insort)*
dc:source100DC-ANY
style189PRESformatxml:lang, requires-(element | text | recurse | value-of)*
dc:subject99DCxml:lang-CMPcontent
symbol136STnamerole, scope, style, class, generated-from, generated-via+type*

columns: selector | 157 | ADT | name | type, scope, role, total, style, class | + |

Table p. 336.94 — 2×7, 0 spanning cell(s)
table130RTxml:id, style, class, index, verbalizes-tr*
term128MTXTcd, namexml:id, role, style, class-CMP content

columns: table | 130 | RT | | xml:id, style, class, index, verbalizes | - | tr*

Table p. 337.95 — 10×7, 0 spanning cell(s)
text190PRES-\#PCDATA
td130RTxml:id, style, class, index, verbalizes-Math Vernacular
th130RTxml:id, style, class, index, verbalizes-Math Vernacular
theory149STxml:idcdbase, style, class+(statement/theory)*
theory-inclusion178CTHfrom, toxml:id, style, class, theory, generated-from, generated-via+(morphism, decomposition?)
tr130RTxml:id, style, class, index, verbalizes-(td|th)*
dc:title98DCxml:lang-CMPcontent
tgroup149DOCxml:id, type, style, class, modules, generated-from, generated-via+top-level or theoryconstitutive element*
type139STsystemxml:id, for, style, class-CMP*, (OMOBJ |m:math |legacy)
dc:type100DC-fixed: "Dataset" or "Text" or "Collection"

columns: text | 190 | PRES | | | - | \#PCDATA

Table p. 337.96 — 5×7, 0 spanning cell(s)
ul130RTxml:id, style, class, index, verbalizes-li*
use194PRESformatxml:lang, requires, fixity, lbrack, rbrack, separator, crossref-symbol, element, attributes-(use | xslt | style)*
value-of190PRESselect-EMPTY
phrase126MTXTxml:id, style, class, index, verbalizes, type-CMP content
xslt189PRESformatxml:lang, requires-XSLT fragment

columns: ul | 130 | RT | | xml:id, style, class, index, verbalizes | - | li*

Table p. 338.97 — 33×3, 9 spanning cell(s)
AttributeelementValues
actiondc:dateunspecified
specifies the action taken on the document on this date.
actionomletexecute, display, other
specifies the action to be taken when executing the omlet, the value is application-defined.
actuateomletonPresent, onLoad, onRequest, other
specifies the timing of the action specified in the action attribute
assertionexample
specifies the assertion that states that the objects given in the example really have the expected properties.
assertionobligation
specifies the assertion that states that the translation of the statement in the source theory specified by the induced-by attribute is valid in the target theory.
attributesuse
the attribute string for the start tag of the XML element substituted for the brackets (this is specified in the element attribute).
attributioncc:requirementsrequired, not_required
Specifies whether the copyright holder/author must be given credit in derivative works
basemorphism
specifies another morphism that should be used as a base for expansion in the definition of this morphism
bracket-stylepresentation, uselisp, math
specifies whether a function application is of the form \(f(a, b)\) or ( \(f a b\) )
cdom: 0MS
specifies the content dictionary of an OpenMath symbol
cdterm
specifies the content dictionary of a technical term
cdbaseom: *
specifies the base URI of the content dictionaries used in an OpenMath object
cdreviewdatetheory
specifies the date until which the content dictionary will remain unchanged
cdrevisiontheory
specifies the minor version number of the content dictionary
cdstatustheoryofficial, experimental, private, obsolete
specifies the content dictionary status
cdurltheory
foundthe main URL, where the newest version of the content dictionary can be

columns: Attribute | element | Values

Table p. 339.98 — 47×3, 14 spanning cell(s)
cdversiontheory
specifies the major version number of the content dictionary
commentignore
specifies a reason why we want to ignore the contents
crossref-symbolpresentation, useall, brackets, lbrack, no, rbrack, separator, yes
specifies whether cross-references to the symbol definition should be generated in the output format.
class*
specifies the CSS class
commercial_usecc:permissionspermitted, prohibited
specifies, whether commercial use of the document with this license is permitted
consistencymorphism, definitionOMDoc reference
points to an assertion stating that the cases are consistent, i.e. that they give the same values, where they overlap
copyleftcc:restrictionsrequired, not_required
specifies whether derived works must be licensed with the same license as the current document.
crelementyes/no
specifies whether an xlink:href cross-reference should be set on the result element.
crefom: *URI reference
extra attribute for cross-references in parallel markup
cridelementXPath expression
the path to the sub-element that corresponds to the result element.
crossref-symbolpresentation, useno, yes, brackets, separator, lbrack, rbrack, all
specifies which generated presentation elements should carry crossreferences to the definition.
dataomlet
points to a private element that contains the data for this omlet
definitionURLm: *URI
points to the definition of a mathematical concept
derivative_workscc:permissionspermitted, not_permitted
specifies whether the document may be used for making derivative works.
distributioncc:permissionspermitted, not_permitted
specifies whether distribution of the current document fragment is permitted.
elementuse
the XML element tags to be substituted for the brackets.
elementomstyle
the XML element, the presentation information contained in the omstyle element should be applied to.
encodingm:annotation,om:0MF0REIGNMIME type of the content
specifies the format of the content
entails, entailed-byalternative
specifies the equivalent formulations of a definition or axiom
entails-thm, entailed-by-thmalternative
specifies the entailment statements for equivalent formulations of a definition or axiom
exhaustivitymorphism, definitionOMDoc reference
points to an assertion that states that the cases are exhaustive.
existencedefinitionOMDoc reference
points to an assertion that states that the symbol described in an implicit
fixitypresentationassoc, infix, postfix, prefix
specifies where the function symbol-of a function application should be
functionomlet

columns: cdversion | theory |

Table p. 340.99 — 50×3, 16 spanning cell(s)
specifies the function to be called when this omlet is activated.
formatdata
specifies the format of the data specified by a data element. The value should e.g. be a MIME type [FB96].
for*
can be used to reference an element by its unique identifier given in its xml:id attribute.
formalismlegacyURI reference
specifies the formalism in which the content is expressed
formatlegacyURI reference
specifies the encoding format of the content
formatusecmml, default, html, mathematica, pmml, TeX,...
specifies the output format for which the notation is specified
fromimports, theory-inclusion, axiom-inclusionURI reference
pointer to source theory of a theory morphism
fromomtextURI reference
points to the source of a relation given by a text type
generated-fromtop-level elementsURI reference
points to a higher-level syntax element, that generates this statement.
generated-viatop-level elements,...URI reference
points to a theory-morphism, via which it is translated from the element pointed to by the generated-from attribute.
globalspath-just
points to the axiom-inclusions or theory-inclusions that is the rest of the inclusion path.
hidingmorphism
specifies the names of symbols that are in the domain of the morphism
hrefdata, link, om:OMRURI reference
a URI to an external file containing the data.
xml:id
\begin{tabular}[t]{l} associates a unique identifier to an element, which can thus be referenced \\ associates a unique identifier to an element, which can thus be referenced by an for or xref attribute. \end{tabular}
xml:base
specifies a base URL for a resource fragment
indexon RT elements
A path identifier to establish multilingual correspondence
induced-byobligation
points to the statement in the source theory that induces this proof obligation
inductiveassumption, hypothesisyes, no
Marks an assumption or hypothesis inductive.
inheritsmetadataURI reference
points to a metadata element from which this one inherits.
jurisdictioncc:licenseIANA Top level Domain designator
specifies the country of jurisdiction for a Creative Commons license
just-bytype
points to an assertion that states the type property in question.
rolesymbol, constructor, recognizer, selector, sortdefobject, type, sort, binder, attribution, semantic-attribution, error
specifies the role (possible syntactic roles) of the symbol in this declaration.
roledc:creator,dc:contributorMARC relators
specifies the role of a person who has contributed to the document
rolepresentationapplied, binding, key
specifies which role of the symbol is annotated with notation information
lbrackpresentation, use
the left bracket to use in the notation of a function symbol
linksdecomposition

columns: format | specifies the function to be called when this omlet is activated. data | specifies the function to be called when this omlet is activated.

Table p. 341.100 — 49×3, 11 spanning cell(s)
specifies a list of theory- or axiom-inclusions that justify (by decomposition) the theory-inclusion specified in the for attribute.
localpath-just
points to the axiom-inclusion that is the first element in the path.
logicFMPtoken
specifies the logical system used to encode the property.
modulesomdoc, omgroupmodule and sub-language shorthands, URI reference
specifies the modules or OMDoc sub-language used in this document fragment
nameom:OMS, om:OMV, symbol, term
the name of a concept referenced by a symbol, variable, or technical term.
nameattribute, element
the local name of generated element.
nameparam
the name of a parameter for an external object.
noticecc:requirementsrequired, not_required
specifies whether copyright and license notices must be kept intact in distributed copies of this document
nselement, attributeURI
specifies the namespace URI of the generated element or attribute node
originaldatalocal, external
specifies whether the local copy in the data element is the original or the external resource pointed to by the href attribute.
parametersadt
The list of formal parameters of a higher-order abstract data type
precedencepresentation
the precedence of a function symbol (for elision of brackets)
proofsassertion
specifies a list of URIs to proofs of this assertion.
pto, pto-versionprivate, code
specifies the system and its version this data or code is private to
rankpremise
specifies the rank (importance) of a premise
rbrackpresentation, use
the right bracket to use in the notation of a function symbol
reformulatesprivate
points to a set of elements whose content is reformulated by the content of the private element for the system.
reproductioncc:permissionspermitted, not_permitted
specifies whether reproduction of the current document fragment is permitted by the licensor
requiresprivate, code, use, xslt, styleURI reference
points to a code element that is needed for the execution of this data by the system.
roledc:creator, dc:collaboratoraft, ant, aqt, aui, aut, clb, edt, ths, trc, trl
the MARC relator code for the contribution of the individual.
rolephrase, term
the role of the phrase annotation
rolepresentationapplied, binding, key
specifies for which role (as the head of a function application, as a binding symbol, or as a key in a attribution, or as a stand-alone symbol (the default)) of the symbol presentation is intended
schemedc:identifierscheme name
specifies the identification scheme (e.g. ISBN) of a resource
scopesymbolglobal, local
\begin{tabular}[t]{l} specifies the visibility of the symbol declared. This is a very crude specifi- \\ specifies the visibility of the symbol declared. This is a very crude specification, it is better to use theories and importing to specify symbol accessibility. \end{tabular}
selectmap, recurse, value-ofXPath expression
specifies the path to the sub-expression to act on

columns: local | specifies a list of theory- or axiom-inclusions that justify (by decomposition) the theory-inclusion specified in the for attribute. path-just | specifies a list of theory- or axiom-inclusions that justify (by decomposition) the theory-inclusion specified in the for attribute.

Table p. 342.101 — 45×3, 13 spanning cell(s)
separatorpresentation, use
the separator for the arguments to use in the notation of a function symbol
showomletnew, replace, embed, other
specifies the desired presentation of the external object.
sizedata
specifies the size the data specified by a data element. The value should be number of kilobytes
sortargument
specifies the argument sort of the constructor
style*
specifies a token for a presentation style to be picked up in a presentation element.
systemtype
A token that specifies the logical type system that governs the type specified in the type element.
theory*
specifies the home theory of an OMDoc statement.
totheory-inclusion, axiom-inclusion
specifies the target theory
totalselectorno, yes
specifies whether the symbol declared here is a total or partial function.
typeadtfree, generated, loose
defines the semantics of an abstract data type free = no junk, no confusion, generated = no junk, loose is the general case.
typeassertiontheorem, lemma, corollary, conjecture, false-conjecture, obligation, postulate, formula, assumption, proposition
tells you more about the intention of the assertion
typedefinitionimplicit, inductive, obj, recursive, simple
specifies the definition principle
typederiveconclusion, gap
singles out special proof steps: conclusions and gaps (unjustified proof steps)
typeexampleagainst, for
specifies whether the objects in this example support or falsify some conjecture
typeignore
specifies the type of error, if ignore is used for in-place error markup
typeimportsglobal, local
local imports only concern the assumptions directly stated in the theory. global imports also concern the ones the source theory inherits.
typemorphism
specifies whether the morphism is recursive or merely pattern-defined
typeomgroup, omdocenumeration, sequence, itemize
the first three give the text category, the second three are used for generalized tables
typeomtextabstract, antithesis, comment, conclusion, elaboration, evidence, introduction, motivation, thesis
a specification of the intention of the text fragment, in reference to context.
typephrase
the linguistic or mathematical type of the phrase
typerefinclude, cite
specifies whether to replace the ref element by the fragment referenced
uniquenessdefinitionURI reference
points to an assertion that states the uniqueness of the concept described
valueparam

columns: separator | presentation, use |

Table p. 343.102 — 25×3, 11 spanning cell(s)
specifies the value of the parameter
valuetypeparam
specifies the type of the value of the parameter
verbalizeson RT elementsURI references
contains a whitespace-separated list of pointers to OMDoc elements that are verbalized
verdictanswer
specifies the truth or falsity of the answer. This can be used e.g. by a grading application.
versionomdoc1.2
specifies the version of the document, so that the right DTD is used
versioncc:license
specifies the version of the Creative Commons license that applies, if not present, the newest one is assumed
viainclusion
points to a theory-inclusion that is required for an actualization
whodc:date
specifies who acted on the document fragment
xml:langCMP, dc:*ISO 639 code
the language the text in the element is expressed in.
xml:languse, xslt, stylewhitespace-separated list of ISO 639 codes
specifies for which language the notation is meant
xlink:*om:OMR, m:*URI reference
specify the link behavior on the elements
xrefref, method, premiseURI reference
Identifies the resource in question
xrefpresentation, omstyleURI reference
The element, this URI points to should be in the place of the object containing this attribute.

columns: valuetype | specifies the value of the parameter param | specifies the value of the parameter