<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet type="text/css"
   href="/~hammond/style/gellmuart.css"?>
<!DOCTYPE article
  PUBLIC "-//GNU GPL: William F. Hammond//DTD GELLMU XML 0.7.6L//EN"
  "http://www.albany.edu/~hammond/gellmu/xml/axgellmu.dtd">
<article stem="silly"
><preamble
><base
>href="http:<sol mml="mo"
/><sol mml="mo"
/>www.albany.edu<sol mml="mo"
/><tld
/>hammond<sol mml="mo"
/>gellmu<sol mml="mo"
/>"</base><surtitle
>W. F. Hammond: The GELLMU Archive</surtitle><title
>A Silly Little <abbr
>GELLMU</abbr> Article</title><author
>William F. Hammond</author><date
>revised March 25, 2006</date></preamble><body
><par
>This is the simplest possible type of article<eos
/>  Its body
consists of just a few paragraphs<eos
/>  It is a <abbr
>GELLMU</abbr>
document<eos
/>  <abbr
>GELLMU</abbr> stands for <quophrase
>Generalized Extensible
<latex
/><hyp
/>Like Markup</quophrase>.</par><par
><abbr
>GELLMU</abbr> is designed to admit <bold
>completely</bold>
automated translation into many document languages<eos
/>
Classical <latex
/> does not have that property; but some <latex
/>
documents do when imported under <abbr
>GELLMU</abbr><eos
/>
Yet <abbr
>GELLMU</abbr> is really no more difficult to edit than <latex
/>.</par><par
>It is relatively easy for a sophisticated <abbr
>GELLMU</abbr>
user with freely available software to add <latex
/><hyp
/>like commands to
<abbr
>GELLMU</abbr>.</par><par
>There is no organization of this article into sections<eos
/>  The
<emph
>content model</emph> for this type of document (<abbr
>GELLMU</abbr>
<quophrase
>article</quophrase>) provides that the document body be organized
either into one or more sections, which may be preceded and followed
by paragraphs outside those sections, or that the document body simply
be organized into <invr
>one</invr> or more paragraphs<eos
/></par><parb
>One thing to notice is that the generalized <latex
/> markup allows
new paragraphs to be opened with the appearance of a blank line in
the marked up document<eos
/></parb><parb
>Another thing to notice is that
<display
><verb
><quo
/><bsl
/>begin<lbr
/>par<rbr
/> ... <bsl
/>end<lbr
/>par<rbr
/><quo
/></verb></display>
and <display
><verb
><quo
/><bsl
/>par<lbr
/> ... <rbr
/><quo
/></verb></display>
are essentially equivalent forms of markup in <abbr
>GELLMU</abbr><eos
/>  That is,
<abbr
>GELLMU</abbr> markup, which is essentially a markup under <abbr
>SGML</abbr>
does not provide its own concept of <quophrase
>environment</quophrase> although
it supports <latex
/><hyp
/>like environmental markup<eos
/></parb><parb
>Just as with <tex
/> or <latex
/> it is easy to provide a mathematical
formula, such as <tmath
>y <eqs
/> x<sup
>3</sup><sol mml="mo"
/>(x<sup
>2</sup> <plu
/> 1)</tmath><aoc
/> either inline or displayed<eos
/>
</parb><par
>This paragraph contains a math display involving the same
formula:
<displaymath
> y <eqs
/> <frac
><numr
>x<sup
>3</sup></numr><denm
>x<sup
>2</sup> <plu
/> 1</denm></frac> <eos
/></displaymath>
Here is a gratuitous inline radical: <tmath
><sqrt
><radx
>3</radx><radicand
>2</radicand></sqrt></tmath><aos
/></par><parb
>The current version of the didactic <abbr
>GELLMU</abbr> <quophrase
>article</quophrase>
definition supports simple mathematical commands such as <qquostr
>frac</qquostr>,
<qquostr
>sum</qquostr>, <qquostr
>int</qquostr>, and <qquostr
>prod</qquostr>, and provides some
<qquostr
>table</qquostr> support<eos
/>   Table models are close adaptations
of the early <abbr
>HTML</abbr> table model, and there is near emulation of
<latex
/><apos
/>s <quophrase
>tabular</quophrase> model<eos
/></parb><parb
>The square root of a compound fraction:
<displaymath
> <sqrt
><frac
><numr
><frac
><numr
>a</numr><denm
>b</denm></frac></numr><denm
><frac
><numr
>c</numr><denm
>d</denm></frac></denm></frac></sqrt> <spc
/><spc
/><eos
/> </displaymath></parb><parb
>This math display was marked up with:
<verblist
><nln
><bsl
/><lsb
/><spc
/><bsl
/>sqrt<lbr
/><bsl
/>frac<lbr
/><bsl
/>frac<lbr
/>a<rbr
/><lbr
/>b<rbr
/><rbr
/><lbr
/><bsl
/>frac<lbr
/>c<rbr
/><lbr
/>d<rbr
/><rbr
/><rbr
/><spc
/><bsl
/><spc
/><bsl
/><spc
/><bsl
/>eos<spc
/><bsl
/><rsb
/></nln></verblist></parb><parb
>The markup <emph
>eos</emph> for <quophrase
>end<hyp
/>of<hyp
/>sentence</quophrase> is used instead of
<lsq
/>.<rsq
/> in order to signal a semantic parser that it is not part of
the mathematical content of the display<eos
/></parb><parb
>Next we present the formula for solving the general quadratic equation:
<displaymath
> a x<sup
>2</sup> <plu
/> b x <plu
/> c <eqs
/> 0 <eos
/> </displaymath>
Its solution is marked up with:
<verblist
><nln
><bsl
/><lsb
/><spc
/>x<spc
/><eqc
/><spc
/><bsl
/>frac<lbr
/><hyp
/>b<spc
/><bsl
/>pm<spc
/><bsl
/>sqrt<lbr
/>b<crt
/>2<spc
/><hyp
/><spc
/>4<spc
/>a<spc
/>c<rbr
/><rbr
/><lbr
/>2<spc
/>a<rbr
/><spc
/><bsl
/>eos<spc
/><bsl
/><rsb
/></nln></verblist>
to give
<displaymath
> x <eqs
/> <frac
><numr
><hyp
/>b <pm
/> <sqrt
>b<sup
>2</sup> <hyp
/> 4 a c</sqrt></numr><denm
>2 a</denm></frac> <eos
/> </displaymath></parb><parb
>And we offer the Taylor series of the <emph
>exponential</emph> function:
<displaymath
> e<sup
>t</sup> <eqs
/> <sum
><sub
>k <eqs
/> 0</sub><sup
><infty
/></sup><sipbody
><hsp
/> <frac
><numr
>t<sup
>k</sup></numr><denm
>k<exc
/></denm></frac></sipbody></sum> <spc
/><spc
/><cma
/> </displaymath>
which is created with the markup:
<verblist
><nln
><bsl
/><lsb
/><spc
/>e<crt
/>t<spc
/><eqc
/><spc
/><bsl
/>sum<lbr
/><und
/><lbr
/>k<spc
/><eqc
/><spc
/>0<rbr
/><crt
/><lbr
/><bsl
/>infty<rbr
/><spc
/><bsl
/><cma
/><spc
/><bsl
/>frac<lbr
/>t<crt
/>k<rbr
/><lbr
/>k<exc
/><rbr
/><rbr
/><spc
/><bsl
/><spc
/><bsl
/><spc
/><bsl
/>cma<spc
/><bsl
/><rsb
/></nln></verblist></parb><parb
>To be sure that <qquostr
>frac</qquostr> is working recursively, we try
<verblist
><nln
><bsl
/><lsb
/><bsl
/>frac<lbr
/>1<spc
/><plu
/><spc
/><bsl
/>sqrt<lbr
/>5<rbr
/><rbr
/><lbr
/>2<rbr
/><spc
/><eqc
/></nln><nln
><spc
/><spc
/><spc
/><spc
/><spc
/>1<spc
/><plu
/><spc
/><bsl
/>frac<lbr
/>1<rbr
/><lbr
/>1<plu
/><bsl
/>frac<lbr
/>1<rbr
/><lbr
/>1<plu
/><bsl
/>frac<lbr
/>1<rbr
/><lbr
/>1<plu
/><bsl
/>frac<lbr
/>1<rbr
/><lbr
/>1<plu
/><bsl
/>ldots;<rbr
/><rbr
/><rbr
/><rbr
/><spc
/><bsl
/>eos<spc
/><bsl
/><rsb
/></nln></verblist>
for the continued fraction expansion of the <emph
>golden mean</emph>, and this
yields:
<displaymath
><frac
><numr
>1 <plu
/> <sqrt
>5</sqrt></numr><denm
>2</denm></frac> <eqs
/>
     1 <plu
