DITA: A Powerful and Flexible Architecture for Technical Content

20 min readFeb 22, 2024

“The future is not something that happens to us, but something we create.”

— Vivek

Have you ever wondered how to create, manage, and deliver technical information consistently, efficiently, and scalable? How to reuse content across different documents, formats, and languages? How do you customize and adapt your content to meet your users’ specific needs and preferences? If you have, you might be interested in learning about DITA or Darwin Information Typing Architecture.

DITA is a standard for creating, structuring, and delivering technical information in different forms, such as web pages, PDFs, eBooks, and help systems. DITA is named after Charles Darwin, the famous naturalist and biologist who proposed the theory of evolution. Just like Darwin’s theory, DITA is based on the idea of adaptation and specialization, allowing users to modify and extend the existing document types to suit their content requirements and scenarios.

DITA offers many benefits for technical communicators, such as:

Content reuse: DITA enables users to create topics, which are small, self-contained units of information that can be reused across different documents and outputs. This reduces duplication, improves consistency, and saves time and effort.
Information typing: DITA allows users to classify topics into different types, such as task, concept, reference, glossary entry, and troubleshooting. This helps users to organize and structure their content according to the purpose and nature of the information, and to apply appropriate style and formatting rules.
Output flexibility: DITA supports multiple output formats and delivery methods, such as HTML, PDF, EPUB, CHM, and more. Users can create maps, which are collections of topics that define the structure and sequence of a publication, and use them to generate different outputs from the same source content. Users can also customize the appearance and behavior of the outputs using various mechanisms, such as DITA Open Toolkit, plugins, and XSLT transformations.
Localization and translation: DITA facilitates the localization and translation of content into different languages and cultures, by separating the content from the presentation, and by using standard XML and Unicode technologies. Users can also leverage the reuse and specialization features of DITA to create and manage multilingual content more efficiently and effectively.

If you are curious to know more about DITA, and how it can help you create, manage, and deliver technical content in a powerful and flexible way, then keep reading this article. We will explain the key concepts and features of DITA, and provide some examples and resources to help you get started with DITA.

DITA Topics

One of the core concepts of DITA is the topic. A topic is a small, self-contained unit of information that can be reused across different documents and outputs. A topic typically covers a single subject or answers a single question, and has a clear title, a short introduction, and a body. A topic can also have other elements, such as related links, images, tables, lists, notes, and more.

Topics are the building blocks of DITA content, and they enable users to create modular and reusable content that can be assembled and delivered in various ways. Topics are also the basis for information typing, which is another key concept of DITA.

Information typing is the process of classifying topics into different types, based on the purpose and nature of the information they contain. DITA defines five specialized topic types, which are:

Task: A task topic describes how to perform a specific procedure or activity, such as installing a software, changing a setting, or troubleshooting a problem. A task topic typically consists of a title, a short description, a list of prerequisites, a series of steps, and a list of expected results or outcomes. A task topic can also have other elements, such as substeps, choices, options, examples, tips, warnings, and more.
Concept: A concept topic explains a general idea, principle, or theory, such as what a software does, how a system works, or why a feature is useful. A concept topic typically consists of a title, a short introduction, and a body. A concept topic can also have other elements, such as definitions, examples, diagrams, tables, lists, notes, and more.
Reference: A reference topic provides factual and detailed information about a specific subject, such as a list of commands, parameters, options, values, or specifications. A reference topic typically consists of a title, a short introduction, and a body. A reference topic can also have other elements, such as tables, lists, notes, and more.
Glossary Entry: A glossary entry topic defines a term or an acronym that is used in the content, such as DITA, XML, or PDF. A glossary entry topic typically consists of a title, which is the term or the acronym, and a body, which is the definition. A glossary entry topic can also have other elements, such as synonyms, antonyms, examples, notes, and more.
Troubleshooting: A troubleshooting topic provides information on how to identify and resolve a common issue or error, such as a system crash, a network failure, or a performance problem. A troubleshooting topic typically consists of a title, which is the name or the description of the issue or the error, a short introduction, and a body. The body can have different elements, such as causes, symptoms, solutions, workarounds, tips, warnings, and more.

