section — A recursive section
section ::=
address
anchor
annotation
bibliolist
blockquote
bridgehead
calloutlist
caution
classsynopsis
cmdsynopsis
constraintdef
constructorsynopsis
destructorsynopsis
epigraph
equation
example
fieldsynopsis
figure
formalpara
funcsynopsis
glosslist
html:form
important
indexterm
(db.indexterm.endofrange)indexterm
(db.indexterm.singular)indexterm
(db.indexterm.startofrange)informalequation
informalexample
informalfigure
informaltable
(db.cals.informaltable)informaltable
(db.html.informaltable)itemizedlist
literallayout
mediaobject
methodsynopsis
msgset
note
orderedlist
para
procedure
productionset
programlisting
programlistingco
qandaset
remark
revhistory
screen
screenco
screenshot
segmentedlist
sidebar
simpara
simplelist
synopsis
table
(db.cals.table)table
(db.html.table)task
tip
variablelist
warning
Section
is one of the top-level sectioning elements in
a component. There are three types of sectioning elements in
DocBook:
Explicitly numbered sections, Sect1
…Sect5
,
which must be properly nested and can only be five levels deep.
Recursive Section
s, which are an alternative to the numbered
sections and have unbounded depth.
SimpleSect
s, which are terminal. SimpleSect
s can
occur as the “leaf” sections in either recursive sections or any
of the numbered sections, or directly in components.
Section
s may be more convenient than numbered
sections in some authoring environments because they can be
moved around in the document hierarchy without renaming.
None of the sectioning elements is allowed to “float” in a component. You can place paragraphs and other block elements before a section, but you cannot place anything after it.
Formatted as a displayed block. Sometimes sections are numbered.
Use of deeply nested Section
s may cause problems
in some processing systems.
Common attributes and common linking attributes.
Specifies an identifying string for presentation purposes
Identifies the editorial or publication status of the element on which it occurs
The following elements occur in section: address
, anchor
, annotation
, bibliography
, bibliolist
, blockquote
, bridgehead
, calloutlist
, caution
, classsynopsis
, cmdsynopsis
, constraintdef
, constructorsynopsis
, destructorsynopsis
, epigraph
, equation
, example
, fieldsynopsis
, figure
, formalpara
, funcsynopsis
, glossary
, glosslist
, html:form
, important
, index
, indexterm
(db.indexterm.endofrange), indexterm
(db.indexterm.singular), indexterm
(db.indexterm.startofrange), info
(db.titleforbidden.info), info
(db.titlereq.info), informalequation
, informalexample
, informalfigure
, informaltable
(db.cals.informaltable), informaltable
(db.html.informaltable), itemizedlist
, literallayout
, mediaobject
, methodsynopsis
, msgset
, note
, orderedlist
, para
, procedure
, productionset
, programlisting
, programlistingco
, qandaset
, refentry
, remark
, revhistory
, screen
, screenco
, screenshot
, section
, segmentedlist
, sidebar
, simpara
, simplelist
, simplesect
, subtitle
, synopsis
, table
(db.cals.table), table
(db.html.table), task
, tip
, title
, titleabbrev
, toc
, variablelist
, warning
.
<article xmlns='http://docbook.org/ns/docbook'> <title>Example section</title> <para>This <tag>article</tag> uses recursive sections.</para> <section> <title>Like a Sect1</title> <subtitle>Or How I Learned to Let Go of Enumeration and Love to Recurse</subtitle> <info> <abstract><para>A trivial example of recursive sections.</para> </abstract> </info> <para>This section is like a Sect1.</para> <section><title>Like a Sect2</title> <para>This section is like a Sect2.</para> <section><title>Like a Sect3</title> <para>This section is like a Sect3.</para> <section><title>Like a Sect4</title> <para>This section is like a Sect4.</para> <section><title>Like a Sect5</title> <para>This section is like a Sect5.</para> <section><title>Would be like a Sect6</title> <para>This section would be like a Sect6, if there was one.</para> <section><title>Would be like a Sect7</title> <para>This section would be like a Sect7, if there was one.</para> </section> </section> </section> </section> </section> </section> </section> </article>
This article
uses recursive sections.