|
|
|
|||
links in the mockup). They provide an extra layer of
information that may not be of interest to casual users, and would perhaps be
distracting, but which may be important for various specialized purposes.
Of particular note:
OpenMath is a developing standard for unambiguous representation of mathematics which will allow importation into a wide spectrum of applications: typesetting, numerical, visualization and computer algebra, to name a few. At the least, it will be possible to `cut and paste' a formula from the DLMF into a computer algebra system for further manipulations. It may also be possible for us to provide a number of transformations on-line; for example, including higher terms in a series expansion, or the capability of numerically testing or comparing formula.
In the HTML version, we have attempted to maximize portability and accessibility. Formulas have been presented as images, a non-ideal solution but the most portable solution at this time; MathML will be prefered once it is widely implemented. We have also declined to make use of Java, Javascript or Dynamic HTML, although these will be useful technologies in the future.
For the XML/MathML version, we translate the LaTeX sources into XML, with formulas being represented by Content MathML. This translation is, at best, semi-automatic; by augmenting the LaTeX with declarations of variable types for example, as well as by encouraging a more semantic as opposed to presentational style of markup, we find that most ambiguities in the sources can be resolved.
Accessibility for all users will always be a primary concern. The mockup attempts to determine the capabilities of the user's browser, and sends the appropriate version.
For the eventual DLMF we will investigate use of OpenMath as a more satisfactory representation of formulas in comparison to MathML. The XML/ OpenMath representations will be stored in a database. They will be used as the source for generating HTML, MathML, LaTeX, postscript and other forms as needed. This approach will allow us to automatically construct a variety of specialized documents, for example as a result of a search query. By storing the data in an unambiguous form, emphasizing the structure and semantics rather than just the appearance, we will have greater flexibility in using the material and will maximize the useful lifetime of the authors' work. It will simplify the customization of the HTML that is delivered to users depending on the capabilities of their browser and platform.
We will also be adding more dynamic elements to the DLMF. One example is automatic generation of tables for user-specified ranges and accuracies; this may be either client-side (eg. using Java) or server-side. Automatic generation of visualizations is another example.
|
Last Modified Sat, Oct 22, 2005 |
|