These topic types are designed to cover the most common types of information that users need and expect from technical content. They also help users to organize and structure their content in a consistent and logical way, and to apply appropriate style and formatting rules for each type of information. For example, a task topic should use imperative verbs, numbered lists, and icons, while a concept topic should use declarative sentences, paragraphs, and headings.

Here are some examples of topics in DITA, using the different topic types:

Task: How to create a DITA topic

This topic describes how to create a DITA topic using an XML editor.

Prerequisites

You have installed an XML editor that supports DITA, such as Oxygen XML Editor, XMetal, or Arbortext Editor.
You have created a folder to store your DITA files.

Steps

Open your XML editor and create a new file.
Select the DITA topic type that you want to create, such as task, concept, reference, glossary entry, or troubleshooting.
Enter a title for your topic in the <title> element.
Enter a short introduction for your topic in the <shortdesc> element.
Enter the body of your topic in the <body> element, using the appropriate elements and attributes for your topic type.
Save your file with the .dita extension in the folder that you created.

Expected results

You have created a DITA topic that conforms to the DITA standard and the selected topic type.
You can reuse your topic across different documents and outputs, by using DITA maps.

Concept: What is XML

This topic explains what XML is, and why it is used for creating and exchanging data.

XML stands for Extensible Markup Language. It is a standard for creating and exchanging data in a structured and readable way. XML is based on the idea of tags, which are keywords enclosed in angle brackets, such as <name>, <address>, or <price>. Tags are used to mark up the data, and to define the structure and the meaning of the data.

XML is extensible, which means that users can create and use their own tags, according to their own needs and preferences. XML is also flexible, which means that users can create and use different types of data, such as text, numbers, images, audio, video, and more. XML is also portable, which means that users can exchange and share data across different platforms, applications, and devices, without losing the structure and the meaning of the data.

XML is widely used for creating and exchanging data in various domains and scenarios, such as web development, e-commerce, e-learning, e-government, and more. XML is also the basis for many other standards and technologies, such as HTML, XHTML, RSS, SVG, SOAP, and more.

One of the standards that is based on XML is DITA, or Darwin Information Typing Architecture. DITA is a standard for creating, structuring, and delivering technical information in different forms, such as web pages, PDFs, eBooks, help systems, and more. DITA uses XML to define the document types, the elements, the attributes, and the rules for creating and processing technical content. DITA also uses XML to enable content reuse, information typing, output flexibility, and localization and translation.

Reference: DITA elements and attributes

This topic provides a list of some of the common elements and attributes that are used in DITA topics.

Elements

<topic>: The root element of a DITA topic. It contains the title, a short description, and the topic’s body. It also has an attribute called id, which is used to identify the topic uniquely.
<title>: The element that contains the title of the topic. It is a required element for every topic.
<shortdesc>: The element that contains a short introduction to the topic. It is an optional element, but it is recommended to use it for every topic, as it helps users understand the purpose and scope of the topic. The short description can also be used as a summary or a teaser for the topic in different outputs, such as search results, tables of contents, or tooltips.
<body>: The element that contains the body of the topic. It can have different child elements, depending on the topic type. For example, a task topic can have <steps>, <prereq>, and <result> elements, while a concept topic can have <section>, <p>, and <fig> elements.
<related-links>: The element that contains links to other topics or resources that are related to the current topic. It is an optional element, but it is useful to provide additional information or guidance for the users. The related links can be grouped into different categories, such as <linklist>, <collection-type>, and <topicref>.
<prolog>: The element that contains metadata about the topic, such as the author, the date, the keywords, the audience, the product, and more. It is an optional element, but it can help users to find and filter the content, and to track the changes and updates of the content. The prolog can have different child elements, such as <author>, <source>, <critdates>, <metadata>, and <permissions>.

Attributes

