Home
Language reference: All-inclusive edition
The language reference portion of the DITA specification contains a topic for each DITA element. The topic defines the element, its inheritance hierarchy, and provides examples of usage. This portion of the DITA specification also includes information about DITA attributes.
Learning and training elements
Elements in the learning and training section include specialized topics, maps, content, and metadata elements specially designed to support instructional content.
Learning and training: topic elements
Use the learning and training topic types to provide the instructional content, according to the needs identified by the learning goals and objectives.
<learningSummary>
A Learning Summary topic recaps and provides context for the achievement or accomplishment of learning objectives, provides guidance to reinforce learning and long-term memory, and can pose questions to enhance encoding and verification of the learning content.

Specification URIs
Notices
Introduction to DITA 1.3
The Darwin Information Typing Architecture (DITA) specification defines a set of document types for authoring and organizing topic-oriented information, as well as a set of mechanisms for combining, extending, and constraining document types.
Architectural specification: All-inclusive edition
The architectural specification portion of the DITA specification outlines the framework of DITA. It contains an overview of DITA markup; addressing; processing; configuration, specialization, generalization, and constraints; as well as information about coding DITA grammar files.
Language reference: All-inclusive edition
The language reference portion of the DITA specification contains a topic for each DITA element. The topic defines the element, its inheritance hierarchy, and provides examples of usage. This portion of the DITA specification also includes information about DITA attributes.
- Element quick reference
  This section contains a listing of DITA elements.
- Topic elements
  The base topic elements include elements that make up the core building blocks of the DITA topic, such as topic, body, and related-links, as well as elements like <p> and <ph> that are used in many topic specializations. Some of these elements are also available inside the <topicmeta> map element.
- Map elements
  Map elements include the core components of DITA maps, such as <topicref> and <reltable>, as well as general purpose map specializations in the map group domain.
- Metadata elements
  Metadata elements include information that is located within the <topicmeta> element (in maps) or <prolog> element (in topics), as well as indexing elements that can be placed in additional locations within topic content.
- Domain elements
  General purpose domains are not specific to any type of information, such as the hazard statement domain that provides elements for describing hazardous situations.
- Classification elements
  Classification elements support managing metadata. Those in the subject scheme map are used to define controlled values and to bind the controlled values to DITA attributes as enumerations. Those declared in the classification domain are used in other maps to classify content according to the scheme.
- Specialization elements
  Several DITA elements exist either for architectural reasons or for support of specialized markup yet to be designed. Although there is little need to use these elements unless you are directed to, some of them, such as <state>, can be used if your content makes use of these semantic distinctions. For example, a discussion of signals on a gate of an integrated logic circuit might use the <state> element to represent either on or off conditions of that gate.
- Legacy conversion elements
  Conversion elements exist primarily to aid in the conversion of content to DITA.
- DITAVAL elements
  A conditional processing profile (DITAVAL file) is used to identify which values are to be used for conditional processing during a particular output, build, or some other purpose. The profile should have an extension of .ditaval.
- Technical content elements
  Elements in the technical content section include the original Concept, Task, and Reference specializations, as well as specializations added in later releases. It also includes domains designed primarily for technical content.
