Archive
Installing the DITA Open Toolkit
Note: this page has been moved to http://dita-ot.sourceforge.net/latest/.
You can download and install the DITA Open Toolkit from SourceForge.net. Before you download, you should read a discription of the various DITA-OT Packages that are available.
Source Forge has a Home Page for the Open Toolkit, although most current user oriented information is located here on dita.xml.org.
DITA architectural specification 1.1
The official specification of the DITA architecture is available from OASIS.
OASIS DITA Version 1.1. Architectural Specification
The architectural reference defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining and extending document types using a process called specialization.
The specification consists of:
DITA language reference 1.1
The official specification of the DITA language is available from OASIS.
OASIS DITA Version 1.1. Language Specification
The language reference describes the elements that comprise the topic DTD and its initial, information-typed descendents: concept, reference, task, and glossentry. It also describes the DITA map DTD and its current specialization (bookmap), as well as various topic and map based DITA domains.
Setting up stylesheets and a publishing system
The DITA Open Toolkit is a modest publishing system. The Toolkit transforms DITA content (maps and topics) into publishing deliverable formats for web (XHTML), print (PDF), and Help (CHM and Eclipse). Your output files are simply generated in your file system. It is up to you to move them to your website, or into your print publishing process.
About storing and managing content
DITA files can simply be kept in a file system, where it is important to observe best practices in naming files and file folders.
They can also be stored in a content management system (CMS). Some CMS's store their files in a file system, but most keep the files in a database. Since DITA files are XML files, there may be an advantage to a CMS that uses a native XML database, though performance claims have been made for ordinary relational databases.