id: The attribute that is used to identify the topic uniquely. It is a required attribute for every topic, and it must have a valid XML ID value, which is a string that starts with a letter or an underscore, and contains only letters, digits, hyphens, underscores, and periods. For example, id="task-install-software".
outputclass: The attribute that is used to specify the style and formatting of the topic or the element. It is an optional attribute, but it can help users to customize and adapt the appearance and behavior of the content for different output types and languages. The outputclass attribute can have different values, depending on the output format and the mechanism that is used to process the content. For example, outputclass="note warning" or outputclass="language-fr".
domains: The attribute that is used to declare the domains that are used in the topic. A domain is a set of elements and attributes that are specialized from the base topic types, to provide additional functionality and semantics for a specific domain or industry, such as software, hardware, learning, or medical. DITA provides some predefined domains, such as the software domain, the user interface domain, the hazard statement domain, and the learning domain. Users can also create and use their own domains, by using the specialization and inheritance features of DITA. The domains attribute is a required attribute for every topic, and it must have a valid DITAVAL value, which is a string that lists the domains that are used in the topic, separated by spaces. For example, domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)".
specialization: The attribute that indicates the specialization hierarchy of the topic or the element. It is an optional attribute, but it is used to show the inheritance and the extension of the document types, the elements, and the attributes. It is a space-separated list of qualified names, such as (topic concept learning2Concept).
<topicref>: The element that references another topic or a map. It is used to create links, to reuse topics, and to define the structure and the sequence of a publication. It has several attributes, such as href, which specifies the location of the referenced topic or map, navtitle, which provides a navigation title for the referenced topic or map, type, which indicates the type of the referenced topic or map, and scope, which indicates whether the referenced topic or map is local or external.
<collection-type>: The element that defines the type of a collection of topics or maps. It is used to group related topics or maps, and to specify how they should be processed and presented. It can have different values, such as sequence, which indicates that the topics or maps should be processed and presented in the order they appear, choice, which indicates that the user can choose one of the topics or maps, or family, which indicates that the topics or maps are related but not ordered or mutually exclusive.
<linklist>: The element that contains a list of links to other topics or resources. It is used to provide additional information or guidance for the users. It can have different child elements, such as <link> or <linkinfo>, which provide the link text and the link destination, and <linktext> or <desc>, which provide the link description or the link summary.
<xref>: The element that creates a cross-reference to another topic, element, or resource. It is used to create links within or across topics or maps, and to provide context or navigation for the users. It has several attributes, such as href, which specifies the location of the target topic, element, or resource, format, which indicates the format of the target topic, element, or resource, scope, which indicates whether the target topic, element, or resource is local or external, and type, which indicates the type of the target topic, element, or resource.

These are some of the common elements and attributes that are used in DITA topics. There are many more elements and attributes that are defined by the DITA standard, and by the different domains and specializations. You can find more information about them in the DITA specification, the DITA reference, and the DITA best practices.

DITA Maps

Another key concept of DITA is the map. A map is a collection of topics that defines the structure and the sequence of a publication, such as a book, a manual, a guide, or a help system. A map can also contain links to other resources, such as images, videos, or web pages. A map is created using the <map> element, which can have different child elements, such as <title>, <topicref>, <collection-type>, <reltable>, and more.

Maps are the glue that holds DITA topics together, and they enable users to organize and link topics into coherent and meaningful publications. Maps also support multiple output formats and delivery methods, such as HTML, PDF, EPUB, CHM, and more. Users can create different maps for different outputs, and use them to generate the outputs from the same source topics. Users can also customize the appearance and the behavior of the outputs using various mechanisms, such as DITA Open Toolkit, plugins, and XSLT transformations.

DITA defines different types of maps, which are:

Base map: The base map is the default map type in DITA. It is used to create general-purpose publications, such as books, manuals, guides, or help systems. It can contain any topic type, and any map element, except for the <bookmap> element.
Book map: The book map is a specialized map type in DITA. It is used to create book-like publications, such as PDFs or eBooks. It can contain only the topic types that are suitable for books, such as concept, task, reference, glossary entry, and troubleshooting. It can also contain specific map elements, such as <frontmatter>, <backmatter>, <chapter>, <appendix>, and more.
Subject scheme map: The subject scheme map is a special map type in DITA. It is used to define the values and the relationships of the attributes that are used in the topics and the maps. It can contain elements, such as <subjectdef>, <subjecthead>, <subjectscheme>, and more. It can also be referenced by other maps, using the <subjectscheme> element.
Learning map: The learning map is a specialized map type in DITA. It is used to create learning and training publications, such as courses, modules, lessons, or assessments. It can contain only the topic types that are related to learning, such as learning overview, learning content, learning summary, learning assessment, and more. It can also contain specific map elements, such as <learningPlan>, <learningGroup>, <learningObject>, and more.

