OASIS, the international e-business standards consortium, announced that its members approved the DITA version 1.0 as an OASIS Standard, a status that signifies the highest level of ratification. Arbortext, BMC Software, IBM, Idiom, Innodata Isogen, Intel, Nokia, Oracle, Sun Microsystems, the U.S. Department of Defense, and others participated in defining this XML architecture for publishing.
Archive - 2006
Members Approve DITA as OASIS Standard
Benefits of using DITA
Why use DITA?
by France Baril
Topic-based DITA offers flexibility in content organization
DITA is a topic-based architecture. It allows you to order, reorder and nest topics to create any kind of information product.
DITA's modularity allows for reuse
Topics can be used in more than one deliverable at once, independently from other topics.
Working with content references (conref)
Content referencing (conref) is a convenient DITA mechanism for reuse of content from other topics or maps. A fragment of content in one topic or map can be pulled by reference into any other topic or map where the content is allowed. To create the reference, start by creating an empty element of the type that you want to pull in, and then use the element's conref attribute to provide the target's location.
The architectural specification describes content referencing at:
Working with conditional text
Conditional processing, also known as profiling, is the filtering or flagging of information based on processing-time criteria. The filtering mechanism first matches against the criteria, and then takes a specified action.
DITA provides several built-in attributes to hold the values for filter criteria for an element. These are:
Introduction to specialization
Specialization is the process by which new designs are created based on existing designs, allowing new kinds of content to be processed using existing processing rules.
It is the means by which the standard DITA language may be extended for new semantic or structural roles.
Specialization allows you to define new kinds of information (new structural types or new domains of information), while reusing as much of existing design and code as possible, and minimizing or eliminating the costs of interchange, migration, and maintenance.