Namespace: |
|
Content: |
25 elements |
Defined: |
globally in topicMod.xsd; see XML source |
Referenced: |
by 2 locations |

Complex Content Model |
Component |
Type / Value |
Occurs |
Nillable? |
Declared In |
Description |
|
1..1 |
||||||
1..1 |
no |
A paragraph element (<p>) is a block of text containing a single main idea.
|
||||
1..1 |
no |
TThe long quote (<lq>) element indicates content quoted from another source. »
|
||||
1..1 |
no |
A <note> element contains information, differentiated from the main text, which expands on or calls attention to a particular point.
|
||||
1..1 |
no |
dl (ver 1)
|
A definition list (<dl>) is a list of terms and corresponding definitions. »
|
|||
1..1 |
no |
The parameter list (<parml>) element contains a list of terms and definitions that describes the parameters in an application programming interface. »
|
||||
1..1 |
no |
In an unordered list (<ul>), the order of the list items is not significant. »
|
||||
1..1 |
no |
An ordered list (<ol>) is a list of items sorted by sequence or order of importance.
|
||||
1..1 |
no |
The <sl> element contains a simple list of items of short, phrase-like content, such as in documenting the materials in a kit or package.
|
||||
1..1 |
no |
pre (ver 1)
|
The preformatted element (<pre>) preserves line breaks and spaces entered manually by the author in the content of the element, and also presents the content in a monospaced type font (depending on your output formatting processor).
|
|||
1..1 |
no |
The <codeblock> element represents lines of program code. »
|
||||
1..1 |
no |
The <screen> element contains or refers to a textual representation of a computer screen or user interface panel (window).
|
||||
1..1 |
no |
The message block (<msgblock>) element contains a multi-line message or set of messages. »
|
||||
1..1 |
no |
The <lines> element may be used to represent dialogs, lists, text fragments, and so forth. »
|
||||
1..1 |
no |
fig (ver 1)
|
The figure (<fig>) element is a display context (sometimes called an exhibit) with an optional title for a wide variety of content. »
|
|||
1..1 |
no |
The syntax diagram (<syntaxdiagram>) element is the main container for all the syntax elements that make up a syntax definition. »
|
||||
1..1 |
no |
The imagemap element supports the basic functionality of the HTML client-side image map markup.
|
||||
1..1 |
no |
Include artwork or images in a DITA topic by using the <image> element. »
|
||||
1..1 |
no |
DITA's <object> element corresponds to the HTML <object> element. »
|
||||
1..1 |
no |
The <table> element organizes arbitrarily complex relationships of tabular information. »
|
||||
1..1 |
no |
The <simpletable> element is used for tables that are regular in structure and do not need a caption. »
|
||||
1..1 |
no |
A <required-cleanup> element is used as a placeholder for migrated elements that cannot be appropriately tagged without manual intervention. »
|
||||
0..∞ |
||||||
1..1 |
no |
The <data> element represents a property within a DITA topic or map. »
|
||||
1..1 |
no |
The <data-about> element identifies the subject of a property when the subject isn't associated with the context in which the property is specified. »
|
||||
1..1 |
no |
The <foreign> element is an open extension that allows information architects to incorporate existing standard vocabularies for non-textual content. like MathML and SVG, as inline objects. »
|
||||
1..1 |
no |
The <unknown> element is an open extension that allows information architects to incorporate xml fragments that does not necessarily fit into an exisitng DITA use case. »
|
||||
XML schema documentation generated with FlexDoc/XML 1.15 using FlexDoc/XML XSDDoc 3.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit. |