<?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.5L//EN"
  "http://www.albany.edu/~hammond/gellmu/xml/axgellmu.dtd">
<article stem="aboutthisx"
><nul
/><nul
/><nul
/><nul
/><nul
/><nul
/><preamble
><surtitle
>The <abbr
>GELLMU</abbr> Archive</surtitle><title
>About the XML Files Found Here</title></preamble><body
><parb
>The files in this directory are all examples under the didactic document
type that is called <emph
>article</emph><eos
/></parb><parb
>From early days of the project until mid 2006 the translator that
converted the <abbr
>SGML</abbr> form of an <emph
>article</emph> to the (only) <abbr
>XML</abbr> form
of <emph
>article</emph> automatically generated section numbers, tables of
contents, and cross<hyp
/>referencing information<eos
/></parb><parb
>Since mid 2006, this stage of the standard pipeline has been split in
two, and there are now two <abbr
>XML</abbr> versions of <emph
>article</emph><eos
/>  The one
produced directly from <abbr
>SGML</abbr> (with suffix <qquostr
>.xml</qquostr>) is
author<hyp
/>level and very nearly equivalent to original source<eos
/>  It
resides under a strict document type definition for the <abbr
>XML</abbr> version
of <emph
>article</emph> that may be regarded as suitable for authors who
wish to write <emph
>article</emph> originally as <abbr
>XML</abbr> source<eos
/>  With the new
standard pipeline these <abbr
>XML</abbr> document instances qualify as
<quophrase
>stand<hyp
/>alone</quophrase> <abbr
>XML</abbr> documents<eos
/></parb><parb
>The second <abbr
>XML</abbr> form of <emph
>article</emph> (with suffix <qquostr
>.exml</qquostr>)
is very nearly equivalent to what was previously the only <abbr
>XML</abbr> form of
<emph
>article</emph> in the production system<eos
/>  For maximum efficiency in
subsequent generation of end formats the translator producing the
second <abbr
>XML</abbr> form simultaneously produces various auxiliary files
containing <label series="axf1"
>xet</label>(<ref
><popkey
/></ref>) <abbr
>XML</abbr> entity definitions (suffix <quostr
>.xet</quostr>)<footnote
>Some of the entity definitions may be superfluous, but they cause no harm<eos
/>
(There is more than one conceivable way to generate the <abbr
>XML</abbr> version of
an article.)</footnote>,
<label series="axf1"
>xlb</label>(<ref
><popkey
/></ref>) label information (suffix <quostr
>.xlb</quostr>), and <label series="axf1"
>xcn</label>(<ref
><popkey
/></ref>) a table of contents (suffix <quostr
>.xcn</quostr>) as
appropriate<eos
/></parb><parb
>The items (<ref
>xet</ref>) and (<ref
>xcn</ref>) represent included entities in the
second <abbr
>XML</abbr> version of an <emph
>article</emph> and, therefore, must be present in
order to produce conforming <abbr
>XML</abbr><eos
/>  This means that the second <abbr
>XML</abbr> form
of an <emph
>article</emph> does not qualify as a <quophrase
>stand<hyp
/>alone</quophrase> <abbr
>XML</abbr> instance<eos
/>
The current formatters for the <abbr
>HTML</abbr> and <latex
/> targets
make use of item (<ref
>xlb</ref>)<eos
/></parb><parb
>In early 2002, motivated by <abbr
>CSS</abbr> handling in the browser
<softw
>Opera<nbs
/>6</softw>, the author began very tentatively building a
<abbr
>CSS</abbr> style sheet for browser<hyp
/>based rendering of the XML version
of the <abbr
>GELLMU</abbr> <emph
>article</emph> document type<eos
/>  The <abbr
>CSS</abbr>
sheet remains very much under construction, and, at best, <abbr
>CSS</abbr> is
a cruder rendering vehicle for arbitrary XML tag vocabularies than a
finely honed translation to standard <abbr
>HTML</abbr> or <abbr
>XHTML</abbr> with
appropriate use of <abbr
>CSS</abbr> styling<eos
/></parb><parb
>In general, there is an expectation that a web browser with <abbr
>XML</abbr>
capability will render an <abbr
>XML</abbr> document that is accompanied by a
<abbr
>CSS</abbr> style sheet, but such browsers, as a general rule,
should not be expected to handle document instances except when
<quophrase
>stand<hyp
/>alone</quophrase><eos
/></parb><parb
>In particular, the first <abbr
>XML</abbr> form of an <emph
>article</emph> is the one
that should be considered most suitable for <abbr
>CSS</abbr><hyp
/>styled
rendering<eos
/>
</parb></body></article>