Here are some examples of maps in DITA, using the different map types:

Base map: User guide for a software product

This map defines the structure and the sequence of a user guide for a software product. It contains topics of different types, such as concept, task, reference, glossary entry, and troubleshooting. It also contains links to other resources, such as images, videos, or web pages.

User Guide for Software Product

<map id="user-guide">
  <title>User Guide for Software Product</title>
  <topicref href="introduction.dita" type="concept"/>
  <topicref href="installation.dita" type="task"/>
  <topicref href="overview.dita" type="concept"/>
  <topicref href="features.dita" type="concept"/>
  <topicref href="how-to.dita" type="task"/>
  <topicref href="commands.dita" type="reference"/>
  <topicref href="settings.dita" type="reference"/>
  <topicref href="glossary.dita" type="glossary"/>
  <topicref href="troubleshooting.dita" type="troubleshooting"/>
  <topicref href="https://www.software.com/support" format="html" scope="external" type="link"/>
  <topicref href="https://www.youtube.com/watch?v=123456" format="html" scope="external" type="link"/>
  <topicref href="logo.png" format="image" scope="local" type="resource"/>
</map>

Book map: User manual for a hardware device

This map defines the structure and the sequence of a user manual for a hardware device. It contains topics of different types, such as concept, task, reference, glossary entry, and troubleshooting. It also contains specific map elements, such as front matter, back matter, chapter, and appendix.

User Manual for Hardware Device UM-HD-001 John Smith Hardware Inc. 2024–02–22 “>

<bookmap id="user-manual">
  <booktitle>
    <mainbooktitle>User Manual for Hardware Device</mainbooktitle>
    <bookid>UM-HD-001</bookid>
    <author>John Smith</author>
    <publisher>Hardware Inc.</publisher>
    <pubdate>2024-02-22</pubdate>
  </booktitle>
  <frontmatter>
    <topicref href="title-page.dita" type="titlepage"/>
    <topicref href="table-of-contents.dita" type="toc"/>
    <topicref href="preface.dita" type="preface"/>
    <topicref href="acknowledgments.dita" type="acknowledgment"/>
    <topicref href="abstract.dita" type="abstract"/>
  </frontmatter>
  <chapter href="introduction.dita" type="concept"/>
  <chapter href="installation.dita" type="task"/>
  <chapter href="overview.dita" type="concept"/>
  <chapter href="features.dita" type="concept"/>
  <chapter href="how-to.dita" type="task"/>
  <chapter href="commands.dita" type="reference"/>
  <chapter href="settings.dita" type="reference"/>
  <backmatter>
    <appendix href="glossary.dita" type="glossary"/>
    <appendix href="troubleshooting.dita" type="troubleshooting"/>
    <appendix href="specifications.dita" type="reference"/>
    <appendix href="warranty.dita" type="reference"/>
    <appendix href="contact.dita" type="reference"/>
    <topicref href="index.dita" type="index"/>
    <topicref href="colophon.dita" type="colophon"/>
  </backmatter>
</bookmap>

Subject scheme map: Values and relationships of attributes

This map defines the values and the relationships of the attributes that are used in the topics and the maps. It contains elements, such as subjectdef, subjecthead, and subjectscheme. It can be referenced by other maps, using the subjectscheme element.

Values and relationships of attributes audience beginner intermediate advanced status draft review final product software hardware “>

<subjectScheme id="attributes">
  <title>Values and relationships of attributes</title>
  <subjectDef keys="audience" type="props">
    <subjectHead>audience</subjectHead>
    <subjectDef keys="beginner" type="value">
      <subjectHead>beginner</subjectHead>
    </subjectDef>
    <subjectDef keys="intermediate" type="value">
      <subjectHead>intermediate</subjectHead>
    </subjectDef>
    <subjectDef keys="advanced" type="value">
      <subjectHead>advanced</subjectHead>
    </subjectDef>
  </subjectDef>
  <subjectDef keys="status" type="props">
    <subjectHead>status</subjectHead>
    <subjectDef keys="draft" type="value">
      <subjectHead>draft</subjectHead>
    </subjectDef>
    <subjectDef keys="review" type="value">
      <subjectHead>review</subjectHead>
    </subjectDef>
    <subjectDef keys="final" type="value">
      <subjectHead>final</subjectHead>
    </subjectDef>
  </subjectDef>
  <subjectDef keys="product" type="props">
    <subjectHead>product</subjectHead>
    <subjectDef keys="software" type="value">
      <subjectHead>software</subjectHead>
    </subjectDef>
    <subjectDef keys="hardware" type="value">
      <subjectHead>hardware</subjectHead>
    </subjectDef>
  </subjectDef>