- Learning and training elements
  Elements in the learning and training section include specialized topics, maps, content, and metadata elements specially designed to support instructional content.
  - Learning and training: topic elements
    Use the learning and training topic types to provide the instructional content, according to the needs identified by the learning goals and objectives.
    - <learningOverview>
      A Learning Overview topic identifies the learning objectives, includes other information helpful to the learner, such as prerequisites, duration, intended audience, and can include information and strategies that seeks to gain attention and stimulate recall of prior learning.
    - <learningOverviewbody>
      The <learningOverviewbody> element is the main body-level element in a <learningOverview> topic. A <learningOverviewbody> has a very specific structure, with the following elements in this order: <lcIntro>, <lcAudience>, <lcDuration>, <lcPrereqs>, <lcObjectives>, <lcResources>, followed by zero or more <section> elements. Each of the <learningOverviewbody> sections are optional.
    - <learningContent>
      A Learning Content topic provides the learning content itself, and enables direct use of content from DITA task, concept, and reference topics, as well as additional content of any topic type that supports specific objectives declared in the Learning Overview topic type.
    - <learningContentbody>
      The <learningContentbody> element is the main body-level element in a <learningContent> topic.
    - <learningSummary>
      A Learning Summary topic recaps and provides context for the achievement or accomplishment of learning objectives, provides guidance to reinforce learning and long-term memory, and can pose questions to enhance encoding and verification of the learning content.
    - <learningSummarybody>
      The <learningSummarybody> element is the main body-level element in a <learningSummary> topic.
    - <learningAssessment>
      A Learning Assessment topic presents questions or interactions that measure progress, encourage recollection, and stimulate reinforcement of the learning content, and can be presented before the content as a pre-assessment or as a post-assessment test. The interactions use a sub-set of the Question-Test Interoperability (QTI) specification, implemented as a DITA domain specialization.
    - <learningAssessmentbody>
      The <learningAssessmentbody> element is the main body-level element in a <learningAssessment> topic.
    - <learningPlan>
      A Learning Plan topic describes learning needs and goals, instructional design models, task analyses, learning taxonomies, and other information necessary to the lesson planning process.
    - <learningPlanbody>
      The <learningPlanbody> element is the main body-level element in a <learningPlan> topic.
    - <learningBase>
      The <learningBase> topic type is not used to deliver any actual learning content, but instead provides a set of common elements for use in the other more specific learning content types: <learningOverview>, <learningContent>, <learningSummary>, <learningAssessment>, and <learningPlan>.
    - <learningBasebody>
      The <learningBasebody> element is the main body-level element in a <learningBase> topic. The <learningBase> topic provides a set of base elements for use in the other specialized learning types. It is not generally intended for creating actual content. As such, each of the body sections in <learningBase> are optional.
  - Learning and training: map types
    Use the learning and training map types to aggregate learning content into individual learning objects, groups of learning objects, or higher-level aggregations of learning groups and objects, according to the needs identified by the learning goals and objectives.
  - Learning and training: map domain elements
    Use the learning and training map domain to organize groups of topics as learning objects. Defined as a map domain, these elements are available for use within any DITA map, not just a learning-specific DITA map. For example, you could include learning objects in a DITA generic map or in a DITA bookmap.
  - Learning and training: interactions domain elements
    Use the learning interactions to construct a basic set of question and response interaction. The domain also provides an <lcInstructornote2> element, which you can use to provide instructor-specific information in the learning topics.
  - Learning and training: interactions domain elements (DEPRECATED)
    Use the learning interactions to construct a basic set of question and response interaction. The domain also provides an <lcInstructornote> element, which you can use to provide instructor-specific information in the learning topics.
  - Learning and training: metadata elements
    Use the learning and training metadata to describe specific characteristics of the learning content. The learning and training metadata elements provide a robust metadata model for learning objects, built upon industry standards and best practices. Defined as a domain, these elements are available for use in both the topic <prolog> and the map <topicmeta>.
  - Learning and training: common content elements
    The learning and training content elements provide specialized content for learning topics.
- Attributes
  This section collects commonly used attributes, with common definitions. If an element uses a different definition, or narrows the scope of, an otherwise common attribute, it will be called out in the topic that defines the element.
Conformance
Conformance to the DITA specification allows documents and document types that are used with different processors or different versions of a processor to produce the same or similar results with little or no reimplementation or modification.
Acknowledgments
(Non-normative) Many members of the OASIS DITA Technical Committee participated in the creation of this specification and are gratefully acknowledged.
Non-normative information
This section contains non-normative information, including topics about new features in DITA 1.3 and migrating from DITA 1.2 to DITA 1.3.
Content models for learning and training package
For each element in the learning and training package, this section presents the content model and a list of parent elements that can contain that element.

`<learningSummary>`

A Learning Summary topic recaps and provides context for the achievement or accomplishment of learning objectives, provides guidance to reinforce learning and long-term memory, and can pose questions to enhance encoding and verification of the learning content.

Content models

See appendix for information about this element in OASIS document type shells.

Inheritance

- topic/topic learningBase/learningBase learningSummary/learningSummary

Example

id="learningSummary_ex">

<learningSummary id="learningsummary">
  <title>Summary: Understanding mail basics</title>
    <learningSummarybody>
      <lcObjectives>
        <lcObjectivesStem>You now know how to perform the following mail basics:</lcObjectivesStem>
        <lcObjectivesGroup>
            <lcObjective>Viewing the inbox</lcObjective>
            <lcObjective>Opening a message</lcObjective>
            <lcObjective>Moving messages to a folder</lcObjective>
        </lcObjectivesGroup>
      </lcObjectives>
    </learningSummarybody>
</learningSummary>

Attributes

The following attributes are available on this element: Universal attribute group (with a narrowed definition of @id, given below), Architectural attribute group, and outputclass.

@id (REQUIRED): An anchor point. This ID is usually required as part of the @href or @conref syntax when cross referencing or reusing content within the topic; it also enables <topicref> elements in DITA maps to optionally reference a specific topic within a DITA document. This attribute is defined with the XML Data Type ID.