This article is very important, covering markup systems, and motivating
the use of SGML. It covers a key topic, and should be read
several times, preferably once before the exercises and once after. The
authors, from Brown University, have training and experience in
English, in document processing and hypertext systems, and in
supporting humanities computing.
The first two pages are a strong indictment of current systems and
practices of word processing. Given the slowness of change, and the
current shifts occuring 5 years after their article was published, it seems
that the authors' were quite insightful! But that also makes sense based
on the forceful logic of the rest of the article.
After the introduction, the article has 3 main sections. At the end is a
short conclusion. In between are the two main parts:
- 1) markup theory:
- where the various types of markup are
explained; and
- 2) advantages/ disadvantages of markup schemes:
- discussed from
perspectives of
- maintainability,
- portability,
- (cognitive) usability,
- support of authors' focus on content, and
- aids for composition and special processing (like
structure-oriented editing).
Be sure to study all of the figures, and to read the footnotes, though you
are not obliged to read the referenced publications. Try to relate the
discussion to your own experience with word processors, and to think
carefully about problems you have experienced, and places where you
have had to waste time because of deficiencies in the tools or systems.
Most of the discussion on markup theory should make sense. However,
you may have a hard time re discussions of referential markup and
metamarkup. The former can be understood if you think back to simple
substitutions or inclusions supported by macro processors and language
preprocessors. Metamarkup will be more understandable when you
work with SGML Document Type Definitions.
The sections on advantages and disadvantages may be meaningful if you
have worked a lot with various word processors. The discussion will
make more sense, however, after you have worked with the various
SGML tools covered in the exercises, and when you reread the article,
comparing systems familiar from your previous experiences with
SoftQuad HoTMetaL and other tools.
Regarding the article, there are many specific comments to be made:
- p. 933, first par., note that we will learn more about much of this
in the next unit, on hypertext.
- p. 934, first column, note that recently there has been more
research in this area, even by developers of word processors, as they deal
with competition, the requirements of CALS and other SGML-based
initiatives, and a desire to reinvest their profits.
- p. 935-8, please read this carefully. Regarding the first column
on p. 938, think about this when you toggle options to show or not show
tags with HoTMetaL, or take similar actions with word processors
regarding rulers, special characters, etc.
- p. 938, second column through p. 939, reflect on your own work
and experiences with different computers and software systems.
- p. 940, first column, note the six advantages - these are
important arguments re using SGML for an electronic library.
- p. 940, second column, note the four alternatives - consider
page images as a fifth - these are the main choices considered today for
electronic archives. In some situations, some of these make sense, but in
the long run they are not ideal. Be prepared to discuss advantages and
disadvantages of all five. Note that the fourth one mentioned
encompasses when people send in ASCII, or simple text-based electronic
mail files.
- p. 941, subsection on Portability, note that today it makes
sense to go with SGML.
- p. 943-4, subsection on Content Orientation, note that they
take the previously required tact that SGML presumes good tools for
writing and editing, and is important even if those don't exist - finally,
however, we have some good tools and translators, so this argument is
more convincing today that it was in 1986.
- p. 944-5, subsection on Composition ..., note that
HoTMetaL supports alternative views and
structure-oriented editing