</subjectScheme>

Learning map: Course on DITA

This map defines the structure and the sequence of a course on DITA. It contains topics of different types, such as learning overview, learning content, learning summary, and learning assessment. It also contains specific map elements, such as learningPlan, learningGroup, and learningObject.

Course on DITA Module 1: Introduction to DITA Module 2: DITA Topics

<learningMap id="course">
  <title>Course on DITA</title>
  <learningPlan href="course-overview.dita" type="learningOverview"/>
  <learningGroup>
    <title>Module 1: Introduction to DITA</title>
    <learningObject href="module-1-overview.dita" type="learningOverview"/>
    <learningObject href="module-1-content-1.dita" type="learningContent"/>
    <learningObject href="module-1-content-2.dita" type="learningContent"/>
    <learningObject href="module-1-summary.dita" type="learningSummary"/>
    <learningObject href="module-1-assessment.dita" type="learningAssessment"/>
  </learningGroup>
  <learningGroup>
    <title>Module 2: DITA Topics</title>
    <learningObject href="module-2-overview.dita" type="learningOverview"/>
    <learningObject href="module-2-content-1.dita" type="learningContent<learningObject href="module-2-content-2.dita" type="learningContent"/>
    <learningObject href="module-2-content-3.dita" type="learningContent"/>
    <learningObject href="module-2-content-4.dita" type="learningContent"/>
    <learningObject href="module-2-content-5.dita" type="learningContent"/>
    <learningObject href="module-2-summary.dita" type="learningSummary"/>
    <learningObject href="module-2-assessment.dita" type="learningAssessment"/>
  </learningGroup>
  <learningGroup>
    <title>Module 3: DITA Maps</title>
    <learningObject href="module-3-overview.dita" type="learningOverview"/>
    <learningObject href="module-3-content-1.dita" type="learningContent"/>
    <learningObject href="module-3-content-2.dita" type="learningContent"/>
    <learningObject href="module-3-content-3.dita" type="learningContent"/>
    <learningObject href="module-3-content-4.dita" type="learningContent"/>
    <learningObject href="module-3-summary.dita" type="learningSummary"/>
    <learningObject href="module-3-assessment.dita" type="learningAssessment"/>
  </learningGroup>
  <learningGroup>
    <title>Module 4: DITA Specialization and Customization</title>
    <learningObject href="module-4-overview.dita" type="learningOverview"/>
    <learningObject href="module-4-content-1.dita" type="learningContent"/>
    <learningObject href="module-4-content-2.dita" type="learningContent"/>
    <learningObject href="module-4-content-3.dita" type="learningContent"/>
    <learningObject href="module-4-content-4.dita" type="learningContent"/>
    <learningObject href="module-4-summary.dita" type="learningSummary"/>
    <learningObject href="module-4-assessment.dita" type="learningAssessment"/>
  </learningGroup>
  <learningSummary href="course-summary.dita" type="learningSummary"/>
  <learningAssessment href="course-assessment.dita" type="learningAssessment"/>
</learningMap>

DITA Specialization and Customization

One of the most powerful and flexible features of DITA is the ability to specialize and customize the existing document types, elements, and attributes to meet the specific content needs and requirements of different domains, industries, and scenarios. DITA specialization and customization are based on the principles of inheritance and extension, which allow users to create new document types, elements, and attributes that are derived from the existing ones, and that retain the properties and the functionality of the parent types, elements, and attributes.

DITA specialization and customization can be done at different levels, such as:

