mmlproc - Roadmap

Upcoming in v0.2

• Implementation of parallel markup.
• Full elision, i.e. considering parameterized threshold

Upcoming in v0.3

• Handling of OMR elements: Following reference and substitute the OMR by the rendered target.
• Defaults for OMA/OMS; OMA/OMV; OMA/OMI; OMA/expr. The last one covers expressions like OMA/OMA/OMS.
• Defaults for OMI[expr[1] and expr[2]]
• Full support for attributions.
• Improving/ Verifying/ Fixing Reflexive XML handling
• Implementation to enable/ disable XML validation, i.e. if not set ignoring DOCTYPE declaration and thus don't throwing an exception if the referenced DTD is not present.
• ImplementING cross-referencing from presentation symbols (e.g. +) to some target URL/selection menu/etc.

Potential innovations for future releases

The list of potential innovations consists of possible future functionalities for mmlproc. There is no concrete implementation schedule yet, though!

• Presentation of bound variables according depending on the binder
• Abbreviations in the omdoc syntax so that one can specify a symbol, e.g., left-associative infix with two implicit arguments
• Default notation specifications that apply, e.g., to any application in which the depth-first symbol has a certain meta-theory
• Automatically consider standard notation definition from the CD
• Prioritization: allow users to indicate their notation definition file (for a whole document); allow user to use omdoc pcontext or pc attribute (see MathUI paper) to link notations or notation element to document fragements; if users have not specified a notation definition use the standard definition in the Content Dictionaries (DC); if that also fails take the defaul Rendering