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 is rendered as single result component (for example, a single HTML page) when it has subordinate topics. The subordinate topics either can be direct child elements or associated through a map. This rendering result can be requested by specifying a value of "to-content" for the @chunk attribute of <topicref> elements that reference <learningContent> topics. This is the default value for the <learningContentRef> element that is provided by the learning map domain.
See appendix for information about this element in OASIS document type shells.
- topic/topic learningBase/learningBase learningContent/learningContent
<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>
- @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.