The <index-base> element allows indexing extensions to be added by specializing off this element. It does not in itself have any meaning and should be ignored in processing.
The <index-base> element can only exist as a child of an <indexterm> element. This characteristic makes it the appropriate element to specialize to add indexing extensions. Specifically, the index-see , index-see-also, and index-sort-as elements only make sense as children of <indexterm> and so are specializations of <index-base>. Those elements are all part of the indexing domain, which is new for DITA 1.1.
On its own, <index-base> has no meaning. Processors should ignore this element and its content if encountered in its unspecialized form.
| Doctype | Content model |
|---|---|
| ditabase, topic, task, reference, concept | ( text data or keyword or option or parmname or apiname or cmdname or msgnum or varname or wintitle or term or data or data-about or foreign or unknown or indexterm) (any number) |
| map, bookmap | ( text data or keyword or term or data or data-about or foreign or unknown or indexterm) (any number) |
| Doctype | Parents |
|---|---|
| bookmap, map, ditabase, topic, task, concept, reference, glossary | indexterm |
- topic/index-base
| Name | Description | Data Type | Default Value | Required? |
|---|---|---|---|---|
| %univ-atts; (%select-atts;, %id-atts;, %localization-atts;) | A set of related attributes, described at %univ-atts; | parameter entity | PE not applicable | Not applicable |
| %global-atts; (xtrf, xtrc) | A set of related attributes, described at %global-atts; | parameter entity | PE not applicable | Not applicable |
| class, keyref | Common attributes described in Other common DITA attributes. |
Return to main page.
OASIS DITA Language Specification v1.1 -- Committee Draft 13 February 2007
Copyright © OASIS Open 2005, 2007. All Rights Reserved.