Appendix ::= ((DocInfo?,Title,Subtitle?,TitleAbbrev?), ToCchap?, (((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)+, (Sect1*| (RefEntry)*| SimpleSect*|Section*))| (Sect1+| (RefEntry)+| SimpleSect+|Section+)))
Name | Type | Default |
| Label | CDATA | None |
| Status | CDATA | None |
The start-tag is required for this element. The end-tag is optional, if your SGML declaration allows minimization.
Appendixes usually occur at the end of a document.
Formatted as a displayed block. Usually introduces a forced page break and often starts on the next recto page. Sometimes restarts page numbering. Typically, appendixes are lettered rather than numbered, and appear in the table of contents.
The following elements occur in Appendix: Abstract, Address, Anchor, AuthorBlurb, BlockQuote, BridgeHead, CalloutList, Caution, CmdSynopsis, Comment, DocInfo, Epigraph, Equation, Example, Figure, FormalPara, FuncSynopsis, GlossList, Graphic, GraphicCO, Highlights, Important, IndexTerm, InformalEquation, InformalExample, InformalFigure, InformalTable, ItemizedList, LiteralLayout, MediaObject, MediaObjectCO, MsgSet, Note, OrderedList, Para, Procedure, ProgramListing, ProgramListingCO, QandASet, RefEntry, Screen, ScreenCO, ScreenShot, Sect1, Section, SegmentedList, Sidebar, SimPara, SimpleList, SimpleSect, Subtitle, Synopsis, Table, Tip, Title, TitleAbbrev, ToCchap, VariableList, Warning.
In some contexts, the following elements are allowed anywhere: BeginPage, IndexTerm.
Label specifies an identifying string for presentation purposes. The second Appendix might be labeled "B", for example.
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 Appendix.
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).
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN"> <book> <chapter><title>Required Chapter</title> <para> At least one chapter, reference, part, or article is required in a book. </para> </chapter> <appendix><title>Demonstration Appendix</title> <para> This appendix demonstrates an appendix in a book. It has the same broad content model as a chapter. </para> </appendix> </book>
For additional examples, see also Book.
Copyright © 1999 O'Reilly & Associates, Inc. All rights reserved.
HIVE: All information for read only. Please respect copyright! |
