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.

A Learning Content topic comprises a set of self-contained content about a single terminal learning objective supported by zero or more enabling learning objectives.

A learning content topic should be rendered as single result component (e.g., a single HTML page) when it has subordinate topics, either as direct child elements or associated via a map. This result can be requested by specifying a value of "to-content" for the chunk attribute of topic refs that point to learningContent topics. This is the default value for the learningContentRef topicref type provided by the learning map domain.

Added explicit statement about requirement to render content topics as single chunks.

Contains

Note

These models represent only the default document types distributed by OASIS. Actual content models will differ with each new document type.
Doctype Content model
learningContent ( (title) then (titlealts) (optional) then (shortdesc or abstract) (optional) then (prolog) (optional) then (learningContentbody) then (related-links) (optional) then ( ( (concept or task or reference or topic) (any number) then (learningAssessment) (optional) then (learningSummary) (optional) ) ) (any number) )

Contained by

This element is not contained by any other elements.

Inheritance

- topic/topic learningBase/learningBase learningContent/learningContent

Example

<learningContent id="learningcontent">
<title>Your Mail Inbox</title>
  <learningContentbody>
    <lcObjectives>
      <lcObjectivesStem>When you complete this topic, you'll understand:</lcObjectivesStem>
        <lcObjectivesGroup>
            <lcObjective>How to use the mail inbox.</lcObjective>
        </lcObjectivesGroup>
    </lcObjectives>
  </learningContentbody>
  <concept id="mail_inbox_concept" xml:lang="en-us">
    <title>Your Mail Inbox</title>
    <shortdesc>Use your mail inbox to track and manage incoming messages.</shortdesc>
    <conbody>
        <p>Knowing which messages you have not yet read and which ones are urgent
        can help you decide how to best review a long list of messages. Unread messages
        are indicated by bold text and a variety of icons identifies a characteristic
        of the message, such as a high priority message or an invitation.</p>
    </conbody>
  </concept>
</learningContent>

Attributes

Name Description Data Type Default Value Required?
id This ID enables topics to be referenced uniquely by topicrefs in DITA maps. ID Yes
conref-atts attribute group (conref, conrefend, conaction, conkeyref) A set of related attributes; includes all of the attributes described in id-atts attribute group except for the id attribute.
xmlns:ditaarch Declares the default DITA namespace. "http://dita.​oasis-open.​org/​architecture/​2005/"
DITAArchVersion Designates the version of the architecture that is in use. The default value will increase with each release of DITA. CDATA "1.2" No
domains Indicates the specialized domains that are included in the DTD or Schema. This value will differ depending on what domains are included in the current DTD or Schema. CDATA Varies based on the DTD or Schema; a sample value is "(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d) (topic ut-d) (topic indexing-d)" No
select-atts attribute group (props, base, platform, product, audience, otherprops, importance, rev, status) A set of related attributes, described in select-atts attribute group
localization-atts attribute group (translate, xml:lang, dir) A set of related attributes, described in localization-atts attribute group.
global-atts attribute group (xtrf, xtrc) A set of related attributes, described in global-atts attribute group
class, outputclass Common attributes described in Other common DITA attributes
domains Indicates the specialized domains that are included in the DTD or Schema. This value will differ depending on what domains are included in the current DTD or Schema. CDATA Varies based on the DTD or Schema; a sample value is "(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d) (topic ut-d) (topic indexing-d)" No

Was this helpful?