* FINALIZING A DTD FOR USE WITH A FRAMEMAKER STRUCTURED APPLICATION *

This article deals with finalizing a Document Type Definition (DTD) created from your FrameMaker Element Definition Document (EDD) (StructureTools > Save As DTD).

This conference is about users. It is about the technical needs that are growing as structured documentation makes major inroads. By combining the ideas of both the technical sides of DITA and XML with the publishing needs of technical communicators that are met by Adobe systems, we feel that this conference provides 2 focused technical days followed by 2 focused publishing and communications days. Monday and Tuesday include technical presentations on DITA and XML, technologies that are storming the gates of technical communications.

For years I have been anxious to implement true single sourcing. As an employee in small tech companies there had never been enough money to do much more than have a style guide. As a contractor for small companies it has been difficult to get them to want more than the status quo using MS Word. I even went as far as learning XML coding eight years ago so that I could be ready for the wave I knew was coming.

This course is for people need to produce content based upon the DITA specification with XMetaL Author. Learn about writing content in a fully structured and easy–to–use environment optimized for producing valid XML and production of multiple outputs for print and online delivery. Acquire hands–on experience with publishing support, including concept, task, and reference topics, DITA maps and relationship tables.

More Info

by Mats Broberg
This article is a description of an XML system for the production of customer documentation. Some time ago, Mats Broberg posted a question to the TECHWR-L email list about XML documentation. In his quest, he found this solution. When he began implementing the system in late 2002, he promised to report back with a detailed description/evaluation in due time, and here it is. Read the article (in PDF format, 560Kb). Used with permission from Technical Communication, the journal of the Society for Technical Communication, Arlington, VA U.S.A.