itemizedlist

Processing expectations

Formatted as a displayed block.

DocBook specifies neither the initial mark nor the sequence of marks to be used in nested lists. If explicit control is desired, the Mark attribute should be used. The values of the Mark attribute are expected to be keywords, not representations (numerical character references, entities, and so on.) of the actual mark.

In order to enforce a standard set of marks at your organization, it may be useful to construct a customization layer that limits the values of the Mark attribute to an enumerated list. See Chapter 5, Customizing DocBook.

Future Changes

Introductory material may appear before the first list item.

Parents

These elements contain itemizedlist: answer, appendix, article, bibliodiv, bibliography, blockquote, callout, caption, caution, chapter, colophon, constraintdef, dedication, entry, example, footnote, glossary, glossdef, glossdiv, highlights, important, index, indexdiv, informalexample, legalnotice, listitem, msgexplan, msgtext, note, para, partintro, preface, procedure, qandadiv, qandaset, question, refsect1, refsect2, refsect3, refsection, refsynopsisdiv, revdescription, sect1, sect2, sect3, sect4, sect5, section, setindex, sidebar, simplesect, step, taskprerequisites, taskrelated, tasksummary, td, textobject, th, tip, warning.

Children

The following elements occur in itemizedlist: abstract, address, anchor, authorblurb, beginpage, blockinfo, blockquote, bridgehead, caution, classsynopsis, cmdsynopsis, constructorsynopsis, destructorsynopsis, epigraph, fieldsynopsis, formalpara, funcsynopsis, graphic, graphicco, highlights, important, indexterm, informalequation, informalexample, informalfigure, informaltable, listitem, literallayout, mediaobject, mediaobjectco, methodsynopsis, note, para, programlisting, programlistingco, remark, screen, screenco, screenshot, simpara, synopsis, tip, title, titleabbrev, warning.