TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> Probably the primary function of these standards is to define
> conventions for exchanging the content between different
> organizations. More recently, they have also focussed on
> issues of managing the content in database applications for
> things like configuration management, versioning, validation,
> etc. Having worked with some of the older military standards
> that had a strong formatting component - I can say that the
> formatting codes made the content more difficult to process -
> and still required substantial work to turn the electronic
> format into a display format.
Bill,
I would agree with you if the standard did not include a major section
about how documentation complying to the standard should be formatted.
But it does, and it does so in a mandatory way. There lies the reason
for my criticism: If it does mandate a special formatting, it should be
backed up with knowledge about how typography and page design works. And
it is not.
However, the DTD itself says nothing about the presenatation of the
documentation - and if it would it would contradict the whole idea of
using a markup language - so there are no formatting codes that obstruct
further processing.
Rumour has it, that ready-made stylesheets (FOSI, DSSSL, or XSL-FO) will
be included in future issues.