DocBook: The Definitive GuideBy Norman Walsh & Leonard Muellner
1st Edition October 1999
1-56592-580-7, Order Number: 5807
652 pages, $36.95 , Includes CD-ROM
Content ModelSection ::= (SectionInfo?, (Title,Subtitle?,TitleAbbrev?), (ToC|LoT|Index|Glossary|Bibliography)*, (((CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList| SimpleList|VariableList|Caution|Important|Note|Tip|Warning| LiteralLayout|ProgramListing|ProgramListingCO|Screen|ScreenCO| ScreenShot|Synopsis|CmdSynopsis|FuncSynopsis|FormalPara|Para| SimPara|Address|BlockQuote|Graphic|GraphicCO|MediaObject| MediaObjectCO|InformalEquation|InformalExample|InformalFigure| InformalTable|Equation|Example|Figure|Table|MsgSet|Procedure| Sidebar|QandASet|Anchor|BridgeHead|Comment|Highlights| Abstract|AuthorBlurb|Epigraph|IndexTerm)+, ((RefEntry)*| Section*))| (RefEntry)+| Section+), (ToC|LoT|Index|Glossary|Bibliography)*)
Label CDATA None Status CDATA None
Both the start- and end-tags are required for this element.
Section is one of the top-level sectioning elements in a component. There are three types of sectioning elements in DocBook:
Recursive Sections, which are an alternative to the numbered sections and have unbounded depth.
Sections 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 Sections may cause problems in some processing systems.
The following elements occur in Section: Abstract, Address, Anchor, AuthorBlurb, Bibliography, BlockQuote, BridgeHead, CalloutList, Caution, CmdSynopsis, Comment, Epigraph, Equation, Example, Figure, FormalPara, FuncSynopsis, Glossary, GlossList, Graphic, GraphicCO, Highlights, Important, Index, IndexTerm, InformalEquation, InformalExample, InformalFigure, InformalTable, ItemizedList, LiteralLayout, LoT, MediaObject, MediaObjectCO, MsgSet, Note, OrderedList, Para, Procedure, ProgramListing, ProgramListingCO, QandASet, RefEntry, Screen, ScreenCO, ScreenShot, Section, SectionInfo, SegmentedList, Sidebar, SimPara, SimpleList, Subtitle, Synopsis, Table, Tip, Title, TitleAbbrev, ToC, VariableList, Warning.
Label specifies an identifying string for presentation purposes.
Generally, an explicit Label attribute is used only if the processing system is incapable of generating the label automatically. If present, the Label is normative; it will used even if the processing system is capable of automatic labelling.
Status identifies the editorial or publication status of the Section.
Publication status might be used to control formatting (for example, printing a "draft" watermark on drafts) or processing (perhaps a document with a status of "final" should not include any components that are not final).
Examples<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V3.1//EN"> <chapter><title>Test Chapter</title> <para>This chapter uses recursive sections.</para> <section> <sectioninfo> <abstract><para>A trivial example of recursive sections.</para> </abstract> </sectioninfo> <title>Like a Sect1</title> <subtitle>Or How I Learned to Let Go of Enumeration and Love to Recurse</subtitle> <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> </chapter>
Back to: DocBook: The Definitive Guide
© 2001, O'Reilly & Associates, Inc.