The text element associates no semantics with its content. It exists to serve as a container for text where a container is needed (e.g., for conref, or for restricted content models in specializations). Unlike ph, text cannot contain images. Unlike keyword, text does not imply keyword-like semantics. The text element contains only text data, or nested text elements. All universal attributes are available on text.
For contexts where ph is available, authors should use that element. Where keyword is available, authors should use that element. Where neither ph nor keyword is available, text can be used to pull content by conref.
topic, map, concept, ditabase, glossary, glossentry, glossgroup, reference, task, bookmap, classifyMap, subjectScheme, machineryTask, learningAssessment, learningBookmap, learningContent, learningMap, learningOverview, learningPlan, learningSummary |
( text data or text) (any number) |
topic (base), map (base), classifyMap, subjectScheme, learningBookmap, learningMap |
|
topic (technical content), map (technical content), concept, ditabase, glossary, glossentry, glossgroup, reference, task (strict), task (general), bookmap |
text, keyword, term, ph, tm, shape, wintitle, shortcut, option, parmname, synph, apiname, kwd, msgnum, cmdname, varname |
learningAssessment, learningContent, learningOverview, learningPlan, learningSummary |
<p>This an example of <keyword><text id="reuse">Text that is reusable</text></keyword>, with no extra semantics attached to the text when it is reused.</p>
univ-atts attribute group (includes select-atts, id-atts, and localization-atts groups) |
A set of related attributes, described in 3.4.1.3 univ-atts attribute group |
|||
A set of related attributes, described in 3.4.1.2 global-atts attribute group |
||||
A common attribute described in 3.4.1.9 Other common DITA attributes |