Added by Geoff Sauer on Jul 17, 2004.
Average rating: 3.33/5.00 (n=6, std dev: 1.37)
 


What happens when the software firm you work for decides it will not deliver large printed manuals any more? Then the request comes to put everything online. Six months later, user profiles shift to the World Wide Web and you're asked to deliver HTML. In the future, a database of SGML information chunks may let us deliver anything, any which way. Today, we must devise a system that allows us to 'author once, publish many'. Such as system is crucial for software and hardware documentation. The method I chose was to go from FrameMaker to Acrobat .pdf files to HTML. I wrote in Adobe FrameMaker, then converted to .pdf files with Adobe Acrobat, and converted FrameMaker to HTML files with Quadralay WebWorks Publisher. But while we're waiting for the future, just learning SGML and diving deep into DTDs alone could be a mistake. SGML is a language which sets out structure, and most of us are concerned with content. Enter Information Mapping, or information types of your own devising. Identifying chunks of information such as a procedure for changing the default printer is extremely important. If we then mark each chunk for an index and record its type and title, we've also got the keywords for a future database.
 
  View all four works by Stieren, Carl  
  View all 5 works published by Simware  

Please share your rating/opinion of "Add One Egg, a Cup of Milk, and Stir: Single Source Documentation for Today".
 PoorExcellent 
click this box if you find the link above broken or out-of-date.

Copyright © 2001-17 by the EServer. All rights reserved.Add a Work | Discussion Forum | Habitués