Text Division at Chapter Level
The text division (e. g. chapters, sections, parts...) of a book is represented by nested <div>
elements. These usually contain an attribute @n
, which specifies the structure level.
<div n="1"> <head>[Title Chapter 1]</head><!-- where available --> <div n="2"> <head>[Title Subchapter 1.1]</head><!-- where available --> <p>[Text]</p> <p>[Text]</p> ... </div> </div>
In addition, the @type
attribute can be used for text sections with a special structure, which specifies them in more detail.
The @type
attribute can have the following values:
abbreviations
|
list of abbreviations |
act
|
act in drama |
advertisement
|
advertisement |
appendix
|
appendix |
bibliography
|
bibliography |
chapter
|
chapter (level 3) |
contents
|
table of contents |
copyright
|
copyright information |
corrigenda
|
errata |
dedication
|
dedication |
diaryEntry
|
journal entry (level 3) |
edition
|
print of an external text source (level 3) |
figures
|
list of illustrations |
frontispiece
|
frontispiece |
imprint
|
imprint |
imprimatur
|
imprimatur |
index
|
register |
letter
|
letter (level 3) |
poem
|
poem |
postface
|
conclusion, epilogue (level 3) |
preface
|
foreword, preface, introduction (level 3) |
recipe
|
recipe (level 3) |
scene
|
scene in drama |
As a rule, documents are structured by <div>
elements. However, exceptions are possible. For example, volumes of poetry can be completely structured with <lg>
s (see chapter poems).
The titles of the (sub-)chapters are enclosed with the <head>
element. It does not matter whether the title is on a separate line or appears at the beginning of the first chapter line. The distances between headings of different levels, the alignment of headings (e. g. centered) and possible Fraktur changes are not tagged separately. On the other hand, line breaks, all typographical features (bold, italic, blocked, etc.) and a change to the Antiqua font are tagged.
Chapter Structuring
Basically, <div>
structuring is done as a chapter classification. If additional structuring approaches are used in the original, these are subordinated to the chapter division, but if possible also mapped.
Different Structuring Approaches at Chapter Level
Subordinate <div>
containers end either with the start of a new division of the same level or with the end of the higher-level division. It is not possible to insert <div>
containers after which the higher division is continued. However, there are cases where it is necessary to interrupt the text flow by a division and resume it at the end of the inserted division. In these cases, the <floatingText>
element is used, within which the inserted division is implemented.