Abstract
It's a rare DTD that never gets revised. But what happens after numerous revision cycles performed by different authors? Sometimes, the answer is confusion.
This presentation will describe the process which was used to reengineer a DTD for publishing textbooks. It will cover:
- The methods which were used to analyze the existing DTD code
- The tools and report formats which were used to support analysis
- The principles which were used to drive design and modularization decisions
- The documentation conventions which were used to manage and document the revision process
- The starting point for a DTD prettyprinter
- The coding standards which were used to anticipate future changes
Keywords
![]() ![]() |
Design & Development by deepX Ltd. 2002 |