Domain specialization: Domain specialization is the process of creating new elements and attributes that are specific to a certain domain, such as learning, machinery, software, or healthcare. Domain specialization can be done by using the <specialize> element, which defines the name, the parent, and the description of the new element or attribute. Domain specialization can also be done by using the <constraint> element, which defines the restrictions or the modifications of the existing element or attribute. Domain specialization can be declared in the topics and the maps, by using the domains attribute, which specifies the domains that are used in the content.
Topic specialization: Topic specialization is the process of creating new topic types that are derived from the existing topic types, such as task, concept, reference, glossary entry, or troubleshooting. Topic specialization can be done by using the <topicType> element, which defines the name, the parent, the description, and the content model of the new topic type. Topic specialization can also be done by using the <topicref> element, which references the new topic type. Topic specialization can be indicated in the topics, by using the specialization attribute, which specifies the specialization hierarchy of the topic type.
Map specialization: Map specialization is the process of creating new map types that are derived from the existing map types, such as base map, book map, subject scheme map, or learning map. Map specialization can be done by using the <mapType> element, which defines the name, the parent, the description, and the content model of the new map type. Map specialization can also be done by using the <mapref> element, which references the new map type. Map specialization can be indicated in the maps, by using the specialization attribute, which specifies the specialization hierarchy of the map type.

DITA specialization and customization enable users to create and use content that is more relevant, accurate, and consistent for their specific domains, industries, and scenarios. They also enable users to leverage the reuse and output features of DITA, as the specialized and customized document types, elements, and attributes are compatible with the existing ones, and can be processed and delivered in the same way.

Here are some examples of DITA specialization and customization, using the different levels and mechanisms:

Domain specialization: Learning domain

This example shows how to create and use new elements and attributes that are specific to the learning domain, such as learning objectives, learning interactions, and learning metadata. The learning domain is defined by the <specialize> and <constraint> elements, and declared by the domains attribute.

<!-- This is the definition of the learning domain -->
<specialize id="learning-domain">
  <title>Learning domain</title>
  <shortdesc>This domain defines the elements and attributes that are specific to the learning domain.</shortdesc>
  <specialize id="learningObjectives" type="element" parent="section">
    <title>learningObjectives</title>
    <shortdesc>This element contains the learning objectives for a learning topic or a learning object.</shortdesc>
  </specialize>
  <specialize id="learningInteractionBase2-d" type="domain">
    <title>learningInteractionBase2-d</title>
    <shortdesc>This domain defines the elements and attributes that are used to create learning interactions, such as quizzes, exercises, or simulations.</shortdesc>
    <specialize id="learningInteractionBase" type="element" parent="fig">
      <title>learningInteractionBase</title>
      <shortdesc>This element is the base element for all learning interactions.</shortdesc>
    </specialize>
    <specialize id="question" type="element" parent="p">
      <title>question</title>
      <shortdesc>This element contains the question for a learning interaction.</shortdesc>
    </specialize>
    <specialize id="answer" type="element" parent="li">
      <title>answer</title>
      <shortdesc>This element contains the answer for a learning interaction.</shortdesc>
      <specialize id="correct" type="attribute" parent="props" values="yes no">
        <title>correct</title>
        <shortdesc>This attribute indicates whether the answer is correct or not.</shortdesc>
      </specialize>
    </specialize>
    <specialize id="feedback" type="element" parent="note">
      <title>feedback</title>
      <shortdesc>This element contains the feedback for a learning interaction.</shortdesc>
    </specialize>
  </specialize>
  <constraint id="learningmeta-d" type="domain">
    <title>learningmeta-d</title>
    <shortdesc>This domain defines the restrictions and the modifications of the metadata elements and attributes for the learning domain.</shortdesc>
    <constraint id="audience" type="attribute" parent="props" values="beginner intermediate advanced">
      <title>audience</title>
      <shortdesc>This attribute specifies the level of the audience for the learning content.</shortdesc>
    </constraint>
    <constraint id="duration" type="attribute" parent="props" values="time">
      <title>duration</title>
      <shortdesc>This attribute specifies the duration of the learning content.</shortdesc>
    </constraint>
    <constraint id="learningRole" type="attribute" parent="props" values="learner instructor">
      <title>learningRole</title>
      <shortdesc>This attribute specifies the role of the user for the learning content.</shortdesc>
    </constraint>
  </constraint>
</specialize>

