<topicapply>The <topicapply> element identifies subjects that qualify the
content for filtering or flagging but not retrieval. The <topicapply> element
can identify a single subject. Additional subjects can be specified by nested
<subjectref> elements.
See appendix for information about this element in OASIS document type shells.
+ map/topicref classify-d/topicapply
The map content should be retrieved for Apache Tomcat and hidden as irrelevant for operating systems other than RedHat or SuSE.
<map>
<title>Installing Apache Tomcat on RedHat or SuSE Linux</title>
<topicsubject href="../controlledValues/tomcatServer.dita"/>
<topicapply>
<subjectref href="../controlledValues/redhatLinux.dita"/>
<subjectref href="../controlledValues/suseLinux.dita"/>
</topicapply>
<!-- ... -->
</map>The following attributes are available on this element: Universal attribute group, Link relationship attribute group (with a narrowed definition of
@href, given below), @navtitle and @query from Topicref element attributes group, outputclass, @keyref, and @keys. This element also uses
@collection-type, @linking, and narrowed definitions of
@processing-role and @toc (given below), from Attributes common to many map elements.
@href<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 @format
attribute to identify the kind of resource being
referenced.@processing-role@processing-role is
"resource-only". Otherwise, the definition matches
the one found in Attributes common to many map elements.@toc@toc is "no". See Attributes common to many map elements for a complete definition of
@toc.