By Eve Maler and Jeanne El Andaloussi
A document type definition (DTD) forms the foundation of an SGML edifice. The goal of Developing SGML Document Type Definitions is to help individuals and organizations develop high-quality, effective DTDs.
We have been involved in a variety of Standard Generalized Markup Language (SGML) projects, including design and development of large DTDs, in computer companies and industry-wide forums. Through these efforts, we've refined a DTD development methodology that can help anyone embarking on SGML projects develop DTDs that meet the goals of those projects. In this book we will describe our methodology and techniques for doing the work of designing, implementing, and documenting DTDs.
We have been involved in a variety of Standard Generalized Markup Language (SGML) projects, including design and development of large DTDs, in computer companies and industry-wide forums. Through these efforts, we've refined a DTD development methodology that can help anyone embarking on SGML projects develop DTDs that meet the goals of those projects. In this book we will describe our methodology and techniques for doing the work of designing, implementing, and documenting DTDs.
Developing SGML Document Type Definitions is intended to serve as a workbook for anyone who is, or might soon be, responsible for developing DTDs. The audience for this book includes people in the following roles:
- Publications and MIS project managers and project leaders responsible for the successful migration to and implementation of SGML-based systems in their environments. If you're a manager in this position, this book will show you how to make the DTD development phase of your SGML project successful through resource and project planning. Part I, “Introduction and Overview” and Part IV, “Documentation, Training, and Support” are meant especially for people in this role.
- Document authors, editors, and other subject matter experts who create, edit, or assemble the targeted information. They are authorities in the required form and content of that information and are typically in the best position to describe many document type requirements. If you're a subject matter expert, this book will show you how to uncover, express, and justify your requirements in clear, usable document analysis reports. Part II, “Document Type Design” is meant especially for people in this role.
- DTD implementors, developers of document-processing applications, and system and database administrators responsible for implementing and maintaining DTDs and the systems and software tools that process the targeted information. If you're a developer, this book will show you how to contribute to the DTD requirements work and how to design and implement DTDs for readability, maintainability, and flexibility. Part III, “DTD Development” and some notes in Chapter 5, Document Type Modeling and Specification are meant especially for people in this role.
If you're embarking on a relatively small SGML project or a pilot for a larger effort, you may find yourself filling all three roles; this is often the case for the “SGML champion” in an organization.