/> <frac
><numr
>1</numr><denm
>1<plu
/><frac
><numr
>1</numr><denm
>1<plu
/><frac
><numr
>1</numr><denm
>1<plu
/><frac
><numr
>1</numr><denm
>1<plu
/><ldots
/></denm></frac></denm></frac></denm></frac></denm></frac> <eos
/> </displaymath></parb><parb
>It is important to understand what is or is not happening here<eos
/>  The
mathematical markup is rather <latex
/><hyp
/>like<eos
/>  In fact, only
the markup for <qquostr
><bsl
/>sum</qquostr> is slightly different from the
mathematical markup used with <latex
/><eos
/>  That is because it is
essential in <abbr
>GELLMU</abbr> to have a precise location for the end of
that which is being summed<footnote
>The reason is that the exact end location for <qquostr
><bsl
/>sum</qquostr> is
not deducible merely from the <emph
>syntax</emph> of its markup but requires
a knowledge of the command name <emph
>sum</emph><eos
/>  This is always the case
for a command with more than one argument<eos
/>  For some such commands it is
inconsequential because the location of the end is determined automatically
at the second stage of processing with sufficient precision<eos
/>  Where greater
precision is needed, however, it must be provided in input markup since the
first stage of processing is allowed to know only syntax<eos
/></footnote><eos
/></parb><parb
>One way for a mathematician to view the difference between
<abbr
>GELLMU</abbr>, <latex
/> and <abbr
>HTML</abbr> is to think about
<quophrase
>rational maps of algebraic surfaces</quophrase><eos
/>  If one wishes to
have an automatic translator from <latex
/> to <abbr
>HTML</abbr> (or even to
<abbr
>HTML</abbr> with provision for mathematical notation), there will be
places where the transformation is singular and fails<eos
/>  Such
singularities may be resolved by moving to a markup designed to
<quophrase
>dominate</quophrase> both targets<eos
/></parb><parb
>I never intend to provide more than a <emph
>didactic</emph> definition of
<quophrase
>article</quophrase> inasmuch as it is my opinion that each author or
work group of authors will ultimately find it essential, just as now
they find essential the <quostr
><bsl
/>newcommand</quostr> feature of <latex
/>,
to be able to provide customization<eos
/>  <emph
>Customization</emph> is
ever so much more important in <abbr
>GELLMU</abbr> than in <latex
/> because
under this design there will never be a full set of ultimate target
formats<eos
/>  With <latex
/> customization is primarily a matter of
authoring convenience; under <abbr
>GELLMU</abbr> customization is required
in order to be able to service all of the desired target formats<eos
/></parb><parb
>Beyond that an author or work group may hope to design a definition
of <quophrase
>article</quophrase> (or of another document type) that is robust
for almost any <emph
>conceivable</emph> target format by thinking carefully
about all possible <quophrase
>content</quophrase> distinctions relevant to
his, her, or its current authoring context<eos
/>  To the extent that this
design meets that goal, the author or work group will have no need
to revisit old documents in order to be able to have automatic
processing to new formats<eos
/>
</parb></body></article>
