In the first article of this 3-part series, Flatiron Solutions CTO Eric Severson introduced component-based authoring and described its significant business benefits over document-based authoring. In this second article, Severson explains how component-based authoring actually works, why DITA is the state-of-the-art XML standard of choice and why a CMS is needed to keep track of all the components.
Read the complete article in eWeek.
Archive - Aug 2008
How Component-Based Authoring Works
SeicoDyne GmbH - Your European DITA Specialist
SeicoDyne provides services in the field of technical documentation. We have specialised in assisting companies such as yours in all process steps of product documentation. One of our greatest strengths is the XML documentation standard DITA.
For more information, please see www.seicodyne.com
SeicoDyne GmbH
Eichenstrasse
16
6015 Reussbuehl
Switzerland:
An Overview of the DITA Open Toolkit
jhackos
DITA to XLIFF and back -- we all need to learn what it means
On September 18 and 23, 2008, the OASIS DITA Adoption Technical Committee will hold its first webinars to present the benefits of using DITA in a translation environments.
To learn more and register for these events, see the Events page on dita.xml.org
The DITA Caper
FrameMaker and dita map
Working with FrameMaker, when you use the menu (DITA > New DITA File) and choose a topic type (topic, task, concept, reference), FrameMaker creates a new file that starts with the "dita" element.
If you plan to create small FrameMaker files that will be components of longer files (such as several topics that will later be combined into a chapter file), note that you will need to ensure your component files do not start with the "dita" element.




