The Darwin Information Typing Architecture (DITA) is an XML-based architecture for authoring, producing, and delivering technical information. DITA divides content into small, self-contained topics that can be reused in different deliverables. The extensibility of DITA permits organizations to define specific information structures and still use standard tools to work with them. DITA is often compared against DocBook, a similar XML schema.
#27078
Transforming Documentation from the XML Doctypes Used for the Apache Website to DITA: A Case Study 
A primary factor behind the enormous interest in XML is the support it provides for transforming documents to meet the needs of information-processing applications as well as human readers working with HTML, print, and other presentation media. This case study reviews the issues we confronted, the tools we implemented, and the procedures we adopted to transform a documentation set from one XML document type to another, and from XML to HTML and Adobe PDF. The documentation set for Xalan, the Apache XSL transformer based largely on code donated by Lotus/IBM, is written in XML, using document types shared by the projects on the Apache XML website. To present Xalan reference releases to IBM project groups, the Cambridge Advanced Technology Group has set up build procedures to transform the Xalan XML documentation to DITA, an extensible XML information typing architecture currently under development in IBM. After verifying that the DITA output conforms to its declared document type, the build publishes the DITA documentation set as HTML and as PDF.
Leslie, Donald M. Cover Pages (2004). Articles>Information Design>XML>DITA
#28773
What Managers Need to Know About DITA
Product documentation is expensive--often, much more expensive than it needs to be. With DITA promising savings of 50% in product documentation preparation costs, and 80% in translation costs, managers need to know what DITA is and if it can work for their organization. This white paper distills the information that managers need to know about DITA.
Reichman, Katriel. Method M (2007). Articles>Documentation>Standards>DITA
#29461
The What, Why, How, and Where of DITA
Is DITA right for your organization? This article provides a starting point for your own research on DITA.
Steiner, Rob. Intercom (2007). Articles>Information Design>XML>DITA
#28750
When in Rome: Describing an API in its Own Terms with DITA 
To tame the API beast, a successful description must: be accurate and complete (of course); take the perspective of the programmer who's going to use the class.
Hennum, Erik and Mariana Alupului. STC Proceedings (2006). Presentations>Documentation>Standards>DITA
#30229
Wikis, Docs, and the Reuse Proposition
The Darwin Informaton Typing Architecture (DITA) is an XML-based document format that was designed from the ground up for reuse. It rocks. Content Managment Systms (CMSes) are designed to hold XML data. So in theory, a CMS system that lets you edit like a Wiki would be everything you need. But getting a system like that to work is a pretty tricky proposition.
Armstrong, Eric. Sun Microsystems (2007). Articles>Content Management>XML>DITA
#29458
The XMetaL-DITA group was founded to educate XMetaL users in working with the DITA standard.
#27640
An XML Architecture for Technical Documentation: The Darwin Information Typing Architecture
DITA is an architecture for creating topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways. It is also an architecture for creating new information types and describing new information domains, allowing groups to create very specific, targeted document type definitions using a process called specialization, while at the same time reusing common output transforms and design rules. We discuss several methods that can be used to extend DITA's basic topic types.
Day, Don, Erik Hennum, John Hunt, Michael Priestley, David Schell and Nancy Harrison. WritersUA (2004). Articles>Documentation>XML>DITA
#32083
The Steepest Part of the Learning Curve is Right at the Start
Microsoft has a lot of information on their sites about these products. Unfortunately, I can never find it. I usually only know it’s there when I stumble on it months after I really needed to know it. The steepest part of the learning curve is at the start. Likewise with another program I use occasionally—DITA. DITA is an xml schema used for writing documentation.
Technical Writer (2008). Articles>Documentation>XML>DITA
#32086
I'm not Technical. Why Should I Bother to Learn DocBook or DITA?
First of all, understand that you don’t have to learn it. Every year more and more toolds come out that help place a layer between you and the native XML. In a few years time you will hardly even realise there is XML underneath.
Technical Writer (2006). Articles>Information Design>DocBook>DITA
#32087
XML is the future. You hear it at every conference you go to, in every magazine you pick up, in every article you read on-line. For technical writers, right now that future comes down to two products—DocBook or DITA. But what exactly are they, and which one should you choose? They are schemas for creating XML.
Technical Writer (2006). Articles>Documentation>DocBook>DITA
#32090
Darwin Information Typing Architecture (DITA) Reading List
Here’s a reading list for DITA materials when you’re just getting started. I’ve been fielding some questions via email and IM about DITA lately, and pulled this blog post out of my drafts. I hope it’s helpful.
Gentle, Anne. Just Write Click (2008). Articles>Bibliographies>XML>DITA
#32091
A brief overview for a couple of fellow Austin writers who have asked me recently how and where to get started with DITA.
Gentle, Anne. Just Write Click (2007). Articles>Information Design>XML>DITA
#32098
Using DITA to Develop a New Information Architecture at BMC Software
The need for us to customize BSM solutions by integrating different software solutions, combined with the maturation of tools for XML-based authoring, make this an ideal time to implement a new information development strategy. After researching materials about content management and studying success stories from companies who have implemented structured authoring, we launched a pilot project.
Rockley, Ann. Rockley Group, The (2007). Articles>Content Management>Case Studies>DITA
#32180
Authoring in XML -- Why Start?
As techcom professionals, we have been talking about authoring in XML for a very long time. At first, it was a lot of hype about a format that required major programming skills and had zero tools’ support, but that is now changing. Today, there are hundreds, if not thousands, of tools that support XML and a standard called DITA that is in constant development to support content publishing for different industries. As a result, more and more companies seem to be embracing this content format.If you are a writer or techcom manager who is encouraging your company to make this change, then what do you need to know to prepare?
Stuhlemmer, Barbara. TechCom Manager (2008). Articles>Writing>XML>DITA
#32183
Calculating the Financial Impact of DITA for Translation
Success in a global marketplace requires translating content into multiple languages. Moving to a topic-based XML architecture, such as the Darwin Information Typing Architecture (DITA), can help you control the translation process and save money.
Swope, Amber. TechCom Manager (2008). Articles>Management>Translation>DITA
#32227
In the past few years, we have implemented both DITA-based and custom XML solutions for our customers. Given the right set of circumstances, DITA provides an excellent foundation for structured content. But I seem to be in significant disagreement with DITA advocates about how often the "right set of circumstances" is present.
O'Keefe, Sarah S. Carolina Communique (2008). Articles>Documentation>XML>DITA
#32365
Linking DITA Topics Through Relationship Tables
DITA provides a powerful means of linking using relationship tables. The benefit of using a relationship table is the ability to create and maintain links in one place with the map rather than in the topics. Links can be created both between topics of the same information type and between topics of different information types that are not directly related through parent/child relationships. Therefore, the best practice for linking in DITA is to use a relationship table within a map.
Bruski, Kylene. Center for Information-Development Management (2005). Articles>Information Design>XML>DITA
#32366
Specializing Topic Types in DITA
The Darwin Information Typing Architecture (DITA) provides a way for documentation authors and architects to create collections of typed topics that can be easily assembled into various delivery contexts. Topic specialization is the process by which authors and architects can define topic types, while maintaining compatibility with existing style sheets, transforms, and processes. The new topic types are defined as an extension, or delta, relative to an existing topic type, thereby reducing the work necessary to define and maintain the new type.
Priestley, Michael. IBM (2001). Articles>Information Design>XML>DITA
#32367
Migrating HTML to DITA, Part 1: Simple Steps to Move from HTML to DITA
The Darwin Information Typing Architecture (DITA) has emerged as a standard topic-oriented document architecture. DITA holds many advantages over information authored directly in HTML, including better reuse, easily changed presentation styles, and easy single sourcing. This article, the first of two parts, explains how to get a quick start with DITA using HTML topics that are already available. It shows you how to use the provided XSLT transform to do the migration, and examines what is needed to ensure quality results.
Anderson, Robert, Don Day and Erik Hennum. IBM (2005). Articles>Information Design>XML>DITA
#32368
Why Use DITA to Produce HTML Deliverables?
The Darwin Information Typing Architecture (DITA) is an XML-based format for structuring and authoring technical content. This article explores advantages DITA provides for producing HTML content -- including easy global changes, portability through standards, superior linking and Web management, conditional processing, content and design reuse, and better writing through focused content. DITA consolidates all of the benefits in a consistent, overall information architecture that can evolve and grow along with your product information needs and delivery modes, and with the evolution of standard tools for delivering XML as the presentation mechanism.
Hunt, John, Don Day, Erik Hennum, Michael Priestley and Dave Schell. IBM (2005). Articles>Information Design>HTML>DITA
#32369
Migrating HTML to DITA, Part 2: Extend the Migration for More Robust Results
The Darwin Information Typing Architecture (DITA) holds many advantages over information authored directly in HTML, including better reuse, easily changed presentation styles, and easy single sourcing. In Part 2 of this two-part series on how to quickly migrate HTML topics to DITA, the author explains the details of migration, and shows you how to override parts of this process for ideal results.
Anderson, Robert. IBM (2005). Articles>Information Design>HTML>DITA
#32792
Introduces readers to the major DITA tools for editing, content and translation management, and publishing.
#32793
DITA and the Technical Communicator 
How will DITA conversion affect your work? Sigman shares what she's learned from her own survey of technical communicators.
Sigman, Christine Marini. Intercom (2008). Articles>TC>XML>DITA
#32794
DITA is known for the rigidity of its structure, but technical communicators have opportunities to adapt it to their content through specialization, a term that refers to the customization of DITA structures.
Sliwinski, Larissa. Intercom (2008). Articles>Information Design>XML>DITA
#32795
The Organization for the Advancement of Structured Information Standards (OASIS) has formed a new committee for encouraging the use of DITA in all areas of business. Readers can learn how to work with their organization to make the sharing of DITA content possible.
Manning, Steve. Intercom (2008). Articles>Business Communication>XML>DITA
