rel-atts is deprecated as of DITA 1.2, retained for backward compatibility.
The <topic> element is the top-level DITA element for a single-subject topic or article. Other top-level DITA elements that are more content-specific are <concept>,
<task>, <reference>, and <glossary>. Category: Topic elements
The alternate title element (<titlealts>) is optional, but can occur after the topic title. Two elements can be inserted as sub-elements of <titlealts>: navigation
title <navtitle> and search title <searchtitle>. Category: Topic elements
When your DITA topic is transformed to XHTML, the <searchtitle> element is used to create a title element at the top of the resulting HTML file. This title is normally
used in search result summaries by some search engines, such as that in Eclipse (http://eclipse.org); if not set, the XHTML's title element defaults to the source topic's title content
(which may not be as well optimized for search summaries) Category: Topic elements
The short description (<shortdesc>) element occurs between the topic title and the topic body, as the initial paragraph-like content of a topic, or it can be embedded
in an abstract element. The short description, which represents the purpose or theme of the topic, is also intended to be used as a link preview and for searching. When used within a
DITA map, the short description of the <topicref> can be used to override the short description in the topic. Category: Topic elements
The abstract element occurs between the topic title and the topic body, as the initial content of a topic. It can contain paragraph-level content as well as one or more
shortdesc elements which can be used for providing link previews or summaries. The <abstract> element cannot be overridden by maps, but its contained <shortdesc> elements can be, for
the purpose of creating link summaries or previews. Category: Topic elements
The <body> element is the container for the main content of a <topic>. Category: Topic elements
The <bodydiv> element is used to contain informal blocks of information within the body of a topic. The bodydiv element is specifically designed to be a grouping element,
without any explicit semantics, other than to organize subsets of content into logical groups that are not intended or should not be contained as a topic. As such, it does not contain an
explicit title to avoid enabling the creation of deeply nested content that would otherwise be written as separate topics. Content that requires a title should use a section element or a
nested topic.
The <no-topic-nesting> element is a placeholder in the DITA architecture. It is not actually used by the default DITA document types; it is for use only when creating a
validly customized document type where the information designer wants to eliminate the ability to nest topics. Not intended for use by authors, and has no associated output processing.
Category: Specialization elements
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. Category: Topic elements
The <sectiondiv> element allows logical grouping of content within a section. There is no additional semantic associated with the sectiondiv element, aside from its
function as a container for other content. The sectiondiv element does not contain a title; the lowest level of titled content within a topic is the section itself. If additional hierarchy
is required, nested topics should be used in place of the section.
The <example> element is a section with the specific role of containing examples that illustrate or support the current topic. The <example> element has the same
content model as <section>. Category: Topic elements
The <prolog> element contains information about the topic as an whole (for example, author information or subject category) that is either entered by the author or
machine-maintained. Much of the metadata inside the <prolog> will not be displayed with the topic on output, but may be used by processes that generate search indexes or customize
navigation. Category: Prolog elements
The related information links of a topic (<related-links> element) are stored in a special section following the body of the topic. After a topic is processed into it
final output form, the related links are usually displayed at the end of the topic, although some Web-based help systems might display them in a separate navigation frame. Category:
Topic elements
The <link> element defines a relationship to another topic. Links represent the types and roles of topics in a web of information, and therefore represent navigational
links within that web. Links are typically sorted on output based on their attributes. The optional container elements for link (<linkpool> and <linklist>) allow authors to define
groups with common attributes, or to preserve the authored sequence of links on output. Links placed in a <linkpool> may be rearranged for display purposes (combined with other local
or map-based links); links in a <linklist> should be displayed in the order they are defined. Refer to those elements for additional explanation. Category: Related Links
elements
The <linktext> element provides the literal label or line of text for a link. In most cases, the text of a link can be resolved during processing by cross reference
with the target resource. Use the <linktext> element only when the target cannot be reached, such as when it is a peer or external link, or the target is local but not in DITA format.
When used inside a topic, it will be used as the text for the specified link; when used within a map, it will be used as the text for generated links that point to the specified topic.
Category: Related Links elements
The <linklist> element defines an author-arranged group of links. Within <linklist>, the organization of links on final output is in the same order as originally
authored in the DITA topic. Category: Related Links elements
NOTE: The TC is maintaining the value "tree", which was
in the 1.2 DTDs but never defined for documented, only in the DTD version
of linklist.
The <linkinfo> element allows you to place a descriptive paragraph following a list of links in a <linklist> element. Category: Related Links
elements
The <linkpool> element defines a group of links that have common characteristics, such as type or audience or source. When links are not in a <linklist> (that is,
they are in <related-links> or <linkpool> elements), the organization of links on final output is determined by the output process, not by the order that the links actually occur
in the DITA topic. Category: Related Links elements
NOTE: The TC is maintaining the value "tree", which was
in the 1.2 DTDs but never defined for documented, only in the DTD version
of linkpool.