The "topicref-atts", "topicref-atts-no-toc", and "topicref-atts-without-format" attribute groups represent collections of attributes used in numerous map elements. With two exceptions, the three groups are identical. Neither "topicref-atts" nor "topicref-atts-without-format" provides a default for the toc attribute, while "topicref-atts-no-toc" provides a default of "no". Both "topicref-atts" and "topicref-atts-no-toc" include the format attribute, while "topicref-atts-without-format" omits the format attribute to allow specialization authors to declare the format attribute with specific default values.
The table below describes the "topicref-atts" attribute group. The "topicref-atts-no-toc" group is the same, except for the toc attribute, which is modified to provide a default of "no". The "topicref-atts-without-format" group is also the same as "topicref-atts", except that it does not define the format attribute.
Collection types describe how links relate to each other. The processing default is "unordered", although no default is specified in the DTD or Schema. Indicates that the order of the child topics is not significant. Indicates that the order of the child topics is significant; output processors will typically link between them in order. Indicates that one of the children should be selected. Represents a tight grouping in which each of the referenced topics not only relates to the current topic but also relate to each other. Usage of the collection-type attribute on <reltable> and <relcolspec> is currently undefined and reserved for future use. |
(unordered | sequence | choice | family | -dita-use-conref-target) |
|||
Describes the processing role of the referenced topic. The processing default is "normal". Normal topic that is a readable part of the information. The topic is used as a resource for processing purposes, but is not a readable unit of information on its own. This topic should not be included in a rendered table of contents, and the topic should not be rendered on its own. |
||||
Describes the target of a reference. See 3.4.2.8 The type attribute for detailed information on supported values and processing implications. |
||||
The scope attribute identifies the closeness of the relationship between the current document and the target resource. See 3.4.2.10 The scope attribute for more information on values. |
||||
If locktitle is set to "yes", the <navtitle> element or @navtitle attribute is used if it is present. Otherwise, the navtitle is ignored and the navigation title is retrieved from the referenced file. The @navtitle attribute is deprecated in favor of the <navtitle> element. When both a <navtitle> element and a navtitle attribute are specified, the <navtitle> element should be used. The navtitle in the map is used. The navtitle or title of the topic is used. This is the processing default. |
||||
The format attribute identifies the format of the resource being referenced. See 3.4.2.9 The format attribute for details on supported values. |
||||
Defines some specific linking characteristics of a topic's current location in the map. A topic can only be linked to and cannot link to other topics. A topic cannot be linked to but can link to other topics. A topic can be linked to and can link to other topics. Use this to override the linking value of a parent topic. |
(targetonly | sourceonly | normal | none | -dita-use-conref-target) |
|||
Specifies whether a topic appears in the table of contents (TOC). If the value is not specified locally, but is specified on an ancestor, the value will cascade from the closest ancestor. |
(yes | no | -dita-use-conref-target) |
|||
Specifies whether the topic should be included in a print-specific rendition, such as PDF. The processing default is "yes". Include the topic in the print-oriented file. Do not include the topic in a print-oriented file. Only include the topic when rendering the DITA content in a print-oriented context; the topic should not be included in other contexts, such as when rendering as HTML. |
||||
When a set of topics is transformed using a map, the chunk attribute allows multi-topic documents to be broken into smaller files and multiple individual topics to be combined into larger combined documents. For a detailed description of the chunk attribute and its usage, see 2.1.3.7 Chunking in the DITA Architectural Specification. |