<!-- This is the use of the learning domain -->
<topic id="learning-topic" domains="(topic learningInteractionBase2-d) (topic learningmeta-d)">
  <title>Learning topic</title>
  <shortdesc>This topic demonstrates the use of the learning domain.</shortdesc>
  <prolog>
    <metadata>
      <audience>beginner</audience>
      <duration>10 minutes</duration>
      <learningRole>learner</learningRole>
    </metadata>
  </prolog>
  <body>
    <section id="learning-objectives">
      <title>Learning objectives</title>
      <learningObjectives>
        <p>After completing this topic, you will be able to:</p>
        <ul>
          <li>Define the learning domain</li>
          <li>Use the learning domain elements and attributes</li>
          <li>Create a learning interaction</li>
        </ul>
      </learningObjectives>
    </section>
    <section id="learning-content">
      <title>Learning content</title>
      <p>The learning domain is a domain specialization that defines the elements and attributes that are specific to the learning domain, such as learning objectives, learning interactions, and learning metadata.</p>
      <p>The learning domain elements and attributes are used to create and structure learning content, such as courses, modules, lessons, or assessments.</p>
      <p>A learning interaction is a learning domain element that is used to create a quiz, an exercise, or a simulation that tests the knowledge or the skill of the learner.</p>
    </section>
    <section id="learning-interaction">
      <title>Learning interaction</title>
      <learningInteractionBase id="learning-quiz" outputclass="multiple-choice">
        <title>Learning quiz</title>
        <question>What is the name of the base element for all learning interactions?</question>
        <ul>
          <li><answer correct="no">learningObjectives</answer></li>
          <li><answer correct="no">learningInteraction</answer></li>
          <li><answer correct="yes">learningInteractionBase</answer></li>
          <li><answer correct="no">learningInteractionType</answer></li>
        </ul>
        <feedback outputclass="correct">Correct! The name of the base element for all learning interactions is learningInteractionBase.</feedback>
        <feedback outputclass="incorrect">Incorrect. The name of the base element for all learning interactions is learningInteractionBase.</feedback>
      </learningInteractionBase>
    </section>
  </body>
</topic>

DITA Tools and Resources

To create, manage, and deliver DITA content, you need various tools and resources that support DITA, such as:

Authoring tools: Authoring tools are software applications that allow you to create and edit DITA topics and maps, using a graphical user interface or a source code editor. Some examples of authoring tools are Oxygen XML Editor, XMetal, Arbortext Editor, and FrameMaker.
Editors: Editors are software applications that allow you to view and modify the source code of DITA topics and maps, using a text editor or an XML editor. Some examples of editors are Notepad++, Sublime Text, Visual Studio Code, and XMLSpy.
Validators: Validators are software applications or services that allow you to check the validity and the quality of DITA topics and maps, using XML schemas, DTDs, Schematrons, or other rules. Some examples of validators are DITA Validator, DITA Checker, DITA QA, and DITA Lint.
Processors: Processors are software applications or services that allow you to transform and publish DITA topics and maps into different output formats and delivery methods, using XSLT, XSL-FO, Ant, or other technologies. Some examples of processors are DITA Open Toolkit, DITA-OT, DITA for Publishers, and easyDITA.
Converters: Converters are software applications or services that allow you to convert DITA topics and maps into or from other formats, such as HTML, PDF, EPUB, Word, Markdown, or AsciiDoc. Some examples of converters are DITA2Go, DITA2HTML, DITA2PDF, and DITA2Word.
Repositories: Repositories are software applications or services that allow you to store, manage, and share DITA topics and maps, using a file system, a database, a content management system, or a cloud service. Some examples of repositories are GitHub, GitLab, Bitbucket, DITA CMS, and DITAToo.

Conclusion

In this article, we have introduced and explained DITA, or Darwin Information Typing Architecture, a standard for creating, structuring, and delivering technical information in different forms. We have covered the key concepts and features of DITA, such as topics, maps, specialization, customization, and more. We have also provided some examples and resources to help you get started with DITA.

DITA is a powerful and flexible architecture for technical content, that offers many benefits for technical communicators, such as content reuse, information typing, output flexibility, and localization and translation. DITA also supports various tools and resources that enable users to create, manage, and deliver DITA content in an efficient and effective way.

If you are interested in learning more about DITA, or if you need any assistance with DITA, please feel free to contact us. We are professionals in this field, and do follow physicsalert.com .