<topicset> element defines a complete unit of content that can
be reused in other DITA maps or other
<topicset> elements. Unlike the
<topicref> element, the
explicitly intended to define a set of topics that are often or always used as a unit; it can be
especially useful for task composition in which larger tasks are composed of smaller tasks. The
@id attribute on a
<topicset> is required, which
ensures that the complete unit is available for reuse in other contexts.
<topicset> is similar to a source file that contains nested
topics, in that the combination of topics constitutes a complete self-contained unit. That
unit of content can stand independently of the containing, prior, and following content
within the original map context.
See appendix for information about this element in OASIS document type shells.
+ map/topicref mapgroup-d/topicset
<topicset> represents a set of overview information about SQL. The
information is reusable as a unit.
<topicset id="sqlbasics" href="sqlOverview.dita"> <topicref href="sqlSelection.dita"/> <topicref href="sqlJoin.dita"/> <topicref href="sqlFilter.dita"/> <!-- ... --> </topicset>
The following attributes are available on this element: Universal attribute group (with a narrowed definition of
@id, given below), Link relationship attribute group (with a narrowed definition of
@href, given below), Attributes common to many map elements, Topicref element attributes group, outputclass,
<topicset>is defined as a reusable unit of information. See ID attribute for more details.
<topicref>. See The href attribute for detailed information on supported values and processing implications. References to DITA content cannot be below the topic level: that is, you cannot reference individual elements inside a topic. References to content other than DITA topics should use the
@formatattribute to identify the kind of resource being referenced.
Return to main page.
Standards Track Work Product
|Copyright © OASIS Open 2016. All Rights Reserved.||25 October 2016|