section

The <section> element represents an organizational division in a topic. Sections are used to organize subsets of information that are directly related to the topic. For example, the titles Reference Syntax, Example and Properties might represent section-level discourse within a topic about a command-line process—the content in each section relates uniquely to the subject of that topic. Multiple sections within a single topic do not represent a hierarchy, but rather peer divisions of that topic. Sections cannot be nested. A section may have an optional title.

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
topic (base)	( text data or dl or fig or imagemap or image or lines or lq or note or hazardstatement or object or ol or p or pre or simpletable or sl or table or ul or boolean or cite or keyword or ph or b or i or sup or sub or tt or u or q or term or tm or xref or state or data or data-about or foreign or unknown or sectiondiv or title or draft-comment or fn or indextermref or indexterm or required-cleanup) (any number)
topic (technical content), concept, ditabase, glossary, glossentry, glossgroup, reference, task	( text data or dl or parml or fig or syntaxdiagram or imagemap or image or lines or lq or note or hazardstatement or object or ol or p or pre or codeblock or msgblock or screen or simpletable or sl or table or ul or boolean or cite or keyword or apiname or option or parmname or cmdname or msgnum or varname or wintitle or ph or b or i or sup or sub or tt or u or codeph or synph or filepath or msgph or systemoutput or userinput or menucascade or uicontrol or q or term or abbreviated-form or tm or xref or state or data or data-about or foreign or unknown or sectiondiv or title or draft-comment or fn or indextermref or indexterm or required-cleanup) (any number)
machineryTask	( text data or dl or fig or imagemap or image or lines or lq or note or hazardstatement or object or ol or p or pre or screen or simpletable or sl or table or ul or boolean or cite or keyword or wintitle or ph or b or i or sup or sub or tt or u or menucascade or uicontrol or q or term or tm or xref or state or data or data-about or foreign or unknown or sectiondiv or title or draft-comment or fn or indextermref or indexterm or required-cleanup) (any number)
learningAssessment, learningContent, learningOverview, learningPlan, learningSummary	( text data or dl or fig or imagemap or lcInteractionBase or lcTrueFalse or lcSingleSelect or lcMultipleSelect or lcSequencing or lcMatching or lcHotspot or lcOpenQuestion or image or lines or lq or note or lcInstructornote or object or ol or p or pre or simpletable or sl or table or ul or boolean or cite or keyword or ph or b or i or sup or sub or tt or u or q or term or tm or xref or state or data or data-about or foreign or unknown or sectiondiv or title or draft-comment or fn or indextermref or indexterm or required-cleanup) (any number)

Contained by

Doctype	Content model
topic (base), topic (technical content), task (strict)	body, bodydiv
concept, glossary, glossentry, glossgroup	body, bodydiv, conbody, conbodydiv
ditabase	body, bodydiv, conbody, conbodydiv, refbody, refbodydiv
reference	body, bodydiv, refbody, refbodydiv
task (general), machineryTask	body, bodydiv, taskbody
learningAssessment	body, bodydiv, learningBasebody, learningAssessmentbody
learningContent	body, bodydiv, learningBasebody, taskbody, conbody, conbodydiv, refbody, refbodydiv, learningSummarybody, learningAssessmentbody, learningContentbody
learningOverview	body, bodydiv, learningBasebody, learningOverviewbody
learningPlan	body, bodydiv, learningBasebody, learningPlanbody
learningSummary	body, bodydiv, learningBasebody, learningSummarybody

Inheritance

- topic/section

Example

<reference id="reference">
 <title>Copy Command</title>
 <refbody>
  <section>
   <title>Purpose</title>
   <p>This little command copies
   things.</p>
  </section>
 </refbody>
</reference>

Attributes

Name	Description	Data Type	Default Value	Required?
spectitle	The specialized title attribute allows architects of specialized types to define a fixed or default title for a specialized element. Not intended for direct use by authors.	CDATA	#IMPLIED	No
univ-atts attribute group (includes select-atts, id-atts, and localization-atts groups)	A set of related attributes, described in univ-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

Darwin Information Typing Architecture (DITA) Version 1.2