Bloomsbury DocBook XML

Specification, Examples and

Data Capture Instructions
Version 2.3.4
Bloomsbury DocBook XML: Specification, Examples and Data
Capture Instructions
Publication date 2024-03-18 17:48:04 (rendered).
Copyright © 2024 Bloomsbury Publishing Plc
Revision History
Revision 2.3.4 18th March 2024 Andrew Sales

Updated series titles.

Revision 2.3.3 21st February 2024 Andrew Sales

Titles with associated Studio Resource(s) must be flagged as such in the XML, see Section 7.5.7, “Studio
content”.

Revision 2.3.2 19th January 2024 Andrew Sales

Looseleaf content must be identified as such in the volume metadata, see Section 32.16.1.1, “Looseleaf content”.

Revision 2.3.1 30th November 2023 Andrew Sales

Updated series titles.

Revision 2.3.0 6th October 2022 Andrew Sales

Schematron version is now incremented to 8 and this value MUST be used from now on.

Supplier details required in book-level metadata.

Biographical information for contributors is now also required at the chunk level, where available.

Updated series titles.

Revision 2.2.2 27th June 2022 Andrew Sales

Updated series titles.

Revision 2.2.1 7th June 2022 Tarquin Acevedo

Updated series titles.

Revision 2.2.0 27th May 2022 Andrew Sales

Schematron version is now incremented to 7 and this value MUST be used from now on. The previous
instructions regarding alt text are now DEPRECATED with this release. The instructions given in Chapter 34,
Accessibility MUST be used instead.

Revision 2.1.6 25 April 2022 Andrew Sales

phrase role=incompleteXref added, see Section 14.3, “@role attributes”.

Revision 2.1.5 14 March 2022 Andrew Sales

Updated series titles.

Revision 2.1.4 14 January 2022 Andrew Sales

Embedded videos.

Revision 2.1.3 29 November 2021 Andrew Sales

Updated series titles.

Revision 2.1.2 15 November 2021 Andrew Sales

Updated series titles.

Revision 2.1.1 11 November 2021 Andrew Sales

Updated series titles.

Revision 2.1.0 5 October 2021 Andrew Sales

Support for LaTeX equations (see LaTeX equations) where specified via additional biblioid otherclass
value latexEquations (see Section 7.5.11, “Other biblioids”).

Revision 2.0.0 1 October 2021 Andrew Sales

Important
As of this release, the documentation will follow the standard versioning scheme
(MAJOR.MINOR.PATCH), as described at https://semver.org/. This version number will
now appear as the filename suffix for the PDF version of this document.

Other major changes:

• Schematron version is now incremented to 6 and this value MUST be used from now on.

• Open Access titles receive new, updated markup as of this version.

• Book titles MUST have the new sortas attribute.

Note also that the instructions on identifier persistence, previously supplied separately, are now incorporated
unchanged into this document.

Revision 1.70 30 June 2021 Andrew Sales

Updated series titles.

Revision 1.69 5 May 2021 Andrew Sales

Updated series titles.

Revision 1.68 23 March 2021 Andrew Sales

Processing instruction to insert end-of-chapter notes disallowed within footnote, see Section 18.2.1, “End of
chapter notes”.

Revision 1.67 2 March 2021 Andrew Sales

Updated series titles.

Revision 1.66 28 January 2020 Andrew Sales

Updated series titles.

Revision 1.65 15 December 2020 Andrew Sales

Updated series titles.

Revision 1.64 14 December 2020 Andrew Sales

Updated series titles.

Revision 1.63 25 November 2020 Andrew Sales

Spaces disallowed in XML ISBNs, see here.

Revision 1.62 18 November 2020 Andrew Sales

phrase role='stageDirection' deprecated, see Section 14.3, “@role attributes”.

Revision 1.61 18 August 2020 Andrew Sales

Reference to audio assets by ID, see Section 22.2, “Audio”.

Revision 1.60 28 July 2020 Andrew Sales

No MathML required in equations on Bloomsbury Collections, see Section 23.3, “More complex equations”.

Revision 1.59 2 July 2020 Andrew Sales

No extraneous XML files to be present in the zip, see Chapter 3, Deliverables and file-naming conventions.

Revision 1.58 25 June 2020 Andrew Sales

pagenums pattern, see Section 9.3.2, “Page range”; links in chunk titles, see Section 9.2, “Chunk and section
titles and numbering”

Revision 1.57 24 April 2020 Andrew Sales

Note to clarify check-label-3 (re full points in @label). Updated series titles.

Revision 1.56 20 January 2020 Andrew Sales

Updated series titles.

Revision 1.55 18 December 2019 Andrew Sales

Updated series titles.

Revision 1.54 2 December 2019 Andrew Sales

Cross-references in titles: Section 9.2, “Chunk and section titles and numbering”; format of nested section
labels.

Revision 1.53 9 September 2019 Andrew Sales

Updated series titles.

Revision 1.52 29 April 2019 Andrew Sales

Added Section 22.1.2, “Reference by ID”.

Revision 1.51 11 April 2019 Andrew Sales

Updated series titles.

Revision 1.50 28 March 2019 Andrew Sales

Updated series titles: Constitutionalism in Asia

Revision 1.49 11 March 2019 Andrew Sales

Updated series titles.

Revision 1.48 12 December 2018 Andrew Sales

Added section on embedded links.

Revision 1.47 26 November 2018 Andrew Sales

Added Section 24.4.5, “Screenplay excerpts”; updated series titles.

Revision 1.46 9 November 2018 Andrew Sales

Updated series titles: Bloomsbury Family Law, Critiquing Religion: Discourse, Culture, Power, Cornerstone
on..., Social Theory and Methodology in Education Research.

Revision 1.45 25 September 2018 Andrew Sales

Updated series titles: 1 KBW on, Arden Studies in Early Modern Drama, Bloomsbury Studies in Critical
Poetics, Animation: Key Films/Filmmakers.

Revision 1.44 15 June 2018 Andrew Sales

Updated series titles

Revision 1.43 24 April 2018 Andrew Sales

Updated series titles

Revision 1.42 18 April 2018 Andrew Sales

Multiple other hardback ISBNs allowed

Revision 1.41 17 April 2018 Andrew Sales

Updated series titles

Revision 1.40 13 December 2017 Andrew Sales

Updated series titles

Revision 1.39 4 December 2017 Andrew Sales

Additional role for partner imprint paperback ISBNs

Revision 1.38 27 November 2017 Andrew Sales

Updated series titles

Revision 1.37 15 November 2017 Andrew Sales

Note added re olink/@type=’glossary’ Section 15.8, “Links to other books”

Revision 1.36 5 October 2017 Andrew Sales

Additional role for partner imprint hardback ISBNs

Revision 1.35 2 October 2017 Andrew Sales

Updated series titles

Revision 1.34 21 July 2017 Andrew Sales

Updated series titles

Revision 1.33 14 July 2017 Andrew Sales

Updated series titles

Revision 1.32 7 July 2017 Andrew Sales

Updated series titles

Revision 1.31 13 April 2017 Andrew Sales

Updated series titles

Revision 1.30 11 April 2017 Andrew Sales

Updated series titles

Revision 1.29 30 March 2017 Andrew Sales

Updated series titles

Revision 1.28 27 March 2017 Andrew Sales

Updated series titles

Revision 1.27 22 March 2017 Andrew Sales

Updated series titles

Revision 1.26 20 March 2017 Andrew Sales

Updated series titles; allowing @outputformat for pubdate and DOIs for sub-articles

Revision 1.25 21 February 2017 Andrew Sales

Updated series titles; added section role for recipes

Revision 1.24 26 January 2017 Andrew Sales

Dedications are allowed directly within book; additional sidebar role values

Revision 1.23 25 July 2016 Brad Scott

Added support for annotated legislation: Section 7.5.11, “Other biblioids”; Section 14.3, “@role attributes”;
Section 14.13, “Notes”; examples in: Section 32.16.8, “Annotated legislation” with an Implementation Note

Revision 1.22 7 July 2016 Brad Scott

Added support for legal Case Reports Section 7.5.11, “Other biblioids”; Section 14.3, “@role attributes”;
Section 14.13, “Notes” And examples in: Section 32.16.7, “Case Reports” with an Implementation Note +
Added support for @label on informalexample (DocBook extension) + Implementation Note: Chapter 28,
Examples

Revision 1.21 25 April 2016 Brad Scott

Amended instructions for bridgehead markup: Section 7.5.15, “Other prelim content”

Revision 1.20 5 April 2016 Brad Scott

Processing instructions must not contain markup or character references: Section 18.2.1, “End of chapter
notes” A book or chunk title must not end with a colon: Section 7.5.1, “Title group”; Section 9.2, “Chunk and
section titles and numbering” Bibliography style (initials with/without stops) can apply at the chunk level:
Section 17.1, “Initials in biblio names”

Revision 1.19 16 February 2016 Brad Scott

schematronVersion MUST = 5, and all IDs MUST now have predictable, consistent structure:Section 5.2, “ID
structure” Block images/tables/sidebars MUST NOT occur within a paragraph:Section 21.4, “Image placement”
A break PI must contain a type: Section 14.5, “Column and line breaks” Notes sections must not have a title in
the end-ch-notes PI: Section 18.2.1, “End of chapter notes” A footnote must not occur within a link: Chapter 18,
Footnotes, endnotes and other notes Rarely, DOIs may not be required: Section 7.5.11, “Other biblioids”

Revision 1.18 11 December 2015 Brad Scott

'Law as stated at date' required for legal texts: Section 32.16.3, “Law stated at date” Numbered lists in legal
texts MUST use variablelist:Section 32.16.6, “Numbered lists in legal books” Small caps must not contain only
upper case content: Section 14.2, “Font styles and font weight” New bibliographic item types: Section 16.13,
“Recordings”, Section 16.14, “Films” 'info' paragraphs: see end of Section 14.1.2, “Paragraphs, vertical white
space and other text separators” Additional clarification on taxon name markup: Section 32.17.3, “Biology-
specific markup” Additional conformancy tests for copyright and ISBNs: Section 7.5.9, “Copyright/CC details”,
Section 7.5.10, “ISBNs, DOI and CIP information”

Revision 1.17 26 November 2015 Brad Scott

Section 9.3.8, “Chunk source and print history”

Revision 1.16 23 November 2015 Brad Scott

Companion website blocks: Section 7.5.6.1, “Companion Website”

Revision 1.15 2 November 2015 Brad Scott

Support for set, pack and other volumes ISBNs: Section 7.5.10, “ISBNs, DOI and CIP information”

Revision 1.14 29 October 2015 Brad Scott

Handling of end-of-paragraph notes (eg as used in legal texts): Section 18.2.3, “End of paragraph notes” New
biblioid (legalContentType) REQUIRED for legal books: Section 7.5.11, “Other biblioids”

Revision 1.13 6/7 October 2015 Brad Scott

Test to ensure that publisher addresses are in the correct location and have the correct content: Section 7.5.6,
“Publisher details”

Revision 1.12 19 September 2015 Brad Scott

Test to ensure correct placement of series data: Section 7.5.4, “Series”

Revision 1.11 19 May 2015 Brad Scott

Tests specifically for biological works comprising taxonomic content (eg Mammals of Africa): Section 14.11,
“Natural history and biology content”; Section 32.17, “Biology and natural history works with taxonomic
content” Tests specifically for Fashion Photography Archive articles

Revision 1.10 1 May 2015 Brad Scott

Improved processing instruction testing (Section 14.10.6, “Processing instructions”) Usually more than one
ISBN is required, and added more clarification about CIP markup (7.5.9 ISBNs, DOI) Clarification about end-
bk-note insert PIs (Section 18.2.2, “End of book notes”)

Revision 1.9 22 April 2015 Brad Scott

Start and end chunk pagenums must match equivalent values in the page PI (Section 9.3.2, “Page range”)
Various minor tests in bibliography content

Revision 1.8 10 April 2015 Brad Scott

The series name MUST exactly match the standard form (Section 7.5.4, “Series”) Abstracts must not contain
indexterms (Section 29.4, “Positioning of index terms”)

Revision 1.7 16 March 2015 Brad Scott

schematronVersion MUST = 4, and chunks and formalparas MUST now have predictable, consistent ID
(Section 5.2.3, “IDs for chunks”) Tests for formalpara//title content (Section 5.2.6, “IDs for formal paragraphs”)
Drama and poetry should usually occur in a blockquote (Section 24.3, “Poetry”) Possible attributions in
lines (Section 24.3.1, “Simple poem”) Paras should not usually start with lower case (see example at end
of Section 14.1.1, “Block elements within paragraphs etc”) Possible missing space (Section 16.16, “Inline
bibliographic references”) Legal monograph examples (Section 32.16, “Hart and Bloomsbury legal texts”)

Revision 1.6 10 March 2015 Brad Scott

Pubdate can take @condition Tests specific to Geographers Biobibliographical series (examples in Section 32.15,
“Geographers Biobibliographical Studies”) New biblioid/@otherclass value of ‘allBiblioItemsUnlinked’ Warns
if there is no series data for academic books

Revision 1.5 29 January 2015 Brad Scott

Chunk IDs MUST begin with the book/@xml:id and schematronVersion MUST equal 3 See: Section 5.2.3, “IDs
for chunks” and Section 7.5.11, “Other biblioids”

Revision 1.4 22 October 2014 Brad Scott

Legal texts. These require careful attention, and include the following features: Numbered paras: Section 14.1.3,
“Formal paragraphs” Special front matter content: Section 10.5, “Tables of cases and statutes” Other, more
complex, features of legal texts remain to be modelled and MUST be referred to Bloomsbury

Revision 1.3 10 September 2014 Brad Scott

Support for bibliographies with no initials in names: biblioType in Section 7.5.11, “Other biblioids” Anchors:
Section 14.12, “Anchors” Special sidebars in some reference content: Section 26.3, “Embedded articles” New
section: Section 9.5.1, “Article @roles”

Revision 1.2 4 September 2014 Brad Scott

How to handle bibliographies with no full stops after the initials: Section 16.1, “Bibliography type”;
Section 17.1, “Initials in biblio names”

Revision 1.1 10 July 2014 Brad Scott

Steps and procedures, eg for practical textbooks: Chapter 27, Steps and procedures Species-specific chapters and
sections (natural history/biology content): Section 14.11, “Natural history and biology content”

Revision 1.0 4 July 2014 Brad Scott

Slightly more fine grained markup and other features for reference works and dictionaries: 9.5.6 Article
components (dictionary-type content) Description of document or chunk keywords: Section 7.5.14,
“Keywords” New @role values for sections and sidebars for special units of content in textbooks: Chapter 26,
Sidebars

Revision 0.27 20 May 2014 Brad Scott

New section to record document revisions: Section 7.5.12, “Revisions” Simple mechanism for indicating that
no digital rights are available for a specific piece of content: Section 14.8, “Rights” New support for sources in
figure captions: Section 21.3, “Image sources” New @role for bibl sections in A-Z articles: Section 9.5.3, “More
complex article and dummy entry” New @role for container for ancillary material: 12.3 Additional media files
(ancillary back-of-book CD content) Outline section on image display: Section 21.1, “Image display” Support
for linking between sections: Section 15.9, “Linking sections and bibliographies”

Revision 0.26 22 April 2014 Brad Scott

Other files that could be within the data package must be within a media directory: Chapter 3, Deliverables and
file-naming conventions. A special back matter container for additional content files: 12.3 Additional media files
(ancillary back-of-book CD content). Linking to such files: Section 15.7, “Links to content in the data package”
(and new implementation note). New section and element (olink): Section 15.8, “Links to other books” (and
new implementation note). Major new worked examples: Section 32.14, “Heavily-designed books”. New
section Section 14.10.5, “Print- or web-only content”, where @outputformat is used for format-specific content.
Updated the list of elements on which @outputformat is permitted: Section 14.7, “@outputformat”. Worked
examples: Section 32.1.1, “Title page and contributors”; Section 32.2.3, “Slightly complex chapter opener style”.

Revision 0.25 4 April 2014 Brad Scott

More robust tests for end-bk-note and end-ch-note footnotes and corresponding processing instructions; and
for book and chunk contributors

Revision 0.24 14 March 2014 Brad Scott

Includes refs to three schematron tests, the most important being end-bk-notes-target

Revision 0.23 24 February 2014 Brad Scott

Included references to minor schematron test changes and additions

Revision 0.22 15 February 2014 Brad Scott

Example for Section 32.2.5, “Chapter Outlines and Abstracts”, and note especially that Chapter Outlines are
NOT to be included in the data if only a ToC: Section 9.4.1, “Chapter Outlines” Asterisks, daggers etc probably
need to be links: Section 14.10.4, “Asterisks etc” Clarification on use of bibliolist[@role=inline]: Section 16.4,
“Bibliographic items” Untagged biblio content: Section 16.6, “Untagged bibliographic content” More examples
added to: Section 14.10.1, “Spaces and emphasis”; Section 21.2, “Image captions”; Section 32.6.2, “Firstname/
surname issues”; Section 32.6.3, “Sibling elements of bibliomset”

Revision 0.21 10 February 2014 Brad Scott

Extended the tests for page break placement: Section 14.4, “Page breaks”, and examples in Section 32.13,
“Page break placement” Additional examples: Section 32.2.4, “Non-sequential heading style”; Section 32.6.1,
“Inconsistent biblio style” Bibliography examples: Section 16.8.3.5, “Book reviews”, Section 16.15.3, “DVDs”

Revision 0.20 29 January 2014 Brad Scott

IMPORTANT: New @role on link now REQUIRED for all new books (but not necessarily for retrospective
conversion projects). This is to support better testing for internal link targets and for which setting
schematronVersion=”2” is REQUIRED. See sections Section 15.1, “Simple internal links” and Section 7.5.11,
“Other biblioids” Restructured section Chapter 17, Names, and added Section 17.3.1, “Confusion between
surnames and firstnames”, which includes a test for strings that look like firstnames encoded as surname; this
will give false positives, and will be refined, but does give a useful means of checking some more complex
bibliographic markup. Worked examples: Section 32.3, “Chapters with appendices etc”; Section 32.5.2, “Same
work in multiple bibliomixeds” Comments are to be avoided: Section 14.10.3, “Comments” Schematron
includes count and percentage of unlinked biblio items: Section 16.3.1, “Standard short form references” Page
break markers must be between sections not in section titles: Section 14.4, “Page breaks”

Revision 0.19 21 January 2014 Brad Scott

Handling of impression numbers in prelims: Section 10.2.1, “Impressions” Initial proposal for some video
support, though this is not yet ready for use: Chapter 22, Other media content Added refs to new tests.

Revision 0.18 13 January 2014 Brad Scott

Blockquote attributions must be within attribution not para[@role=right]: see section Section 24.1,
“Blockquotes”. Inline abbreviations may be marked up with abbrev: see at the end of section Section 10.8,
“Glossaries and abbreviations lists” Title page logo: Section 7.5.8, “Imprint logo” New bibliography example:
Section 16.10, “Email messages” More examples of short-form links: section Section 32.5.1, “Short-form
bibliographic references” An example of archival lists within a bibliography: Section 32.12.1, “Archive list”

Revision 0.17 19 December 2013 Brad Scott

New major section: 9.5 A-Z (reference) content Minor notes for new schematron tests

Revision 0.16 13 December 2013 Brad Scott

Permitted @mark=none for itemizedlists, see section 19.2 Unordered (bulleted) lists New worked examples:
Section 32.1, “Front matter”; Section 32.2.2, “More unusual structure and labels”; Section 32.7, “Lists”;
Section 32.9, “Appendices”; Section 32.10.1, “Different fonts in fiction” Minor notes documenting new
schematron tests, especially for bibliographic items and names

Revision 0.15 2 December 2013 Brad Scott

New major section: Chapter 32, Worked examples A new DocBook extension: Section 2.1.1, “Extensions to
DocBook Publishers schema” Further clarifications and examples with refs to additional tests: Chapter 4,
Encoding; Section 4.1, “Right-to-left writing systems”; Section 7.4, “Digital-only books”; Section 7.5.2,
“Author group”; Section 7.5.6, “Publisher details”; Section 7.5.11, “Other biblioids”; Section 9.2, “Chunk and
section titles and numbering”; Section 9.2.1, “Chunks with no titles”; Section 9.3.7, “Running headers and
footers”; Section 11.4, “General use of @label”; Section 14.1.2, “Paragraphs, vertical white space and other
text separators”; Section 14.7, “@outputformat”; Section 14.10, “General text issues”; Section 16.5, “Dates
in bibliographies”; Chapter 17, Names; Section 21.6, “Plate sections”; more bibliography examples: Play
performances,radio broadcasts etc, Section 16.9.2, “Personal communications”, Section 16.9.4, “Conference
papers, other meetings and reports” (including document reference numbers),

Revision 0.14 14 October 2013 Brad Scott

Minor additions and expansions, tests

Revision 0.13 3 October 2013 Brad Scott

Expanded Chapter 29, Indexes and index terms, and numerous Schematron cross references. Added new @role
on end book and end chapter Notes sections (Section 18.2, “Note placement”)

Revision 0.12 25 September 2013 Brad Scott

Simplified options for internal linking, so now only use link, not biblioref and xref, see Chapter 15, Cross
references and linking and Section 16.3, “Inline citations”. Added Section 15.6, “DOI links”; Section 5.2.5, “IDs for
bibliographic items”; Section 16.19, “Non-permitted content of bibliographic items”; Chapter 31, Schematron.
Changed title of prelims chunk (Section 10.3, “Prelims chunk”). Modified requirements for Section 7.5.2,
“Author group”. Minor revisions to: Section 7.5.6, “Publisher details” (more examples); Section 10.4, “Table
of contents” (needs further expansion); Section 14.4, “Page breaks” (more detail on placement); Section 16.4,
“Bibliographic items” (many examples have more detail and links to tests); Chapter 21, Figures and images
(@outputformat); Chapter 29, Indexes and index terms (needs further expansion). Added many more cross refs to
the Schematron tests, and expanded test coverage.

Revision 0.11 10 September 2013 Brad Scott

Added journal issue example in Section 16.8, “Journals” and conference example in Section 16.9,
“Unpublished”; new section Section 14.9, “Addresses”; added xrefs in Section 14.3, “@role attributes”; + other
bibliography examples: Section 16.7.7, “Anonymous items and “et al””, Section 16.7.11, “Ibid, loc cit, and op.
cit.”, Section 16.8.3.3, “Newspaper item”, Section 16.11.2, “Minimal web site reference”;
Revision 0.10 3 September 2013 Brad Scott

New section Section 7.5.11, “Other biblioids”. Added clarification to [deleted sections]. Added bibliosource to
Chapter 30, Elements we might not need we might not need.

Revision 0.9 15 August 2013 Brad Scott

Added clarification on Bloomsbury Open legalnotice markup (Section 7.5.9, “Copyright/CC details”); case
regularisation (Section 8.1, “Case regularisation”)

Revision 0.8 30 July 2013 Brad Scott

Beta release to supplier. Added note on @condition, updated ID requirements, added more detail on chunking,
minor bibliography-related revisions

Revision 0.7 19 July 2013 Brad Scott

Released for supplier review. Taken in feedback from Propagator/editorial. Added material on blockquotes,
drama, poetry, and moved epigraphs to same section. Updated ID requirements, and book/info, edition, series.
Small-scale restructuring, amending.

Revision 0.6 15 July 2013 Brad Scott

Released for Propagator and internal review. Added/extended sections on: inline bibliographies; footnotes/end
notes; equations; deliverables

Revision 0.5 12 July 2013 Brad Scott

For Akan, internal review

Revision 0.4 27 June 2013 Brad Scott

As released to data suppliers

Revision 0.3 25 June 2013 Brad Scott

@role; figures (formats); some additions to bibliographic markup

Revision 0.2 14 June 2013 Brad Scott

First release

Revision 0.1 8 May 2013 Brad Scott

Created
Table of Contents
Release notes: Schematron schema version 8 ............................................................................ xviii
1. Background ............................................................................................................................. 1
1.1. Principles ...................................................................................................................... 2
2. Schema .................................................................................................................................... 3
2.1. Local modifications ....................................................................................................... 3
2.1.1. Extensions to DocBook Publishers schema ........................................................... 3
2.1.2. Constraints on the DocBook Publishers schema .................................................... 3
3. Deliverables and file-naming conventions ................................................................................. 4
3.1. Platform-specific considerations ..................................................................................... 4
4. Encoding ................................................................................................................................. 6
4.1. Right-to-left writing systems .......................................................................................... 6
5. Identifiers ................................................................................................................................ 7
5.1. Where IDs are required ................................................................................................. 7
5.2. ID structure .................................................................................................................. 7
5.2.1. Previous instructions .......................................................................................... 8
5.2.2. IDs for the book and set ..................................................................................... 8
5.2.3. IDs for chunks .................................................................................................... 8
5.2.4. IDs for glossary terms ......................................................................................... 9
5.2.5. IDs for bibliographic items ................................................................................ 10
5.2.6. IDs for formal paragraphs ................................................................................. 10
5.2.7. IDs for annotated legislation .............................................................................. 11
5.3. Identifier Persistence .................................................................................................... 11
5.3.1. Chunks ............................................................................................................. 12
5.3.2. Tables and figures ............................................................................................. 12
5.3.3. ID report on re-supply ...................................................................................... 12
6. Root elements ........................................................................................................................ 18
7. Book and set metadata ........................................................................................................... 19
7.1. The relationship between the prelims and book metadata .............................................. 19
7.2. Language metadata ..................................................................................................... 19
7.3. Content type ............................................................................................................... 19
7.4. Digital-only books ....................................................................................................... 20
7.5. Metadata ..................................................................................................................... 20
7.5.1. Title group ....................................................................................................... 21
7.5.2. Author group ................................................................................................... 22
7.5.3. Edition ............................................................................................................. 25
7.5.4. Series ................................................................................................................ 25
7.5.5. Publication date ................................................................................................ 26
7.5.6. Publisher details ............................................................................................... 26
7.5.7. Studio content ................................................................................................... 29
7.5.8. Imprint logo ..................................................................................................... 29
7.5.9. Copyright/CC details ........................................................................................ 29
7.5.10. ISBNs, DOI and CIP information ...................................................................... 31
7.5.11. Other biblioids ................................................................................................ 33
7.5.12. Revisions ........................................................................................................ 36
7.5.13. Blurb/abstract .................................................................................................. 37
7.5.14. Keywords ....................................................................................................... 37
7.5.15. Other prelim content ....................................................................................... 37
8. Editorial standardisation ........................................................................................................ 40
8.1. Case regularisation ...................................................................................................... 40
9. Chunking and high-level structure ......................................................................................... 41
9.1. Chunking example ...................................................................................................... 41
9.2. Chunk and section titles and numbering ...................................................................... 44
9.2.1. Chunks with no titles ........................................................................................ 46
9.3. Chunk metadata .......................................................................................................... 46
9.3.1. Chunk author(s) ................................................................................................ 46

xi
 Bloomsbury DocBook XML

9.3.2. Page range ........................................................................................................ 48

9.3.3. PDF file reference and file naming ..................................................................... 49
9.3.4. Chunk DOI ....................................................................................................... 50
9.3.5. Chunk abstract/extract ....................................................................................... 51
9.3.6. Keywords ......................................................................................................... 51
9.3.7. Running headers and footers ............................................................................. 51
9.3.8. Chunk source and print history ......................................................................... 52
9.4. Chunk content ............................................................................................................. 52
9.4.1. Chapter Outlines ............................................................................................... 52
9.5. A-Z (reference) content ................................................................................................ 52
9.5.1. Article @roles .................................................................................................... 53
9.5.2. General A-Z reference content ........................................................................... 53
9.5.3. More complex article and dummy entry ............................................................. 55
9.5.4. Article parts and dummy headings .................................................................... 57
9.5.5. High-level structure (A-Z container) .................................................................. 59
9.5.6. Article components (dictionary-type content) ..................................................... 60
10. Front matter ......................................................................................................................... 64
10.1. Front matter container ............................................................................................... 64
10.2. Colophon .................................................................................................................. 65
10.2.1. Impressions ..................................................................................................... 65
10.3. Prelims chunk ........................................................................................................... 65
10.4. Table of contents ........................................................................................................ 66
10.4.1. ToC contents ................................................................................................... 66
10.5. Tables of cases and statutes ........................................................................................ 67
10.6. Dedication ................................................................................................................. 68
10.7. Acknowledgements .................................................................................................... 69
10.8. Glossaries and abbreviations lists ............................................................................... 70
10.9. Prefaces ..................................................................................................................... 72
11. Introductions, chapters, parts, titles and @labels ..................................................................... 73
11.1. Usage of chapter and part elements ............................................................................ 73
11.2. Introductions ............................................................................................................. 73
11.3. Chapter and Part labelling ......................................................................................... 74
11.4. General use of @label ................................................................................................. 74
12. Back matter .......................................................................................................................... 76
12.1. Back matter container ................................................................................................ 76
12.2. Back matter elements ................................................................................................. 76
12.3. Additional media files (ancillary back-of-book CD content) .......................................... 77
13. Multi-volume works ............................................................................................................. 78
14. Common components ........................................................................................................... 79
14.1. Paragraphs ................................................................................................................ 79
14.1.1. Block elements within paragraphs etc ............................................................... 79
14.1.2. Paragraphs, vertical white space and other text separators ................................. 80
14.1.3. Formal paragraphs .......................................................................................... 84
14.2. Font styles and font weight ........................................................................................ 85
14.3. @role attributes .......................................................................................................... 86
14.4. Page breaks ............................................................................................................... 91
14.5. Column and line breaks ............................................................................................. 92
14.6. Conditional processing with @condition ...................................................................... 93
14.7. @outputformat ........................................................................................................... 94
14.8. Rights ........................................................................................................................ 94
14.9. Addresses .................................................................................................................. 94
14.10. General text issues ................................................................................................... 95
14.10.1. Spaces and emphasis ..................................................................................... 95
14.10.2. Minimal content in emphasis ......................................................................... 96
14.10.3. Comments ..................................................................................................... 96
14.10.4. Asterisks etc .................................................................................................. 96
14.10.5. Print- or web-only content ............................................................................. 96
14.10.6. Processing instructions ................................................................................... 97

xii
 Bloomsbury DocBook XML

14.11. Natural history and biology content .......................................................................... 97

14.12. Anchors ................................................................................................................... 98
14.13. Notes ....................................................................................................................... 98
15. Cross references and linking ............................................................................................... 100
15.1. Simple internal links ................................................................................................ 100
15.2. Glossary links .......................................................................................................... 101
15.3. Links to page numbers ............................................................................................. 102
15.4. Internal links with generated text .............................................................................. 102
15.4.1. footnoteref ..................................................................................................... 102
15.5. External links ........................................................................................................... 102
15.5.1. Embedded links (online only) ......................................................................... 103
15.5.2. Other uses ..................................................................................................... 103
15.6. DOI links ................................................................................................................. 103
15.7. Links to content in the data package ......................................................................... 103
15.8. Links to other books ................................................................................................ 104
15.9. Linking sections and bibliographies .......................................................................... 105
16. Bibliographies and components ........................................................................................... 107
16.1. Bibliography type ..................................................................................................... 107
16.2. Bibliography container ............................................................................................. 107
16.3. Inline citations ......................................................................................................... 108
16.3.1. Standard short form references ....................................................................... 108
16.3.2. Irregular cross references ............................................................................... 110
16.3.3. Application of biblio references ...................................................................... 110
16.4. Bibliographic items .................................................................................................. 111
16.4.1. Language ...................................................................................................... 112
16.4.2. @xml:id ......................................................................................................... 112
16.4.3. @role ............................................................................................................. 112
16.4.4. Personal names .............................................................................................. 113
16.5. Dates in bibliographies ............................................................................................. 113
16.6. Untagged bibliographic content ................................................................................ 114
16.7. Books ...................................................................................................................... 115
16.7.1. Single author book ........................................................................................ 115
16.7.2. Single author book with surname first ............................................................ 116
16.7.3. Multiple editors ............................................................................................. 116
16.7.4. Chapter in edited book .................................................................................. 116
16.7.5. Multiple editions ........................................................................................... 117
16.7.6. Item in a numbered volume, with annotation .................................................. 117
16.7.7. Anonymous items and “et al” ........................................................................ 118
16.7.8. Publisher address .......................................................................................... 118
16.7.9. Work within a book ....................................................................................... 118
16.7.10. Implied authors (books) ............................................................................... 118
16.7.11. Ibid, loc cit, and op. cit. ................................................................................ 119
16.7.12. Classical authors/single names + series .......................................................... 120
16.7.13. Reprint ........................................................................................................ 120
16.7.14. Online version of a text ................................................................................ 120
16.7.15. Multi-volume, abbreviated form and translated versions ................................ 121
16.7.16. Other editions .............................................................................................. 121
16.8. Journals ................................................................................................................... 121
16.8.1. Journal issue .................................................................................................. 121
16.8.2. Standard journal article .................................................................................. 122
16.8.3. Journal article with URL ................................................................................ 122
16.9. Unpublished ............................................................................................................ 124
16.9.1. Thesis ............................................................................................................ 124
16.9.2. Personal communications ............................................................................... 124
16.9.3. Interviews ..................................................................................................... 124
16.9.4. Conference papers, other meetings and reports ............................................... 124
16.10. Email messages ...................................................................................................... 125
16.11. Web sites ................................................................................................................ 125

xiii
 Bloomsbury DocBook XML

16.11.1. Article on web with access date .................................................................... 125

16.11.2. Minimal web site reference ........................................................................... 126
16.11.3. Music .......................................................................................................... 126
16.12. Legal references ...................................................................................................... 126
16.12.1. Cases ........................................................................................................... 126
16.12.2. Legislation and other statutory instruments ................................................... 127
16.13. Recordings ............................................................................................................. 128
16.14. Films ...................................................................................................................... 128
16.15. Other items ............................................................................................................ 128
16.15.1. Reports and organisation names ................................................................... 128
16.15.2. Play performances, radio broadcasts etc ........................................................ 129
16.15.3. DVDs .......................................................................................................... 129
16.16. Inline bibliographic references ................................................................................. 129
16.17. Abbreviated forms .................................................................................................. 131
16.18. Annotated bibliographies ........................................................................................ 131
16.19. Non-permitted content of bibliographic items .......................................................... 132
17. Names ................................................................................................................................ 133
17.1. Initials in biblio names ............................................................................................. 133
17.2. Overview of name markup ....................................................................................... 133
17.3. Specific name encoding issues .................................................................................. 135
17.3.1. Confusion between surnames and firstnames .................................................. 135
17.3.2. Lineage and honorific .................................................................................... 136
17.3.3. Other name mark-up issues ........................................................................... 136
18. Footnotes, endnotes and other notes .................................................................................... 137
18.1. Notes content ........................................................................................................... 138
18.1.1. Note with link to bibliography ....................................................................... 138
18.1.2. Note with a bibliographic reference ................................................................ 138
18.1.3. Notes with a bibliographic item ..................................................................... 138
18.1.4. Ibids, loc cits and op cits in footnotes ............................................................. 139
18.1.5. A footnote sequence ...................................................................................... 139
18.1.6. Further examples ........................................................................................... 140
18.1.7. Incorrect footnote markup .............................................................................. 141
18.2. Note placement ........................................................................................................ 142
18.2.1. End of chapter notes ...................................................................................... 142
18.2.2. End of book notes ......................................................................................... 143
18.2.3. End of paragraph notes ................................................................................. 144
18.3. Marginal notes ......................................................................................................... 145
19. Lists ................................................................................................................................... 146
19.1. Simple lists .............................................................................................................. 146
19.2. Unordered (bulleted) lists ......................................................................................... 146
19.3. Ordered (numbered) lists ......................................................................................... 147
19.4. Variable lists ............................................................................................................ 148
20. Tables ................................................................................................................................. 149
20.1. Table placement ....................................................................................................... 151
21. Figures and images ............................................................................................................. 152
21.1. Image display .......................................................................................................... 153
21.2. Image captions ......................................................................................................... 153
21.3. Image sources .......................................................................................................... 154
21.4. Image placement ...................................................................................................... 155
21.5. Image alt text ........................................................................................................... 155
21.6. Plate sections ........................................................................................................... 156
22. Other media content ........................................................................................................... 157
22.1. Video ....................................................................................................................... 157
22.1.1. Embedded video ........................................................................................... 157
22.1.2. Reference by ID ............................................................................................. 157
22.2. Audio ...................................................................................................................... 157
22.2.1. Reference by ID ............................................................................................. 157
23. Equations ........................................................................................................................... 158

xiv
 Bloomsbury DocBook XML

23.1. Equation basics ........................................................................................................ 158

23.2. Simple equations ...................................................................................................... 158
23.3. More complex equations .......................................................................................... 158

23.4. equations ................................................................................................ 160

24. Blockquotes, epigraphs, poetry and drama ........................................................................... 162
24.1. Blockquotes ............................................................................................................. 162
24.2. Epigraphs ................................................................................................................ 162
24.3. Poetry ...................................................................................................................... 163
24.3.1. Simple poem ................................................................................................. 163
24.3.2. Poem with verses ........................................................................................... 164
24.3.3. Line formatting ............................................................................................. 164
24.3.4. More complex poems, and line numbers ......................................................... 165
24.3.5. Poem with epigraph ...................................................................................... 166
24.4. Drama ..................................................................................................................... 166
24.4.1. Simple dramatic text ...................................................................................... 167
24.4.2. Line following speaker in dramatic text .......................................................... 167
24.4.3. Split lines ...................................................................................................... 167
24.4.4. More complex dramatic work ......................................................................... 168
24.4.5. Screenplay excerpts ....................................................................................... 169
24.5. Incorrect block markup ............................................................................................ 169
25. Interviews, questions/answers ............................................................................................. 171
26. Sidebars ............................................................................................................................. 172
26.1. Simple sidebars ........................................................................................................ 172
26.2. Semantic sidebars in textbooks ................................................................................. 174
26.3. Embedded articles .................................................................................................... 174
26.4. Sidebar placement .................................................................................................... 174
27. Steps and procedures .......................................................................................................... 175
28. Examples ............................................................................................................................ 176
29. Indexes and index terms ..................................................................................................... 177
29.1. Index chunk ............................................................................................................. 177
29.2. Multiple indexes ...................................................................................................... 177
29.3. Types of index terms ................................................................................................ 178
29.4. Positioning of index terms ........................................................................................ 178
29.5. Cross references within an index .............................................................................. 179
29.5.1. “see” in index ................................................................................................ 179
29.5.2. “see also” in index ......................................................................................... 179
30. Elements we might not need ............................................................................................... 180
31. Schematron ........................................................................................................................ 181
32. Worked examples ............................................................................................................... 183
32.1. Front matter ............................................................................................................. 183
32.1.1. Title page and contributors ............................................................................ 183
32.1.2. Book lists ...................................................................................................... 183
32.1.3. CIP block ...................................................................................................... 184
32.2. Parts, chunks and labels ........................................................................................... 185
32.2.1. Unusual part structure and labels ................................................................... 185
32.2.2. More unusual structure and labels .................................................................. 187
32.2.3. Slightly complex chapter opener style ............................................................. 189
32.2.4. Non-sequential heading style ......................................................................... 190
32.2.5. Chapter Outlines and Abstracts ...................................................................... 191
32.3. Chapters with appendices etc ................................................................................... 193
32.4. Glossary .................................................................................................................. 195
32.5. Linking .................................................................................................................... 196
32.5.1. Short-form bibliographic references ................................................................ 196
32.5.2. Same work in multiple bibliomixeds ............................................................... 197
32.6. Bibliographies .......................................................................................................... 198
32.6.1. Inconsistent biblio style .................................................................................. 198
32.6.2. Firstname/surname issues .............................................................................. 198

xv
 Bloomsbury DocBook XML

32.6.3. Sibling elements of bibliomset ........................................................................ 199

32.7. Lists ........................................................................................................................ 200
32.7.1. A simple list with title, columns and notes ...................................................... 200
32.8. Tables ...................................................................................................................... 201
32.8.1. A relatively simple table ................................................................................ 201
32.9. Appendices .............................................................................................................. 205
32.9.1. Lists and spacing 1 ........................................................................................ 206
32.9.2. Lists and spacing 2 ........................................................................................ 207
32.9.3. Lists and spacing 3 ........................................................................................ 208
32.10. Complex and unusual layouts ................................................................................. 209
32.10.1. Different fonts in fiction ............................................................................... 210
32.10.2. Linguistic example 1 .................................................................................... 211
32.10.3. Linguistic example 2 .................................................................................... 211
32.11. Poetry .................................................................................................................... 213
32.11.1. Marginal line numbers, spacing and translation ............................................. 213
32.12. References .............................................................................................................. 214
32.12.1. Archive list .................................................................................................. 214
32.13. Page break placement ............................................................................................. 215
32.13.1. Page breaks and back-of-book/end-of-chapter notes ....................................... 215
32.13.2. Footnotes and page breaks ........................................................................... 216
32.14. Heavily-designed books .......................................................................................... 218
32.14.1. Part divider with quote ................................................................................ 218
32.14.2. Subsequent part content ............................................................................... 219
32.14.3. Content chunks ............................................................................................ 220
32.14.4. Chunk content ............................................................................................. 221
32.14.5. Print-specific content .................................................................................... 221
32.15. Geographers Biobibliographical Studies ................................................................... 222
32.15.1. Series data ................................................................................................... 222
32.15.2. Cross references to other books in the series .................................................. 222
32.15.3. Implied authors in bibliographies ................................................................. 223
32.16. Hart and Bloomsbury legal texts ............................................................................. 224
32.16.1. Legal content type ....................................................................................... 224
32.16.2. More strict ID rules ...................................................................................... 224
32.16.3. Law stated at date ....................................................................................... 224
32.16.4. Legal contents .............................................................................................. 225
32.16.5. Numbered paragraphs ................................................................................. 226
32.16.6. Numbered lists in legal books ...................................................................... 227
32.16.7. Case Reports ................................................................................................ 228
32.16.8. Annotated legislation ................................................................................... 230
32.17. Biology and natural history works with taxonomic content ....................................... 232
32.17.1. Structure of chunks ...................................................................................... 232
32.17.2. High-level data requirements ........................................................................ 234
32.17.3. Biology-specific markup ............................................................................... 234
33. Series names ....................................................................................................................... 237
34. Accessibility ....................................................................................................................... 258
34.1. Alt text for images and other items ........................................................................... 258
34.1.1. Example usage .............................................................................................. 258
I. Back matter .......................................................................................................................... 260
Index ............................................................................................................................... 262

xvi
List of Examples
5.1. ID change report ................................................................................................................. 14
5.2. Structural change ................................................................................................................. 15
5.3. Textual change ..................................................................................................................... 16
34.1. Table ................................................................................................................................ 258
34.2. Informal table .................................................................................................................. 258
34.3. Display images ................................................................................................................ 259
34.4. Inline images ................................................................................................................... 259
34.5. Equations ......................................................................................................................... 259
34.6. Informal equations ........................................................................................................... 259
34.7. Video ............................................................................................................................... 259
34.8. Audio .............................................................................................................................. 259

xvii
Release notes: Schematron schema
version 8
This version of the schema, which MUST be used for all new supplies, requires:

• supplier details, to be included in the book-level metadata;

• biographical information for contributors at the chunk level, where available.

xviii
Chapter 1. Background
This document specifies the usage of the DocBook Publishers schema within Bloomsbury.

It substantially draws on and replaces the existing Bloomsbury DocBook documentation1, and

• provides further detailed examples of REQUIRED usage

• indicates where previous usage is now DEPRECATED and what the new REQUIREMENT is

In the past, the DocBook Publishers schema was used at Bloomsbury for the Bloomsbury Academic
website content, which contained Open Access (Bloomsbury Open) content, using this model. The
model was subsequently also utilised for the non play text content in Bloomsbury’s Drama Online.

The model as now described by this document updates the previous usage, and is also to be used for
the new Bloomsbury Collections site.

The revised schema as described in this document is a true subset of the previous instance of the
DocBook Publishers schema in use at Bloomsbury2. However, data captured using the previous
version will not validate against the new version because the new version includes:

• More defined attribute values to enforce consistency

• Places where some attributes are now REQUIRED

Furthermore, these new instructions include places where elements MUST be used, though may
not previously have been so in the past (for example, the addition of chunk metadata as described in
Section 9.3, “Chunk metadata”).

This document notes the corresponding paragraph number in the previous Bloomsbury DocBook
documentation, and particularly notes where this document departs from it. References to the
previous documentation is in the form “§1.2”. See also the Index to locate references to the previous
documentation.

Sections that were not covered at all in the previous documentation (even if they are completely
standard DocBook) are:

• Section 7.3, “Content type”

• Section 7.5.3, “Edition”

• Section 7.5.4, “Series”

• Section 7.5.13, “Blurb/abstract”

• Section 7.5.15, “Other prelim content”

• Chapter 9, Chunking and high-level structure

• Section 10.1, “Front matter container”

• Section 10.2, “Colophon”

• Section 10.4, “Table of contents”

• Chapter 11, Introductions, chapters, parts, titles and @labels

• Chapter 12, Back matter

1
Nic Gibson. ‘Bloomsbury Academic: Digital Content Specifications’. 10 May 2010
2
With three exceptions, see Section 2.1.1, “Extensions to DocBook Publishers schema”

1
 Background

• Chapter 13, Multi-volume works

• Section 14.1.2, “Paragraphs, vertical white space and other text separators”

• Section 14.3, “@role attributes”

• Section 14.4, “Page breaks”

• Section 14.5, “Column and line breaks”

• Section 15.2, “Glossary links”

• Chapter 19, Lists

• Chapter 20, Tables

• Chapter 23, Equations

• Chapter 25, Interviews, questions/answers

• Chapter 26, Sidebars

This document also includes several “Implementation notes”; these are for the benefit of suppliers
who will consume data provided to this specification, and note where extensions and modifications
will be required to the standard DocBook XSL toolkit. They are listed in the Index.

1.1. Principles
The following guiding principles have been adopted in compiling these data instructions and
examples:

1. Adopt standard DocBook practice as is supported by the latest DocBook XSL tools as much as
possible, and document any deviations from such usage

2. Broadly speaking, all text, punctuation and formatting (italicisation, bold, small caps etc) within a
book MUST be captured within the XML so that the data as it appeared in print can be reproduced
exactly. However, the following items MUST NOT be captured in the data and will be generated
by the application UNLESS otherwise instructed for a specific book:

a. Generic heading styles

b. List labels

c. Footnote and endnote numbering

d. Page layout templates

3. The previous item does not mean that we should slavishly attempt to replicate the book in the
exact data order as was manifested in the print edition, especially in respect of the metadata/
prelims content, since the print edition is just one manifestation of how the book data can be
presented. The requirement is that the printed edition can be generated from the data.

4. Adopt previous Bloomsbury usage if it does not conflict with the previous items. Where the new
instructions deviate from previous usage, this will be clearly indicated

5. If there is more than one way a specific feature could be marked up with standard DocBook, these
instructions will provide the REQUIRED form

2
Chapter 2. Schema
Ref: §1.2

All files MUST validate against the DocBook Publishers schema (rnc format), version 5.1CR (25 June
2013),1 with the local modifications as defined in the latest version of bloomsbury-mods.rnc.

2.1. Local modifications

Ref: §1.3

The local modifications comprise the following:

2.1.1. Extensions to DocBook Publishers schema

Change Rationale
footnote/@label changed from NMTOKEN to allow for dagger/asterisk etc
to text
Added part into db.components to allow for nested major divisions within books
Extended content model of formalpara to allow for more complex structuring in legal
texts
Allowed @label on informalexample So is consistent with the other informal elements

2.1.2. Constraints on the DocBook Publishers schema

Change See section
Enforce IDs in some places
Enforce @role values Section 14.3, “@role attributes”
Enforce values of @condition
Enforce values of @relation

In addition, a Schematron is provided, which extends the tests for the data. This builds on the
previously available suite, and this document also records where such tests have been provided.

Such Schematron tests are recorded in the footnotes and the index.

1
Available from http://www.docbook.org/xml/publishers/5.1CR1/. See also the documentation (not quite for the
same version): http://www.docbook.org/tdg5/publishers/5.1b3/en/html/docbook.html

3
Chapter 3. Deliverables and file-
naming conventions
Ref: §3.1, §1.21

NOTE: This differs from the previous instructions

Books MUST be supplied as a single XML file, named [ISBN13]_txt_xml.xml, where the ISBN
is the eISBN for the XML format and MUST match the //biblioid[@role=xml] (though without
spaces/hyphens) for the book.

Important
Other than XML files referenced by means of XInclude from this file, there MUST NOT
be any other XML files present anywhere in the zip.

Book data packages MUST be supplied in the following structure within a zip file
([ISBN13]_txt_xml.zip):

• [ISBN13]_txt_xml.xml

• images/

• pdfs/

• media/

All images files of whatever format called from within the XML file MUST be within the images/
directory, including the cover image (with filename [XML-ISBN13].jpg [specify size]); and all pdf
chunk files MUST be within the pdfs/ directory. Other media files (eg audio, video, Excel, Word,
any of which could potentially be bundled with a book, ie if it is otherwise bundled on a back-of-the
book CD) MUST be within the media/ directory.

PDF files of each chunk MUST usually follow the following numbering sequence:

[ISBN13]-nnn1.pdf

where the ISBN is the eISBN of the XML format (same as the book), followed by a zero-padded
number, which matches the chunk DOI (for those chunks that have DOIs; note that not all chunks
require a DOI, see Section 9.3.4, “Chunk DOI”, though all chunks REQUIRE a PDF). Chunks with
@labels MUST follow the numbering scheme as laid out in Section 9.1, “Chunking example”, eg:

[ISBN13].ch-nnn1.pdf

3.1. Platform-specific considerations

Important
Certain titles are for publication on the Bloomsbury Collections platform.

Bloomsbury will advise if this applies.

Where this is the case, the XML MUST contain the following metadata flag:

<biblioid class='other' otherclass='targetPlatform'>https://www.bloomsburycollections.com/</

biblioid>

4
 Deliverables and file-
naming conventions

This ensures that further checks are performed on the digital bundle. See also
Section 7.5.11, “Other biblioids”.

5
Chapter 4. Encoding
Ref: §1.22, §1.23, §1.24

XML files MUST be encoded using UTF8.

Since the content is to be encoded using Unicode encoding, character or numeric entities MUST NOT
be used. All characters should be marked-up directly.

When ligatures are used in the text for AE, ae, OE, and oe these MUST be entered using the Unicode
characters: Æ, æ, Œ and œ. Ligatures introduced as part of typesetting, such as ff, fi, fl, ffi, and ffl,
MUST be encoded using the individual letters and not the Unicode characters for these ligatures.1

Occasionally, as a result of conversion (especially from data derived from Biblio), some escaped
entities, encoding and characters may be inadvertently introduced into the data. These MUST be
cleaned up and correct Unicode used.2

4.1. Right-to-left writing systems

Occasionaly, some texts may include quotations or more extended material in a language that uses a
right-to-left writing system. In such cases (notably Arabic and Hebrew), such text MUST be enclosed
within a foreignphrase element,3 use the correct @xml:lang value for that language4 and set
@dir=’rtl’.5

<foreignphrase xml:lang="he" dir="rtl">‫<יבתר יהו‬/foreignphrase>

Tip:

When keying right-to-left text, it can be easier if you use character references though you MUST
put them in left-to-right sequence, which means that the rendering engine (HTML etc) will
reverse the entire sequence and hence display them correctly. For example, here is an example
which starts with an alef character (&#x05D0; -- ‫)א‬, and when it is rendered it is at the right-
hand end of the string:

<foreignphrase xml:lang="he" dir="rtl">

&#x05D0;&#x05DC;&#x05D4;&#x0020;&#x05EA;&#x05D5;&#x05DC;&#x05D3;&#x05D5;&#x05EA;
</foreignphrase>

See also Section 7.2, “Language metadata”

Implementation note: Ensure that @dir is supported in any downstream processing, and that
the default DocBook styling of foreignphrase is switched off

1
Tested in Schematron: ligature-ff and accompanying rules
2
Tested in Schematron: ampersand, less-than, greater-than, em-ghost [and related tests for strong, div, b, i,
br and common HTML entities]
3
Tested in Schematron: hebrew, arabic
4
Tested in Schematron: foreignphrase-lang, foreignphrase-he, foreignphrase-ar
5
Tested in Schematron: rtl-scripts, non-rtl-scripts

6
Chapter 5. Identifiers
5.1. Where IDs are required
Ref: §1.14

The following elements MUST have IDs (@xml:id) (though if any occur within a bibliomixed
they are NOT REQUIRED therein):1

abstract acknowledgements address anchor

appendix article bibliodiv biblioentry
bibliography bibliolist bibliomixed bibliomset
biblioset blockquote bridgehead book
callout calloutlist caption caution
chapter colophon cover dedication
dialogue drama entry epigraph
equation example figure footnote
formalpara glossary glossdef glossdiv
glossentry glosslist glosssee glossseealso
imageobjectco imageobject inlineequation index
indexdiv indexterm info informalequation
informalexample informalfigure informaltable inlinemediaobject
itemizedlist itermset keyword keywordset
legalnotice line linegroup listitem
mathphrase mediaobject member orderedlist
para part partintro personblurb
poetry preface primaryie printhistory
qandadiv qandaentry qandaset secondaryie
section seealsoie seeie set
setindex sidebar simpara simplelist
simplesect speaker subtitle table
term tertiaryie title toc
variablelist

5.2. ID structure
Ref: §1.15, §1.17, §1.18, §1.19, §1.20

NOTE: This differs from the previous instructions

Other than as described in the following sections, all identifiers simply need to be XML IDs (ie unique
within the document), which is enforced in the schema.
1
Tested in Schematron: missing_id_rule

7
 Identifiers

The @xml:id MUST be in the following form:

[book/@xml:id]-uniqueValue

and schematronVersion must be set to '5' (see Section 7.5.11, “Other biblioids”).2

5.2.1. Previous instructions

This section is included for reference only, for existing works with schematronVersion < 5.
FOR ALL NEW DATA THIS SECTION IN GREY IS NOW INVALID.

THIS INSTRUCTION HAS BEEN SUPERSEDED It is preferable that IDs are not over-long, so
that the text is more readable. Other than as detailed in below, it is suggested that IDs take the
following form:

b-0000001

ie a seven digit, zero-padded number, prefaced by ‘b-’.

THIS INSTRUCTION HAS BEEN SUPERSEDED Note that, for books that are to be converted
from an existing XML form with IDs, it is NOT REQUIRED to convert all the IDs to the form as
specified herein. The only REQUIREMENT is that the IDs are valid XML IDs.

Note that identifiers should not normally change once created. If corrections to a title are required,
any existing identifiers MUST be retained unchanged. Deletions are allowed as are insertions. If
elements are added or deleted it is NOT REQUIRED to maintain the increasing numeric sequence of
the IDs.

5.2.2. IDs for the book and set

Ref: §1.16

The ID for the book element must consist solely of the prefix and the XML ISBN:3

<book xmlns=“http://docbook.org/ns/docbook” version=“5.0” xmlns:xlink=“http://www.w3.org/1999/xlink”

xml:lang=“en” xml:id=“b–9781849665605” role=“fullText”>

[Add set example]

5.2.3. IDs for chunks

For all chunk blocks, ie the following nodes:

• chapter

• acknowledgements

• book/glossary

• book/part/glossary
2
Tested in Schematron: all-id-test
3
Tested in Schematron: book-id-start, book-id-end

8
 Identifiers

• preface

• index

• book/bibliography

• part/bibliography

• appendix

• part[partintro]

• toc

• dedication

• article

the @xml:id MUST be in the following form:

[book/@xml:id]-uniqueValue

For chapter chunks with a numeric @label value, this MUST be:

b-9781501312076-chapter15

and similarly for part and appendix IDs:

b-9781501312076-partII
b-9781501312076-appendixA

where the end part of the ID string comprises the element name followed by the @label value.4 If
chapter, part or appendix elements do not have a numeric @label, their ID MUST follow the
form for all other chunks:

b-9781501312076-0000067

However, for all chunk IDs the key requirement is that they start with the book XML ID and a
hyphen.5

This does not apply to some chunks within annotated legislation. See Section 5.2.7, “IDs for annotated
legislation”.

See also Section 7.5.11, “Other biblioids” for further details about schematronVersion.

5.2.4. IDs for glossary terms

The ID for glossaries MUST follow the general rules above; it MAY be desirable to include a
predictable component to the ID based on the glossary term, eg:

<glossentry xml:id="b-9781234567897-Skt">
<glossterm>Skt.</glossterm>
<glossdef><para>Sanskrit</para></glossdef>
</glossentry>

4
Tested in Schematron: enforce-id-1 through enforce-id-6, for which schematronVersion = 4 is REQUIRED. See
Section 7.5.11, “Other biblioids”.
5
Tested in Schematron: chunk-id, chunk-id2

9
 Identifiers

This section is included for reference only, for existing works with schematronVersion < 5.
FOR ALL NEW DATA THIS SECTION IN GREY IS NOW INVALID.

THIS INSTRUCTION HAS BEEN SUPERSEDED Where there is a glossary within the book
and the glossary markup is used (see Section 10.8, “Glossaries and abbreviations lists”), the
glossentry ID MUST be the same as the text content of the glossterm with spacing and
punctuation removed. This is to make it easier to predict the target ID in the data processing.

<glossentry xml:id="Skt">

<glossterm>Skt.</glossterm>
<glossdef><para>Sanskrit</para></glossdef>
</glossentry>
Or, a more complex example:
<glossentry xml:id="BṛUB">
<glossterm><emphasis role="italic">Bṛ. UB.</emphasis></glossterm>
<glossdef><para>Bṛhad-āraṇyaka Upaniṣadbhāṣya</para></glossdef>
</glossentry>

5.2.5. IDs for bibliographic items

The ID for glossaries MUST follow the general rules above; it MAY be desirable to include a
predictable component to the ID based on the glossary term, eg:

<bibliomixed role="monograph" xml:id="b-9781234567897-gouldner1970">

This section is included for reference only, for existing works with schematronVersion < 5.
FOR ALL NEW DATA THIS SECTION IN GREY IS NOW INVALID.

This instruction has been supersededSince many links will be REQUIRED to point to
bibliographic items, if it makes it easier to create accurate data, it MAY be useful to use some
sort of human-readable ID structure for bibliomixed items. The precise details of this can
be up to the data supplier, though IDs should ideally not be too long, and must obviously be
unique. For example:

<bibliomixed role="monograph" xml:id="gouldner1970"><author><personname role="last-

first"><surname>Gouldner</surname><firstname role="initials">A.</firstname></personname></author>
(<pubdate>1970</pubdate>) <title xml:id="ba-9781780933405-0003693"><emphasis role="italic">The Coming
Crisis in Western Sociology</emphasis></title>. <address xml:id="ba-9781780933405-0003694"><city>New
York</city></address>: <publishername>Basic Books</publishername>.</bibliomixed>

5.2.6. IDs for formal paragraphs

Formal paragraphs are those paragraphs which have a title. Ordinarily, their ID structure should
follow that of any regular, non-chunk ID (ie simply a valid XML ID). However, for works other than
Case Reports, where the formalpara//title contains a paragraph number (as is commonly the
case in legal texts) the formalpara ID MUST be of the form:

b-9781501312076-fp1.1

where the final numeric part exactly matches the number in the title element:6

<formalpara xml:id="b-9781234567897-fp1.01">

6
Tested in Schematron: enforce-id-7 and enforce-id-8

10
 Identifiers

<info xml:id="djdid">

<title xml:id="lk98">1.01</title>
</info>
<para xml:id="dj87"><emphasis role="bold">Subject matter of the book.</emphasis> The subject matter of this
book is the rules governing the voluntary inter vivos assignment of contractual rights. Such transactions
involve the transfer ....</para>
</formalpara>

This REQUIREMENT is enforced using biblioid ‘formalparaNumeric’, which is itself

REQUIRED if all formalpara//titles have a numeric value. See also Section 7.5.11, “Other
biblioids”.7

5.2.7. IDs for annotated legislation

Annotated legislation volumes are those that contain all or part of the text of statutes together with
some commentary. Each statute or legislative item MUST be within a chapter and MUST have an
@xml:id from a defined list, which will be a short-form abbreviation of the title. For example, the
content with the title "Provisional Collection of Taxes Act 1927" will have the ID "PCTA1927".8

Various divisions within a piece of legislation will be within a DocBook section and MUST have IDs
related to the parent chapter ID:9

Division of legislation biblioDivType ID structure/example

Section section [chapterID]s[section/@label]

PCTA1927s4A
Part part [chapterID]pt[section/@label]

TCA1997pt1
Chapter chapter [chapterID]pt[PartSection/
@label]ch[section/@label]

TCA1997pt1ch4
Schedule schedule [chapterID]sch[section/@label]?

PCTA1927sch

See examples in Section 32.16.8, “Annotated legislation”.

5.3. Identifier Persistence

Important
This section contains new instructions which DO NOT apply to all content: Bloomsbury
will instruct when they apply.

Bloomsbury requires that the identifier of certain key elements does not alter between deliveries of
the XML.

More specifically, the identifiers described below MUST NOT change after initial supply.

Initial supply is defined as the first point XML is delivered to Bloomsbury. This MAY vary from project
to project and MAY include, but is not limited to, work that is at the proofing stage.
7
Tested in Schematron: formalpara-title, formalpara-title2
8
Tested in Schematron: legislation-ids
9
Tested in Schematron: legal-section-ids1, legal-section-ids2, legal-section-ids3

11
 Identifiers

Note
Bloomsbury MAY request proof at any time that these identifiers have not changed.

5.3.1. Chunks
The xml:id of all elements identified by the XPaths below MUST remain the same each time the
XML is supplied to Bloomsbury.

Note that this list may change over time, or per specific project. Bloomsbury will advise where this is
the case.

Chunk name XPath

Acknowledgements /book//acknowledgements
Appendix /book//appendix
Article /book//article
Bibliography /book/bibliography |

/book/part/bibliography
Chapter /book//chapter
Dedication /book//dedication
Glossary /book/glossary | /book/part/glossary
Index /book//index
Part introduction /book/part[partintro]
Preface /book//preface
Sub-article /book//section[@role=’subArticle’]
Table of contents /book//toc

5.3.2. Tables and figures

In addition, the xml:id of the following elements MUST remain unchanged on re-supply:

Element name XPath

Figures //informalfigure | //figure
Tables //informaltable | //table

5.3.3. ID report on re-supply

In some cases when XML is re-supplied, the xml:id cannot be preserved. In such cases, a report
MUST be included in the XML to indicate what has changed.

Note
Only changes affecting chunks, tables and figures, as listed above, need be recorded.

It is NOT necessary to report ID changes for any other element.

5.3.3.1. Minimal impact of changes

Any changes MUST be effected with minimal impact to the overall document.

12
 Identifiers

For example, where a change takes place which influences the number or sequence of images, only
the IDs of the affected (informal~)figures should change: it is NOT acceptable for a significant
change to an element to affect all subsequent IDs.

This will reduce the amount of reporting work at the supplier and subsequent verification at
Bloomsbury.

5.3.3.2. How to record changes

The table below shows the types of changes and how they should be recorded, with references to the
markup example beneath it.

Type of change Example Impact on existing How to record change

XML
Element created A new element is added Element receives new Indicates an added
to the document ID element
ID of the added
element
Element deleted An element is removed [Element ID is Indicates a deleted
from the document necessarily also deleted] element
ID of the deleted
element
Element moved An element is moved Element retains its ID No report entry required
within the document
Element changed: name One of the following, Element ID remains Indicates changed
only while the content of the unchanged element
elementa is unaltered: ID of the changed
element
1. Name of a chunk
changed to another
chunk name

2. Name change from

informaltable to
table or vice versa

3. Name change from

informalfigure to
figure or vice versa
Element content The content of an Element ID remains Indicates changed
changed elementa is altered unchanged element
ID of the changed
element

See also the

examples given in
Section 5.3.3.2.1,
“Element content
change examples”.
Element split An existing element is ID of element split is Indicates split
split into two or more discarded; new IDs element
new elements are assigned to new Indicates a deleted
elements element
ID of the deleted
element
Indicates an added
element

13
 Identifiers

Type of change Example Impact on existing How to record change

XML
ID of an added
element
Element merge Two or more existing IDs of elements merged Indicates merge
elements are merged are discarded; new element
into a single new ID assigned to new Indicates an added
element element element
ID of an added
element
Indicates a deleted
element
ID of the deleted
element
a
which may also include the content of any node descendants; only report changes to the descendant nodes if they belong to the
lists given in Section 5.3.1, “Chunks” or Section 5.3.2, “Tables and figures”

Example 5.1. ID change report

<revhistory role="revisionReport">

<revision role="elementAdded" xml:id="b-9781350029637-0000033a">

<date>2018-06-06</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781350029637-0000001" xlink:role="contentIdentifier"/>
</revision>

<revision role="elementDeleted" xml:id="b-9781350029637-0000033b">

<date>2018-06-06</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781350029637-askldjfasdf" xlink:role="contentIdentifier"/>
</revision>

<revision role="elementNameChanged" xml:id="b-9781350029637-0000033d">

<date>2018-06-06</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781350029637-qweryuio" xlink:role="contentIdentifier"/>
</revision>

<revision role="elementContentChanged" xml:id="b-9781350029637-0000033e">

<date>2018-06-06</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781350029637-qnducywns" xlink:role="contentIdentifier"/>
</revision>

<revision role="elementSplit" xml:id="b-9781350029637-0000033f">

<date>2018-06-06</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark>
<remark revisionflag="deleted" xlink:href="b-9781350029637-nqkjln5454"
xlink:role="contentIdentifier"/>
<remark revisionflag="added" xlink:href="b-9781350029637-nqkjasdf5454"
xlink:role="contentIdentifier"/>
<remark revisionflag="added" xlink:href="b-9781350029637-nqkjlnawer54"
xlink:role="contentIdentifier"/>
</revremark>
</revision>

<revision role="elementMerged" xml:id="b-9781350029637-0000033g">

<date>2018-06-06</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark>
<remark revisionflag="added" xlink:href="b-9781350029637-43kf8j"
xlink:role="contentIdentifier"/>
<remark revisionflag="deleted" xlink:href="b-9781350029637-k4908j"
xlink:role="contentIdentifier"/>
<remark revisionflag="deleted" xlink:href="b-9781350029637-2398vbm"
xlink:role="contentIdentifier"/>
</revremark>
</revision>

14
 Identifiers

</revhistory>

Important
The changes above MUST be recorded using /book/info/
revhistory/revision as shown, and <biblioid class='other'
otherclass='revisionReportRequired'> MUST be present.

5.3.3.2.1. Element content change examples

Example 5.2. Structural change

This example shows a change to the structure of a chunk (a chapter), and how to record it.

Here, the structure is altered by renaming an element (an informalfigure). This element is one
for which changes MUST be recorded (see Section 5.3.2, “Tables and figures”), so this change also
appears in the revision report.

Note that the IDs shown in bold have not changed here; only the highlighted element name differs.

BEFORE:

<chapter xml:id="b-9781474218405-chapter1" label="1">

<info xml:id="b-9781474218405-0000100">
<title xml:id="b-9781474218405-0000101">What is Textile Design?</title>
</info>
<informalfigure label="2" xml:id="b-9781474218405-0000109">
<mediaobject xml:id="b-9781474218405-0000110">
<imageobject xml:id="b-9781474218405-0000111">
<imagedata fileref="images/14_1.jpg" format="image/jpeg"/>
</imageobject>
</mediaobject>
<caption xml:id="b-9781474218405-0000112">
<para xml:id="b-9781474218405-0000114">A student sketchbook showing an investigation into current knit
designers. Awareness and understanding of what others are doing is an essential part of learning, as it
gives insight into textile processes, techniques and contexts.</para></caption>
</informalfigure>
[...]
</chapter>

AFTER:

<chapter xml:id="b-9781474218405-chapter1" label="1">

<info xml:id="b-9781474218405-0000100">
<title xml:id="b-9781474218405-0000101">What is Textile Design?</title>
</info>
<figure label="2" xml:id="b-9781474218405-0000109">
<title>Student sketchbook</title>
<mediaobject xml:id="b-9781474218405-0000110">
<imageobject xml:id="b-9781474218405-0000111">
<imagedata fileref="images/14_1.jpg" format="image/jpeg"/>
</imageobject>
</mediaobject>
<caption xml:id="b-9781474218405-0000112">
<para xml:id="b-9781474218405-0000114">A student sketchbook showing an investigation into current knit
designers. Awareness and understanding of what others are doing is an essential part of learning, as it
gives insight into textile processes, techniques and contexts.</para></caption>
</figure>
[...]
</chapter>

REPORT:

<revhistory role="revisionReport">

<!-- records change from informalfigure to figure -->

<revision role="elementNameChanged" xml:id="b-9781474218405-0000097d">

15
 Identifiers

<date>2019-05-14</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781474218405-0000109" xlink:role="contentIdentifier"/>
</revision>

<!-- records change to chapter structure, caused by above change -->

<revision role="elementContentChanged" xml:id="b-9781474218405-0000098e">
<date>2019-05-14</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781474218405-chapter1" xlink:role="contentIdentifier"/>
</revision>

</revhistory>

Reflects the change of element name from informalfigure to figure

Gives the ID of the element whose name has changed
Reflects the (structural) change of content to this element
Gives the ID of the element whose content has changed

Example 5.3. Textual change

This example shows a change to the text of a chunk (a chapter again), and how to record it.

Important
A textual change is defined as a significant editorial change to the text, either by addition
or deletion of text. Typographic corrections are NOT significant and MUST NOT be
reported.

In the example below, the highlighted text has been changed.

BEFORE:

<chapter xml:id="b-9781474218405-chapter1" label="1">

<info xml:id="b-9781474218405-0000100">
<title xml:id="b-9781474218405-0000101">What is Textile Design?</title>
</info>
<informalfigure label="2" xml:id="b-9781474218405-0000109">
<mediaobject xml:id="b-9781474218405-0000110">
<imageobject xml:id="b-9781474218405-0000111">
<imagedata fileref="images/14_1.jpg" format="image/jpeg"/>
</imageobject>
</mediaobject>
<caption xml:id="b-9781474218405-0000112">
<para xml:id="b-9781474218405-0000114">A student sketchbook showing an investigation into current knit
designers. Awareness and understanding of what others are doing is an essential part of learning, as it
gives insight into textile processes, techniques and contexts.</para></caption>
</informalfigure>
[...]
</chapter>

AFTER:

<chapter xml:id="b-9781474218405-chapter1" label="1">

<info xml:id="b-9781474218405-0000100">
<title xml:id="b-9781474218405-0000101">What is Textile Design?</title>
</info>
<informalfigure label="2" xml:id="b-9781474218405-0000109">
<mediaobject xml:id="b-9781474218405-0000110">
<imageobject xml:id="b-9781474218405-0000111">
<imagedata fileref="images/14_1.jpg" format="image/jpeg"/>
</imageobject>
</mediaobject>
<caption xml:id="b-9781474218405-0000112">
<para xml:id="b-9781474218405-0000114">A student sketchbook showing an investigation into current knit
designers.</para></caption>
</informalfigure>
[...]
</chapter>

16
 Identifiers

REPORT:

<revhistory role="revisionReport">

<!-- records change to chapter text -->

<revision role="elementContentChanged" xml:id="b-9781474218405-0000099e">
<date>2019-05-14</date>
<author><orgname>[name of supplier]</orgname></author>
<revremark xlink:href="b-9781474218405-chapter1" xlink:role="contentIdentifier"/>
</revision>

</revhistory>

Reflects the textual change to the para descendant of this chunk

Gives the ID of the chunk (here the chapter) whose text has changed

17
Chapter 6. Root elements
Ref: §1.9

The root element MUST be book, unless it is a multi-volume work, in which case set MUST
normally be used. See Chapter 13, Multi-volume works for further information on handling multi-
volume works.

Validation: The schema does not enforce this; it also allows other root elements

18
Chapter 7. Book and set metadata
7.1. The relationship between the prelims and
book metadata
Ref: §1.32, §1.33

See also Section 7.5.15, “Other prelim content”, Chapter 10, Front matter, and especially Section 10.3,
“Prelims chunk”.

In the DocBook model, most of the content within the preliminary material within a book (ie the half
title, half title verso, title page, and title verso (copyright page) MUST be encoded within specific
elements within the book metadata (book/info), along with some additional metadata that does
not occur in the print edition.1 In addition, a small amount of the content on the title verso MUST be
encoded within the book/colophon (see Section 7.5.15.3, “Colophon”). The table below summarises
the mapping between the print source and the main DocBook targets, and the following sections
provide further detail and examples.

Component Elements
Half title title
Half title verso cover
Title page title, subtitle, author | authorgroup,
pubdate, biblioset [and others? Check some
of the more irregular title pages]
Title verso biblioset, copyright, legalnotice +
book/colophon

7.2. Language metadata

Ref: §1.27

All xml files MUST have an @xml:lang attribute on the root element to specify the (human)
language of the text, the value of which MUST be from the ISO 639 code set, and will typically be
“en”.2

When the text includes content in a different language to the default, that text MUST be marked up
with an @xml:lang attribute to indicate the language of that text. If there is no element that spans all
of the text then the phrase element should be used as the container to mark up the text language.3

The ISO 639 two-letter code values MUST be used if one exists. If no two-letter code exists for a given
language, the three-letter code MUST be used (eg for Ancient Greek “grc”).4

See also Section 4.1, “Right-to-left writing systems”

7.3. Content type

NOTE: This is a new requirement

1
See generally the tests in the Schematron pattern: book_metadata
2
Tested in Schematron: lang-attribute
3
Occurrences reported in Schematron: non-english-text
4
Tested in Schematron: lang-attribute-value

19
 Book and set metadata

Each book MUST have a @role, with the value of either fullText or pdfOnly, the latter being for
backlist titles for which only a pdf version is available.

7.4. Digital-only books

Some books (eg Bloomsbury Spark titles) are digital only, and do not (at present) have a print
incarnation. In such circumstances, the root book element MUST have @outputformat="e-
Only".5

In such books, pagenums, page break markers and pdf chunks are not required.6

7.5. Metadata
Ref: §1.34

The REQUIRED book/info metadata components are:

• Title group

• Author group

• Publication date

• Publisher details

• Copyright/CC details

• ISBNs

• Supplier details (as of Schematron version 8).

Furthermore, other components MAY be REQUIRED:

• Edition

• Series

It is preferable that book metadata components are included in book/info in a consistent, standard
sequence, as follows (some components may not be required for all books):

1. title

2. subtitle

3. authorgroup | author | editor | othercredit

4. edition

5. biblioset[@role="series"]

6. publisher

7. pubdate

8. printhistory | copyright | legalnotice

9. biblioset[@role="isbns"]
5
Tested in Schematron: outputformat-e-only, page-breaks-present
6
Tested in Schematron: pagenums-e-only

20
 Book and set metadata

10.biblioid[@class="doi"]

11.biblioid[@otherclass="schemaVersion"]

12.biblioid[@otherclass="schematronVersion"]

13.cover

14.abstract

15.keywords

This sequence broadly follows data order in the prelims, but moves the half title and half title verso
content (if any) to the end.7

7.5.1. Title group

Ref: §1.35

The title (and subtitle, if one exists) of a book must be marked up using title and subtitle
elements.8

<title>Norbert Elias and Modern Sociology</title>

<subtitle>Knowledge, Interdependence, Power, Process</subtitle>

Italicisation/bold etc MUST NOT be encoded in the title group in the book metadata, if that is how
it was styled in the print edition.9 However, if the book title includes names of works (eg books) that
are rendered differently, their formatting MUST be captured:

<title><emphasis role="italic">To Gaurus On How Embryos are Ensouled</emphasis> and <emphasis

role="italic">On What is in Our Power</emphasis></title>

In addition, a book or chunk title MUST NOT end with a colon.10

Occasionally a book may have a previous title that MUST be recorded.11 This could be where the
content remains unchanged, but the title has changed due to an acquisition and it will be useful for
search for the previous title to be included, for example:

<info>
<title>The Bloomsbury Guide to Aquinas</title>
<bibliomisc role="previousTitle">The Continuum Guide to Aquinas</bibliomisc>

[Workflow for ensuring these are communicated to the supplier?]

Implementation note: Handling of previous titles will need to be supported

Footnotes MAY occur in chunk titles, though not in that for the book itself:

<chapter xml:id="jg846" label="2">

<info xml:id="hg1">
<title xml:id="hg2">H. G. Wells’s Critical Reception in France<footnote xml:id="hg3" label="1"><para
xml:id="hg4">A longer version of this chapter originally appeared in French as ‘Réception critique’, in
my <emphasis role="italic">H. G. Wells: parcours d’une oeuvre</emphasis> in 1998 (pp. 116–32).</para></
footnote></title>

7
See generally the tests in the Schematron pattern: book_metadata
8
Tested in Schematron: title-present
9
Tested in Schematron: title-not-all-emphasis
10
Tested in Schematron: chunk-colon
11
Occurrences reported in Schematron: previous-title

21
 Book and set metadata

Implementation note: Where footnotes occur in titles the footnote label must not be displayed
in generated tables of contents

See also the REQUIREMENT in Section 8.1, “Case regularisation”.

7.5.1.1. Title sort key

As of Schematron version 6, all book titles MUST include a sortas attribute.12 Chunk titles
SHOULD include this attribute, with an appropriate value.

The value of sortas is the string of the title text following any (for English-language titles) definite
or indefinite articles (i.e. the words "A" or "The"), with whitespace normalized:

<book xmlns="http://docbook.org/ns/docbook" role="fullText" xml:id="b-9781234567890">

<info><title sortas="Title of The Book">The Title of The Book</title></info>
</book>

7.5.2. Author group

Ref: §1.38, §1.39

See also the REQUIREMENT in Section 8.1, “Case regularisation”, and the details on name components
in Chapter 17, Names.

DocBook requirements for contributor mark up are relatively simple. If a title has a single author (or
editor) then a single author or editor element must be used to mark up the information.

<info>
<title>Globalizing Cricket</title>
<subtitle>Englishness, Empire and Identity</subtitle>
<author>
<personname role="first-last">
<firstname>Dominic</firstname>
<surname>Malcolm</surname>
</personname>
</author>

Note that within an info element, names are invariably in the order firstname followed by
surname.13

Note also that if there are multiple authored chunks within the book, then it is very likely that the
book will need an editor.14

If multiple contributors are present, then they MUST be wrapped in an authorgroup element.15
Comma and other separators between names MUST NOT be included. Note that for edited books,
the text “Edited by” etc that appears on the title page MUST NOT be included:

<book xmlns="http://docbook.org/ns/docbook" version="5.0" xmlns:xlink="http://www.w3.org/1999/xlink"

xml:lang="en" xml:id="b-9781780930114">
<info>
<title>Families – Beyond the Nuclear Ideal</title>
<authorgroup>
<editor>
<personname role="first-last">
<firstname>Daniela</firstname>
<surname>Cutas</surname>

12
Tested in Schematron book-title-sort-key-test
13
Tested in Schematron: name-order-info
14
Tested in Schematron: possible-edited-book, authorgroup-required-1, authorgroup-required-2,
authorgroup-required-3, othercredit-class-required
15
Tested in Schematron: no-contributor-in-book

22
 Book and set metadata

</personname>
</editor>
<editor>
<personname role="first-last">
<firstname>Sarah</firstname>
<surname>Chan</surname>
</personname>
</editor>
</authorgroup>

Occasionally, books may be authored by an organisation, in which case the organisation name MUST
be encoded within the orgname element within author:

<author>
<orgname>Food and Agriculture Organization of the United Nations</orgname>
</author>

Translators, General editors etc: Contributors other than authors and editors who appear on the title
page of the book MUST be marked up using the othercredit element. Their contribution as stated
in the text MUST be marked up using a child contrib element, which follows the personname in
the data, even if it precedes it in the print edition.

It is often appropriate to indicate the role played by an editor within contrib since there may be
more than one type of editor (e.g. series and general editors). A contrib is not permissible on an
author or editor element;16 if a contrib is required it suggests that the parent element should be
othercredit. Note that othercredit takes a @class attribute, which should not be confused with
@role.17

Note in the example below that the author is separate from the othercredits, ie the three are
NOT included in an authorgroup, since the translator and general editor are not authors of this
work.

<info>
<title><emphasis role="italic">To Gaurus On How Embryos are Ensouled</emphasis> and <emphasis
role="italic">On What is in Our Power</emphasis></title><author>
<personname role="first-last"><surname>Porphyry</surname></personname>
</author>
<othercredit class="translator">
<personname role="first-last">
<firstname>James</firstname>
<surname>Wilberding</surname>
</personname>
<contrib>Translated by</contrib>
</othercredit>
<othercredit>
<personname role="first-last">
<firstname>Richard</firstname>
<surname>Sorabji</surname>
</personname>
<contrib>General Editor</contrib>
</othercredit>

However, sometimes it may be necessary to have multiple authorgroups if there are multiple
contributors in one or more role. For example, this title page author information:

Edited by Richard Sorabji and John Jones

Translated by James Wilberding and Karen Miles

which would be encoded as:

<authorgroup>

16
Tested in Schematron: contrib-present
17
Tested in Schematron: role-or-class

23
 Book and set metadata

<editor xlink:href="Con12345" xlink:role="biblioAuID"><personname role="first-last"><firstname>Richard</

firstname> <surname>Sorabji</surname></personname>
<personblurb xml:id="p1"><para xml:id="p2">Person bio</para></personblurb>
</editor>
<editor xlink:href="Con12346" xlink:role="biblioAuID"><personname role="first-last"><firstname>John</
firstname> <surname>Jones</surname></personname>
<personblurb xml:id="p3"><para xml:id="p4">Person bio</para></personblurb>
</editor>
</authorgroup>
<authorgroup>
<othercredit class="translator" xlink:href="Con12347" xlink:role="biblioAuID"><personname role="first-
last"><firstname>James</firstname> <surname>Wilberding</surname></personname><contrib>Translated by</
contrib><personblurb xml:id="p5"><para xml:id="p6">James Wilberding is ...</para></personblurb>
</othercredit>
<othercredit class="translator" xlink:href="Con12348" xlink:role="biblioAuID"><personname role="first-
last"><firstname>Karen</firstname> <surname>Miles</surname></personname><personblurb xml:id="p7"><para
xml:id="p8">Karen Miles ...</para></personblurb>
</othercredit>

</authorgroup>

Note that the first othercredit within an authorgroup contains the contrib that defines the role
of all the contributors in the authorgroup.18 No other othercredits within the authorgroup
have a contrib.19 Note also that all othercredits within an authorgroup should share the same
@class.20

In this final example, only one person is named on the title page, but is neither the author nor simply
“editor” so othercredit MUST be used:

<title>The Continuum Companion to Leibniz</title>

<othercredit class="other" otherclass="generalEditor">
<personname role="first-last"><firstname>Brandon C.</firstname> <surname>Look</surname></personname>
<contrib>General Editor</contrib>
</othercredit>

Implementation note: Handling of othercredit may need refinement in the output

See also the example in Section 32.1.1, “Title page and contributors”.

Finally, book-level contributors (ie author, editor and othercredit in book/info), MUST
include a single short biographical statement in personblurb, together with the corresponding
Bloomsbury Biblio person ID:21

<editor xlink:role="biblioAuID" xlink:href="Con154010">

<personname role="first-last">
<firstname>Robert</firstname>
<surname>Lake</surname>
</personname>
<personblurb>
<para>Dr. Robert Lake is an Assistant Professor at Georgia Southern University and teaches both
undergraduate and graduate courses in multicultural education from both a local and global perspective.
He is the editor of Dear Maxine: Letters from the Unfinished Conversation with Maxine Greene and Dear Nel:
Letters to Nel Noddings from Circles of Care (In Press). Both of these volumes are published by Teachers
College Press He is also the author of Vygotsky on Education (In Press) in the Peter Lang Primer Series
and A Curriculum of Imagination in an Era of Standardization: An Imaginative Dialogue with Maxine Greene
and Paulo Freire (In press) with Information Age Publishers.</para>
</personblurb>
</editor>

It is unusual for a personblurb to contain more than one paragraph, and for multiple
personblurbs in the same book to be identical.22
18
Tested in Schematron: contrib-required
19
Tested in Schematron: multiple-othercredits-1
20
Tested in Schematron: multiple-othercredits-2
21
Tested in Schematron: personblurb-present, author-id-present, au-id-marker, multiple-personblurb
22
Tested in Schematron: personblurb-para, personblurb-duplicate

24
 Book and set metadata

7.5.2.1. Chunk-level contributors

As of Schematron version 8, where biographical information about the contributor to a chunk is
available in the text, this MUST be included within personblurb in the chunk metadata.

This is likely to occur in e.g. edited volumes and where a "Notes on Contributors" section appears in
the prelims or at the end of a work.

7.5.3. Edition
If present, the edition data MUST be recorded exactly as it appears in the book.

Typically, for editions other than the first, this should appear on the title page, though may only
appear on the title verso page within the publisher details and print history block (see Section 7.5.6,
“Publisher details”). In any event, there MUST be a separate statement of the edition number.23

<edition role="2">Second edition</edition>

Typically, for first editions no edition statement is mentioned in the prelims at all. Even if this is so, an
edition statement MUST be included, with standard text content:

<edition role="1">First edition</edition>

For all editions, the @role MUST take a numeric value equal to the edition number.24

7.5.4. Series
Most often, if the book is in a series, such details MUST be placed within a biblioset, and may
contain several data components:25

• Series title

• Volume number (for numbered series)

• A previous title by which the series may have been known26

• A series ISSN

• A date (for a series of annual volumes)

<biblioset role="series" xml:id="ait555">

<title role="series" xml:id="ser1">Library of Hebrew Bible/Old Testament Studies</title>
<volumenum role="series">567</volumenum>
<bibliomisc role="previousTitle">Journal of Old Testament Studies</bibliomisc>
<biblioid class="issn">1234-5678</biblioid>
<date>2008</date>
</biblioset>

A very high proportion of academic titles will be in a series, so it is relatively unusual for a book not
to have one.27 The text string in the title MUST exactly match the standard form of the series
name.28
23
Tested in Schematron: edition-present
24
Tested in Schematron: edition-role-present
25
Basic tests in Schematron pattern: series
26
Tested in Schematron: See all the tests in the group previous-series-*
27
Tested in Schematron: no-series
28
Tested in Schematron: series-name-list. The complete list of permissible series names is given in section Chapter 33,
Series names

25
 Book and set metadata

Alternatively, some series data may be presented on the half title, for which see Section 7.5.15.1, “Half
title”.

The series data will normally be included as a child of book/info. Occasionally, it MAY occur within a
cover (see Section 7.5.15, “Other prelim content”).29

Implementation note: Whether series data is in biblioset or cover, the key data
components are:

book/info//title[@role="series"]

book/info//volumenum[@role="series"]

etc

7.5.5. Publication date

Ref: §1.40, §1.49

NOTE: This differs from the previous instructions

If the publication date is present it must be marked up using a pubdate element with a @role
attribute set to the value published.30 This is typically a year and matches that on the title or
imprint page.31

<pubdate role="published">2013</pubdate>

7.5.6. Publisher details

Ref: §1.36, §1.37, §1.49

NOTE: This differs from the previous instructions

The publisher information (including its address) MUST be contained within a

biblioset[@role=publisher].32

The DocBook model does not have a specific imprint element, so the imprint information MUST be
bundled in a biblioset with the publisher details.

The bibliomisc[@role="imprint"] SHOULD be the same as that on the title page AND on the
title verso. If the two do not match, please inform Bloomsbury.33 The imprint is usually distinct from
the publisher name. For example, Bloomsbury Academic is an imprint of Bloomsbury Publishing,34
and (for backlist books) Continuum may be the imprint while Continuum International Publishing
Group is publishername;35 however, this MUST follow usage in the book prelims. Typically, an
imprint must have initial capitals and should not contain emphasis.36
29
Tested in Schematron: series-location
30
Tested in Schematron: pubdate-present
31
Tested in Schematron: pubdate-four-digits
32
Tested in Schematron: publisher-no-biblioset; publisher-biblioset; biblioset-publisher; publisher-
address
33
Tested in Schematron: imprint-present; imprint-in-biblioset; imprint-position
34
Tested in Schematron: imprint-bloomsbury-publishing
35
Tested in Schematron: imprint-continuum
36
Tested in Schematron: imprint-emphasis, lower-case-imprint

26
 Book and set metadata

The biblioset publisher block should just contain details of the publisher of the current edition.
For that purpose it MAY need to include printhistory relating to the current edition, but NOT
historical editions and printings.37

<biblioset role="publisher">
<printhistory><para>First published 2013 by</para></printhistory>
<bibliomisc role="imprint">Bristol Classical Press</bibliomisc>
<phrase>An imprint of</phrase>
<publisher>
<publishername>Bloomsbury Publishing Plc</publishername>
<address><street>50 Bedford Square</street> <city>London</city> <postcode>WC1B 3DP</postcode> <country>UK</
country></address>
<address><street>175 Fifth Avenue</street> <city>New York</city> <state>NY</state> <postcode>10010</
postcode> <country>USA</country></address></publisher>
</biblioset>

Note that, the publishername MUST just contain the name of the publisher (hence “An imprint of”
is within a preceding phrase),38 and that within the book/info the address MUST include the
granular component markup.39 Typically, a publishername should not contain emphasis.40

Furthermore, the address MUST be within the publisher, and the address[1] must contain a
city, as in the example above.41

The example below shows a slightly more complicated print history for a second edition. Note that
though both lines from the imprint page are included in a printhistory element, only the current
edition has the imprint encoded, ie this is the imprint that appears on the title page, and only this
one MUST be marked as the imprint. That is, there MUST only be one imprint in the publisher
biblioset.42

<printhistory><para>First published in 2005 by Thomson Learning</para></printhistory>

<biblioset role="publisher">
<printhistory><para>This second edition published in 2011 by</para></printhistory>
<bibliomisc role="imprint">Methuen Drama</bibliomisc>

The following example includes a more complex printhistory:

<printhistory xml:id="w1">
<para xml:id="w2">First published in 1965 by<?break type='line'?>Methuen &amp; Co. Ltd</para>
<para xml:id="w3">Reprinted 1968</para>
<para xml:id="w4">Second edition 1971</para>
<para xml:id="w5">Reprinted five times</para>
<para xml:id="w6">Third edition 1983</para>
</printhistory>
<biblioset role="publisher" xml:id="sw1">
<printhistory xml:id="w7">
<para xml:id="w8">Reprinted in 1988, 1992, 1994 by</para>
</printhistory>
<bibliomisc role="imprint">Bloomsbury Academic</bibliomisc>
<publisher>
<publishername>Bloomsbury</publishername>
<address xml:id="w9"><street>50 Bedford Square</street> <city>London</city> <postcode>WC1B 3DP</postcode>
<country>UK</country></address>
<address xml:id="w10"><street>175 Fifth Avenue</street> <city>New York</city> <state>NY</state>
<postcode>10010</postcode> <country>USA</country></address>
<address xml:id="m65">
<link xlink:href="http://www.bloomsbury.com">
<uri>www.bloomsbury.com</uri>
</link>
</address>
</publisher>
</biblioset>

37
See also: Bob Stayton. ‘Chapter 29. Revision control’ in DocBook XSL. Sagehill. http://www.sagehill.net/
docbookxsl/RevisionControl.html
38
Tested in Schematron: phrase-in-publishername
39
Tested in Schematron: address-components, unmarked-address
40
Tested in Schematron: publishername-emphasis
41
Tested in Schematron: pub-address-location, pub-address-missing, pub-city-missing, pub-city-content
42
Tested in Schematron: imprint-count

27
 Book and set metadata

Note also how the publisher web address is marked up within the publisher address block.43

The examples above include a printhistory within the publisher biblioset where it makes most
sense (grammatically) to group them together. Other more complex histories and layouts on the title
verso may require a separation, eg where the copyright line is in the middle of the block, in which
case multiple printhistory elements may be required:

<biblioset role="publisher">
<bibliomisc role="imprint"><emphasis role="bold">Continuum</emphasis></bibliomisc>
<address>
<otheraddr>The Tower Building</otheraddr>
<street>11 York Road</street>
<city>London</city> <postcode>SE1 7NX</postcode>
</address>
</biblioset>
<printhistory>
<para>First published in Great Britain, 1987<?break type="line"?>by The Athlone Press</para>
</printhistory>
<printhistory>
<para>This edition 2004</para>
</printhistory>
<copyright>
<year>1987</year>
<holder>The Athlone Press</holder>
</copyright>
<printhistory>
<para>Originally published as <emphasis role="italic">Critique et Vérité</emphasis>,<?break type="line"?>by
Editions de Seuil, Paris, 1966</para>
</printhistory>
<printhistory>
<para>The Publishers wish to acknowledge the financial assistance of the French Ministry of Culture and
Communications in the translation of this work.</para>
</printhistory>

7.5.6.1. Companion Website

Occasionally some books may contain a notice indicating that there is a companion website:

This MUST be captured within the biblioset[@role=publisher]44:

<biblioset role="companionWebsite" xml:id="p1">

<phrase>This book is supported by a companion website, which includes and extended bibliography and seminar
exercises.</phrase>
<phrase>Website materials can be accessed at <link xlink:href="http://www.bloomsbury.com/
crimeinengland"><uri>www.bloomsbury.com/crimeinengland</uri></link></phrase>
</biblioset>

and the following biblioid MUST be present45 :

43
Tested in Schematron: publisher-url
44
Tested in Schematron:companion-location
45
Tested in Schematron:companion-flag

28
 Book and set metadata

<biblioid class="other" otherclass="hasOnlineResources">Y</biblioid>

See also Section 7.5.11, “Other biblioids”.

7.5.7. Studio content

Some books have Studio content available online, providing extended resources. Bloomsbury will
advise if this applies. The ePub version of the book, which is generated from the DocBook XML, will
need to include a link which targets the Studio webpage. To enable this, such books MUST be flagged
in the DocBook XML by the addition of a biblioid:

<biblioid class="other" otherclass="hasStudioResources">1</biblioid>

See also Section 7.5.11, “Other biblioids”.

7.5.8. Imprint logo

Some books may have an image logo on their title page. These MUST be captured within the book/
info:

<cover role="titlePage" xml:id="cv1">

<mediaobject role="imprintLogo" xml:id="cv2">
<imageobject outputformat="web" xml:id="cv3"><imagedata fileref="images/logo.png" format="image/png"/></
imageobject>
<imageobject outputformat="print" xml:id="cv4"><imagedata fileref="images/logo.tiff" format="image/tiff"/
></imageobject>
</mediaobject>
</cover>

7.5.9. Copyright/CC details

Ref: §1.41, §1.42, §1.43, §1.44, §1.49

NOTE: This differs slightly from the previous instructions

7.5.9.1. Copyright
Copyright information must be marked up in the metadata. The copyright element MUST be used
for this purpose.46 The copyright symbol (©) and the word “Copyright” MUST NOT be included in
the XML.47

If multiple contributors are mentioned in a single copyright line, this MUST be marked up as a single
copyright statement.

<copyright>
<year>2011</year>
<holder>Jonathan Bate and contributors</holder>
</copyright>

These may also be slightly more complicated, with indications of the responsibilities of the copyright
holders. The text sequence MUST follow that in the print edition:
46
Tested in Schematron: copyright-present; info-copyright
47
Tested in Schematron: copyright-holder, copyright-year

29
 Book and set metadata

<copyright>

<year>2012</year>

<holder><phrase role="resp">Editorial matter and arrangement:</phrase> Marguerite Johnson

and Harold Tarrant</holder>

<holder>The contributors retain copyright in their individual chapters.</holder>

</copyright>

Note also that the copyright year MUST NOT be in the holder element;48 it belongs in year.
Furthermore, assertions of moral rights etc belong in a legalnotice element, not within copyright.49

Implementation note: Display and appropriate rendering of multiple holder and

responsibilities is not supported in DocBook XSL

7.5.9.2. Creative Commons and Open Access content

Important
This section applies to version 6 or later of the Schematron schema.

Bloomsbury Open Access content is that which is freely available to users online. As of this version
of the schema, open-access content MUST include a Creative Commons licence, of which there are
currently four allowed types:

Licence Allowed valuea

Attribution CC-BY
Attribution-NonCommercial-NoDerivs CC-BY-NC-ND
Attribution-NonCommercial-ShareAlike CC-BY-NC-SA
Attribution-NoDerivs CC-BY-ND
a
Denoted by legalnotice/@role

In addition, the attribute oa:licenceVersion is now provided to indicate the version of the CC
licence.

7.5.9.2.1. Open Access: books and chapters

Whole books or individual chapters can now be identified as being Open Access. Bloomsbury will
specify the type of licence to use in each case, and at which level to indicate them in the markup. This
markup is allowed within book/info or chapter/info only.50

Here is a book-level example:

<book>
<info><legalnotice role="CC-BY-ND" xml:id="b-9781838606947-0000020"><para xml:id="b-9781838606947-1000020"/
></legalnotice></info></book><

And here is a chapter-level example:

<chapter xml:id="b-9780755607815-0000231" label="part1" role="labelOverRide">

<info xml:id="b-9780755607815-0000232">
<legalnotice xml:id="b-9780755607815-1000234" role="CC-BY"><para xml:id="b-9780755607815-2000234"
role="funder"><orgname>University College London</orgname></para></legalnotice>

48
Tested in Schematron: holder-year
49
Tested in Schematron: holder-act
50
Tested in Schematron open-access-2

30
 Book and set metadata

</info></chapter>

Note
In this version of the schema, the wording of the particular Creative Commons licence is
NOT required to be captured in the markup. The para within legalnotice is required,
and is therefore allowed to be empty in this context.

7.5.9.2.2. Funding bodies

Where information about the funding body is available, this MUST be captured within para
role='funder', with each individual funder marked up separately using orgname51 e.g.

<legalnotice role="CC-BY-NC-SA" xml:id="b-9780755602216-ch20-ba-1"><para role="funder"

xml:id="b-9780755602216-ch20-ba-2">
<orgname>Wellcome Collection</orgname>
<orgname>SOAS</orgname></para></legalnotice>

Note that the funder information should be captured using orgname only, and no other punctuation
or text should be included.52 The rendering application is expected to supply any delimiting text or
punctuation.

7.5.9.3. Other legal text

Other legal and rights-related text following the copyright statement MUST be included within a
legalnotice:

<legalnotice>
<para>All rights reserved. No part of this publication may be reproduced or transmitted in any form or
by any means, electronic or mechanical, including photocopying, recording, or any information storage or
retrieval system, without prior permission in writing from the publishers.</para>
<para>Seán Sheehan has asserted his right under the Copyright, Designs and Patents Act, 1988, to be
identified as Author of this work.</para>
</legalnotice>

7.5.10. ISBNs, DOI and CIP information

Ref: §1.45, §1.46, §1.47, §1.48, §1.49

NOTE: This differs slightly from the previous instructions

The list of ISBN(s) associated with the book MUST be included, and contained within using a
biblioset element with a @role attribute set to the value isbns.53

Such list will usually be preceded or followed by the CIP (Cataloguing in Publication) statement(s)
from the British Library and/or the Library of Congress, which MUST be included within separate
legalnotice[@role="CIP"].54 (See below.)

The XML ISBN provided by Bloomsbury must always be inserted into the document markup. This
ISBN must be marked with a @role attribute value of xml.55

Important
XML ISBNs MUST NOT contain spaces.56

51
Tested in Schematron funder-para-orgnames
52
Tested in Schematron funder-para-only-orgnames
53
Tested in Schematron: isbn-present; isbns-in-biblioset; biblioset-isbns; isbns-role
54
Tested in Schematron: bl-cip, loc-cip, loc-cip2
55
Tested in Schematron: xml-isbn
56
Tested in Schematron: xml-isbn-format

31
 Book and set metadata

The SBNs MUST be correctly formatted, i.e. include hyphens or spaces as presented on the imprint
page of the book.57

If any other ISBN values are available (either supplied by Bloomsbury or within the prelims of an
existing text or PDF), these MUST be marked up and have the correct @role.58 Duplicate ISBNs are
NOT permitted.59

Note that as of Schematron version 6, an ePDF ISBN is mandatory for Open Access titles (see
Section 7.5.9.2.1, “Open Access: books and chapters”) appearing on the Bloomsbury Collections
platform (see Section 3.1, “Platform-specific considerations”).60

The @class attribute of each ISBN’s biblioid MUST be set to the correct value (which for ISBNs
this MUST always be isbn). If additional information is provided that provides the print format
associated with a given ISBN then this must be indicated using the @role attribute. Permitted values
are given below, should match those in the prelims, and there MUST be no more than one of each
@role, with the exception of otherHardback, which MAY appear more than once.61 All ISBNs
in the prelims MUST be captured; if there is no apparent @role which is suitable, please contact
Bloomsbury.

@role value Usage

hardback HB/Cloth
paperback PB
xml The current file
epdf ePDF / epub PDF
epub Epub
trade-pbk Trade paperback
set Set
pack Pack
otherVolume All other volumes (v1, v2 etc)
otherHardback Other HB/Cloth, e.g. from a partner imprint
otherPaperback Other PB, e.g. from a partner imprint
discovery For internal use only
specialEdition Special edition
openAccess Open Access

ISBNs of other volumes MUST be marked up as follows, with the value of @xlink:label being the
volume number:62

<biblioid class="isbn" role="otherVolume" xlink:type="resource" xlink:label="1">978-1-60903-222-7</

biblioid>

The book DOI MUST also be included in the metadata, which MUST have @class="doi", and
use the biblioid[@class="isbn"][@role="xml"] as its root.63 DOIs within a book MUST be
unique:64
57
Tested in Schematron: isbn-length; isbn-format
58
Tested in Schematron: insufficient-isbns, isbn-role
59
Tested in Schematron: dupe-isbns
60
Tested in Schematron: open-access-4
61
Tested in Schematron: isbn-types
62
Tested in Schematron : resource-required, label-required
63
Tested in Schematron: doi-present; info-doi; book-doi-isbn; doi-format; doi-isbn
64
Tested in Schematron: duplicate-doi

32
 Book and set metadata

<legalnotice xml:id='b-0015' role="CIP">

<para>CIP records for this book are available from the British Library
and the Library of Congress</para>
</legalnotice>
<biblioset xml:id='b-0016' role="isbns">
<biblioid class="isbn" role="paperback">978 1 84966 002 0</biblioid>
<biblioid class="isbn" role="epub">978 1 84966 012 9</biblioid>
<biblioid class="isbn" role="xml">978-1-12345-678-9</biblioid>
</biblioset>
<biblioid class="doi">10.5040/9781123456789</biblioid>

On rare occasions, DOIs are not required within a book. Bloomsbury will instruct if this is the case.
If so, the book/info MUST contain a biblioid with DOInotRequired (see Section 7.5.11, “Other
biblioids”).

7.5.10.1. CIP (Cataloguing in Publication data)

The CIP data block typically appears on p. iv of the prelims of a book and contains cataloguing
information from the Library of Congress and/or the British Library, though often the BL information
is not explicitly included.

This data MUST be encoded within the legalnotice[@role=CIP], and it is important to

recognise which components in the prelims are to be included. It is often incorrectly included in
colophon.

Note that there are distinct legalnotice elements for each of the two CIP items:

<legalnotice xml:id="b-9780857854148-0000018" role="CIP">

<para xml:id="b-9780857854148-0000019"><emphasis role="bold">Library of Congress Cataloging-in-Publication
Data</emphasis></para>
<para xml:id="b-9780857854148-0000020">Entwistle, Joanne.</para>
<para xml:id="b-9780857854148-0000021">The aesthetic economy of fashion : markets and value in</para>
<para xml:id="b-9780857854148-0000022">clothing and modelling / Joanne Entwistle. &#x2014; English ed.</
para>
<para xml:id="b-9780857854148-0000023">p. cm. &#x2014; (Dress, body, culture, ISSN 1360-466X)</para>
<para xml:id="b-9780857854148-0000024">Includes bibliographical references and index.</para>
<para xml:id="b-9780857854148-0000025">ISBN-13: 978-1-84520-473-0 (pbk.)</para>
<para xml:id="b-9780857854148-0000026">ISBN-10: 1-84520-473-5 (pbk.)</para>
<para xml:id="b-9780857854148-0000027">ISBN-13: 978-1-84520-472-3 (cloth)</para>
<para xml:id="b-9780857854148-0000028">ISBN-10: 1-84520-472-7 (cloth)</para>
<para xml:id="b-9780857854148-0000029">1. Clothing trade. 2. Fashion. I.Title.</para>
<para xml:id="b-9780857854148-0000030">HD9940.A2E58 2009</para>
<para xml:id="b-9780857854148-0000031">381&#x0027;.4574692&#x2014;dc22</para>
<para xml:id="b-9780857854148-0000032">2009020435</para>
</legalnotice>
<legalnotice xml:id="b-9780857854148-0000018a" role="CIP">
<para xml:id="b-9780857854148-0000033"><emphasis role="bold">British Library Cataloguing-in-Publication
Data</emphasis></para>
<para xml:id="b-9780857854148-0000034">A catalogue record for this book is available from the British
Library.</para>
</legalnotice>

The order of items in the Library of Congress CIP data follows a standard pattern, so it should be
straightforward to determine where it starts and ends.

See also http://www.loc.gov/publish/cip/techinfo/databook.html for examples of

CIP blocks, though note also that it will be changing slightly later in 2015: http://www.loc.gov/
publish/cip/news/index.html

7.5.11. Other biblioids

The biblioid element is also used to provide other metadata flags:65

<biblioid class="other" otherclass="schemaVersion">1</biblioid>

65
Tested in Schematron: non-permitted-otherclass

33
 Book and set metadata

<biblioid class="other" otherclass="schematronVersion">5</biblioid>

Value of otherclass Usage

fiction “0” or “1” (zero implied). This is an optional
element, and is used as a flag to indicate if the
book is a work of fiction, in which case some tests
will not be applieda
hasOnlineResources “Y” and "N" are the only permitted values,
and is used to indicate if supporting additional
online resources are available on the book page
of bloomsbury.com (eg the “Online Resources”
section of http://www.bloomsbury.com/
uk/how-creativity-is-changing-
china-9781849666190/ b

See also the Section 7.5.6.1, “Companion Website”.

hasStudioResources "0" and "1" are the only permitted values
(zero implied). This is used to indicate
if related Studio content is available and
hence whether a referral link is needed
in the ePub version (e.g. https://
bloomsburyonlineresources.com/
fairchild-books?
docid=b-9781501387920) c

See also the Section 7.5.7, “Studio content”.

biblioType Either “initials-with-stops” (default) or “initials-
without-stops” to indicate the required style for
the bibliographyd
schemaVersion To record the schema version number against
which the document validatese
schematronVersion To record the Schematron version number against
which the document validatesf

This MUST be set to “6” for all new books and

books made open-access retrospectively, which
activates the REQUIREMENT for the revised
Open Access (see Section 7.5.9.2, “Creative
Commons and Open Access content”) and title
sort order (see Section 7.5.1.1, “Title sort key”)
markup.
suppressChapterNumeration “0” or “1” (zero implied). This is an optional
element, and is used as a flag to indicate if the
book should not have any auto-generated chapter
numbering, in which case some tests will not be
appliedg
allBiblioItemsUnlinked “0” or “1” (zero implied). This is an optional
element, and is used as a flag to indicate if the
book should not have any linked bibliographic
items, in which case some tests will not be
applied.
formalparaNumeric “0” or “1” (zero implied). This is an optional
element, and is used as a flag to indicate if the
formalpara//titles are ALL numeric and

34
 Book and set metadata

Value of otherclass Usage

therefore more strict ID rules are required for
the formalpara. See Section 5.2.6, “IDs for formal
paragraphs”
legalContentType 'commentary', 'legislation', 'cases', 'newsletter',
'precedents'. All legal books MUST include this
content type indication.

• A 'commentary' is a monograph-like book

containing chapters, and may contain
numbered paragraphs.

• A 'legislation' volume contains (annotated)

statutes

• A 'cases' volume is a collection of case reports

If it is not clear which value is required, please

contact Bloomsbury
DOInotRequired “0” or “1” (zero implied). This is an optional
element, and is used as a flag to indicate if
DOIs are NOT required within the book.
Bloomsbury will instruct if this is the case. See
Section 7.5.10, “ISBNs, DOI and CIP information”
and Section 9.3.4, “Chunk DOI”
caseCitation Only permissible when the book
legalContentType='cases', and only permissible in
chapters.h

eg: [2016] 1 FCR 65

See Section 32.16.7, “Case Reports”

courtCode Only permissible when the book
legalContentType='cases', and only permissible in
chapters.

eg: CA

See Section 32.16.7, “Case Reports”

decisionDate Only permissible when the book
legalContentType='cases', and only permissible in
chapters.

eg: 2015-06-15

Such date MUST be in ISO date format.i See

Section 32.16.7, “Case Reports”
shortCaseName Only permissible when the book
legalContentType='cases', and only permissible in
chapters.

eg: Re X

See Section 32.16.7, “Case Reports”

shortCourtName Only permissible when the book
legalContentType='cases', and only permissible in
chapters.

35
 Book and set metadata

Value of otherclass Usage

eg: CA

See Section 32.16.7, “Case Reports”

legalJurisdiction Only permissible when the book
legalContentType='legislation', and only
permissible in book/info.

See Section 32.16.8, “Annotated legislation”

legalDivType Only permissible when the book
legalContentType='legislation', and only
permissible in chapters and sections.

See Section 32.16.8, “Annotated legislation”

targetPlatform At time of writing, only the value https://
www.bloomsburycollections.com/ is
allowed.

See Section 3.1, “Platform-specific considerations”

latexEquations 0 or 1 (zero implied). Triggers the additional
supply of equations as LaTeX: Bloomsbury will
instruct if this is the case.

See LaTeX equations

legalBPrOLooseleaf 0 or 1 (zero implied). Identifies the content
as Bloomsbury Professional looseleaf content:
Bloomsbury will instruct if this is the case.

See Section 32.16.1.1, “Looseleaf content”

a
Tested in Schematron: fiction-test
b
Tested in Schematron : hasOnlineResources-test
c
Tested in Schematron : hasStudioResources-test
d
Tested in Schematron : biblioType-test
e
Tested in Schematron : schema-version-present , schema-version-test
f
Tested in Schematron: schematron-version-present, schematron-version-test
g
Tested in Schematron: chapter-numeration-test
h
Tested in Schematron: case-id-types, case-biblioid-location
i
Tested in Schematron: decision-date

7.5.12. Revisions
Once a document is released, from time to time it may be necessary to make some revisions to it. If
this is so, it is recommended that a revision history is maintained in the book metadata.66

Such a revision history MUST be in date order (most recent first), record the name of the person or
organisation responsible for the revision, and a brief description of the change.67 It is possible to link
to specific targets within the content from such revision description:

<revhistory>
<revision xml:id="rev1">
<date>2014-05-21</date>
<author><personname>Brad Scott</personname></author>
<revremark>Corrected typos in Preface</revremark>
</revision>
<revision xml:id="rev">

66
Tested in Schematron: revhistory-location
67
Tested in Schematron: revision-sequence, revisions-date-format, revision-author, revision-revremark

36
 Book and set metadata

<date>2014-05-20</date>
<author><personname>Brad Scott</personname></author>
<revremark>Added @role to the <link linkend="ki1" role="xref">appendix of the ancillary materials</link></
revremark>
</revision>

<revision xml:id="rev2">
<date>2014-05-19</date>
<author><orgname>NewGen</orgname></author>
<revremark>Fixed layout of Table 1</revremark>
</revision>
</revhistory>

Implementation note: The default behaviour of DocBook XSL is to render the revisions in the
header, which may need to be suppressed by a downstream processor

7.5.12.1. Supplier details

As of Schematron version 8, an entry MUST appear in the revision history, containing the name of the
supplier delivering the XML and the date of supply.68 For example:

<revhistory>
<revision xml:id="xyz987">
<date>2022-10-06</date>
<author><orgname>NewGen</orgname></author>
<revremark>Initial supply</revremark>
</revision>
</revhistory>

7.5.13. Blurb/abstract
The book blurb data MUST be added to the book/info with correct markup for italicisation etc.69
In the event that lists etc are required within the blurb, these MUST be added within a para, since
the content model of abstract does not allow them as direct child elements.

<abstract role="blurb">
<para>Gilles Deleuze is without question one of the most influential thinkers of the twentieth century.
<emphasis role="italic">Difference and Repetition</emphasis> is a classic work of contemporary philosophy
and a key text in Deleuze's oeuvre, a brilliant exposition of the critique of identity that develops two
key concepts: pure difference and complex repetition. <emphasis role="italic">Deleuze's 'Difference and
Repetition': A Reader's Guide</emphasis> offers a concise and accessible introduction to this hugely
important and yet notoriously demanding work.</para>
</abstract>

7.5.14. Keywords
Keywords can occur at the book or chunk level, and occur within a keywordset:

<keywordset xml:id="ki9876">
<keyword xml:id="d5">Word</keyword>
<keyword xml:id="d4">Another key word</keyword>
</keywordset>

7.5.15. Other prelim content

7.5.15.1. Half title
The half title (p. i) typically contains only the book title, in which case no specific markup is required
(since the book title is captured as book/info/title).
68
Tested in Schematron: supplier-details-required
69
Tested in Schematron: blurb-present

37
 Book and set metadata

However, in a small number of cases, the half title page MAY contain other information such as
review quotes, or even extensive series information, which MUST be captured within a cover
element.

These will typically have @role=halfTitle, and may require a bridgehead element for titles
(which MUST take a @renderas=sect1 | sect2 | sect3 | sect4 | sect5 to specify
heading level style, where the attribute value corresponds with the nested section style).70 This
example contains quotes and endorsements (which may also occur on the half title verso):

<cover role="halfTitle">
<bridgehead renderas="sect1">Advance Praise for Norbert Elias and Modern Sociology: Knowledge,
Interdependence, Power, Process</bridgehead>
<blockquote>
<para>This is an engagingly written book by two of the world’s leading experts on the work of Norbert
Elias. Focusing on Elias’s sociology of knowledge they show how this might bring sociologists nearer to a
cumulative theoretical and empirical science of human social relations. Indispensable.</para>
<para role="right"><emphasis role="bold">– Ian Burkitt, Reader in Social Science, University of Bradford,
UK</emphasis></para>
</blockquote>
<blockquote>
<para>A state-of-the-art assessment of the significance of Norbert Elias’s contribution to sociological
knowledge and thought.</para>
<para role="right"><emphasis role="bold">– Professor Johan Goudsblom, University of Amsterdam, The
Netherlands</emphasis></para>
</blockquote>
</cover>

Rarely, half titles may contain rather more complex data, such as series bibliographic data:

which would be marked up as follows (some content removed for clarity). Note the use of @role
attributes for controlling aspects of style and for differentiating content:

<cover role="series" xml:id="id0252">

70
Tested in Schematron: bridgehead-renderas, bridgehead-role

38
 Book and set metadata

<bibliolist xml:id="id0253">
<bibliomixed xml:id="aa1" role="series">
<title role="series">Library of Hebrew Bible/Old Testament Studies</title>
<volumenum role="series">567</volumenum>
<bibliomisc role="previousTitle">Formerly Journal for the Study of the Old Testament Supplement Series</
bibliomisc>
<bibliomisc role="heading1">Editors</bibliomisc>
<othercredit>
<personname role="first-last"><firstname>Claudia V.</firstname> <surname>Camp</surname></personname>
<affiliation><orgname>Texas Christian University</orgname></affiliation>
</othercredit>
<bibliomisc role="heading2">Founding Editors</bibliomisc>
<phrase><personname>David J. A. Clines</personname>, <personname>Philip R. Davies</personname> and
<personname>David Gunn</personname></phrase>
<title>Playing the Texts</title>
<volumenum>17</volumenum>
<bibliomisc role="heading1">Editor</bibliomisc>
<othercredit>
<personname role="first-last"><firstname>George</firstname> <surname>Achiele</surname></personname>
<affiliation><orgname>Adrian College, Michigan</orgname></affiliation>
</othercredit>
</bibliomixed>
</bibliolist>
</cover>

See also more conventional series data in Section 7.5.4, “Series”.

7.5.15.2. Half title verso

Typically, the half title verso (p. ii) is blank, in which case the metadata does not need to contain
anything. However, some content MAY appear in this location (eg related titles, series information,
quotes and endorsements), which MUST be captured within the book/info. This example contains
a related titles list:

<cover role="halfTitleVerso">
<bridgehead renderas="sect2">Also available from Continuum</bridgehead>
<simplelist xml:id="id0256">
<member xml:id="f5"><emphasis role="italic">Charisma and Myth</emphasis>, Raphael Falco</member>
<member xml:id="f6"><emphasis role="italic">Edward Said’s Rhetoric of the Secular</emphasis>, Mathieu E.
Courville</member>
</simplelist>
</cover>

7.5.15.3. Colophon
The only remaining content within the prelims is usually the typesetting and printing information.
For the treatment of this see Section 10.2, “Colophon”.

39
Chapter 8. Editorial standardisation
8.1. Case regularisation
Ref: §1.31

Where titles or contributor (author, editor or other contributor) names are presented in upper case,
the text must be captured in sentence case.1

This applies in the following contexts:

• //info/title

• //info/subtitle

• //info//author

• //info//editor

• //info//othercredit

• book/info/biblioset[@role=’publisher’]/bibliomisc[@role=’imprint’]

That is, there MUST be capitalisation of only the first word, proper nouns and as dictated by other
specific English rules.

Furthermore, acronyms in a title/subtitle MUST NOT be converted to Title Case, eg Using IT in the
Classroom.

For example:

1. Exploring the work of Edward S. Casey

2. New philosophies of film

3. Written space in the Latin West, 200 BC to AD 300

4. Maria Montessori

5. I. A. Richards and the rise of cognitive stylistics

1
Tested in Schematron: case-regularisation

40
Chapter 9. Chunking and high-level
structure
Ref: §1.10

NOTE: This differs markedly from the previous instructions

When considering the high-level structure of a book, it is important to think about the book as a pdf,
as well as a structured piece of XML.

Each page of the printed pdf MUST have some representation within the body of the XML (however
simple), with a discrete non-overlapping range of pdf pages that correspond to it. Such unit will
typically be a chapter, preface, appendix etc, but will also include the prelims (typically pp i-iv)
and the contents page(s), etc, and each ALWAYS starts on a new page. Such units are called content
“chunks” in this document.

It is REQUIRED that each content chunk includes:

• the page range of the chunk (see Section 9.3.2, “Page range”),

• a file reference to the corresponding chunk of the print pdf (see Section 9.3.3, “PDF file reference and
file naming”),

• AND that such separate pdf is supplied with the XML (see Chapter 3, Deliverables and file-naming
conventions).

Chunks MAY also require other metadata components as detailed later in this section.

Other elements that are usually technically permissible in a DocBook chunk info will generate a
warning in this instance of DocBook, since they are unusual: date.1

The following elements are content chunks where they occur as children of book or part:

chapter acknowledgements glossary preface

index dedication bibliography appendix
part[partintro] toc

9.1. Chunking example

The following example from The Continuum Companion to Leibniz (9780826429759) is provided to
introduce the general principles:

1
Tested in Schematron : date-in-info

41
 Chunking and high-
level structure

The table below shows the structure of the book.

Label Title
Prelims (pp i-iv in the current book)
Contents page
List of Contributors
PART I LEIBNIZ’S TIMES AND PHILOSOPHICAL
PRECURSORS
1 INTRODUCTION: LEIBNIZ’S LIFE AND
WORKS
2 DESCARTES AND LEIBNIZ
3 LEIBNIZ AND HOBBES
4 LEIBNIZ’S FASCINATION WITH SPINOZA
5 MALEBRANCHE AND LEIBNIZ
PART II LEIBNIZ’S PHILOSOPHY
6 LEIBNIZ’S METAPHYSICS: THE PATH TO THE
MONADOLOGY

42
 Chunking and high-
level structure

Label Title
7 LOGICAL THEORY IN LEIBNIZ
8 LEIBNIZ’S THEORY OF COGNITION
9 LEIBNIZ’S THEORY OF MODALITY
10 LEIBNIZ’S THEORY OF CAUSATION
11 LEIBNIZ’S PHILOSOPHICAL THEOLOGY
12 LEIBNIZ ON FREE WILL
13 LEIBNIZ’S MORAL PHILOSOPHY
14 LEIBNIZ’S CONTRIBUTION TO NATURAL
PHILOSOPHY
15 LEIBNIZ AND THE LIFE SCIENCES
16 LEIBNIZIAN MATHEMATICS
PART III THE AFTERMATH
17 KANT, THE LEIBNIZIANS AND LEIBNIZ
Bibliography
Index of Names

The following table shows how this maps to the XML structure and the pdf chunks.

Label Title XPath Chunk filename

Prelims book/ 9780826429759.0001.pdf
part[@role=’front’]/
preface
Contents book/ 9780826429759.0002.pdf
part[@role=’front’]/toc
List of Contributors book/ 9780826429759.0003.pdf
part[@role=’front’]/
preface
PART I LEIBNIZ’S TIMES AND book/part 9780826429759.pt-001.pdf
PHILOSOPHICAL
PRECURSORS
1 INTRODUCTION: book/part/chapter 9780826429759.ch-001.pdf
LEIBNIZ’S LIFE AND
WORKS
2 DESCARTES AND book/part/chapter 9780826429759.ch-002.pdf
LEIBNIZ
3 LEIBNIZ AND book/part/chapter 9780826429759.ch-003.pdf
HOBBES
4 LEIBNIZ’S book/part/chapter 9780826429759.ch-004.pdf
FASCINATION WITH
SPINOZA
5 MALEBRANCHE AND book/part/chapter 9780826429759.ch-005.pdf
LEIBNIZ
PART II LEIBNIZ’S book/part 9780826429759.pt-002.pdf
PHILOSOPHY
6 LEIBNIZ’S book/part/chapter 9780826429759.ch-006.pdf
METAPHYSICS:

43
 Chunking and high-
level structure

Label Title XPath Chunk filename

THE PATH TO THE
MONADOLOGY
7 LOGICAL THEORY IN book/part/chapter 9780826429759.ch-007.pdf
LEIBNIZ
8 LEIBNIZ’S THEORY OF book/part/chapter 9780826429759.ch-008.pdf
COGNITION
9 LEIBNIZ’S THEORY OF book/part/chapter 9780826429759.ch-009.pdf
MODALITY
10 LEIBNIZ’S THEORY OF book/part/chapter 9780826429759.ch-010.pdf
CAUSATION
11 LEIBNIZ’S book/part/chapter 9780826429759.ch-011.pdf
PHILOSOPHICAL
THEOLOGY
12 LEIBNIZ ON FREE book/part/chapter 9780826429759.ch-012.pdf
WILL
13 LEIBNIZ’S MORAL book/part/chapter 9780826429759.ch-013.pdf
PHILOSOPHY
14 LEIBNIZ’S book/part/chapter 9780826429759.ch-014.pdf
CONTRIBUTION
TO NATURAL
PHILOSOPHY
15 LEIBNIZ AND THE book/part/chapter 9780826429759.ch-015.pdf
LIFE SCIENCES
16 LEIBNIZIAN book/part/chapter 9780826429759.ch-016.pdf
MATHEMATICS
PART III THE AFTERMATH book/part 9780826429759.pt-003.pdf
17 KANT, THE book/part/chapter 9780826429759.ch-017.pdf
LEIBNIZIANS AND
LEIBNIZ
Bibliography book/part[@role=’back’]/ 9780826429759.0004.pdf
bibliography
Index of Names book/part[@role=’back’]/ 9780826429759.0005.pdf
index

Note that it is an ERROR for a book to only contain front and back matter (ie with no body content)
and for a body part to contain no chapters or articles,2 and that it is highly irregular for a book
to contain only one part (over and above front/back).3

See also Chapter 10, Front matter and Chapter 12, Back matter.

9.2. Chunk and section titles and numbering

Ref: §1.11, §1.13

Content chunks MUST contain a title within an info metadata container.4 If the chunk has a
clearly typographically differentiated subtitle, that MUST be contained within a subtitle element.

2
Tested in Schematron: front-back-only, no-chs-in-part
3
Tested in Schematron: only-one-part
4
Tested in Schematron: title-within-info, title-required

44
 Chunking and high-
level structure

Ordinarily, content chunks with a colon-separated title MUST NOT be split into title and
subtitle elements, since it is not a completely reliable means of doing so.

In addition, a book or chunk title MUST NOT end with a colon.5 A chunk title MUST NOT contain a
cross-reference to an item in the bibliography.6

If a chunk also has a label (eg “Chapter 1”, “PART II”), its numeric value MUST be captured using
the @label and MUST NOT be included in the title.7 The numeric value MUST follow the style
as used in the print, ie use Roman or Arabic numbers as appropriate. (In the event that the print style
is to deviate from this (eg “chapter three”), use Arabic numbers for the value of @label.)8

If a chunk title ONLY comprises the number (“3”) or with a label (“Part III”), that MUST be within
the title, NOT included in the @label. Empty title elements are NOT ALLOWED.9 Typically,
therefore, if a chunk title begins with the words “chapter”, “part”, “appendix” etc that is an error if
there is also a numeric value and a more expansive, descriptive title.10 (See also Section 7.5.11, “Other
biblioids”.)

Note that @xreflabel is NOT REQUIRED.11

<chapter label="2" xml:id="chapter-003">

<info xml:id="b-0000600">
<title xml:id="b-0000601">The ‘National Game’</title>
<subtitle xml:id="b-0000602">Cricket in nineteenth-century England</subtitle>
</info>

This use of @label is also REQUIRED for all other elements that can take title and a @label
attribute, ie section, figure, table, example, glossdiv, bibliodiv, etc.

Occasionally, non-standard labels may be required, ie a division may be called a “Section”, even
though it is structurally a DocBook part. In such cases, the entire label (eg “Section 1”) MUST
be included in @label, TOGETHER WITH @role=labelOverRide.12 This is so that the usual
processing rules for @label will not be applied:

<part xml:id="p1" role="labelOverRide" label="Section 1">

<info xml:id="cp5-1">
<title xml:id="cp5-2">Introduction to Epistemology</title>

On online platforms, full points SHOULD NOT be included in the value of @label in nested
sections, as these will be provided by the renderer.13 If there is no alternative to including a full point
– for instance if the numbering system is non-standard – then this warning can be avoided, again by
using @role=labelOverRide:

<section label='1'>
<section label='1.a' role='labelOverRide'>[...]

See also examples in Section 11.4, “General use of @label” and Chapter 11, Introductions, chapters, parts,
titles and @labels

5
Tested in Schematron: chunk-colon
6
Tested in Schematron: link-in-title
7
Tested in Schematron: chunk-title-starts-with-number
8
Tested in Schematron: one-in-label and related tests
9
Tested in Schematron: impermissible-empty-element
10
Tested in Schematron: check-title, part-label-issue, chapter-label-issue, appendix-label-issue
11
Tested in Schematron: xreflabel-not-required
12
Tested in Schematron: label-required2
13
Tested in Schematron : check-label-3

45
 Chunking and high-
level structure

Implementation note: For elements that may include @label, an autogenerated title (“Chapter
2”) must only be added if an @label value is present. If there is no @label, no autogenerated
text or number is to be added in the output.

If @role=labelOverRide, then the value of @label only MUST be displayed with no

autogenerated text.

9.2.1. Chunks with no titles

As indicated above, it is an ERROR for a chunk not to have a title. However, some content doesn’t
have a title on the printed page. In such circumstances a title MUST be included with an appropriate
attribute to indicate this.

A dedication page is a typical example; they usually do not include any title at all. The only content
is the dedication text. In such cases, a title MUST be added with an @outputformat attribute,14
and then the dedication content will be included in regular paras or other appropriate elements:

<dedication xml:id="b-0022">
<info xml:id="b-0023">
<title xml:id="b-0024" outputformat="e-Only">Dedication</title>

Other cases where this may be required include illustrations sections, which may not have any title.
The book’s table of contents may be a useful guide here, since that may include a heading, even if it
does not appear on the printed page:

<title xml:id="b-0059" outputformat="e-Only">Illustrations</title>

See also Section 14.7, “@outputformat”

9.3. Chunk metadata

In addition to the chunk title, there are other additional components that may be required within the
chunk info. All chunks REQUIRE a page range and pdf file reference if there is a print edition (see
also Section 7.4, “Digital-only books”).

Several of these chunk metadata components are not permitted anywhere other than in chunk
blocks.15

9.3.1. Chunk author(s)

If the content chunk has a clearly designated author, they MUST be included within the chunk info:

<chapter label="10" xml:id="b-00005">

<info xml:id="ba-9781780930114-0003431"><title xml:id="b-0003432">Liberal Feminism and the Ethics of
Polygamy</title>
<author>
<personname role="first-last">
<firstname>Simon</firstname>
<othername role="middle-name">Căbulea</othername>
<surname>May</surname>
</personname>
</author>

Monograph books with single or multiple authors MUST NOT have their book/info author details
added to every content chunk. Author details are only REQUIRED for chunks for edited books and
for other chunks with named authors (eg a Foreword).
14
Tested in Schematron: dedication-in-title, epigraph-in-title
15
Tested in Schematron: doi-not-req, pagenums-not-req, mediaobject-not-req

46
 Chunking and high-
level structure

Note that occasionally the style of the work may be to include the chunk author name at the end
of the chunk. In such cases, the chunk author MUST still be included within the chunk info, and
MUST NOT be located in the data at the end of the chunk (the assumption being that the processing
application will place it there. However, this only applies to chapter content, not to signed prefaces
etc.

Note that within an info element, names are invariably in the order firstname followed by
surname.16

As with author details for the book, multiple authors MUST be within an authorgroup:17

<chapter xml:id="b-00002">
<info xml:id="b-0019">
<title xml:id="b-0020">Introduction</title>
<authorgroup>
<author>
<personname role="first-last">
<firstname>Hans</firstname>

<surname>Geybels</surname>
</personname>
</author>
<author>
<personname role="first-last">
<firstname>Walter</firstname>
<surname>Van Herck</surname>
</personname>
</author>
</authorgroup>

For content chunks, most of the names will be within author elements, but occasionally a translator or
other name container may be required:

<chapter xml:id="jg846" label="2">

<info xml:id="hg1">
<title xml:id="hg2">H. G. Wells’s Critical Reception in France</title>
<author><personname role="first-last"><firstname>Joseph</firstname> <surname>Altairac</surname></
personname></author>
<authorgroup>
<othercredit class="translator"><personname role="first-last"><firstname>Barbara</firstname>
<surname>Ghiringhelli</surname></personname></othercredit>
<othercredit class="translator"><personname role="first-last"><firstname>R. H.</firstname>
<surname>Hibbitt</surname></personname></othercredit>
</authorgroup>
<bibliomisc role="contributorStatement">Joseph Altairac; trans. Barbara Ghiringhelli and R. H. Hibbitt</
bibliomisc>

In this particular case, because the way the authorship of the chunk is presented in the print edition
departs from normal practice, a distinct contributor statement is also included. If the presentational
style of the names of the author(s) and other contributors is non-standard, such a contributor
statement MUST be included.18

It is very unlikely that an editor will be REQUIRED within a chunk.19 However, complex contributor
groups may require multiple containers:

Éric Alliez and Jean-Claude Bonne

Translated by Rafael Winkler

Revised by Robin Mackey

16
Tested in Schematron: name-order-info
17
Tested in Schematron: authorgroup-required-1, authorgroup-required-2, authorgroup-required-3
18
Tested in Schematron: contrib-statement-location and presence reported in: contrib-statement-present
19
Tested in Schematron: chunk-editor-present

47
 Chunking and high-
level structure

which would be encoded as:

<authorgroup>
<author>
<personname role="first-last"><firstname>&#x00C9;ric</firstname><surname>Alliez</surname></personname>
</author>
<author>

<personname role="first-last"><firstname>Jean-Claude</firstname><surname>Bonne</surname></personname>
</author></authorgroup>
<authorgroup>
<othercredit>
<personname role="first-last"><firstname>Rafael</firstname><surname>Winkler</surname></personname>
<contrib>Translated by</contrib>
</othercredit>
</authorgroup>
<authorgroup>
<othercredit>
<personname role="first-last"><firstname>Robin</firstname><surname>Mackey</surname></personname>
<contrib>Revised by</contrib>
</othercredit>
</authorgroup>

It is an ERROR for an author, editor or othercredit to be within a title or subtitle.20

Implementation note: If a chunk includes a contributor statement this must be displayed

instead of the generated author statement. This is not supported in DocBook XSL

9.3.2. Page range

Each content chunk MUST include the page range of the corresponding print edition,
and there MUST be only one pagenums within a chunk.21 If there is no print edition (ie
book[@outputformat=’e-Only’]) then page ranges are NOT REQUIRED (see Section 7.4,
“Digital-only books”).

<chapter xml:id="b-000003" label="3">

<info xml:id="b-000041">
<title xml:id="b-000042">Humour in Hinduism</title>
<author>
<personname role="first-last">
<firstname>Koenraad</firstname>
<surname>Elst</surname>
</personname>
</author>
<pagenums>35–53</pagenums>

The start and end page number MUST be separated by an en dash (Unicode &#&#x2013;;), be
composed of letters and digits only,22 and MUST NOT contain any leading or trailing spaces.23
Start pages MUST be before end pages,24 and if there is only one page, only a single number is
REQUIRED.25

However, ALL pages within the printed book MUST be represented within the page ranges for the
book, so blank pages MUST be added to the end of the preceding chunk (NOT to the beginning of
the following one),26 eg for this one page acknowledgement:

<acknowledgements xml:id="b-0000044">
<info xml:id="b-0000045">

20
Tested in Schematron : contributor-in-title
21
Tested in Schematron : pagenums-present, pagenums-count
22
Tested in Schematron: pagenums-must-match
23
Tested in Schematron: pagenums-spaces, pagenums-ndash-1, pagenums-ndash-2
24
Tested in Schematron: endp-before-startp
25
Tested in Schematron: single-page
26
Tested in Schematron: pagenums-sequence

48
 Chunking and high-
level structure

<title xml:id="b-0000046">Acknowledgements</title>
<pagenums>xv–xvi</pagenums>

Page ranges for part divisions MUST only include the physical pages for the division itself, not the
child chapters within it. For example, though this Part includes chapter content up to page 268, its
own page range is just limited to the Part cover page(s):

<part xml:id="b-part-002" label="2">

<info xml:id="b-0094">
<title xml:id="b-0095">Laughing at Religion</title>
<pagenums>189–190</pagenums>

Finally, the first and last page number in the pagenums MUST match the equivalent values in that
chunk’s page PIs (see Section 14.4, “Page breaks”).27

Implementation note: The display of chunk pagenums is not supported in DocBook XSL

9.3.3. PDF file reference and file naming

Each content chunk MUST include a reference to the pdf filename of its corresponding pages in the
print edition.28 If there is no print edition (ie book[@outputformat=’e-Only’]) then pdf file
references and content chunks are NOT REQUIRED (see Section 7.4, “Digital-only books”).

<chapter xml:id="b-0038">
<info xml:id="b-0039">
<title xml:id="b-0040">Introduction</title>
<pagenums>1–2</pagenums>
<mediaobject xml:id="b-0041">
<imageobject xml:id="b-0042"><imagedata format="application/pdf" fileref="pdfs/9781472554871.0006.pdf"/></
imageobject>
</mediaobject>

Chunk filenames MUST have the XML ISBN as its root and follow a sequential pattern. It is
recommended that numbered chapter, part and appendix chunks have a numbering style that
is predictable based on their chapter/part/appendix number. An element is “numbered” if it has
@label numbered as described in Section 11.3, “Chapter and Part labelling”. (See also the table of
filenames in Section 9.1, “Chunking example”, and note the relationship between the pdf filename and
the DOI in Section 9.3.4, “Chunk DOI”29 )

<chapter label="7" xml:id="b-0002307">

<info xml:id="b-0002308"><title xml:id="b-0002309">Choosing Single Motherhood?</title>
<author>
<personname role="first-last">
<firstname>Susanna</firstname>
<surname>Graham</surname>
</personname>
</author>
<pagenums>97–109</pagenums>
<mediaobject xml:id=" b-0002310">
<imageobject xml:id=" b-0002312"><imagedata fileref="pdfs/9781780930114.ch-007.pdf" format="application/
pdf"/></imageobject>
</mediaobject>

Note that if the numbering of the chunk uses Roman numbers, the pdf file name MUST use Arabic
numbers:

<part xml:id="b-part-003" label="III">

27
Tested in Schematron : page-no-match1, page-no-match2
28
Tested in Schematron : chunk-pdf-present
29
Tested in Schematron: ch-doi-no-label, part-no-label, part-filename-no-label

49
 Chunking and high-
level structure

<info xml:id="b-0025">
<title xml:id="b-0026">Religious Laughter</title>
<pagenums>239–240</pagenums>
<mediaobject xml:id="b-0027">
<imageobject role="suppressPDF" xml:id="b-9781474208482-0003050">
<imagedata fileref="pdfs/9781472549075.pt-003.pdf" format="application/pdf"
/>
</imageobject>
</mediaobject>

Note also the presence of @role=suppressPDF in this example. If a content chunk part container
contains no content other than child chapters (or parts), this attribute MUST be applied.30

This is to identify instances where the part divider only contains the title and it may be desirable to
treat the behaviour of such nodes differently in a processing application.

Note though that if the part contains any content at all (most likely within a partintro), this
@role MUST NOT be applied.31

Implementation note: The display and handing of chunk pdfs is not supported in DocBook XSL

9.3.4. Chunk DOI

The following content chunks MUST also have a DOI:32

• chapter

• part[partintro]

the form of which MUST exactly match the chunk filename with a prefix = 10.5040/,33 and DOIs
within a book MUST be unique.34 Furthermore, if a chunk DOI has a numbered chapter or part, its
DOI/filename structure MUST match the label numbering.35

<chapter xml:id="b-00015" label="15">

<info xml:id="b-0000116">
<title xml:id="b-0000117">Humour, Religion and Politics in Greek Cartoons: Symbiosis or Conflict?</title>
<author>
<personname role="first-last">
<firstname>Villy</firstname>
<surname>Tsakona</surname>
</personname>
</author>
<pagenums>248–268</pagenums>
<biblioid class="doi">10.5040/9781472549075.ch-015</biblioid>
<mediaobject xml:id="b-0000118">
<imageobject xml:id="b-0000119">
<imagedata fileref="pdfs/9781472549075.ch-015.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>

Other content chunks MUST NOT have a DOI.36 However, note that articles in A-Z reference content
MUST have DOIs (see Section 9.5, “A-Z (reference) content”).

Also note that sub-articles in reference content (see Section 9.5.6, “Article components (dictionary-type
content)”) MAY require DOIs: Bloomsbury will instruct if this is the case.
30
Tested in Schematron: suppress-pdf-required, part-suppress-pdf
31
Tested in Schematron : pdf-suppress-incorrect, suppress-pdf-abstract, suppress-pdf-partintro
32
Tested in Schematron : chunk-doi-present, part-doi-required, part-no-doi
33
Tested in Schematron : non-matching-doi-pdf
34
Tested in Schematron : duplicate-doi
35
Tested in Schematron : ch-doi-no-label, part-no-label, part-filename-no-label
36
Tested in Schematron: doi-not-required

50
 Chunking and high-
level structure

On rare occasions, DOIs are not required within a book. Bloomsbury will instruct if this is the case.
If so, the book/info MUST contain a biblioid with DOInotRequired (see Section 7.5.11, “Other
biblioids”).

Implementation note: The display of chunk DOIs is not supported in DocBook XSL

9.3.5. Chunk abstract/extract

If author-derived abstracts have been provided, these MUST be included within the chunk info. The
text content of an abstract is likely to be simple, but in the event that lists or more complex features
are required, these MUST be included within a para, since the content model does not otherwise
allow them.

<abstract role="authorAbstract" xml:id="b-0000001">

<para xml:id="a52">This is location of the abstract of the chapter, written by the author. Lorem ipsum
dolor sit amet, consectetur adipiscing elit. Proin eu venenatis libero. Aenean sed suscipit ante, a
bibendum nisi. Cras tincidunt pellentesque eleifend. Donec dignissim bibendum tortor quis pulvinar.
Pellentesque rhoncus tincidunt nisi at porta. Suspendisse libero nulla, pretium in adipiscing quis,
bibendum nec elit. Integer id eleifend turpis, eu.</para>
</abstract>

Author abstracts will only be supplied for new (front list) books. Older titles and those that are to be
converted will almost certainly not have such content. For full text chunks, only authorAbstracts
are permissible.37

If a book contains a section headed “Abstract” that MUST be contained within an abstract
element in the info (not a section) and MUST NOT have a title containing just the word
“Abstract” (since that can be autogenerated by a downstream application.38

Parts (ie part) with no content other than child chapters or articles, or partintro MUST NOT
contain an abstract.39

Backlist books which are to be created as pdf-only metadata files (ie book[@role=pdfOnly])
(see Section 7.3, “Content type”) MUST include a text extract.40 An extract is the first 150 words of
the chunk content, excluding epigraph(s), headings, footnote refs,41 and will be displayed to non-
authenticated users of the online service. This does not apply to full text XML titles.

See also the example in Section 32.2.5, “Chapter Outlines and Abstracts”

9.3.6. Keywords
Keywords may occur in a chunk; as with keywords at the book level, they belong in the chunk info.
See Section 7.5.14, “Keywords”.

9.3.7. Running headers and footers

DocBook does not require specific header and footer elements; its default behaviour is to use the
book, chunk, or section title, as necessary. The DocBook customization layer then offers great
flexibility in selecting other element and page number components one may want to insert in the
various locations that page designs may require.42
37
Tested in Schematron: full-text-extract
38
Tested in Schematron: possible-abstract
39
Tested in Schematron: part-abstract
40
Tested in Schematron: pdf-only-extract
41
Tested in Schematron: poss-footnote-marker
42
See more in Bob Stayton. ‘Chapter 13. Print customizations: Running headers and footers’ in DocBook XSL. Sagehill.http://
www.sagehill.net/docbookxsl/PrintHeaders.html

51
 Chunking and high-
level structure

However, some chunk or section titles may be very long and the most common occurrence is to have
a short form of the title specifically for the header. If that is required (and most chunks and sections
will not need it), then a titleabbrev MUST be added to the info. DocBook’s default behaviour is
to use that for the running header if present, otherwise the title will be used.

<chapter xml:id="a1" label="7">

<info xml:id="a2"><title xml:id="a3">Deference or Defiance? The Role of the Gentry</title>
<titleabbrev>The Role of the Gentry</titleabbrev>

Implementation note: If more complexity in selection of content for inclusion in running

headers or footers is required further specification will be necessary.

9.3.8. Chunk source and print history

Very occasionally, a chapter or article may have information about the print history or source of the
content. This MAY be added to the chunk info/printhistory:

<printhistory xml:id="ph5">
<para xml:id="id01001837"><emphasis role="bold">Source:</emphasis> <emphasis role="italic">Fragments for a
History of the Human Body, Part 2</emphasis> (New York: Zone Books, 1989), 148–99.</para>
<para xml:id="id01001838">From <emphasis role="italic">Le corps redressé: Histoire d'un pouvoir
pédagogique,</emphasis> Paris, Editions Delarge, 1978. <emphasis role="bold">Translated by Ughetta Lubin</
emphasis>.</para>
</printhistory>

Implementation note: This will need to be handled in the site code since it is not supported in
DocBook XSL. Display as block with border

9.4. Chunk content

Content chunks usually contain a range of mixed content: paragraphs, tables, sections, figures, etc. If
it contains only a blockquote it is almost certainly WRONG.43 Typically, this may occur if all of the
child content of the chunk is erroneously placed within one of those elements.

9.4.1. Chapter Outlines

Chapter Outlines features in some Bloomsbury design templates. If these are only chunk tables of
contents then they MUST NOT be included in the data (since they could equally easily be generated
from the XML).

See example in Section 32.2.5, “Chapter Outlines and Abstracts”

9.5. A-Z (reference) content

A to Z content MUST generally be organised differently from other content. Typically, an A-Z work
comprises letter chunks with short(ish) articles within them. Each letter division tends to start a new
page, so they are chunks as defined above, and MUST be contained within a part. All the individual
items within the letter chunk MUST then be contained within article elements.

There are some other specific features that A-Z content has, which are best illustrated with a series of
examples.
43
Tested in Schematron: only-blockquote-content

52
 Chunking and high-
level structure

9.5.1. Article @roles

An article may take one of a number of @role values. The table below summarises the differences:

@role Usage See also

articleGroup Where a reference entry itself Section 9.5.6.3, “Article Groups”
contains other sub-entries in Section 9.5.6, “Article
components (dictionary-type
content)”
biblioArticle Where a reference entry is an
annotated bibliography
lessonPlan Where an article is a lesson plan
snapshotArticle Where a reference entry is a
discrete item set apart from the
other reference content often by
style or formatting
xref Where a reference entry is solely Section 9.5.3, “More complex
functioning as an internal cross article and dummy entry”
reference (a ‘dummy entry’)

9.5.2. General A-Z reference content

This work has clear letter divisions, and then all the articles within the chunk run on in sequence.
Note also the position of the article authors and the ‘see also’ list:

53
 Chunking and high-
level structure

Points to note:

1. The “F” part has the pagenums range for the entire chunk (ie all the “F” articles)

2. It also has a DOI44 and PDF file reference, just like all chunks

3. The container part imageobject MUST not have @role=suppressPDF45 (compare with Section 9.3.3,
“PDF file reference and file naming”)

4. The image on the part opener is simply an informalfigure with a caption for the copyright
line

5. Each item is an article

6. The article’s title is in mixed case, not all upper case (see Section 8.1, “Case regularisation”)

7. The article authors are placed within the article/info NOT at the end of the article. This is
identical to the situation where chapter authors are placed at the chapter end; it is assumed that the
placement of the authors is controlled by the a template style

8. Each article MUST include a pagenums range for that article.46 These are excluded from the
regular sequential pagenums test

9. Each article MUST include a DOI,47 but NOT a file reference, since it is not a chunk
44
Tested in Schematron: part-article-doi
45
Tested in Schematron : suppress-pdf-article
46
Tested in Schematron : article-pagenums
47
Tested in Schematron : article-doi

54
 Chunking and high-
level structure

10.The ‘see also’ references are in a para[@role=see] at the end of the article48

<part xml:id="f-1">
<info xml:id="f-2">
<title xml:id="f-3">F</title>
<pagenums>81–86</pagenums>
<biblioid class="doi">10.5040/9781609032229.011</biblioid>
<mediaobject xml:id="w1"><imageobject xml:id="w2"><imagedata fileref="pdfs/9781609032229.011.pdf"
format="application/pdf"/></imageobject></mediaobject>
</info>
<partintro xml:id="f-4">
<informalfigure xml:id="f-5">
<mediaobject xml:id="f-6"><imageobject xml:id="f-7"><imagedata fileref="images/f.png" format="image/png"/
></imageobject></mediaobject>
<caption xml:id="f-8">
<para xml:id="f-9">Farming © Angela Meah</para>
</caption>
</informalfigure>
</partintro>
<article xml:id="f-10">
<info xml:id="f-11">
<title xml:id="f-12">Farming</title>
<authorgroup>
<author><personname role="first-last"><firstname>Peter</firstname><surname>Jackson</surname></personname></
author>
<author><personname role="first-last"><firstname>Richard</firstname><surname>Lee</surname></personname></
author>
</authorgroup>
<pagenums>82–83</pagenums>
<biblioid class="doi">10.5040/9781609032229.012</biblioid>
</info>
<para xml:id="f-13">Farming encompasses a wide range of organized land- or marine-based activities intended
to produce food and other materials for domestic consumption or for sale through a market mechanism....</
para>
<para xml:id="f14" role="see"><emphasis role="bold"><emphasis role="italic">See also</emphasis></emphasis>
<link role="xref" linkend="a1">ecology</link>, <link role="xref" linkend="a1">governance</link>, <link
linkend="a1">security</link>, <link role="xref" linkend="a1">sustainability</link>.</para>
</article>
</part>

9.5.3. More complex article and dummy entry

Here, the first item is simply a cross reference to other articles, and there is also a bibliography:

48
Tested in Schematron: article-para-links

55
 Chunking and high-
level structure

Points to note:

1. The dummy entry comprising just cross references MUST have @role=xref49

2. The bibliography is within a section (with @role=bibliography)50 in this case because the
data here cannot be modelled within a bibliography, though in principle an article MAY
have a bibliography

3. Again, the ‘see also’ list is in a special para at the end

<part xml:id="s1">
<info xml:id="s2">
<title xml:id="s3">S</title>
<pagenums>496–544</pagenums>
<biblioid class="doi">10.5040/9781609032229.0037</biblioid>
<mediaobject xml:id="s3a"><imageobject xml:id="s3b"><imagedata fileref="pdfs/9781609032229.0037.pdf"
format="application/pdf"/></imageobject></mediaobject>
</info>
<article xml:id="s4" role="xref">
<info xml:id="s5">
<title xml:id="s6">Satisfaction</title>
<pagenums>496</pagenums>
<biblioid class="doi">10.5040/9781609032229.0038</biblioid>
</info>

<para xml:id="s7" role="see"><emphasis role="italic">See</emphasis> <link role="xref"

linkend="a12">Happiness</link>; <link role="xref" linkend="a19">Pain</link>; <link role="xref"
linkend="a6">Pleasure</link>; <link role="xref" linkend="a22">Preferences (Preferentialism)</link>.</para>
</article>
<article xml:id="s8">
<info xml:id="s9">
<title xml:id="s10">Satisficing</title>
<author>
<personname role="first-last"><firstname>John</firstname><surname>Turri</surname></personname>

49
Tested in Schematron : article-xref
50
Tested in Schematron: article-section-role

56
 Chunking and high-
level structure

<affiliation><orgname>University of Warerloo</orgname></affiliation>
</author>
<pagenums>496–497</pagenums>
<biblioid class="doi">10.5040/9781609032229.0039</biblioid>
</info>
<para xml:id="s11">Classical Utilitarianism is a consequentialist moral theory. ...</para>
<section xml:id="s12" role="bibliography">
<info xml:id="s13">
<title xml:id="s13a">Bibliography</title>
</info>
<bibliolist xml:id="s14">
<bibliomixed role="article" xml:id="b-9781474208482-0003344"><bibliomset
relation="article"><author><personname role="last-first"><surname>Bradley</surname><firstname>Ben</
firstname></personname></author>. "<title>Against Satisficing Consequentialism</title>,"</bibliomset>
<bibliomset relation="journal"><title><emphasis role="italic">Utilitas</emphasis></title>, <volumenum>18</
volumenum>, no. <issuenum>2</issuenum> (<pubdate>2006</pubdate>): <pagenums>97–108</pagenums>.</
bibliomset></bibliomixed>
</bibliolist>
<bibliolist xml:id="s16">
<info xml:id="s17">
<title xml:id="s18">Further reading</title>
</info>
<bibliomixed role="monograph" xml:id="s19"><editor><personname role="last-first"><surname>Byron</
surname><firstname>Michael</firstname></personname></editor>, ed. <title><emphasis
role="italic">Satisficing and Maximizing</emphasis></title> (<address><city>Cambridge</city></address>,
<pubdate>2004</pubdate>).</bibliomixed>
</bibliolist>
<para xml:id="s20" role="see"><emphasis role="italic">See also</emphasis> <link role="xref"
linkend="a3">Consequentialism</link>; <link role="xref" linkend="a16">Maximization</link>; <link
role="xref" linkend="a17">Supererogation</link>.</para>
</section>
</article>
</part>

9.5.4. Article parts and dummy headings

The examples above both have a letter heading printed on the page at the start of the letter chunk.
However, not all A-Z content has this. For example, the following book has three A-Z divisions (“The
Key Terms”; “The Key Thinkers”; and “The Key Works”), each of which is presented in letter chunks
(ie the “B” entries etc start on a new page), but there is no letter heading (“A”, “B” etc):

57
 Chunking and high-
level structure

This MUST be modelled as follows:

<part xml:id="k1">
<info xml:id="k2">
<title xml:id="k3" role="keepWithNext">The Key Thinkers</title>
</info>
<part xml:id="k4">
<info xml:id="k5">
<title xml:id="k6" outputformat="e-Only">A</title>
<pagenums>160</pagenums>
<biblioid class="doi">10.5040/9781609032229.012</biblioid>
<mediaobject xml:id="b1"><imageobject xml:id="b2"><imagedata fileref="pdfs/9781609032229.012.pdf"
format="application/pdf"/></imageobject></mediaobject>
</info>
<article xml:id="k7">
<info xml:id="k8">
<title xml:id="k9">Louis Althusser</title>
<pagenums>160</pagenums>
<biblioid class="doi">10.5040/9781609032229.013</biblioid>
</info>

<para xml:id="k9a">An Algerian philosopher, Althusser was influenced by Marx as well as the psychoanalysts
Freud and Lacan. ...</para>
</article>
<article xml:id="k10">
<info xml:id="k11">
<title xml:id="k12">J.L. Austin</title>
<pagenums>160</pagenums>
<biblioid class="doi">10.5040/9781609032229.014</biblioid>
</info>
<para xml:id="k13">A British philosopher of language who developed the concept of speech act and its
associated theory. ...</para>
</article>
<article xml:id="k14">
<info xml:id="k15">

58
 Chunking and high-
level structure

<title xml:id="k16">&#x2018;On the Phenomenology of Language&#x2019; (1951) [<emphasis role="italic">S</

emphasis>]</title>
<pagenums>547–549</pagenums>
<biblioid class="doi">10.5040/9781609032229.012c</biblioid>
</info>
<para xml:id="k17">This essay is one of Merleau Ponty's most direct statements of his understanding
of <emphasis role="bold"><link role="xref" linkend="a12">Husserl</link></emphasis>'s early and late
accounts of language, and its potential relationship to <emphasis role="bold"><link role="xref"
linkend="a14">structuralism</link></emphasis>.</para>
<section xml:id="k18">
<info xml:id="k19">
<title xml:id="k20">Husserl and the Problem of Language</title>
</info>
<para xml:id="k21">For Merleau-Ponty, Husserl's understanding of language evolved in important ways. ...</
para>
</section>
</article>
</part>
</part>

Points to note:

1. The heading “The Key Thinkers” refers to the entire A-Z division, but happens to be placed at the
beginning of the “A” section. The latter is a chunk, so the parent heading (“The Key Thinkers”)
needs to have a special attribute on its title since it is not serving as a chunk itself.51

2. The “A” chunk doesn’t actually have a heading in the printed book, but it MUST have one in the
data. Because it is not presented in the print edition it MUST have @outputformat=e-Only.

3. Articles MAY have nested sections.

9.5.5. High-level structure (A-Z container)

The previous example illustrates that all A-Z content MUST have a part container for all of the letter
divisions. However, sometimes the printed book does not contain any such heading (though it MAY
do so in the table of contents). Even so, such part container and heading MUST be present, even if
that requires @outputformat on the part:

<part xml:id="z1">
<info xml:id="z2">
<title xml:id="z3" outputformat="e-Only">A-Z</title>
</info>
<part xml:id="a">
<info xml:id="a1">
<title xml:id="a2" outputformat="e-Only">A</title>
<pagenums>203–222</pagenums>
<biblioid class="doi">10.5040/9781609032229.010</biblioid>
<mediaobject xml:id="a3">
<imageobject xml:id="a4"><imagedata fileref="pdfs/9781609032229.010.pdf" format="application/pdf"/></
imageobject>
</mediaobject>

</info>
<article xml:id="a5">
<info xml:id="a6">
<title xml:id="a7">verb</title>
<pagenums>203</pagenums>
<biblioid class="doi">10.5040/9781609032229.011</biblioid>
</info>
<para xml:id="a8">Words which relate to actions, occurrences or states of being. Different languages
can modify verb forms according to tense, aspect, mood and voice. Verbs may also need to agree with
the person, gender and number that they refer to. See also <emphasis role="bold"><link role="xref"
linkend="a16">agency</link></emphasis>, <emphasis role="bold"><link role="xref" linkend="a19">ergativity</
link></emphasis>.</para>
</article>

Note also that inline cross references within an A-Z work MUST be linked.52
51
Tested in Schematron: keep-with-next, keep-with-next-pagenums, keep-with-next-mediaobject
52
Tested in Schematron: possible-article-link

59
 Chunking and high-
level structure

9.5.6. Article components (dictionary-type content)

Some categories of reference material (particularly dictionaries) include additional components that
may need to be marked up distinctly, either to enable a different style to be applied when rendered
online, or for extra weight to be given to the phrase for search retrieval. This includes features, such as
pronunciation, word origin/etymology, synonyms.

9.5.6.1. Phrases and article types

The dictionary above contains several features that may occasionally be seen:

(a) Synonyms: in this dictionary displayed in italic:

<article xml:id="dict1">
<info xml:id="qwe1"><title xml:id="qwe2">aoudad sheep</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.045</biblioid>
</info>
<para xml:id="qw3">1. <link role="xref" linkend="a"><emphasis role="smallcaps">Argali sheep</emphasis></
link>. Synonym: <phrase role="synonym"><emphasis role="italic">bearded argali</emphasis></phrase>.
2. Such wild sheep as the bighorn of North America. Also known as <phrase role="synonym"><emphasis
role="italic">barbary sheep</emphasis></phrase>, which predominate in Tunisia, Libya, and Algeria.</para>
</article>

(b) Pronunciation guide: in this dictionary in square brackets:

<article xml:id="dict2">
<info xml:id="qwe4"><title xml:id="qwe5">appliqué</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.046</biblioid>
</info>
<para xml:id="qw6"><phrase role="pronunciation">[ap-luh-kay']</phrase> Material that is cut out
and sewn, embriodered, or fastened to a fabric. See <link role="xref" linkend="a1"><emphasis
role="smallcaps">Appliqué lace</emphasis></link>.</para>

60
 Chunking and high-
level structure

</article>

(c) Word origins: in this dictionary in round brackets at the beginning of the item:

<article xml:id="dict4">
<info xml:id="qwe10"><title xml:id="qwe11">apret de laine</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.048</biblioid>
</info>
<para xml:id="qw12"><phrase role="origin">(French)</phrase> A soft, permanent finish used for Italian
cloth.</para>
</article>

(d) Article type: In this dictionary a special symbol is used to indicate an archaic word. Rather than
include the symbol in the headword, it is preferable to include a category in the article metadata,
which can then be used by a downstream processor. If this approach is required for a given book a
special instruction will be received from Bloomsbury.

<article xml:id="dict3">
<info xml:id="qwe7"><title xml:id="qwe8">appret guignet</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.047</biblioid>
<bibliomisc role="category">archaic</bibliomisc>
</info>
<para xml:id="qw9">As used in Great Britain, a finish formerly used to waterproof fabrics. The cloth was
soaked in a bath of alumina and iron sulfate. The finish supposedly imparted resistance to rot and mold.</
para>
</article>

9.5.6.2. Linking to other books

Very occasionally, one book may implicitly link to another. This book uses the dagger (†) to indicate
that a fuller definition is available in a companion dictionary. For such cases, the article should
be linked to the target article as well. This will rarely be required, and if it is, Bloomsbury will

61
 Chunking and high-
level structure

provide additional instructions. In this example {targetdocid} is the xml:id of the target book, and the
{targetid} is the id of the target article:

<article xml:id="dict5" xlink:role="{targetdocid}" xlink:label="otherBook" xlink:href="{targetid}"

xlink:type="locator">
<info xml:id="qwe13"><title xml:id="qwe14">astrakhan/astrakan</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.049</biblioid>
</info>
<para xml:id="qw15">1. Fabric with a heavy, curly pile made to imitate karakul lamb fleece. May be woven
or knitten. Used as trimming or for men's hats. 2. Wool from the karakul lamb. See under Furs: karakul.</
para>
</article>

More explicit inline linking to other books is available using olink. See Section 15.8, “Links to other
books”.

9.5.6.3. Article Groups

Some dictionaries contain groups of articles:

In this case, the article ‘academic costume’ would follow on directly from the article ‘abstract’:

<article xml:id="dict6" role="articleGroup">

<info xml:id="qwe16"><title xml:id="qwe17">academic costume</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.050</biblioid>
</info>
<para xml:id="qw19">Outfits consisting of caps, called mortarboards (see under academic costume), gowns and
hoods traditionally work at commencement...</para>

62
 Chunking and high-
level structure

<section role="subArticle" xml:id="qw19">

<info xml:id="qw20">
<title xml:id="qw21">academic hood</title>
<pagenums>2</pagenums>
</info>
<para xml:id="qw22">Decorative drape that comes close to the neck...</para>
</section>
<section role="subArticle" xml:id="qwe23">
<info xml:id="qw24">
<title xml:id="qw25">academic hood colors</title>
<pagenums>2</pagenums>
</info>
<para xml:id="qw26">The lining colors at the back of the academic hood...</para>
</section>
</article>

See also Section 26.3, “Embedded articles”, where ‘sub-articles’ may occur anywhere within a parent
article and require the use of a sidebar.

Implementation note: Support for: searching weighting of synonyms; article type/categories;

linking to other books; and the chunking of subArticles is not included in standard DocBook
XSL

63
Chapter 10. Front matter
‘Front matter’ is here defined as all of that content of the book which typically precedes the content
starting on page 1 (ie all the content that is conventionally numbered within Roman numbers).1

10.1. Front matter container

Within a book, the content of the prelims and front matter will be contained in the following elements
and structure (though not necessarily precisely in this order), with the front part immediately
following the info or (if present) the colophon:2

• info

• colophon

• part[@role=’front’]

˚preface[@role=’prelims’]

˚dedication

˚toc

˚acknowledgements

˚preface

˚glossary

˚chapter

The glossary element may not always be in the front matter. Such content may also occur in the
back matter or even within other content chunks.

An acknowledgements section may occur in either the front or back matter.3

Introductory chapters MAY occur within the front matter, though it is very unusual for numbered
chapters to do so.4 The most reliable guide as to whether a chunk is to be included in front or not is
whether it has Roman pagination.

All the front matter not included within book/info (see Section 7.1, “The relationship between the
prelims and book metadata” and Section 7.2, “Language metadata”) or colophon(see Section 10.2,
“Colophon”) MUST be contained within a part[@role=’front’]. The front matter content
will variously be derived from material within book/info, as well as any child elements of
part[@role=’front’].

Though each of the child chunks within the front matter container MUST contain key metadata, the
front part container itself MUST NOT contain: pagenums;5 a DOI;6 or a pdf file reference.7

The content of part[@role=’front’]/info/title MUST be “Front matter”.8

1
Tested in Schematron : page-1-front, poss-front-matter
2
Tested in Schematron : front-chunk, first-element-after-info and first-element-after-colophon
3
Tested in Schematron : acknowledgements-chunk
4
Tested in Schematron : numbered-chapter-front
5
Tested in Schematron : no-pagenums-front
6
Tested in Schematron : no-doi-front
7
Tested in Schematron : no-pdf-front
8
Tested in Schematron: front-matter-title

64
 Front matter

<part xml:id="b-00012" role="front">

<info>
<title>Front matter</title>
</info>

Implementation note: Such ‘front’ (or ‘back’) part container is included so it is possible to
easily hide the sections in the early part of the book (or the appendices etc) from the ToC, if
necessary, and only reveal the structured ToC for the main parts and chapters.

If the XML is ever to be used for generating print, the part[@role=’front’]/info/title

(or @role=’back’]) MUST NOT be displayed.

See also Section 12.1, “Back matter container”

10.2. Colophon
The only content within the prelims material that does not reside in the book/info should just be
the details of the typesetter and printer. These MUST appear within the colophon, which MUST be
the first element after book/info.9

<colophon>
<para>Typeset by Newgen Imaging Systems Pvt Ltd, Chennai, India</para>
<para>Printed and bound in Great Britain by the MPG Books Group</para>
</colophon>

Implementation note: The colophon is not to be displayed in online contexts

10.2.1. Impressions
If a book contains information about the impression number on the imprint page, this belongs in
the colophon.10 Such data is typically a string of numbers, the lowest of which is the number of the
current impression:

<para role="impressions">10 9 8 7</para>

10.3. Prelims chunk

The content chunk that contains the prelims (half title, half title verso, title, title verso) needs special
handling in the data. This is so that the physical structure of the book can be represented in the
high-level XML nesting and correlated with the relevant pdf pages, even though the actual data
components that make up the prelims are included within the book/info.

Consequently, the prelims stub content MUST be located within a preface element with
@role=prelims, and a title with content “Title Pages” and no subtitle,11 MUST
be the first child element of the front matter,12 and MUST contain a remark element with
@condition=hidden as in the example below. The latter is REQUIRED so that the file parses:

<preface xml:id="b-00001" role="prelims">

<info xml:id="b-0015">
<title xml:id="b-0016">Title Pages</title>
<pagenums>i–iv</pagenums>

9
Tested in Schematron: first-element-after-info
10
Tested in Schematron: colophon-impressions
11
Tested in Schematron : prelims-title, prelims-subtitle
12
Tested in Schematron : first-element-front

65
 Front matter

<mediaobject xml:id="b-0017">
<imageobject xml:id="b-0018">
<imagedata fileref="pdfs/9781780930114.0001.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<remark condition="hidden">Note that this is a placeholder for the pdf of the prelims and no full text
content is included at this point</remark>
</preface>

See also Section 7.1, “The relationship between the prelims and book metadata” and Section 14.6, “Conditional
processing with @condition”

10.4. Table of contents

The front matter container SHOULD contain a toc chunk.13

All contents lists in the front matter MUST be represented by a toc element (eg for “Lists of
Illustrations”, as well as the “Table of Contents”). It is an ERROR for other container elements to be
used for this content14 (other than tables of cases and statutes etc in legal texts for which a preface is
REQUIRED (see Section 10.5, “Tables of cases and statutes”)).

The table(s) of contents MUST be represented within the XML structure in the toc element(s), and
the target chapter/part numbers MUST NOT be included within the data.15

The only location where a toc MAY occur is within the front matter; if a book appears to require a
toc in any other location, please contact the publisher.16

10.4.1. ToC contents

Most books only REQUIRE a minimal toc with its chunk info:

<toc xml:id="ba-9781849666336-toc-001">
<info xml:id="ba-9781849666336-toc-001a">
<title xml:id="ba-9781849666336-toc-001b"><?page value="vii"?>Contents</title>
<pagenums>vii</pagenums>
<mediaobject xml:id="ba-9781849666336-toc-001c">
<imageobject xml:id="ba-9781849666336-toc-001d">
<imagedata fileref="pdfs/9781849666336.0003.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
</toc>

This is because most applications can generate a fully structured table of contents from the data; the
pdf is also included so that the pages of the print edition can correspond with the relevant node in the
data.

Different book style templates may adopt different levels of structure in a table of contents; this is
application-dependent and does not need to be captured in the toc.

However, there are some occasions when it is REQUIRED that the table of contents is modelled in the
data:

10.4.1.1. Structured table of contents

Occasionally, a table of contents can include structure that is not otherwise represented in the
structure of the XML. In such cases, the toc MUST include such representation in its content.
13
Tested in Schematron : toc-present
14
Tested in Schematron : title-starts-with-list
15
Tested in Schematron : toc-list-starts-with-number
16
Tested in Schematron : toc-warning

66
 Front matter

For example, in this book the headings “French”, “Russian” and “German” are not part dividers in
the body of the book and only appear in the table of contents:

Consequently, this MUST be captured as:

[Add more and examples]

10.5. Tables of cases and statutes

Most legal texts have tables of cases or statutes in the prelims. These effectively function as indices to
the content, and MUST NOT use the toc element.17

The preface element MUST be used with @role=legalContents, the content MUST be in a
variablelist (which may require nesting, as in this example), and the targets MUST be linked:18

<preface xml:id="v-1" role="legalContents">

17
Tested in Schematron: legal-toc
18
Tested in Schematron: legal-contents, legal-preface, legal-contents-links

67
 Front matter

<info xml:id="v-2">
<title xml:id="v-3">Statutory Instruments</title>
<pagenums>vii–x</pagenums>
<mediaobject xml:id="v-4">
<imageobject xml:id="v-5"><imagedata fileref="pdfs/9781609032229.001b.pdf" format="application/pdf"/></
imageobject>
</mediaobject>
</info>
<variablelist xml:id="v-6">
<varlistentry>
<term xml:id="v-7">SR &amp; O 1912/348 Public Trustee</term>
<listitem xml:id="v-9"><para xml:id="v-10">[<link linkend="p13_12" role="xref">13.12</link>]</para></
listitem>
</varlistentry>
<varlistentry>
<term xml:id="v-11">SR &amp; O 1925/857 LRR 192</term>
<listitem xml:id="v-12"><para xml:id="v-13">[<link linkend="p25_09" role="xref">25.09</link>]</para>
<variablelist xml:id="v-14">
<varlistentry>
<term xml:id="v-15">r 14</term>
<listitem xml:id="v-16"><para xml:id="v-17">[<link linkend="p11_45" role="xref">11.45</link>]</para></
listitem>
</varlistentry>
<varlistentry>
<term xml:id="v-18">r 16</term>
<listitem xml:id="v-19"><para xml:id="v-20">[<link linkend="p20_12" role="xref">20.12</link>]</para></
listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
</variablelist>
</preface>

In some cases, for example where the entry is a cross-reference to another entry in the table, no second
portion present, and the listitem may be left empty:

This should be captured as:

<varlistentry>
<term>A (A Child) (Rev 1), Re. See A (A Child) (FGM: Appeal), Re</term>
<listitem>
<para/>
</listitem>
19
</varlistentry>

See also the example in Section 32.16.4, “Legal contents”.

10.6. Dedication
Ref: §1.50

Dedications MAY appear in the front matter, most often on a separate page (usually p. v, sometimes p.
i), though may also appear on the title verso. [How best to indicate location where it occurs, and if not
in front matter (ie in prelims) then where does it live in the data?]

In all but exceptional cases, dedications SHOULD normally be the first element in the
part[@role=’front’].

In Memoriam

Patricia Mary Davis

19
See Schematron : empty-context.

68
 Front matter

1930–1987

which would be marked up as:

<dedication xml:id="id3">
<info><title>In Memoriam</title>
</info><para>Patricia Mary Davis</para>
<para>1930–1987</para>
</dedication>

This second example requires some line breaks:

For My Beloved Wife Angie Ahn

To My Former Colleagues at Århus University

the markup for which would be:

<dedication xml:id="ded1">
<info xml:id="d1"><title xml:id="e1" outputformat="e-Only">Dedication</title><!-- and other chunk content
--></info>
<para><emphasis role="italic">For My Beloved Wife<?break type="line"?>Angie Ahn</emphasis></para>
<para><emphasis role="italic">To My Former Colleagues at<?break type="line"?>Århus University</emphasis></
para>
</dedication>

Note the additional title and attribute, even though it does not appear on the printed page.

In the rare case where a dedication appears immediately before the back matter, it MUST be
positioned there in the markup, directly within book:20

<!-- last chapter in body ends here -->

[...]
<para>—Hello?</para></chapter>
<dedication xml:id="ded1"><info xml:id="info1"><title outputformat="e-Only"
xml:id="b-9781474208482-0003783">Dedication</title><!-- and other chunk content --></info><para>(RIP
P<emphasis role="smallcaps">rince</emphasis>)</para></dedication>
<!-- back matter container starts here --><part role="back" xml:id="back1">
[...]

For backlist books supplied as pdf-only content, only the standard remark content MUST be
included; it is NOT REQUIRED to include the dedication content.21

See also Section 9.2.1, “Chunks with no titles” and Section 14.5, “Column and line breaks”.

10.7. Acknowledgements
Ref: §1.91

An Acknowledgements section within the front matter MUST be included within an

acknowledgements element.22

<acknowledgements xml:id="b-0000100">
<info>
<title>Acknowledgements</title>
</info>

20
Tested in Schematron : book-level-dedication
21
Tested in Schematron: para-dedication-pdfonly
22
Tested in Schematron: acknowledgements-present

69
 Front matter

<para xml:id="b-0000103">This book is the product of around sixteen years of work so there are many people
to thank who have helped along the way. In particular, I am grateful to the small number of people with
whom I have collaborated on cricket-related research over the years: Alan Bairner, Graham Curry, Jon
Gemmell, Nalin Mehta, Matt Parry and Phillipa Velija.</para>
<para xml:id="b-0000104">I would also like to thank John Wiley and Sons for kind permission to reprint
aspects of <link role="bib" linkend="b-0003496">Dominic Malcolm, ‘The Diffusion of Cricket to America:
A Figurational Sociological Examination’, <emphasis role="italic">Journal of Historical Sociology</
emphasis>, June 2006, pp. 151–173</link>; Dominic Malcolm, ‘It's Just Not Cricket: Colonial Legacies and
Contemporary Inequalities’, <emphasis role="italic">Journal of Historical Sociology</emphasis>, September
2001, pp. 253–275, and Taylor &amp; Francis for kind permission to reprint excerpts from Dominic Malcolm,
Jon Gemmell and Nalin Mehta, ‘Cricket and Modernity: International and Interdisciplinary Perspectives on
the Study of the Imperial Game’, <emphasis role="italic">Sport in Society</emphasis>, May 2009, vol. 12,
Issue 4–5.</para>
<para xml:id="b-0000105">Thanks also go to colleagues both at Leicester and Loughborough universities
who have been happy to chat about cricket and who I have mined for ideas over the years, especially
Eric Dunning. Most of all, though, I would particularly like to thank my family who firstly fostered my
fascination with cricket and who subsequently have had to learn to tolerate it.</para>
</acknowledgements>

Acknowledgements sections may end with a sign-off by the author. For examples on how these are to
be marked up see Section 10.9, “Prefaces”.

10.8. Glossaries and abbreviations lists

Ref: §1.68, §1.69

NOTE: This differs slightly from the previous instructions

See also Chapter 19, Lists.

Glossaries and abbreviation lists SHOULD usually be contained within a glossary. The only
exception to this MAY be where the chunk also contains other more complex structural divisions for
which multiple nested sections may be needed, in which case preface may be most suitable.

Chronology sections in the front matter or elsewhere MUST NOT be contained within a
glossary; the preface element SHOULD normally be used for such content if in the front
matter (or an appendix if in the back matter), normally within a variablelist, or possibly a
table/informaltable for multi-column chronologies. See Section 10.9, “Prefaces” and Section 19.4,
“Variable lists”.

All glossary/abbreviation items MUST be within a glossentry, and each glossentry MUST
have an ID, as described in Section 5.2.4, “IDs for glossary terms”. The formatting of terms and their
definitions (ie italicisation etc) MUST be preserved.

Simple glossary lists MUST be a sequence of glossentry elements:

<glossary xml:id="b-001">
<info xml:id="b-0002168">
<title xml:id="b-0003219"><?page value="ix"?>Abbreviations</title>
<pagenums>ix–x</pagenums>
<mediaobject xml:id="b-glossary-001c">
<imageobject xml:id="b-glossary-001d">
<imagedata fileref="pdfs/9781849664554.0004.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<glossentry xml:id="b-0000036">
<glossterm>AARP</glossterm>
<glossdef xml:id="b-0000037">
<para xml:id="b-0000038">American Association of Retired Persons</para>
</glossdef>
</glossentry>
<glossentry xml:id="b-0000039">
<glossterm>AFL-CIO</glossterm>
<glossdef xml:id="b-0000040">
<para xml:id="b-0000041">American Federation of Labor/Congress of Industrial Organizations</para>
</glossdef>

70
 Front matter

</glossentry>

If there are headings within the glossary, glossdiv sections MUST be used.

Note also that, for glossary lists with other content (paragraphs and floating headings etc) or if there
is a space between two lists of abbreviations/terms, the lists MUST be in a separate glosslist (see
example below):

<glossary xml:id="id4">
<info>
<title>Abbreviations and Conventions</title>
</info>
<glosslist>
<glossentry xml:id="BṛUB">
<glossterm><emphasis role="italic">Bṛ. UB.</emphasis></glossterm>
<glossdef><para>Bṛhad-āraṇyaka Upaniṣadbhāṣya</para></glossdef>
</glossentry>
<glossentry xml:id="GK">
<glossterm><emphasis role="italic">GK</emphasis></glossterm>
<glossdef><para>Kārikās on the Māṇdūkya Upaniṣad a.k.a. the Gauḍapādīya-kārikā</para></glossdef>
</glossentry>
</glosslist>

<glosslist>
<glossentry xml:id="C">
<glossterm>C.</glossterm>
<glossdef><para>Chinese</para></glossdef>
</glossentry>
<glossentry xml:id="Skt">
<glossterm>Skt.</glossterm>
<glossdef><para>Sanskrit</para></glossdef>
</glossentry>
</glosslist>

Cross references within the body text to terms in the glossary SHOULD be explicitly linked23:

<para>‘Then there is only one way left, viz., to describe It as “Not this, Not this,” by eliminating
all possible specifications of It that have been known’ (<glossterm linkend="BṛUB"><emphasis
role="italic">Bṛ.UB.</emphasis></glossterm> 2.3.6).</para>

However, note that some instances of abbreviations may be in a plural form; these still MUST be
linked:

<para xml:id="b-0000264">The willingness to recognize and acknowledge the complexity of relationships that
extend beyond traditional nuclear family boundaries is an important feature of Adrienne Asch's concept
of ‘parental fitness’, in <link role="xref" linkend="b-chapter-009">Chapter 9</link>. Asch revisits
the idea of licensing parenthood, particularly in relation to the provision of assisted reproductive
technologies (<glossterm linkend="ART">ART</glossterm>s), and argues that parental responsibility, rather
than procreative liberty, is a better criterion upon which to base access to assisted reproduction. The
creation of children via the use of <glossterm linkend="ART">ART</glossterm>s has implications <?page
value="10"?>for the special responsibilities imposed upon parents in this situation, including obligations
of openness about children's origins.</para>

Implementation note: The default DocBook stylesheets render glossterm as italic (at least in
the pdf output). This is WRONG, and the style of the text MUST be preserved.

In those cases where abbreviations are included in the text, but only defined on their first occurrence
(ie there is no glossary or abbreviations list), it is desirable that each subsequent instance of the
abbreviation in the text includes an expansion within an alt element:

<footnote role="end-bk-note" xml:id="b-9781474208482-0002330"><para

xml:id="ba-9781849662932-0002331">‘Social Science European Fellowship Committee 1934–35’, 15 April 1931,
RF, RG 1.1, s. 717, b. 16, f. 151, <abbrev><alt>Rockefeller Archive Center</alt>RAC</abbrev>.</para></
footnote>

23
Bob Stayton ‘Linking to a glossary entry’ DocBook XSL. Sagehill. http://www.sagehill.net/docbookxsl/
LinkToGlossary.html

71
 Front matter

10.9. Prefaces
Ref: §1.51

The preface element MUST be used to contain front matter content that does not otherwise belong
in one of the other front matter-type elements (see Section 10.1, “Front matter container”, though note
also that occasionally an introduction MAY occur within the front matter, for which see Section 11.2,
“Introductions”).

Typically a preface will have a title of “Preface”, though a range of other front matter content MAY
be contained within this element, eg:

• A timeline or chronology (the content of which MAY be in a variablelist or even a table or

informaltable)

• A table

• Series preface

• Foreword

• The prelims chunk (see Section 10.3, “Prelims chunk”)

<preface xml:id="b-preface-001">
<info>
<title>Globalizing Sport Studies Series Editor's Preface</title>
</info>
<para xml:id="b-0000093">There is now a considerable amount of expertise nationally and internationally
in the social scientific and cultural analysis of sport in relation to the economy and society more
generally. Contemporary research topics, such as sport and social justice, science and technology and
sport, global social movements and sport, sports mega-events, sports participation and engagement and the
role of sport in social development, suggest that sport and social relations need to be understood in non-
Western developing economies, as well as European, North American and other advanced capitalist societies.
The current high global visibility of sport makes this an excellent time to launch a major new book series
that takes sport seriously, and makes this research accessible to a wide readership.</para>
<!--content omitted for clarity -->
<para role="right" xml:id="b-9781474208482-0000099">John Horne, Preston and Edinburgh 2012</para>
</preface>

Occasionally, Prefaces or Forewords may be signed, ie include the author’s name, city, date etc at the
end of the text, which may also be right aligned, as in the example above. [Signed Forewords at top of
page need to have author in info]

The example above shows that it may be permissible to use the para element, when the signature
statement runs on. However, it is PREFERABLE to use address, whether or not a place is actually
mentioned eg:

<para xml:id="id0039">This is the final paragraph.</para>

<address xml:id="ju765" role="right"><personname>David E. James</personname>
<city>Los Angeles</city>, <date>June 15, 2000</date></address>
</preface>

Note that, in this context, personname does not require a @role or name components within it.

72
Chapter 11. Introductions, chapters,
parts, titles and @labels
11.1. Usage of chapter and part elements
The chapter and part elements are the primary containers for the bulk of the content within any
book.

The part element MUST be used for:

• The front matter container (see Section 10.1, “Front matter container”)

• Numbered (or occasionally, unnumbered) Part divisions, containing child chapters or other
parts

• Other numbered (or unnumbered) grouping containers within a Part (eg Sections containing
chapters)[include example in the labelling section below, since auto-generated label may be
affected]

• The back matter container (see Section 12.1, “Back matter container”)

The chapter element MUST be used for:

• Introductions

• Numbered chapters

• Other content chunks in the body text or back matter for which no other element is appropriate
[OK? Give examples]

11.2. Introductions
Ref: §1.51

The Introduction is a chapter at the beginning of the book, usually titled “Introduction” or
related, and without a chapter number. If an Introduction exists, it will usually be the chapter
on page 1 (Arabic numeration), though occasionally an Introduction may have Roman numerals
and contained within the front matter. In the latter such cases, they MUST be contained within
part[@role=’front’] (see Section 10.1, “Front matter container”).

The title of the Introduction MUST be included within the title exactly as it appears in the
book, and MAY also have a subtitle. Introductions MUST NOT have a @label, unless they are
explicitly numbered as a chapter:

<chapter xml:id="b-0061">
<info>
<title>Introduction</title>
<subtitle>Sociology and its discontents</subtitle>

It is possible that some books may have a numbered chapter with a title “Introduction”. Such items
would be marked up as a regular numbered chapter (see Section 11.3, “Chapter and Part labelling”):

<chapter label="1" xml:id="b-chapter-001">

<info>
<title>Introduction</title>

73
 Introductions, chapters,
parts, titles and @labels

11.3. Chapter and Part labelling

All numbered parts and chapters MUST use the @label to record the Part/Chapter number in
a numeric (Arabic or Roman) form. Even if the print style is to spell the chapter numbers in words
(eg “Chapter Three”), the @label value MUST be numeric (usually Arabic, but often Roman for Part
titles). 1 Furthermore, the @label MUST NOT include words or abbreviations such as “Chapter”,
“Part”, “Ch.” Etc.

Note that @xreflabel is NOT REQUIRED.2

<part label="I" xml:id="id12345">

<info>
<title>A part title</title>
</info>
<chapter xml:id="id1234456" label="2">
<info>
<title>Chapter title here</title>
</info>

If there is no number for the content (eg for unnumbered Introductions, see Section 11.2,
“Introductions”), there MUST NOT be a @label on the element.

See also Section 9.2, “Chunk and section titles and numbering”.

11.4. General use of @label

Just as with parts and chapters, the @label attribute can be used on many other elements that can
take numbers, such as appendix, equation, example, table, figure, section. The @label
MUST store the numeric value of the label, unless the only text that should appear in the title is a
simple string, as the following table illustrates:

Printed form Container element @label <title>

Chapter 1: The chapter 1 The beginning
beginning
Chapter One chapter Chapter One
Part IV: Aristotle in the part IV Aristotle in the Middle
Middle Ages Ages
PART 2 part Part 2
Appendix B: appendix B Chronologies
Chronologies
Appendix appendix Appendix
Figure 2: Place des figure 2 Place des Vosges
Vosges
4. Creativity in China section 4 Creativity in China

Typically, therefore, if a title begins with the words “chapter”, “equation”, “figure” etc that is an error
if there is also a numeric value and a more expansive, descriptive title.3 In addition, the @label
should not start with similar words,4 nor should it – in the context of a nested section – contain a
full point.5
1
Tested in Schematron : one-in-label and related tests
2
Tested in Schematron : xreflabel-not-required
3
Tested in Schematron : check-title, appendix-tests
4
Tested in Schematron : check-label
5
Tested in Schematron : check-label-3

74
 Introductions, chapters,
parts, titles and @labels

If non-standard labels are required (eg “Section 1” for a part element), use @role=labelOverRide
and add the entire label content to @label.

See also Section 7.5.11, “Other biblioids”, Section 9.2, “Chunk and section titles and numbering”.

75
Chapter 12. Back matter
The back matter is here defined as containing any or all of the following chunks:

• Afterword

• Conclusion

• Postscript

• Acknowledgements

• Appendix

• Addendum

• Back of book Glossary (some occur within the front matter)

• Notes

• Bibliography

• Index

In addition, the back matter MAY contain a web-only container for content that appears in print in a
back-of-book CD or other media insert.

12.1. Back matter container

By analogy with front matter, the back matter MUST be contained within a part[@role=’back’]

Though each of the child chunks within the back matter container MUST contain key metadata, the
back container itself MUST NOT contain: pagenums;1 a DOI;2 or a pdf file reference.3

The content of part[@role=’back’]/info/title MUST be “Back matter”.4

<part xml:id="b-00212" role="back">

<info>
<title>Back matter</title>
</info>

12.2. Back matter elements

Container elements for back matter content will most likely be:5

Element Section
chapter
appendix
glossary Section 10.8, “Glossaries and abbreviations lists”
bibliography Section 16.2, “Bibliography container”

1
Tested in Schematron :no-pagenums-back
2
Tested in Schematron :no-doi-back
3
Tested in Schematron :no-pdf-back
4
Tested in Schematron: back-matter-title
5
Tested in Schematron: back-chunk

76
 Back matter

Element Section
Index Chapter 29, Indexes and index terms

12.3. Additional media files (ancillary back-of-

book CD content)
Some books contain additional materials in a back-of-book CD. It MAY be required that such material
is also made available in an online edition and so MUST be included in the data package (see
Chapter 3, Deliverables and file-naming conventions).

If that is the case, there MUST be a container within the back matter that contains links to all the extra
media files. This MUST have an @role=ancillary, and text for the content will be provided by
Bloomsbury.

<appendix xml:id="ki1" outputformat="e-Only" role="ancillary">

<info xml:id="ki2">
<title xml:id="ki3">Additional materials</title>
</info>
<para xml:id="ki4">The following supporting materials are available:</para>
<itemizedlist xml:id="sk438" mark="none">
<listitem xml:id="dk39s"><para xml:id="dle0">Unit I: Merchandising for a profit</para>
<itemizedlist xml:id="so49">
<listitem xml:id="sgo59"><para xml:id="dlr9f"><link xlink:href="media/I%20Defining%20the%20Basic%20Profit
%20Factors.xls" role="relative" conformance="application/excel">I: Defining the Basic Profit Factors</
link></para></listitem>
<listitem xml:id="sgo52"><para xml:id="dlr3f"><link xlink:href="media/II%20Profit%20and%20Loss
%20Statements.xls" role="relative" conformance="application/excel">II: Profit and Loss Statements</link></
para></listitem>
</itemizedlist></listitem>
</itemizedlist>
</appendix>

See also Section 15.7, “Links to content in the data package”.

77
Chapter 13. Multi-volume works
[add details and examples]

78
Chapter 14. Common components
14.1. Paragraphs
[Intro]

Implementation note: para[1] within any block should be full out, and then subsequent ones
should have first line indented as is usual in the printed book.

14.1.1. Block elements within paragraphs etc

Ref: §1.25

Block elements within paragraphs or inline elements (such as inlinemediaobject) which are
the only child of a paragraph are generally ERRORS.1 The containing para element is NOT
REQUIRED in such circumstances. Inline elements MUST be replaced with block equivalents and
block elements such as itemizedlist must replace their containing paragraph if they are the only
child element.2

For example, the following is WRONG3:

<para>Now let's have a numbered list:</para>

<para><orderedlist>
<listitem><para>First item</para></listitem>
<listitem><para>Second item</para></listitem>
<listitem><para>Third item</para></listitem>
</orderedlist></para>

It MUST be encoded as:

<para>Now let's have a numbered list:</para>

<orderedlist>
<listitem><para>First item</para></listitem>
<listitem><para>Second item</para></listitem>
<listitem><para>Third item</para></listitem>
</orderedlist>

The only occasion when block elements SHOULD appear within a para is when it forms a
grammatical part of the text and typically the following text after the block is full out (see also the
next section):

<para>Sometimes it may be necessary to have a list within a paragraph, such as here:

<itemizedlist>
<listitem><para>Item 1</para></listitem>
<listitem><para>Item 2</para></listitem>
</itemizedlist>
which only makes sense if the sentence continues after the list. Otherwise, the lists must be siblings of
the paras.</para>

It would be an ERROR to encode the text starting “which only makes sense” in the preceding
example as a new para. Consequently, a para SHOULD NOT start with a lower case letter, unless it
is part of a list of some sort.4 For example, the following is INCORRECT:
1
Tested in Schematron: convert-inline-to-block
2
Tested in Schematron: para-single-block
3
The single exception to this rule is where a list may be required within an abstract; since abstract has a limited content
model, it is permissible to include a list within a para in this context, though that is likely to be very rare.
4
Tested in Schematron: para-lower-case

79
 Common components

place, the present during the murder, and the past afterwards, as it acts as a reminder of the murder that
has happened. The linearity of time is</para>
<?page value="67"?>
<para xml:id="b-9781408174654-0001086">abolished, the materiality of the tapestry is defamiliarised as
Polonius&#8217;

which should be:

place, the present during the murder, and the past afterwards, as it acts as a reminder of the murder that
has happened. The linearity of time is
<?page value="67"?>abolished, the materiality of the tapestry is defamiliarised as Polonius&#8217;

14.1.2. Paragraphs, vertical white space and other text

separators
Normal paragraph style in print is for the first paragraph after a heading to be full out, and then
subsequent paragraphs to have the first line indented, as in the following example:

which would simply be marked up with unadorned paras:

<section xml:id="s" label="1">

<info xml:id="s1">
<title xml:id="s2">Psychoanalysis</title>
</info>
<para xml:id="s3">Schelling's connections to psychoanalysis are conceptually clear. He developed a theory
of the unconscious as a set of pre-personal drives that matches the contours of Freud's account. Canonical
works like Hartmann's groundbreaking <emphasis role="italic">Philosophy of the Unconscious</emphasis>
acknowledge the centrality of Schelling's contribution here.</para>
<para xml:id="s4">In his article, 'Several Connections between Aesthetics and Therapeutics in Nineteenth-
century Philosophy' (which has been translated into English ...</para>

(Note the use of the @label on section, see Section 9.2, “Chunk and section titles and numbering”)

However, if a para needs to be full out in another context, use @role with either:

• fullOut

• spaceBefore

Usage of these two options is described below.

The @role=fullOut is simply for when paragraphs must not be indented for whatever reason, yet
have otherwise the same styling as regular paragraphs.

[add examples]

80
 Common components

However, @role=spaceBefore is for when the flow of text is broken either by some white space:

in which case we need to add a @role to the para to indicate that it is separated off from the
preceding one:

<section xml:id="s5">
<info xml:id="s6">
<title xml:id="s7">Method</title>
</info>

<para xml:id="s8">The heart of the instructional process is the matching of the predispositions and
expectancies of the child to the demands of the new content. Bruner’s preferred means for achieving that
match are through the process of discovery....</para>
<para xml:id="s9" role="spaceBefore">Bruner cited some evidence produced by his wife and collaborator Carol
Feldman that nicely illustrated the common absence of the hypothetical mode in most classroom contexts.
Feldman had recorded the teacher’s use</para>

A similar example is here, where some text has been omitted by the editor:

81
 Common components

which would be encoded as:

<para xml:id="s10">... between two ways of not being a being (<emphasis role="italic">Nichtseiendem</
emphasis>) (<emphasis role="italic">ouk on</emphasis> and <emphasis role="italic">me on</emphasis>) it is,
on the contrary, Schelling who can help Sartre make important distinctions.</para>
<para xml:id="s11" role="spaceBefore">[...]</para>
<para xml:id="s12" role="spaceBefore">Gerhard Seel, in what is currently the best German-language book on
Sartre's philosophy, suggested that Sartre's method be interpreted as dialectical.</para>

However, note that full out paragraphs after blockquotes suggest that the blockquote should be
contained within the paragraph:

as follows:

<para xml:id="s13">It is this joint or shared attention and sensitivity to the meanings and intentions of
others that makes the acquisition of language possible, Bruner argued. Although Bruner was an enthusiastic
supporter of Chomsky’s notion of a generative grammar, a kind of linguistic competence unique to human
beings, Bruner thought Chomsky attributed too much of language learning to an innate grammar. On the basis
of his observations of children he wrote:
<blockquote xml:id="s14">
<para xml:id="s15">What was very soon plain was that mother and child were negotiating their respective
intentions through communication: using whatever conventional means could be brought to bear and inventing
conventions where none had yet been established. The <emphasis role="italic">last</emphasis> thing our
children were doing, it seemed to me, was concentrating on literal utterances, extracting deep rules of
universal grammar from them. And the last thing our mothers seemed concerned about was giving ‘grammar
lessons’. (Bruner 1983a, p. 167; 1983b)</para>
</blockquote>
The pragmatics of language, its use for communication and for elaborating subjectivity, was seen as
primary; acquiring the structure of language was the byproduct of shared meanings.</para>

Occasionally there may be some separator between paragraphs, eg asterisks as in the example below:

82
 Common components

which would be encoded as:

<para xml:id="s16">... Vater's conclusion is that Schelling cannot avoid this; but it is only by renouncing
a philosophical enterprise that the Buddhist tradition succeeds.</para>
<para xml:id="s17" role="center">* * *</para>
<para xml:id="s18" role="spaceBefore">The heterogeneity of the articles collected in this volume is
testimony to the diversity and fruitfulness of Schelling's thought ...</para>

Finally, if a paragraph is separated from the main flow of text, often following a title, as here:

then it MUST take @role='info':

<article xml:id="b-9781609032227-e1">
<info xml:id="b-9781609032227-e2">
<title xml:id="b-9781609032227-e3">United States of America</title>
<pagenums>1–26</pagenums>
<biblioid class="doi">10.5040/9781609032227.051</biblioid>
</info>

<para xml:id="b-9781609032227-e4" role="info">Population: 281,421,906 (2000)</para>

<para xml:id="b-9781609032227-e5">The United States of America is one of three countries on the North
American continent, sharing borders with Canada to the north and Mexicco to the south.</para>

83
 Common components

In short, empty para elements MUST NOT be used to add extra vertical white space between
paragraphs, and filling them with a non-breaking space character isn’t allowed either.5

Implementation note: para[@role] is not supported in the standard DocBook stylesheets.

@role=’spaceBefore’ needs to add some vertical white space before the paragraph as well
as rendering it out.

14.1.3. Formal paragraphs

A formal paragraph is one with a title. Typically, these occur most often in legal texts where
paragraphs are numbered, and may contain blockquotes and lists as well as paras:

For such features, a formalpara MUST be used:

<formalpara xml:id="b-9781234567890-fp4.03">
<info xml:id="n1">
<title xml:id="n2">4.03</title>
</info>
<para xml:id="n3">By virtue of Article 256 TFEU, the General Court has first-instance jurisdiction over
direct actions brought by <emphasis role="italic">individuals</emphasis> who seek:</para>
<orderedlist xml:id="n4" numeration="loweralpha">
<listitem xml:id="n5"><para xml:id="n6">to challenge the validity of legislative acts and other acts
intended to produce
legal effects <emphasis role="italic">vis-a-vis</emphasis> third parties (Article 263 TFEU);</para></
listitem>
<listitem xml:id="n7"><para xml:id="n8">to review the lawfulness of failures to act on the part of the
institutions of the
Union (Article 265 TFEU)...</para></listitem>
</orderedlist>
</formalpara>

For works other than Case Reports, it is REQUIRED to use predictable IDs for the formalpara since
such texts often have extensive internal cross references that use them (see Section 5.2.6, “IDs for formal
paragraphs”).

Note that the inclusion of other block content is an extension to DocBook; multiple paras are
permissible since they do sometimes occur within a single numbered item.

See also the different style in the following example, where the brackets around the para number
MUST also be retained in the title, and the formalpara would contain both these paragraphs. Note
also the internal links to numbered paragraphsin the footnotes:

5
Tested in Schematron: impermissible-empty-element, only-contains-nbsp

84
 Common components

If footnotes occur at the end of the paragraph, a specific @role is REQUIRED. See Section 18.2.3, “End
of paragraph notes”.

14.2. Font styles and font weight

Ref §1.26, §1.96, §1.97, §1.98, §1.99

NOTE: This is stricter than the previous instructions

Inline emphasis MUST be preserved using the emphasis element. Emphasis on elements such as
title need not be preserved if the emphasis can be predicted from the markup. For example, if
all B-heads are fully italicised then the emphasis MUST NOT be marked up. The @role value is
REQUIRED and MUST take one of the following values:

• italic

• bold

• underline

• line-through

• roman

• monospace

• smallcaps

• larger

• smaller

• sans-serif

85
 Common components

• serif

For instance, this small caps example:

<emphasis role="smallcaps">J. Arthur Rank</emphasis>

would be rendered as:

J. Arthur Rank

Similarly,

<emphasis role="smallcaps">weight</emphasis>

would be rendered as:

WEIGHT

It is an ERROR for small caps to contain only upper case content.6

In addition, making all of a title italic, simply to follow the print style is WRONG:7

<title xml:id="id0213"><emphasis role="italic">The Unchained Bible</emphasis></title>

whereas the following example correctly uses emphasis in a title since the emphasised text are
work titles:

<title xml:id="id0201"><emphasis role="italic">To Gaurus On How Embryos are Ensouled</emphasis> and

<emphasis role="italic">On What is in Our Power</emphasis></title>

Note that “superscript” and “subscript” are not valid values for @role; use the corresponding
elements instead.8

Implementation note: Only italic and bold appear to work in the current DocBook XSL

14.3. @role attributes

Ref: §1.28, §1.29, §1.30

NOTE: This differs markedly from the previous instructions

The @role attribute MAY occur on a number of elements to provide additional semantic information.
The standard DocBook schema does not mandate any specific usage, though some are implied in the
DocBook XSL tools.

Our approach here is to enforce defined lists of @role values within the local customisation of the
DocBook Publishers schema. If values are implied by the DocBook XSL tools we will use those,
possibly with some extensions; otherwise, we will mandate specific values for @role and when they
are to be used.9
6
Tested in Schematron: smallcaps-test
7
Tested in Schematron: title-not-all-emphasis
8
Tested in Schematron: superscript, subscript
9
Tested in Schematron: test-role-attribute

86
 Common components

The following table summarises all such values, and provides cross references to the corresponding
sections elsewhere in this document where their usage is discussed:

Element Values of @role Section

book fullText Section 7.3, “Content type”
pdfOnly
abstract authorAbstract Section 7.5.13, “Blurb/abstract”; Section 9.3.5,
blurb “Chunk abstract/extract”
extract
address center Section 10.9, “Prefaces”
left
right
appendix ancillary Section 12.3, “Additional media files (ancillary
back-of-book CD content)”
article articleGroup Section 9.5.3, “More complex article and
biblioArticle dummy entry”; Section 9.5.6, “Article
lessonPlan components (dictionary-type content)” and
snapshotArticle especially Section 9.5.1, “Article @roles”
xref
attribution center Section 24.2, “Epigraphs”
left
right
bibliography further-reading
biblioid discovery Section 7.5.10, “ISBNs, DOI and CIP
epdf information”
epub
hardback
paperback
xml
bibliolist inline Section 16.16, “Inline bibliographic references”
bibliomisc anon Section 7.5.1, “Title group”; Section 7.5.4,
category “Series”; Section 7.5.15, “Other prelim
contributorStatement content”; Section 16.7.12, “Classical authors/
description single names + series”; Section 9.3.1, “Chunk
heading1 author(s)”; Section 16.12, “Legal references”;
heading2 Section 9.5.6, “Article components (dictionary-
imprint type content)”
legalRef
previousTitle
series
species
bibliomixed article Section 16.4, “Bibliographic items”
case
contribution
legislation
message
monograph
other
serial
series
unpublished

87
 Common components

Element Values of @role Section

website
biblioset isbns Section 7.5.4, “Series”; Section 7.5.6,
publisher “Publisher details”; Section 7.5.10, “ISBNs,
series DOI and CIP information”
chapter labelOverRide Section 18.2.2, “End of book notes”; Section 9.2,
notes “Chunk and section titles and numbering”
cover halfTitleVerso Section 7.5.15, “Other prelim content”;
series Section 7.5.8, “Imprint logo”
titlePage
date accessed Section 16.11, “Web sites”
dialogue line-below-speaker Section 24.4, “Drama”
line-follows-speaker
drama screenplay Section 24.4.5, “Screenplay excerpts”
emphasis bold Section 14.2, “Font styles and font weight”
italic
larger
line-through
monospace
roman
sans-serif
serif
smallcaps
smaller
underline
firstname initials Chapter 17, Names
footnote end-bk-note Chapter 18, Footnotes, endnotes and other notes
end-ch-note
margin1
margin2
imageobject suppressPDF Section 9.3.3, “PDF file reference and file
naming”
keywordset BergGlossary Currently for backlist conversion only
BergKeywords
legalnotice CC Section 7.5.9, “Copyright/CC details”
CIP
Open
line center Section 24.3, “Poetry”; Section 24.4, “Drama”
left
partFinal
partInitial
partMedial
right
stageDirection
lineage comma-before Chapter 17, Names
mediaobject imprintLogo Section 7.5.8, “Imprint logo”
note annotations Section 14.13, “Notes”; Section 32.16.7, “Case
disposition Reports”
facts

88
 Common components

Element Values of @role Section

history
holding
judgment
othername middle Chapter 17, Names
middle-initials
para caseNumber Section 14.1.2, “Paragraphs, vertical
catchwords white space and other text separators”;
center Section 9.5.2, “General A-Z reference content”;
court Section 10.2.1, “Impressions”; Section 21.3,
fullOut “Image sources”; Section 32.17, “Biology and
gender natural history works with taxonomic content”;
hearingDate Section 32.16.7, “Case Reports”
impressions
info
judgmentBy
judgmentDate
left
legalRepresentation
oao
panel
period
right
see
source
spaceBefore
taxonAuthority
part back Section 10.1, “Front matter container”;
front Chapter 12, Back matter; Section 9.2, “Chunk
labelOverRide and section titles and numbering”
personname first-last Section 16.4.4, “Personal names”
last-first
phrase articleTitle Section 7.5.9, “Copyright/CC details”;
audioID Section 21.3, “Image sources”; Section 24.4,
bibleRef “Drama”; Section 9.5.6, “Article components
bookTitle (dictionary-type content)”; Section 32.17,
caseName “Biology and natural history works with
continuation taxonomic content”; Section 32.16.7, “Case
origin Reports”
periodicalTitle
philosopherName
pronunciation
resp
seg
source
stageDirectiona
synonym
taxonEnglish
taxonName
taxonRank
term
videoID

89
 Common components

Element Values of @role Section

The following values are
specifically for use in
architecture works, and only
when advised by Bloomsbury:

architect
buildingType
date
geolocation
material
peoplesCultures
placeRegion
structuralFeature
style

The following value(s) are for

internal/future use and only
when adivsed by Bloomsbury:

incompleteXref
preface contributors Section 10.3, “Prelims chunk”; [add section on
legalContents contributor]; Section 10.5, “Tables of cases and
prelims statutes”
pubdate published Section 7.5.5, “Publication date”
section bibliography Section 18.2.1, “End of chapter notes”;
exercises-activities Section 9.2, “Chunk and section titles and
labelOverRide numbering”; Section 9.5.3, “More complex
notes article and dummy entry”; Section 9.5.6,
overview-objectives “Article components (dictionary-type content)”
recipe
subArticle
terms
sidebar embeddedArticle Chapter 26, Sidebars; Section 21.6, “Plate
exercises-activities sections”
overview-objectives
plateSection
sidebar1
sidebar2
sidebar3
sidebar4
sidebar5
sidebar6
sidebar7
sidebar8
sidebar9
terms
title keepWithNext Section 7.5.4, “Series”; Section 9.5.4, “Article
series parts and dummy headings”
translation
volumenum series Section 7.5.4, “Series”
a
This value is now deprecated and should not be used. Reported by Schematron stageDirectionDeprecated

90
 Common components

14.4. Page breaks

Markers at the beginning of a page in the print edition MUST be inserted using processing
instructions.10 If there is no print edition (ie book[@outputformat=’e-Only’]) then page break
markers are NOT REQUIRED (see Section 7.4, “Digital-only books”).

<?page value="2"?>

These MUST be inserted where they occur in the text and MUST be sequential; where chunk
elements start a new page, they MUST be inserted at the beginning of the text in the title
element:11

</chapter>
<chapter xml:id="c1" label="2">
<info>
<title><?page value="36"?>The reign of Victoria</title>

</info>

ie the following, placed before the preceding block elements is WRONG:

<?page value="36"?></para></chapter>
<chapter xml:id="c1" label="2">
<info>
<title>The reign of Victoria</title>
</info>

Similarly, placing the page break marker within the text of the previous chunk is also WRONG.

It is also an error for a page break to be the first node before an info, and it is usually wrong for it to
immediately follow and info.12

Where page breaks occur between paragraphs or items in a bibliography etc, the marker MUST be
placed between those elements, NOT as the first or last child of one of them:13

<bibliomixed xreflabel="Choe 2009" role="article" xml:id="ba-9781849664554-0002597"><bibliomset

relation="article" xml:id="ba-9781849664554-0002598"><author><personname role="last-first"><surname>Choe</
surname><firstname role="initials">S.-H.</firstname></personname></author> (<pubdate>2009</pubdate>),
&#x2018;<title xml:id="ba-9781849664554-0002599">South Korea Fights Slump through Hiring, Not Firing</
title>&#x2019;</bibliomset>, <bibliomset relation="journal" xml:id="ba-9781849664554-0002600"><title
xml:id="ba-9781849664554-0002601"><emphasis role="italic">International Herald Tribune</emphasis></title>,
2 April, <pagenums>p. 1</pagenums>, <pagenums>p. 4</pagenums></bibliomset>.</bibliomixed>
<?page value="185"?>
<bibliomixed role="article" xml:id="ba-9781849664554-0002602"><bibliomset relation="article"
xml:id="ba-9781849664554-0002603"><author><personname role="last-first"><surname>Coase</surname><firstname
role="initials">R.H.</firstname></personname></author> (<pubdate>1937</pubdate>), &#x2018;<title
xml:id="ba-9781849664554-0002604">The Nature of the Firm</title>&#x2019;</bibliomset>, <bibliomset
relation="journal" xml:id="ba-9781849664554-0002605"><title xml:id="ba-9781849664554-0002606"><emphasis
role="italic">Economica</emphasis></title>, <volumenum>4</volumenum>(<issuenum>16</issuenum>):
<pagenums>386–405</pagenums></bibliomset>.</bibliomixed>

Similarly, page break markers must be placed between sections when a section starts a new page;
placing the PI within the section title is WRONG:14

question, nevertheless, remains as to how long microfinance can continue to provide consumption-smoothing
support or extending the payments schedule. To be able to serve as a viable poverty reduction strategy,
micro-credit financed enterprises must expand and create decent jobs for the growing labour force.</para>

10
Tested in Schematron : page-breaks-missing, page-breaks-missing-2, page-break-format
11
Tested in Schematron : page-break-sequence, page-break-pos-1. Page breaks are not permitted as direct children of:
set, book, info, part, mediaobject, imageobject, videoobject, audioobject, primary, secondary, tertiary,
see, seealso, alt, inlinemediaobject, remark, indexterm, itermset, varlistentry, figure, informalfigure
12
Tested in Schematron : info-before-pb, info-after-pb
13
Tested in Schematron : page-break-pos-2, page-break-pos-3
14
Tested in Schematron: pb-section-title

91
 Common components

</section>
<?page value="178"?>
<section xml:id="ba-9781849664530-0003700">

<info xml:id="ba-9781849664530-0003701">
<title xml:id="ba-9781849664530-0003702">Concluding Remarks</title>
</info>
<para xml:id="ba-9781849664530-0003703">It is often claimed that the greatest discovery of the Grameen-led
microfinance movement has been the credit worthiness of the poor. Related to this has been the discovery
of the dynamism of Microenterprises. In reality, however, neither is new. The poor have been borrowing
from money lenders (landlords) from time immemorial. Microenterprises have been operating for a long time
in many poor societies, and form the vast informal sector

Furthermore, a sequence of page break markers grouped together is usually WRONG, unless there is
a sequence of blank pages ending a chunk, and page break markers are not permitted as a child of a
footnote.15

Finally, the first and last page number in the page PI MUST match the equivalent values in that
chunk’s pagenums.16

See also worked examples in Section 32.13, “Page break placement”

Implementation note: Page break markers may need to have a subtle indicator in the text of
some applications, and also be an anchor point for any page-based navigation that the site will
support.

Page break markers must not be displayed if they occur in title elements (see examples),
though hidden anchors must be retained.

14.5. Column and line breaks

The placement of column break markers MUST be handled in the same way as page breaks with the
following processing instruction:

<?break type="column"?>

For multi-column page layouts, this break PI is sufficient since the previous and following page break
markers show the start and end point of the columns. However, for other text presented in columns it
is necessary to use start and end point markers as well:17

<?break type="column-start"?>
<glossentry xml:id="b-0000042">
<glossterm>BBVA</glossterm>
<glossdef xml:id="b-0000043">
<para xml:id="b-0000044">Banco Bilbao Vizcaya Argentaria</para>
</glossdef>
</glossentry>
<glossentry xml:id="b-0000045">
<glossterm>BIEN</glossterm>

<glossdef xml:id="b-0000046">
<para xml:id="b-0000047">Basic Income Earth Network</para>
</glossdef>
</glossentry>
<glossentry xml:id="b-0000048">
<glossterm>CBT</glossterm>
<glossdef xml:id="b-0000049">
<para xml:id="b-0000050">Cognitive behavioural therapy</para>
</glossdef>
</glossentry>
<glossentry xml:id="b-0000051">
<glossterm>CCT</glossterm>
<glossdef xml:id="b-0000052">

15
Tested in Schematron : page-break-sequence, pb-in-footnote
16
Tested in Schematron : page-no-match1, page-no-match1
17
Presence reported in Schematron : columns-present

92
 Common components

<para xml:id="b-0000053">Conditional cash transfer</para>

</glossdef>
</glossentry>
<?break type="column"?>
<glossentry xml:id="b-0000054">
<glossterm>CIA</glossterm>
<glossdef xml:id="b-0000055">
<para xml:id="b-0000056">Central Intelligence Agency</para>
</glossdef>
</glossentry>
<glossentry xml:id="b-0000057">
<glossterm>CRI</glossterm>
<glossdef xml:id="b-0000058">
<para xml:id="b-0000059">Crime Reduction Initiatives</para>
</glossdef>
</glossentry>
<glossentry xml:id="b-0000060">
<glossterm>EHRC</glossterm>
<glossdef xml:id="b-0000061">
<para xml:id="b-0000062">Equality and Human Rights Commission (UK)</para>
</glossdef>
</glossentry>
<?break type="column-end"?>

Line breaks MUST only be used sparingly; ordinarily, if there is a line break in the print layout, it will
be effected by regular markup. However, very rarely, some formatting MAY be necessary to force a
line break other than simply to replicate page layout. In such cases the following PI MUST be used:18

<?break type="line"?>

The break PI MUST contain a type, which MUST be one of the values described above.19

See examples in Section 10.6, “Dedication” and Section 16.2, “Bibliography container”.

Implementation note: Not supported in standard DocBook XSL

14.6. Conditional processing with @condition

DocBook supports conditional processing using the @condition attribute. It is REQUIRED in only a
small number of instances:20

Usage Rationale See also

1. Implied authors and other To support occasions where Examples under: Section 16.7.10,
bibliographic information in displayed content is insufficient “Implied authors (books)”,
some references to support the generation of Section 16.7.15, “Multi-volume,
OpenURL queries: uses values: abbreviated form and translated
display | hiddena versions”, Section 32.15.3,
“Implied authors in bibliographies”,
Section 16.7.11, “Ibid, loc cit, and
op. cit.”
2. Equation handling To support both graphics and Section Section 23.3, “More
MathML representation of complex equations”
equations: uses values: mathmal
| non-mathml
3. Handling of generic non- To support specific instances Sections Section 10.3, “Prelims
display content where unused content elements chunk”,

[Add section]
18
Presence reported in Schematron : line-break-present
19
Tested in Schematron : break-type, break-typology
20
Presence reported in Schematron : condition-present

93
 Common components

Usage Rationale See also

are included in the data to create
a valid file: uses value: hidden
a
Tested in Schematron : display-item-but-no-hidden-sibling

The following elements are most likely to require @condition for one of these uses:21

author, bibliomset, editor, equation, glossterm, informalequation,

inlineequation, inlinemediaobject, phrase, pubdate, remark, title

14.7. @outputformat
The @outputformat attribute is available on some elements to control the conditions when its
content is to be used. Typically, this is used for figures where different versions of an image are
supplied for print or web use (see Chapter 21, Figures and images).

In addition, @outputformat may be used for specifying which output formats should display a
chunk title or when a book has only a digital (no-print) manifestation. See Section 9.2.1, “Chunks
with no titles” and Section 7.4, “Digital-only books”.

Or, this attribute may also be used for other content which should only be displayed for a specific
output type. See Section 14.10.5, “Print- or web-only content” and the example in Section 32.14.5, “Print-
specific content”.

The following elements are likely to require @outputformat for one of these uses:22

imagedata, title, book, phrase, member, para, mediaobject, appendix,

part, chapter, section

14.8. Rights
Most of the time rights will have been cleared for all uses of a particular piece of content. However,
if digital rights are not available for an image or data chunk, this can be indicated in the metadata for
that item.

<informalfigure xml:id="ij8h" label="1.2">

<mediaobject xml:id="if9f9">
<info xml:id="hbgvc">
<releaseinfo role="noDigitalRights"></releaseinfo>
</info>
<imageobject xml:id="ji58jd"><imagedata fileref="images/fig_1-2.jpg" format="image/jpeg" /></imageobject>
</mediaobject>
</informalfigure>

Implementation note: Such content will need to be suppressed for digital usage, perhaps with a
textual indicator to note that something is not present. Not supported in standard DocBook XSL

14.9. Addresses
Address components typically occur in:
21
Tested in Schematron: test-condition-attribute
22
Tested in Schematron: outputformat-attribute

94
 Common components

• book/info

• bibliomixed

• at the end of some front matter chunks (eg Preface)

• chapter/info

They MAY contain any of the following address component elements:

• street

• city

• state

• country

• postcode

• pob

• otheraddr

Addresses should usually have their component parts encoded.23

<publisher>
<publishername>Bloomsbury Publishing Plc</publishername>
<address xml:id="b-0000078"><street>50 Bedford Square</street> <city>London</city> <postcode>WC1B 3DP</
postcode> <country>UK</country></address>

<address xml:id="b-0000079"><street>175 Fifth Avenue</street> <city>New York</city> <state>NY</state>

<postcode>10010</postcode> <country>USA</country></address>
<address xml:id="m65"><link xlink:href="http://www.bloomsbury.com"><uri>www.bloomsbury.com</uri></link></
address>
</publisher>

14.10. General text issues

This section details some general problems that may sometimes occur within a marked-up text.

14.10.1. Spaces and emphasis

Text capture MUST reflect the author’s text, including use of spaces. Some text capture processes may
inadvertently lead to loss of some white space before and after emphasis, which MUST be corrected
(though note that not all emphasis is necessarily surrounded by white space).24

The test in the preceding footnote generates the following warning:

Description: An emphasis element is followed by text node with no space between

This can be where there is an indexterm and no space between, in which case add a space before the
indexterm(if it is added after the indexterm there is a possibility that the wrong page number will
get added when the DocBook autogenerated index is created:

<para xml:id="ba-9781849666015-0002404">Two specific issues in relation

to <emphasis role="italic">Prevent</emphasis><indexterm class="singular"

23
Tested in Schematron : bibliomixed-address, country-name-test, address-components
24
Tested in Schematron : possible-missing-space, possible-missing-space2

95
 Common components

xml:id="ba-9781849666015-0002405"><primary>far-right extremism</primary><secondary>and universities</

secondary><seealso>BNP</seealso><seealso>BNP</seealso></indexterm>and universities arguably show the

In addition, we sometimes get these being picked up by the same warning:

However, the gravity of the charge and its potential impact on <emphasis role="italic">Prevent</emphasis>‘s
success means that it must be analysed in greater depth, and that is what this chapter attempts to do.

In this case, the apostrophe s has the wrong character; it should be &#x2019; (right single quote) but
we have &#x2018; (left single quote).

A space is also REQUIRED before an inline bibliolist (see Section 16.16, “Inline bibliographic
references”).

14.10.2. Minimal content in emphasis

If an emphasis element contains ONLY a comma, full stop or most other punctuation, that is an
ERROR.25

14.10.3. Comments
Though there MAY be a case for including XML comments in a text, as a rule they are to avoided.26

14.10.4. Asterisks etc

When asterisks, daggers and double daggers appear in text, they usually indicate a note of some sort,
so typically should be in a link, or they may need to be an @label of a footnote.27

For example, in a bibliography preceded by this text:

<section xml:id="ba-9781472555564-0000617"><info xml:id="ba-9781472555564-0000618"><title

xml:id="ba-9781472555564-0000619">Select Bibliography</title></info>
<para role="fullOut" xml:id="ba-9781472555564-0000620">Note: we have placed an asterisk next to those
titles that have proved particularly useful to us in the writing of the chapters as a guide to further
reading.</para>
</section>

and then individual items within the bibliography have asterisks which are linked back to this text:

<bibliomixed role="monograph" xml:id="ba-9781472555564-0000641"><link

linkend="ba-9781472555564-0000620">*</link><author><personname role="last-first"><surname>Anderegg</
surname><firstname>Michael</firstname></personname></author> (<pubdate>1999</pubdate>), <title
xml:id="ba-9781472555564-0000642"><emphasis role="italic">Orson Welles, Shakespeare and Popular
Culture</emphasis></title>. <address xml:id="ba-9781472555564-0000643"><city>New York</city></address>:
<publishername>Columbia University Press</publishername>.</bibliomixed>

Note that the asterisk is not within any of the name components, which is NOT ALLOWED.28

14.10.5. Print- or web-only content

There are occasions when textual content is different for print or online usage. For example, if there
are explicit references to the print edition and to page numbers it may be desirable to provide an
alternative form of the text for a non-print version. The @outputformat attribute is available to
support such different usages.
25
Tested in Schematron : emphasis-comma, emphasis-stop, emphasis-colon, emphasis-semicolon, emphasis-
empty, emphasis-lsquo, emphasis-rsquo, emphasis-rdquo, emphasis-ldquo
26
Tested in Schematron : comment-present
27
Tested in Schematron : asterisk-in-text
28
Tested in Schematron : asterisk-in-name

96
 Common components

Here, it is desirable to add a ‘print-only’ indicator on the containing member element so that text can
be suppressed online, and also to ensure that the the textual quote is itself a link back to its source
on page 1:

<simplelist>
<member xml:id="a1" outputformat="print"><emphasis role="bold">Page 1</emphasis></member>
<member xml:id="a2"><link linkend="t1">"For as long as I can remember"</link></member>
<member>From acceptance speech for Screen Actors Guild Award for Outstanding Performance by a Male Actor
in a Leading Role (<emphasis role="italic">There Will Be Blood</emphasis>, Daniel Day-Lewis, January 27,
2008.</member>
</simplelist>

Furthermore, on page 1, the actual quote needs to point to the above target in the Textual References:

and he said <link linkend=a2>"For as long as I can remember"</link>

14.10.6. Processing instructions

The following processing instruction types are permitted29 :

Type Usage See

break Line and column breaks Section 14.5, “Column and line
breaks”
insert Placement of end of chapter or Section 18.2, “Note placement”
end of book notes
page Page breaks Section 14.4, “Page breaks”
oxygen For use with the Oxygen editor
dbhtml For control of table HTML Section 32.8.1, “A relatively simple
formatting using DocBook XSL table”
dbfo For control of table FO Section 32.8.1, “A relatively simple
formatting using DocBook XSL table”

14.11. Natural history and biology content

If a chapter, article or section is about a single taxon or species, and Bloomsbury have instructed for
this feature to be applied, the name components MUST be marked up and a biblioid included to
record the Taxon Rank. So, for a simple work, this could be like this:
29
Tested in Schematron : invalid-pi

97
 Common components

<chapter>
<info>
<title><phrase role="taxonEnglish">Bullfinch</phrase></title>
<subtitle><phrase role="taxonName">Pyrrhula pyrrhula</phrase></subtitle>
<biblioid class="other" otherclass="taxonRank">species</bibliomisc>
</info>

For further detail and examples see Section 32.17, “Biology and natural history works with taxonomic
content”.30

14.12. Anchors
For the most part, if internal links are required there will normally be a block element that contains a
suitable @xml:id that can form the target. In very rare circumstances, there might not be an element
in the target location, in which case the DocBook anchor element MUST be used. In the following
example, a paragraph is broken by a very long sidebar, and there is text which alerts the reader to
this:

<para>...Trainees are most often recent college graduates and are viewed by <phrase
role="continuation">(continued on <link role="xref" linkend="X"><phrase outputformat=print>page 13</
phrase><phrase outputformat="online">below</phrase></link>)</phrase>
<sidebar>
<info><title>Careers Up Close</title></info>
<!—content omitted for clarity -->
</sidebar>
<?page value=13?>
<anchor id="X"/>the company as potential buyers or managers. Because the competition for department
store training programs is stiff, a bachelor’s degree is necessary, as is a high grade
point average and prior retail experience.</para>

In the print edition of this example, the text within the phrase[@role=continuation] is
displayed as a catchword-type feature, outside of the main flow of the text, so containing it within this
element allows it to be located specially, if required.

Note also the alternatives for print and online usage within the link.

14.13. Notes
The note element MAY be needed in some specialised content, namely legal Case Reports
and annotated legislation. In such content it is used as a container for specific components, and
MUST have a @role.31 Note that, if headings are needed within a note, then the bridgehead
element MUST be used, and for @role=annotations, such bridgehead MUST have
@renderas=sect3.32

<note xml:id="b-9781849664554-0000109" role="history">

<bridgehead renderas="sect1" xml:id="b-9781849664554-0000109b">Appeals</bridgehead>
<para xml:id="b-9781849664554-0000109c">AC, GS and the Law Society of England and Wales appealed from
two judgments of the President of the Court of Protection, Sir James Munby, of 7 August 2014 (<emphasis
role="italic">Re X (deprivation of liberty) (no 1)</emphasis> [2014] EWCOP 25, [2015] 2 FCR 15, [2015] 2
All ER 1154) and 16 October 2014 <emphasis role="italic">Re X (deprivation of liberty) (no 2)</emphasis>
[2014] EWCOP 37, [2015] 2 FCR 28, [2015] 2 All ER 1165). The Secretary of State for Health and the
Secretary of State for Justice also appeared and the Official Solicitor intervened. The facts are set out
in the judgment of Black LJ.</para>
</note>

For annotated legislation, the note/@role MUST take the value 'annotations'; other values are those
permitted in a Case Report.33
30
Tested in Schematron : taxon-siblings, taxon-rank-check, taxonRank-test
31
Tested in Schematron: note-cases, note-role
32
Tested in Schematron: bridgehead-annotations
33
Tested in Schematron: leg-note, leg-case

98
 Common components

See also Section 14.3, “@role attributes”, and examples in Section 32.16.7, “Case Reports” and
Section 32.16.8, “Annotated legislation”.

99
Chapter 15. Cross references and
linking
Ref: §1.79, §1.80, §1.81, §1.82, §1.83, §1.84, §1.85

There are several types of link available in DocBook and it can normally be difficult to determine
which linking element should be used in a given context. Additionally, DocBook 5.0 allows almost
any element to be the source of a link by use of XLink; however, such linking is NOT PERMITTED.
This document takes a simple and consistent approach to linking and specifies how linking elements
MUST be used for Bloomsbury content.

15.1. Simple internal links

The link element is for most internal links within the book. This is for those situations where the link
text is in the body of the text, apart from the examples in sections below. For example:

<para xml:id="id0082">Paragraphs can have internal links, which contain <link linkend="c2"
role="xref">inline text</link>.</para>

The link element MUST have either a @linkend OR @xlink:href (for the latter see Section 15.5,
“External links”),1 and MUST have content (ie empty link elements are NOT ALLOWED).2

In addition, for internal links (ie when link[@linkend]), the link MUST also have a @role to
indicate the nature of the link target:3

@role value Usage

figure Link target is a figure element
table Link target is a table element
bib Link target is a bibliomixed element (ie for
bibliographic linking)
relative Link target is a separate, distinct file within the
data bundle (see Section 15.7, “Links to content in
the data package”)
xref All other internal linking (eg to chapters,
examples, equations etc)

IMPORTANT: This use of @role is REQUIRED for all new books (though MAY NOT be for data
conversion projects), and to activate it the book’s schematronVersion MUST be set to 2 (or
greater).4 See Section 7.5.11, “Other biblioids”.

Note also that Section 5.2.5, “IDs for bibliographic items” suggests that it MAY be desirable to adopt a
more human-readable form of ID for bibliomixed (or indeed for any often-used link target) if that
makes it easier to resolve the links.

See some examples of links to bibliographic items using this method in Section 16.3.2, “Irregular cross
references”.

This is a link to another chapter in the book, which uses @role=xref:

1
Tested in Schematron : linkend-or-href
2
Tested in Schematron : empty-link
3
Tested in Schematron : role-or-href, link-target-figure, link-target-table, link-target-bibliomixed,
link-target-xref
4
Tested in Schematron : link-role-required, link-role-version

100
 Cross references and linking

<para xml:id="si31">In <link role="xref" linkend="ch2">Chapter 2</link>, I surveyed the main currents of
Shakespeare criticism from 1904 to the 1970s. One of the most obvious differences between the critics we
looked at in that chapter and the new ...</para>

<para xml:id="sb1">... which is supported by a Higher Education Academy grant (see <link role="xref"
linkend="sb2">Vignette 1</link>). He argues that involving students as co-producers, more properly perhaps
co-participants in teaching, is the route to excellence. It is also much more appropriate to the ‘wicked
problems’ that exist outside Oxford’s dreaming spires: its Fellows may continue to dream while the rest of
the world accelerates into potential nightmares.</para>

Furthermore, note that not all textual references to “chapter 3” may be to the chapter 3 in the current
book. Please check all cross references for context to ensure that the link target implied by the author
is the one in the current book. For example, in this text the chapter references are to the cited work,
though the Appendix is in the current book, so only the short form reference and the Appendix
reference should be links:

An excellent meta-analysis is provided in VLRC (2007), especially chapters 2 and 12, and
Appendix 1.

The span included within the link MUST NOT include unbalanced brackets.5

[Add example of unbalanced brackets]

Furthermore, if a link span includes quotes and brackets, or is particularly long, it is likely that the
span is too long and the wrong component MAY be included.6

In addition, if a name is followed by a date in brackets, it is the date only that MUST be linked:

<para xml:id="ba-9781849661812-0000560">Some of the negative environmental effects of pesticides are listed

by Dinham (<link role="bib" linkend="ba-9781849661812-0006826">1993</link>, p. 64) as: ‘water pollution,
soil degradation, insect resistance and resurgence, the destruction of native flora and fauna, and some,
as ozone depleters, contribute to the greenhouse effect’.</para>

ie, the following is WRONG:

<para xml:id="ba-9781849661812-0000560">Some of the negative environmental effects of pesticides are listed

by <link role="bib" linkend="ba-9781849661812-0006826">Dinham (1993, p. 64)</link> as: ‘water pollution,
soil degradation, insect resistance and resurgence, the destruction of native flora and fauna, and some,
as ozone depleters, contribute to the greenhouse effect’.</para>

[Add more examples]

Note that xref and biblioref, and @endterm7 are NOT TO BE USED.

See also Section 16.3, “Inline citations” for further information on linking to bibliographic items.

Finally, note that links in titles which are only one character long may need to be rendered as a
superscript.8

15.2. Glossary links

Where terms and phrases are mentioned in the text that are included in a glossary or list of
abbreviations, these MUST be linked using the glossterm element with a @linkend corresponding
with its target in the glossary.

For a full description and examples see Section 10.8, “Glossaries and abbreviations lists”.
5
Tested in Schematron : unbalanced-brackets-1 and unbalanced-brackets-2
6
Tested in Schematron : suspicious-link-content and long-link-content
7
Tested in Schematron : endterm-present
8
Tested in Schematron : short-link-text

101
 Cross references and linking

15.3. Links to page numbers

It is common for titles to include internal cross-references of the type "see page 125" or "on pages
120-121" (although the copy-editing guidelines discourage the use of cross-references to page
numbers). When these types of cross-references occur they must be marked up as internal links (using
the link element in these cases), the target of which MUST be the page processing instruction’s
parent element (processing-instruction(page)/parent::*[@xml:id]). The linking text
must be that part of the text which refers to the target as shown in the example below.

<para xml:id='b-0017'>A picture captures the point much better than words. Using data provided (generously
for free) by BigChampagne Online Media Measurement, we can graph the average number of p2p users from
August 2002 to October 2006 (see <link role="xref" linkend='b-1023'>pages 112–13</link>). The gray bar
indicates when the Supreme Court decided <emphasis role="italic"> MGM v. Grokster, </emphasis>holding p2p
file sharing to be illegal… </para>

See also Section 14.4, “Page breaks”.

15.4. Internal links with generated text

On rare occasions it is not appropriate to use a link element for an internal link. This is because some
internal links point to targets with a standard means of addressing them, so MUST use the empty
pointer element footnoteref.

15.4.1. footnoteref
The footnote element generates or includes the actual footnote number/marker that is displayed
in the text. However, if a subsequent reference to the same footnote target is required, this MUST be
achieved using the footnoteref element, the @linkend of which MUST be the ID of the target
footnote element.9

<footnoteref linkend="a1"/>

A @label on footnoteref should not be required, since that will be derived from the footnote
target.10

15.5. External links

The link element MUST be used for external links and MUST use the @xlink:href attribute to
indicate the target URI of the link.11

As the example below illustrates, the link MAY contain text, though normally will contain a web or
email address. When web addresses are included in the text, they MUST also be included within a
uri element12 which must not contain spaces,13 and the @xlink:href MUST be a valid URL14
and include the http:// protocol, even if the URL in the text does not. Email addresses MUST also
be included within an email element, and the @xlink:href MUST have a mailto: prefix15 :

<para xml:id="id0084">The link element must be used for links to external sites, using <emphasis
role="monospace">@xlink:href</emphasis>. The link element can <link xlink:href="http://
www.bloomsbury.com">contain text</link> though normally will contain a URL, as here: <link

9
Tested in Schematron : footnoteref-target
10
Tested in Schematron : footnoteref-label
11
Tested in Schematron : linkend-or-href
12
Tested in Schematron : external-link-content, untagged-url, empty-href
13
Tested in Schematron : uri-spaces
14
Tested in Schematron : whitespace-in-href, uri-check
15
Tested in Schematron : email-tests

102
 Cross references and linking

xlink:href="http://www.oxforddnb.com"><uri>www.oxforddnb.com</uri></link> and email: <link

xlink:href="mailto:[email protected]"><email>[email protected]</email></link></para>

15.5.1. Embedded links (online only)

In content featured in online products, where the end-point of the link should be presented embedded
within the flow of the surrounding content, attribute xlink:show MUST be used:16

<link xlink:href="http://databank.worldbank.org/data/embed/CountryProfile/id/b450fd57/wd/0/ht/0/tbar/y/dd/
y" xlink:show="embed">
<uri>http://databank.worldbank.org/data/embed/CountryProfile/id/b450fd57/wd/0/ht/0/tbar/y/dd/y</uri>
</link>

The expected rendering here might be to use the URL as the src attribute of an HTML5 iframe.
Note that the relevant URI is still included as the content of the element; this may be suppressed by
the renderer.

15.5.2. Other uses

The only other instance where linking is used is for recording the Bloomsbury person ID for book
authors and editors (see Section 7.5.2, “Author group”). In that case, xlink attributes are included on
the corresponding elements. Consequently, xlink linking attributes are only permissible on author,
editor, othercredit and link, and only in the combinations as specified in this document.17

15.6. DOI links

If DOIs occur in the text they MUST be encoded as links.18 Typically these will occur in bibliographic
items. They MAY have a “http://” prefix, but often they will not.

<bibliomixed role="article" xml:id="b-0000292"><bibliomset relation="article"

xml:id="b-0000293"><author><personname role="last-first"><surname>Cutas</surname><firstname
role="initials">D.</firstname></personname></author>, (<pubdate>2011</pubdate>) ‘<title>On Triparenting:
Is having three committed parents better than having only two?</title>’</bibliomset>, <bibliomset
relation="journal"><title><emphasis role="italic">Journal of Medical Ethics</emphasis></title> doi: <link
xlink:href="http://dx.doi.org/10.1136/jme.2011.043745">10.1136/jme.2011.043745</link></bibliomset></
bibliomixed>

Note that where a DOI is present not in a URL form (as in the example above), its textual value
MUST stay the same, but the prefix “http://dx.doi.org/” MUST be added to the @xlink:href.19

15.7. Links to content in the data package

Physical copies of books may sometimes contain a CD in the back of the book that contains additional
content (Word or Excel files, images, or whatever). Such content MAY also need to be represented
in the XML (see Section 12.3, “Additional media files (ancillary back-of-book CD content)”), and may in
any event need to be explicitly linked from the book text. In such cases, the target data MUST be
bundled in the same zipped data package as the book XML (see Chapter 3, Deliverables and file-naming
conventions).

For example, here is a reference to one such file with the book body text:

<simplelist xml:id="qw1">

16
See Schematron xlink-testing-4
17
Tested in Schematron : biblio-id-present, biblio-id-format, and patterns: xlink-testing-1, xlink-
testing-2, xlink-testing-3, xlink-testing-4
18
Tested in Schematron: unlinked-doi, external-link-content, untagged-doi
19
Tested in Schematron : doi-href

103
 Cross references and linking

<member xml:id="qw2"><link xlink:href="media/APPENDIX%20I%20-%20Basics%20of%20EXCEL

%20-2.doc" role="relative" conformance="application/msword">The Basics of Microsoft Excel Spreadsheets</
link> [Word]</member>
</simplelist>

These links to files within the data package MUST have @role=relative AND @xlink:href; and
their targets MUST be within one of the directories within the package (images, pdfs, media).20
The @conformance attribute MUST also be present, and its value MUST be the MIME type of the
target file.21 Permissible values are:

MIME type File extensions

application/msword .doc, .docx
application/excel .xls, .xlsx
application/postscript .ps
application/pdf .pdf
application/mspowerpoint .ppt, .pptx
text/plain .txt
text/html .html, .htm
text/css .css
text/xml .xml
image/png .png
image/gif .gif
image/jpeg .jpeg, .jpg
image/bmp .bmp
image/tiff .tiff, .tif
video/mpeg .mpeg, .mpg, .mp3

Implementation note: This may need an extension to regular link processing to ensure such
links are handled appropriately.

15.8. Links to other books

Very occasionally, it may be necessary to link to content in other books. This will always be a special
instruction for a specific book, and will require the target book data to be available.

There are two methods available: for inline linking (see this section); and other (implied) links, for
which see Section 9.5.6, “Article components (dictionary-type content)”: Section 9.5.6.2, “Linking to other
books”

The element for such inline links is olink, which MUST only be used for this specific purpose.

Typical cases where this might be required are in reference works, where works may cite material in
other books.

An olink MUST have @type=otherBook, and @targetdoc and @targetptr, where

@targetdoc MUST be the @xml:id of the target book, and @targetptr MUST be a valid ID
within the target book.22
20
Tested in Schematron : relative-href, relative-link-dir
21
Tested in Schematron : conformance-required, conformance-values, link-conformance-1 through to link-
conformance-23
22
Tested in Schematron : olink-targetdoc, olink-targetptr, olink-type, olink-targetdoc-id1, olink-
targetdoc-id2, olink-targetdoc-id3, olink-targetptr-id

104
 Cross references and linking

<para xml:id="kis4">See also the article <olink targetdoc="b-9781234567890" targetptr="targetid"

type="otherBook">Green economics</olink> in the companion volume to the current work.</para>

Occasionally, olink may have @type=glossary, in order to drive presentation of online glossary entries.
Bloomsbury will specify for which books this value MUST be applied.

Implementation note: This is not supported in standard DocBook XSL and will need
downstream support.

See also the example in Section 32.15.2, “Cross references to other books in the series”.

15.9. Linking sections and bibliographies

Occasionally, it may be desirable to encode a link relationship between two sections in a book. This is
not normally required, and Bloomsbury will specify for which books it MUST be applied.

The example below illustrates how a section in the text body can use @linkend to point to a
corresponding section elsewhere in the text, in this case to explicitly link to the bibliographic items
that relate to the section:

<chapter label="18" xml:id="c18">

<info xml:id="q1">
<title xml:id="q2">Art and Literature of the Avant-Gardes, 1897-1918</title>
<!-- Other info content here -->
</info>
<section xml:id="s1">
<info xml:id="s2">
<title xml:id="s3">Origin of the Avant-Garde</title>
</info>
<para xml:id="p1">Early in the 19th century, the term “avant-garde,” which originally described the
position of an army on the battlefield came to characterize the arts as well. In 1845, a Frenchman,
Gabriel Désiré Laverdant, ...</para>
</section>
<section xml:id="s4">
<info xml:id="s5">
<title xml:id="s6">Expressionism</title>
</info>
<para xml:id="p2">While in Tahiti, Gauguin rediscovered the woodcut....</para>
</section>
<section xml:id="s7" linkend="hy7">
<info xml:id="s8">
<title xml:id="s9">Cubism and Orphism</title>
</info>
<para xml:id="p3">Of all the avant-garde movements, Cubism had the most powerful effect on commercial art
and graphic design. ....</para>
</section>
<section xml:id="s4a" role="bibliography">
<info xml:id="s5a">
<title xml:id="s6a">Bibliography</title>
</info>
<section xml:id="sie8">
<info xml:id="de54"><title xml:id="xi9">Bibliographic essay</title>
</info>
<para xml:id="p1a">Renato Poggioli’s <emphasis role="italic">The Theory of the Avant-Garde</emphasis> was
an early attempt in the later 1960s to theorize avant-garde practice in terms of its aesthetic and social
significance. ....</para>
</section>
<section xml:id="s12">
<info xml:id="er5">
<title xml:id="dei6">Books</title>
</info>
<section xml:id="sw3">
<info xml:id="ft5"><title xml:id="de4">General</title></info>
<bibliolist xml:id="hy2">
<bibliomixed role="monograph" xml:id="swi8"><!-- Biblio content here --></bibliomixed>
</bibliolist>
</section>
<section xml:id="hy7">
<info xml:id="gt5">
<title xml:id="i4s">Cubism and Orphism</title>

105
 Cross references and linking

</info>
<bibliolist xml:id="ytre">
<bibliomixed role="monograph" xml:id="k85"><!-- Biblio content here --></bibliomixed>
</bibliolist>
</section>
</section>

The @linkend attribute is only permitted on link and section elements.23

Implementation note: This is not supported in standard DocBook XSL and will need
downstream support.

23
Tested in Schematron: test-linkend-attribute

106
Chapter 16. Bibliographies and
components
Ref: §1.56, §1.57

NOTE: This differs markedly from the previous instructions

16.1. Bibliography type

The usual Bloomsbury style for Bibliographies is for initials to use stops after them. If this is not the
case, a special flag MUST be added to the header of the file. See Section 17.1, “Initials in biblio names”

Baudot, F (1997) Paul Poiret Thames and Hudson

16.2. Bibliography container

Bibliographies are generally marked up using the bibliography element. Any section of text
labelled as either a bibliography or as references MUST be marked up using one of the bibliography
elements. The bibliography element can occur at the same hierarchical level as a chapter
or within chapter-type elements. When an untitled list of citations is used within content, the
bibliolist element should be used to wrap the citations, which MUST have a @role=inline if it
flows within a paragraph. See example below.

Bibliographies may be divided using bibliodiv elements, which MUST have a title. If the
bibliography is divided up using white space as in this example:

this can be achieved using (preferably) a sequence of bibliolists, or a Processing Instruction (see
Section 14.5, “Column and line breaks”):

<?break type="line"?>
<bibliomixed role="monograph" xml:id="beau-001"><author><personname role="last-first"><surname>Beaumont</
surname> <firstname>Francis</firstname></personname></author> and <author><personname role="last-
first"><surname>Fletcher</surname> <firstname>John</firstname></personname></author>, <title><emphasis
role="italic">The Dramatic Works</emphasis></title>, ed. <editor><personname role="first-
last"><firstname>Fredson</firstname> <surname>Bowers</surname></personname></editor>, 9 vols,

107
 Bibliographies and components

<address><city>Cambridge</city></address>: <publishername>Cambridge University Press</publishername>,

<pubdate>1966-94</pubdate>.</bibliomixed>

Implementation note: Display of bibliodiv titles when they are within info is not
supported in DocBook XSL

16.3. Inline citations

Items in bibliographies are usually referenced elsewhere in the text.1 This section covers such cases
where there is a short form bibliographic reference in the text, pointing to an item in the bibliography.
For instances where there is a full bibliographic reference in the text distinct from a true bibliography
see Section 16.16, “Inline bibliographic references”.

16.3.1. Standard short form references

Where there are bibliographic items referred to in the running text using a standard short form
(typically ‘Surname, yyyy’ or ‘Surname yyyy’):

The old order has the picks of a hundred rebellions thrust into its hide. (Gouldner 1970: vii)

these MUST be linked using the link element (with @role; see Section 15.1, “Simple internal links”):

<para>The old order has the picks of a hundred rebellions thrust into its hide. (<link role="bib"
linkend="b-0003692">Gouldner 1970</link>: vii)</para>

where the target is in the bibliography:

<bibliomixed role="monograph" xml:id="b-0003692"><author><personname role="last-first"><surname>Gouldner</

surname><firstname role="initials">A.</firstname></personname></author> (<pubdate>1970</pubdate>) <title
xml:id="b-0003693"><emphasis role="italic">The Coming Crisis in Western Sociology</emphasis></title>.
<address xml:id="b-0003694"><city>New York</city></address>: <publishername>Basic Books</publishername></
bibliomixed>

The target MUST be the bibliomixed.2 It is an ERROR for the target to be one of the child
elements of bibliomixed.3

Here is another standard short form reference in the form “Surname YYYY”:

The bibliographic item itself (ie the target of the short form reference) would be marked as follows:
1
Tested in Schematron: bibliomixed-referenced, unlinked-bibliomixed-count. If no biblio items in the book are
cross referenced at all, these tests can be switched off with the allBiblioItemsUnlinked flag. See Section 7.5.11, “Other
biblioids”.
2
Tested in Schematron: link-target-bibliomixed
3
Tested in Schematron: link-target-title

108
 Bibliographies and components

<bibliomixed role="monograph" xml:id="bir"><author><personname role="last-first"><surname>Birley</

surname> <firstname>D.</firstname></personname></author> (<pubdate>1999</pubdate>), <title><emphasis
role="italic">A Social History of English Cricket</emphasis></title>, <address><city>London</city></
address>: <publishername>Aurum Press</publishername>.</bibliomixed>

and the footnote text encoded as:

<footnote xml:id="fn1"><para xml:id="fn2">The Star and Garter Club in London also played a key role in the
foundation of horse racing’s Jockey Club (<link role="bib" linkend="bir">Birley 1999</link>: 31).</para></
footnote>

For a slightly more complex example, this endnote:

11 See discussion of income differences in the United States in Paul Krugman, The Conscience of a
Liberal, W.W. Norton and Company, New York, 2009 and 2007, Chapter 1.

points to this item in the bibliography:

<bibliomixed role="monograph" xml:id="ba-9781849661003-cs0003540"><author><personname role="last-

first"><surname>Krugman</surname><firstname role="initials">P.</firstname></personname></author>, <title
xml:id="ba-9781849661003-cs0003541"><emphasis role="italic">The Conscience of a Liberal</emphasis></
title>, <publishername>W.W. Norton</publishername>, <address xml:id="ba-9781849661003-cs0003542"><city>New
York</city></address><address xml:id="ba-9781849661003-cs0003543"><city>London</city></address>,
<pubdate>2009</pubdate>.</bibliomixed>

So, the text in the footnote which references it will be:

<footnote role="end-bk-note" xml:id="ba-9781849661003-cs0001661"><para xml:id="ba-9781849661003-

cs0001662">See discussion of income differences in the United States in <link role="bib"
linkend="ba-9781849661003-cs0003540">Paul Krugman, <emphasis role="italic">The Conscience of a Liberal</
emphasis></link>, W.W. Norton and Company, New York, 2009 and 2007, Chapter 1.</para></footnote>

Such short form cross references MUST NOT be included within a bibliomixed.4 For example, the
following is WRONG:

<footnote role="end-bk-note" xml:id="ba-9781472554932-0001969"><para

xml:id="ba-9781472554932-0001970"><bibliolist xml:id="ba-9781472554932-0001971" role="inline"><bibliomixed
role="other" xml:id="ba-9781472554932-0001972"><author><personname role="last-first"><surname>Olivier</
surname></personname></author>, &#x2018;<title xml:id="ba-9781472554932-0001973">An Essay</title>&#x2019;,
<pagenums>15</pagenums>.</bibliomixed></bibliolist></para>
</footnote>

Note also that note content of the form “See ...” may well be followed by material that needs to be
linked or converted to a full bibliographic reference. In addition, references to “Chapter” etc may
also need to be linked to targets elsewhere in the current book, though as the example above shows
that care MUST be taken in doing so since the context is important and the text may be pointing
to a different book entirely.5 Such cross references are NOT REQUIRED in works of fiction (see
Section 7.5.11, “Other biblioids”).

Here is an “et al”-type short form reference:

<footnote xml:id="bai"><para xml:id="bai1">This chapter builds on prior collaborative work with Alan
Bairner. I am grateful to him for allowing me to draw on ideas we discussed in previous conference papers
(eg <link role="bib" linkend="bi1">Bairner <emphasis role="italic">et al.</emphasis> 2007</link>). Any
errors in the current analysis are of course my own.</para></footnote>

See also Section 16.3.2, “Irregular cross references”, and further examples in Section 32.5.1, “Short-form
bibliographic references”.
4
Tested in Schematron: short-biblio
5
Tested in Schematron: possible-chapter-link, possible-appendix-link

109
 Bibliographies and components

In addition, see Section 32.5.2, “Same work in multiple bibliomixeds” for an example where the same
work may appear multiple times in bibliographies in a book, so it is important that each cross
reference points to the correct target instance.

16.3.2. Irregular cross references

If works are cited in the running text that are NOT in the standard short form, they may need special
consideration:

A number of excellent introductory texts on the work of Norbert Elias have already been
published. Central among them are Stephen Mennell’s seminal Norbert Elias: an Introduction
(1998); Richard Kilminster’s pathbreaking The Sociological Revolution (1998) and Norbert Elias:
Post-Philosophical Sociology (2007);

these MUST be cross referenced using a link around the date to the expanded form in the
bibliography (or elsewhere):

<para xml:id="b-0000055">A number of excellent introductory texts on the work of Norbert Elias have already
been published. Central among them are Stephen Mennell’s seminal <emphasis role="italic">Norbert Elias:
an Introduction</emphasis> (<link role="bib" linkend="b-0003857">1998</link>); Richard Kilminster's
path-breaking <emphasis role="italic">The Sociological Revolution</emphasis> (<link role="bib"
linkend="b-0003738">1998</link>) and <emphasis role="italic">Norbert Elias: Post-Philosophical Sociology</
emphasis> (<link role="bib" linkend="b-0003748">2007</link>);

the first item of which points to:

<bibliomixed role="monograph" xml:id="b-0003857"><author><personname role="last-first"><surname>Mennell</

surname><firstname role="initials">S.</firstname></personname></author> (<pubdate>1998</pubdate>) <title
xml:id="b-0003858"><emphasis role="italic">Norbert Elias: an Introduction</emphasis></title>, <address
xml:id="b-0003859"><city>Dublin</city></address>: <publishername>UCD Press</publishername></bibliomixed>

Note also the placement of the link container elements; link elements MUST NOT straddle one of
a pair of brackets6 , so here only the year MUST be within the link element:

Major (2007: 42) concludes, ‘a rough and tumble, or an illegal affray, was a frequent
accompaniment to a competitive game or an unsettled bet, and in a violent age that may have
been an added attraction’.

If this reference had been of the form “Major (2007) concludes...”, then the string “2007” would have
been within the link.

16.3.3. Application of biblio references

There are three references in the following extract:

6
Tested in Schematron: unbalanced-brackets-1; unbalanced-brackets-2

110
 Bibliographies and components

In 1970, a highly influential book by Alvin Gouldner was published with the title, The Coming
Crisis of Western Sociology. Gouldner’s central thesis in that book was that America was then in
the throes of a multi-layered rebellion in which the black civil rights movement, the women’s
movement, and protest against the Vietnam War were central. It was a rebellion mainly of
younger people which spread widely through the West, with university campuses forming
major sites of resistance to the status quo. In such a context, Gouldner argued rhetorically that:

Social theorists today work within a crumbling social matrix of paralyzed urban centers and
battered campuses. Some may put cotton in their ears, but their bodies still feel the shock
waves. It is no exaggeration to say that we theorize today within the sound of guns. The old
order has the picks of a hundred rebellions thrust into its hide. (Gouldner 1970: vii)

In such a context, Gouldner maintained, sociologists were becoming increasingly drawn into
‘the coalescing military-industrial-welfare complex’ with the consequence that it was becoming
‘unthinkingly evident that sociology has become dangerously dependent on the very world
it has pledged to study objectively’ (1970: 511). In short, sociologists were being increasingly
incorporated into the status quo and used as instruments of management and social control.
They were, Gouldner proposed, producing ‘interested’ accounts of the social world and, in that
way, becoming both part of the problem and of the forthcoming sociological crisis as Gouldner
envisaged it. His solution was to call for the development of a ‘radical’ and ‘reflexive’ sociology
practised by self-aware and critical sociologists dedicated to gathering knowledge which could
be used in ushering in a new era.

The full title of the book does not need to be linked to the bibliography. The two others (“Gouldner
1970” and “1970: 511”) MUST be linked, using link.

16.4. Bibliographic items

Ref: §1.58, §1.59, §1.60, §1.61, §1.62, §1.63, §1.64

NOTE: This differs markedly from the previous instructions

Full bibliographic citations tend to occur at the end of chapters or at the back of books.

These MUST use bibliomixed as their container, ie biblioentry is NOT PERMITTED. The
content of the bibliomixed element MUST represent the appearance of the content in the original
text as far as possible. All formatting, spacing and punctuation MUST be present in the marked up
text, as far as is possible with the content model. For example, there MUST be a space between the
word “in” and the following element:7

<bibliomixed role="contribution" xml:id="b-0005922"><bibliomset relation="part"><author><personname

role="last-first"><surname>Barnathan</surname><firstname>J.</firstname></personname></author>
(<pubdate>1964</pubdate>), &#x2018;<title>The business of research</title>&#x2019;,</bibliomset>
in <bibliomset relation="book"><editor><personname role="first-last"><firstname>Yale</
firstname><surname>Roe</surname></personname></editor> (ed.), <title><emphasis role="italic">Television
Station Management</emphasis></title>: <subtitle>The Business of Broadcasting</subtitle>,
<address><city>New York</city>, <state>NY</state></address>: <publishername>Hastings House</
publishername>, <pagenums>171–80</pagenums>.</bibliomset></bibliomixed>

And there MUST be space between successive contributors,8 between an author/editor and a
following title9 or a following opening bracket.10 Similarly, beware of missing spaces before, or
brackets immediately following an address,11 and a space before a title12 or publishername.13
7
Tested in Schematron: space-before-bibliomset-required
8
Tested in Schematron: bibliomixed-successive-contributors
9
Tested in Schematron: author-title-space
10
Tested in Schematron: name-bracket
11
Tested in Schematron: no-space-before-address, bracket-following-address, bibliomixed-address-space

111
 Bibliographies and components

The only elements which can’t take PCDATA content (and hence have punctuation and spacing
controlled by the downstream processing) are:

• personname (see Section 16.4.4, “Personal names”)

• lineage (see Chapter 17, Names)

The components of the bibliographic reference MUST be marked up using the correct semantic
elements.

Note that @xreflabel is NOT REQUIRED.14

Numerous examples are included below, and draw on the usage for @relation specified on the
DocBook wiki and ISO 690.15

Implementation note: Bibliographic markup is required primarily to support the creation

of good OpenURL queries and citation exports using RIS format. A full specification for the
generation of these queries is required.

16.4.1. Language
If a bibliographic entry is not in English, the language MUST be marked up using the @xml:lang
attribute.

<bibliomixed xml:id="bibl18" role="monograph" xml:lang="fr"><author><personname role="last-

first"><surname>Thétard</surname> <firstname role="initials">H.</firstname></personname></author>,
<pubdate>1978</pubdate> [<date>1947</date>]. <title><emphasis role="italic">La merveilleuse histoire du
cirque</emphasis></title>. <address><city>Paris</city></address>: <publishername>Prisma</publishername>.</
bibliomixed>

16.4.2. @xml:id
All bibliomixed items MUST have an id.

16.4.3. @role
All bibliomixed MUST have a @role. This indicates the type of bibliographic item it is, and can
take one of the following values:

Value Usage
monograph All books, where the citation is to the complete
book
serial Journals and magazines, where the reference is to
the title only (eg for references to a complete issue
or volume, rather than a specific item therein)
contribution A chapter or other contribution to a monograph
article An article of other contribution in a serial
message An email message
website Content on a website

12
Tested in Schematron: no-space-before-title
13
Tested in Schematron: bibliomixed-publishername-space
14
Tested in Schematron: xreflabel-not-required
15
Jana Dvoráková. ‘Bibliography according to ISO 690 and ISO 690-2 standards.’ 8 March 2012. DocBook wiki. http://
wiki.docbook.org/ISO690Bibliography?action=AttachFile&do=view&target=doc.html#d4e309 (includes
numerous examples)

112
 Bibliographies and components

Value Usage
unpublished Material that is otherwise unpublished (eg from
an archive, or a thesis)
case A legal case (eg in the form Smith v. Jones, 1994)
legislation A statute, regulation, directive, treaty or similar
legal instrument
other Any other type of cited material. See Section 16.15,
“Other items”

16.4.4. Personal names

In the DocBook schema, punctuation is not permitted within a personname, which means that this
is a rare occasion where punctuation will need to be controlled by the output stylesheet. To ensure
that names are correctly styled, the personname element MUST include a @role attribute indicating
whether it is a reference style with the first name or surname first.

If the style is first name first, then this would be adopted:16

<author><personname role="first-last"><firstname>Tony</firstname> <surname>Mitchell</surname></

personname></author>

However, if the surname is first, this is REQUIRED:17

<author><personname role="last-first"><surname>Mitchell</surname> <firstname>Tony</firstname></

personname></author>

which will result in the output stylesheet adding a comma+space after the surname.

Therefore, it is very important that the order of the name components in personname exactly
follows that in the original print. It is an ERROR for name components to be the direct children of
bibliomixed or bibliomset; they MUST occur within a personname.18

Note that, except in very unusual circumstances, any bibliographic list (bibliography, bibliodiv
or bibliolist) SHOULD have the same personname @role style for the first-named person in all
items.19 (See example and XPaths for testing this in Section 32.6.1, “Inconsistent biblio style”)

See also Chapter 17, Names.

16.5. Dates in bibliographies

A date in a bibliographic reference MAY occur within one of three elements:20

Element Usage Examples

pubdate The date (usually year) of Section 16.7.1, “Single author
publication of the cited item, ie book”; Section 16.7.5, “Multiple
pubdate is WRONG within an editions”; Section 16.7.13,
unpublished work “Reprint”; Section 16.7.16, “Other
editions”; Section 16.8.2, “Standard
journal article”; Section 16.8.3.3,
“Newspaper item”; Section 16.11.1,
“Article on web with access date”

16
Tested in Schematron: first-last-1, first-last-2
17
Tested in Schematron: last-first-1
18
Tested in Schematron: bibliomixed-name
19
Tested in Schematron: mixed-personname-style
20
Tested in Schematron: untagged-month

113
 Bibliographies and components

Element Usage Examples

date Other dates within a Section 16.7.5, “Multiple editions”;
bibliographic item, including Section 16.7.13, “Reprint”;
original publication date (if, for Section 16.11.1, “Article on web
example, the cited version is with access date”
more recent), or (for an online
source) the date it was accessed
confdates The dates of a conference, which Conference paper
will most likely only occur
within an unpublished item

16.6. Untagged bibliographic content

It is highly desirable that all significant content in a bibliographic reference is marked up in some
way.21 The test mentioned in the preceding note reports high proportions of untagged content, and
the warning also includes the untagged content strings:

Description: Possible untagged content in biblio item. percent = 31.606217616580310881% [untagged content =
(). (Publications of the American Dialect Society, 84). : .] untaggedLength = 61; total = 193

If untagged content is just punctuation and strings like “ed.” etc, these can be ignored, but it is very
desirable that the other content has some markup.

If these warnings occur, it can also reveal instances of biblio items that are generally incorrectly
marked up, anyway.

Typical content and elements for this untagged content is given in the table below:

Example Use tag

bibliomisc[@role="series"]
<bibliomixed role="monograph"
xml:id="b-0001526"><author><personname role="last-
first"><surname>Gordon</surname><firstname
role="initials">M.J.</firstname></personname></
author> (<pubdate>2001</pubdate>). <title
xml:id="b-0001527"><emphasis role="italic">Small-
Town Values and Big-City Vowels: A Study
of the Northern Cities Shift in Michigan</
emphasis></title> (Publications of the
American Dialect Society, 84). <address
xml:id="b-0001528"><city>Durham</city>, <state>NC</
state></address>: <publishername>Duke University
Press</publishername>.</bibliomixed>

bibliomisc[@role="description"]
<bibliomixed role="article"
xml:id="b-0001592"><bibliomset
relation="article"><author><personname role="last-
first"><surname>Labov</surname><firstname
role="initials">W.</firstname></personname></
author> (<pubdate>1963</pubdate>). &#x201C;<title
xml:id="b-0001593">The social motivation of
a sound change</title>.&#x201D;</bibliomset>
<bibliomset relation="journal"><title
xml:id="b-0001594"><emphasis role="italic">Word</
emphasis></title>, <volumenum>19</
volumenum>, <pagenums>273&#x2013;309</
pagenums>. Reprinted in W. Labov (<link
linkend="ba-9781472541673-0001607">1972b</link>).</
bibliomset></bibliomixed>

bibliomisc[@role="description"]
<bibliomixed role="monograph"
xml:id="b-0001788"><author><personname role="last-

21
Tested in Schematron: untagged-biblio-content

114
 Bibliographies and components

Example Use tag

first"><surname>Saussure</surname><firstname
role="initials">F.</firstname><othername
role="middle">de</othername></personname></
author>. (<pubdate>1959</pubdate>). <title
xml:id="b-0001789"><emphasis role="italic">Course
in General Linguistics</emphasis></title>
(<othercredit class="translator"><personname
role="first-last"><firstname role="initials">W.</
firstname><surname>Baskin</surname></
personname></othercredit>, Trans.). <address
xml:id="b-0001790"><city>New York</city></address>:
<publishername>McGraw-Hill</publishername>.
(Original work published in <date>1916</date>).</
bibliomixed>

Orgname
<bibliomixed role="article"
xml:id="ba-9781472555564-0000649"><bibliomset
relation="article"
xml:id="ba-9781472555564-0000650"><author><personname
role="last-first"><surname>Ashizu</
surname><firstname>Kaori</firstname></personname></
author> (<pubdate>1995</pubdate>), &#x2018;<title
xml:id="ba-9781472555564-0000651">Kurosawa&#x2019;s
<emphasis role="italic">Hamlet</
emphasis>?</title>&#x2019;</bibliomset>.
<bibliomset relation="journal"><title
xml:id="ba-9781472555564-0000652"><emphasis
role="italic">Shakespeare Studies</emphasis></
title>, Shakespeare Society of Japan,
<volumenum>33</volumenum>, <pagenums>71&#x2013;99</
pagenums>.</bibliomset></bibliomixed>

othercredit-class=translator] (for the

<bibliomixed role="monograph"
xml:id="ba-9781472548207-0000777"><author><personnamename, and leave “trans.” untagged)
role="last-first"><surname>Badiou</
surname><firstname>Alain</firstname></personname></
author> (<pubdate>2013</pubdate>) <title
xml:id="ba-9781472548207-0000778"><emphasis
role="italic">Theory of the Subject</emphasis></
title>, trans. Bruno Bosteels, <address
xml:id="ba-9781472548207-0000779"><city>London</
city></address>: <publishername>Continuum</
publishername>.</bibliomixed>

16.7. Books
16.7.1. Single author book
Books (as opposed to chapters in books) have @role=monograph. They MUST have a title and
an author/editor.22 Note that, if the title is rendered in italic, an emphasis MUST be present and
typically that includes all of the title content.23

Note also in this example that the pubdate belongs around the date of the edition cited, not the
original date of publication:

<bibliomixed xml:id="bibl1" role="monograph"><author><personname role="first-last"><firstname>Tony</

firstname> <surname>Mitchell</surname></personname></author>, <title><emphasis role="italic">Dario Fo:
People's Court Jester</emphasis></title>, <address><city>London</city></address>, Methuen, <date>1984</
date>; revised and expanded version, <publishername>Methuen</publishername>, <pubdate>1986</pubdate>.</
bibliomixed>

Formally published items (including books, journals, newspapers etc) MUST have a pubdate.24
22
Tested in Schematron: monograph-title, monograph-authors, and more generally in bibliomixed-author
23
Tested in Schematron: title-emphasis
24
Tested in Schematron: bibliomixed-pubdate, bibliomixed-multiple-pubdate

115
 Bibliographies and components

If a bibliomixed item does not have a publishername or address and occurs in a footnote or
other inline location, it is possible that it is not a full biblio reference and should be a link to the full
reference elsewhere in the document.25 See also Section 16.3.2, “Irregular cross references”.

A ‘monograph’ will never need a child bibliomset;26 if a bibliomset is REQUIRED and the item
is a book, it is most likely to be a Section 16.7.4, “Chapter in edited book”.

In any bibliographic reference, a title should never contain an author, publishername, pubdate
etc.27

16.7.2. Single author book with surname first

Note also how this specific reference is from a book with a different editorial style compared with the
first (date and publisher being in different places, and with different surrounding punctuation):

<bibliomixed role="monograph" xml:id="b-0003692"><author><personname role="last-first"><surname>Gouldner</

surname><firstname role="initials">A.</firstname></personname></author> (<pubdate>1970</pubdate>) <title
xml:id="b-0003693"><emphasis role="italic">The Coming Crisis in Western Sociology</emphasis></title>.
<address xml:id="b-0003694"><city>New York</city></address>: <publishername>Basic Books</publishername>.</
bibliomixed>

16.7.3. Multiple editors

Note that no authorgroup container is used here for multiple editors (or authors),28 since
that doesn’t allow PCDATA between components. Multiple, successive authors and editors MUST
have punctuation and other PCDATA between them exactly as in the print edition.29 Note also that
“(eds.)” is included in the text, exactly as it appears in the print edition:

<bibliomixed xml:id="bibl2" role="monograph"><editor><personname role="first-last"><firstname>Joseph</

firstname> <surname>Farrell</surname></personname></editor> and <editor><personname role="first-
last"><firstname>Antonio</firstname> <surname>Scuderi</surname></personname></editor> (eds.),
<title><emphasis role="italic">Dario Fo: Stage, Text and Tradition</emphasis></title>,
<address><city>Carbondale</city></address>, <publishername>Southern Illinois University Press</
publishername>, <pubdate>1999</pubdate>, forthcoming.</bibliomixed>

A @role=monograph is for the book as a whole (as in the example above). If a component of the
book is cited use the form in the following example.30

16.7.4. Chapter in edited book

Note @role=contribution, and the two bibliomset[@relation] values,31 that the single
quotes around the “part” title are exactly as in the print edition, and that the “part” contains an
author (not an editor)32 . A bibliomset ‘book’ or ‘part’ MUST occur within a ‘contribution’:33

<bibliomixed xml:id="bibl3" role="contribution"><bibliomset relation="part"><author><personname

role="first-last"><firstname>Lino</firstname> <surname>Pertile</surname></personname></author>,
‘<title>Dario Fo</title>’.</bibliomset> In <bibliomset relation="book"><editor><personname
role="first-last"><firstname>Michael</firstname> <surname>Caesar</surname></personname></editor> and
<editor><personname role="first-last"><firstname>Peter</firstname> <surname>Hainsworth</surname></
personname></editor> (eds.), <title><emphasis role="italic">Writers and Society in Contemporary

25
Tested in Schematron: possible-short-form-ref
26
Tested in Schematron: mono-book
27
Tested in Schematron: bad-title-content
28
Tested in Schematron: bibliomixed-authorgroup
29
Tested in Schematron: bibliomixed-successive-authors, bibliomixed-successive-editors
30
Tested in Schematron: mono-not-article, mono-not-journal
31
Tested in Schematron: contribution-not-article, contribution-not-journal, contribution-
partcontribution-book
32
Tested in Schematron: part-author, part-editor
33
Tested in Schematron: book-contribution, part-contribution

116
 Bibliographies and components

Italy</emphasis></title>, <address><city>New York</city></address>, <publishername>St Martin's Press</

publishername>, <pubdate>1984</pubdate></bibliomset>, pp. <pagenums>167–90</pagenums></bibliomixed>

Generally, a bibliomset MUST contain a title,34 and MUST NOT contain another bibliomset
itself.35 Where bibliomsets occur they tend to be in pairs.36 Note also that, if the book title is
rendered in italic, an emphasis MUST be present and typically that includes all of the title
content.37

The use of the word “in” is a good indicator that the first part of the item is a component of a larger
work and suggests that a bibliomset is REQUIRED.38 Furthermore, when any bibliomixed
contains bibliomset, all the other elements should be within a bibliomset; it is almost inconceivable
that any other bibliographic components would be siblings of a bibliomset (see also examples in
Section 32.6.3, “Sibling elements of bibliomset”).39

Note that any quotes surrounding a chapter/part title MUST be outside the title:40

“<title>Understanding the Use of Celebrity Endorsers for Hospitality Firms</title>”

ie, the following is WRONG:

<title>“Understanding the Use of Celebrity Endorsers for Hospitality Firms”</title>

But note that sometimes it is legitimate to have quotes within a title or subtitle:

&#x2018;<title>Signed, sealed and delivered</title>: <subtitle>“big tobacco” in Hollywood, 1927–51</

subtitle>&#x2019;

16.7.5. Multiple editions

Here there is more than one date in the reference; the most recent work is the actual one cited so that
must be the pubdate:

<bibliomixed xml:id="bibl15" role="monograph"><author><personname role="first-last"><firstname>John</

firstname> <surname>Willett</surname></personname></author>, <title><emphasis role="italic">Brecht
in Context</emphasis></title> (<address><city>London</city></address>: <date>1984</date>, revised
<pubdate>1998</pubdate>)</bibliomixed>

Note that this is a revised edition, which is therefore substantively different from a reprint, so the
revised date is the pubdate. Compare the situation with a Section 16.7.13, “Reprint” below.

16.7.6. Item in a numbered volume, with annotation

The editorial annotation at the end only needs formatting markup.

<bibliomixed xml:id="bibl4" role="contribution"><bibliomset relation="part"><author><personname

role="first-last"><firstname>Vittorio</firstname> <surname>Felaco</surname></personname></
author>, ‘<title>New Teeth for an Old Shark</title>’.</bibliomset> In <bibliomset
relation="book"><editor><personname role="first-last"><firstname>John</firstname> <surname>Fuegi</
surname></personname></editor> et al. (eds.), <title><emphasis role="italic">Beyond Brecht: Brecht
Yearbook</emphasis></title>, vol. <volumenum>11</volumenum>, <date>1982</date>, <address><city>Detroit</
city></address>, <publishername>Wayne State University Press</publishername>, <pubdate>1983</pubdate></
bibliomset>, pp. <pagenums>57–71</pagenums> (Fo and Rame as inheritors of Brechtian theatre concepts;
<emphasis role="italic">The Opera of Guffaws</emphasis>.)</bibliomixed>

34
Tested in Schematron: bibliomset-title
35
Tested in Schematron: nested-bibliomset
36
Tested in Schematron: single-bibliomset
37
Tested in Schematron: title-emphasis
38
Tested in Schematron: in-sans-bibliomset
39
Tested in Schematron: element-not-bibliomset
40
Tested in Schematron: bib-title-start-quote, bib-title-end-quote

117
 Bibliographies and components

Note that volumenum contains just the volume number, not the text “vol.” etc.41

16.7.7. Anonymous items and “et al”

For bibliographic items with anonymous authors, ie those that are explicitly marked as “Anon” in
the text, it is an ERROR to use the author element and its children; bibliomisc[@role=anon]
MUST be used:42

<bibliomixed xml:id="bibl6" role="contribution"><bibliomset relation="part"><bibliomisc role="anon">Anon.</

bibliomisc>, ‘<title>Dario Fo</title>’</bibliomset> in <bibliomset relation="book"><editor><personname
role="first-last"><firstname>Michael</firstname> <surname>Anderson</surname></personname></editor>
<emphasis role="italic">et al</emphasis> (eds.), <title><emphasis role="italic">A Handbook of Contemporary
Drama</emphasis></title>, <address><city>London</city></address>, <publishername>Pitman</publishername>,
<pubdate>1974</pubdate></bibliomset>, pp. <pagenums>152–3</pagenums></bibliomixed>

Note also that “et al.” MUST NOT be captured within one of the name elements.43

16.7.8. Publisher address

Here we have multiple addresses (cities), one of which has a US state abbreviation:

<bibliomixed xml:id="bibl17" role="monograph"><editor><personname role="first-last"><firstname>Steve</

firstname> <surname>Giles</surname></personname></editor> and <editor><personname role="first-
last"><firstname>Rodney</firstname> <surname>Livingstone</surname></personname></editor>
(eds), <title><emphasis role="italic">Bertolt Brecht: Centenary Essays</emphasis></title>,
(<address><city>Amsterdam</city></address> and <address><city>Atlanta</city> <state>GA</state></address>,
<pubdate>1998</pubdate>)</bibliomixed>

16.7.9. Work within a book

Here is a book that is contained within another book, ie a modern commentary on a Renaissance text.
Note that the translator name does not need to be marked up (though it is nice if it is), only the author
and editor:

<bibliomixed xml:id="bibl13" role="contribution"><bibliomset relation="part"><author><personname

role="last-first"><surname>Gil</surname> <firstname>Alexander</firstname></personname></author>,
<title><emphasis role="italic">Logonomia Anglica</emphasis></title> (<date>1619</date>)</
bibliomset>, in <bibliomset relation="book"><editor><personname role="first-last"><firstname>Bror</
firstname> <surname>Danielsson</surname></personname></editor> and <editor><personname role="first-
last"><firstname>Arvid</firstname> <surname>Gabrielson</surname></personname></editor> (eds),
<title><emphasis role="italic">Alexander Gil’s Logonomia Anglica (1619)</emphasis></title> (vol.
2), trans. Robin Alston (<address><city>Stockholm</city></address>, <pubdate>1972</pubdate>)</
bibliomset></bibliomixed>

However, if the translator is not marked up with name components, it MUST just be text within the
bibliomixed (or bibliomset).44 It is an ERROR to include the translator in other content:

<bibliomixed role="monograph" xml:id="ba-9781472548375-0000949"><author><personname role="first-

last"><firstname role="initials">G. W. F.</firstname> <surname>Hegel</surname></personname></author>,
<title xml:id="ba-9781472548375-0000950"><emphasis role="italic">Philosophy of Mind</emphasis>,
trans. W. Wallace and A. V. Miller</title> (<address xml:id="ba-9781472548375-0000951"><city>Oxford</
city></address>: <publishername>Oxford University Press</publishername>, <pubdate>2007</pubdate>), p.
<pagenums>65</pagenums>)</bibliomixed>

16.7.10. Implied authors (books)

The author of an item may be implied in the text context for two reasons: (a) to save space in the print
edition, using long dashes to suggest that an item has the same author as the previous one. In this
41
Tested in Schematron: volume-issue-numeric
42
Tested in Schematron: anon-present
43
Tested in Schematron: et-al-present
44
Tested in Schematron: trans-in-title

118
 Bibliographies and components

case, the author details MUST be added in with @condition=hidden, and the long dashes included
within phrase[@condition=display]:

<bibliomixed xml:id="bibl10" role="contribution"><bibliomset relation="part"><author

condition="hidden"><personname role="last-first"><surname>Adamson</surname> <firstname>Sylvia</
firstname></personname></author><phrase condition="display">————</phrase>, ‘<title>The Literary
Language</title>’</bibliomset>, in <bibliomset relation="book"><editor><personname role="first-
last"><firstname>Roger</firstname> <surname>Lass</surname></personname></editor> (ed.), <title><emphasis
role="italic">The Cambridge History of the English Language: Volume 3, 1476–1776</emphasis></title>
(<address><city>Cambridge</city></address>, <pubdate>2000</pubdate>)</bibliomset>, pp. <pagenums>539–653</
pagenums></bibliomixed>

or, (b) where there is a list of works by a named individual (eg the subject of the book etc) and the
editorial style in the book is to omit the repetition of the author’s name. For example, in this list of
“Works by Brecht”:

<bibliomixed xml:id="bibl8" role="monograph"><author condition="hidden"><personname role="first-

last"><firstname>Berthold</firstname> <surname>Brecht</surname></personname></author><title><emphasis
role="italic">Poems and Songs from the Plays</emphasis></title>, edited and mainly translated by
<editor><personname role="first-last"><firstname>John</firstname> <surname>Willett</surname></
personname></editor> (<address><city>London</city></address>: <publishername>Methuen</publishername>,
<pubdate>1990</pubdate>)</bibliomixed>

See also Section 14.6, “Conditional processing with @condition”, and the example in Section 32.15.3,
“Implied authors in bibliographies”.

Implementation note: This is not supported in DocBook XSL

16.7.11. Ibid, loc cit, and op. cit.

Occasionally, an “Ibid”, “loc. cit.” or “op. cit.” may be used within a formal bibliography, where one
bibliographic item refers to another.45

For example, this item:

Joel Schechter, ‘Beyond Brecht: New Authors, New Spectators’. In Fuegi et al., Beyond Brecht,
op.cit., pp. 43–53

refers to this one:

Vittorio Felaco, ‘New Teeth for an Old Shark’. In John Fuegi et al. (eds.), Beyond Brecht: Brecht
Yearbook, vol. 11, 1982, Detroit, Wayne State University Press, 1983, pp. 57–71

The latter can be marked up thus, as a regular contribution in a book:

<bibliomixed xml:id="bibl4" role="contribution"><bibliomset relation="part"><author><personname

role="first-last"><firstname>Vittorio</firstname> <surname>Felaco</surname></personname></
author>, ‘<title>New Teeth for an Old Shark</title>’.</bibliomset> In <bibliomset
relation="book"><editor><personname role="first-last"><firstname>John</firstname> <surname>Fuegi</
surname></personname></editor> et al. (eds.), <title><emphasis role="italic">Beyond Brecht: Brecht
Yearbook</emphasis></title>, vol. <volumenum>11</volumenum>, <date>1982</date>, <address><city>Detroit</
city></address>, <publishername>Wayne State University Press</publishername>, <pubdate>1983</pubdate></
bibliomset>, pp. <pagenums>57–71</pagenums></bibliomixed>

Then, in the former we need to include text for display as well as the more detailed bibliographic data
that needs to be hidden for use in the creation of an OpenURL query by a downstream processor. As
elsewhere, this is achieved using @condition:
45
Tested in Schematron: op-cit-present, ibid-present, loc-cit-present

119
 Bibliographies and components

<bibliomixed xml:id="bibl5" role="contribution"><bibliomset relation="part"><author><personname

role="first-last"><firstname>Joel</firstname> <surname>Schechter</surname></personname></
author>, ‘<title>Beyond Brecht: New Authors, New Spectators</title>’.</bibliomset> In <phrase
condition="display">Fuegi <emphasis role="italic">et al.</emphasis>, <emphasis role="italic">Beyond
Brecht</emphasis>, op.cit.</phrase><bibliomset condition="hidden" relation="book"><editor><personname
role="first-last"><firstname>John</firstname> <surname>Fuegi</surname></personname></editor> et
al. (eds.), <title><emphasis role="italic">Beyond Brecht: Brecht Yearbook</emphasis></title>,
vol. <volumenum>11</volumenum>, <date>1982</date>, <address><city>Detroit</city></address>,
<publishername>Wayne State University Press</publishername>, <pubdate>1983</pubdate></bibliomset>, pp.
<pagenums>43–53</pagenums></bibliomixed>

Note that the pagination in this example is outside the hidden bibliomset, since it is displayed to
all users.

See also Section 14.6, “Conditional processing with @condition” and Section 18.1.4, “Ibids, loc cits and op cits
in footnotes”

16.7.12. Classical authors/single names + series

Series names aren’t often recorded in bibliographies, though they may be for some famous ones, as
in the example below. Note too that where there is a classical author with a single name (“Lucian”),
that MUST be placed in surname in a personname[@role=first-last] (ie so that no comma is
autogenerated after the surname):

<bibliomixed xml:id="bibl14" role="monograph"><author><personname role="first-last"><surname>Lucian</

surname></personname></author>, <title><emphasis role="italic">Heracles [etc.]</emphasis></title>,
trans. <othercredit class="translator"><personname role="first-last"><firstname>A.M.</firstname>
<surname>Harmon</surname></personname></othercredit>, <bibliomisc role="series">Loeb Classical Library</
bibliomisc> (<address><city>New Haven</city></address>, <pubdate>1913</pubdate>)</bibliomixed>

16.7.13. Reprint
For works that are marked as a reprint, rather than a different edition, the original publication date is
best marked with pubdate and the reprint date can be left untagged (or tagged with date):

<bibliomixed role="contribution" xml:id="b-9002780"><bibliomset relation="part" xml:id="b-9302780">'<title

xml:id="b-9402780">The Mask: Coming out of Our Shell</title>',</bibliomset> <bibliomset relation="book"
xml:id="b-9502780"><title xml:id="b-9602780"><emphasis role="italic">The Shifting Point: Forty years of
theatrical exploration 1946–1987</emphasis></title> (<address xml:id="b-9702780"><city>London</city></
address>: <pubdate>1987</pubdate>; repr. 1995), <pagenums>231</pagenums></bibliomset></bibliomixed>

Compare this with the example of a revised edition above (Section 16.7.5, “Multiple editions”).

16.7.14. Online version of a text

Though this is a source on the internet with a URL, it still has all the components of an item in a
monograph-like text, so MUST be encoded as a “contribution”:

<bibliomixed xml:id="bibl16" role="contribution"><bibliomset relation="part"><author><personname

role="last-first"><surname>Mendyk</surname> <firstname role="initials">S.</firstname></
personname></author>, ‘<title>Carew, Richard (1555–1620)</title>’</bibliomset>, <bibliomset
relation="book"><title><emphasis role="italic">Oxford Dictionary of National Biography</emphasis></title>
(<address><city>Oxford</city></address>, <pubdate>2004</pubdate>)</bibliomset>: <link xlink:href="http://
www.oxforddnb.com/view/article/4635"><uri>www.oxforddnb.com/view/article/4635</uri></link></bibliomixed>

Likewise, a bibliomixed[@role=monograph] MAY also have a web manifestation, eg via an

online publishing platform. However, it is prudent to check all instances of biblio items with web
addresses in case they have the wrong @role, and should in fact be @role=website.46
46
Tested in Schematron: mono-url, contribution-url

120
 Bibliographies and components

16.7.15. Multi-volume, abbreviated form and translated

versions
The first item here is a 20 volume work, which gets treated as a monograph, and includes an
abbreviation by which it is referenced later in the bibliography:

<bibliomixed role="monograph" xml:id="adgs"><author><personname role="last-first"><surname>Adorno</surname>

<firstname>Theodor W.</firstname></personname></author>, <title><emphasis role="italic">Gesammelte
Schriften</emphasis></title> (hereafter <emphasis role="italic">GS</emphasis>), 20
vols (<address><city>Frankfurt am Main Suhrkamp</city></address>, <pubdate>1972</pubdate> ff.).</
bibliomixed>

Then, subsequent items from the collected works are cited with an author name, so an implied
name MUST be added, and the individual volume bibliographic details are given for both
the original language edition, and an English translation, so this is a rare occasion when other
bibliomset[@relation] values are REQUIRED:47

<bibliomixed role="monograph" xml:id="adgs11"><author condition="hidden"><personname role="last-

first"><surname>Adorno</surname> <firstname>Theodor W.</firstname></personname></author><phrase
condition="display">—</phrase>, <bibliomset relation="originalLang"><title><emphasis role="italic">Noten
zur Literatur</emphasis></title> (<emphasis role="italic">GS</emphasis> 11)</bibliomset>. Eng.-lang.
edn: <bibliomset relation="translation"><title><emphasis role="italic">Notes to Literature</emphasis></
title>, 2 vols, Shierry Weber Nicholsen (New York: Columbia University Press, <pubdate>1991-2</pubdate>).</
bibliomset></bibliomixed>

It is rare for a biblio item to have more than one publishername, though if this example had
included the publisher name of the original language edition it would have been permissible.
Ordinarily, though, multiple publishername is an ERROR.48

See also Section 14.6, “Conditional processing with @condition”

16.7.16. Other editions

As in the last example with a translation, some bibliographic references may contain multiple
editions. The primary edition is tagged as elsewhere, and the other edition wrapped in a
bibliomset:

<bibliomixed xml:id="ba-9781408163023-5003097" role="monograph"><author><personname role="first-

last"><firstname>Cole</firstname> <surname>Lesley</surname></personname></author>, <title><emphasis
role="italic">The Life of Noël Coward</emphasis></title> (<address><city>London</city></address>:
<publishername>Jonathan Cape</publishername>, <pubdate>1976</pubdate>). <bibliomset
relation="otherEdition">Published in the USA as <title><emphasis role="italic">Remembered Laughter</
emphasis></title> (<address><city>New York</city></address>: <publishername>Alfred A. Knopf</
publishername>, <pubdate>1976</pubdate>)</bibliomset></bibliomixed>

16.8. Journals
16.8.1. Journal issue
If a journal issue is cited, there will not be an author,49 so the @role MUST be set to serial:

<bibliomixed xml:id="b2" role="serial"><title><emphasis role="italic">International Journal of Cultural

Studies</emphasis></title> <volumenum>9</volumenum> (<issuenum>3</issuenum>), <pubdate>2006</pubdate></
bibliomixed>

47
This and the follow example are reported in Schematron: other-editions-etc
48
Tested in Schematron: bibliomixed-multiple-publishername
49
Tested in Schematron: serial-author

121
 Bibliographies and components

Note that no child bibliomset is required in this instance.50 In addition, if the jounal title is
rendered in italic, an emphasis MUST be present and typically that includes all of the title
content.51

16.8.2. Standard journal article

Journal articles MUST have @role=article, and contain bibliomsets for the article and
journal.52 A bibliomset ‘article’ or ‘journal’ MUST occur within a ‘contribution’.53 This example
includes multiple authors, plus volume and issue numbers. Note that is is extremely unusual for
journal articles ever to have an editor and such an occurrence is most likely an ERROR54:

<bibliomixed xml:id="bibl22" role="article"><bibliomset relation="article"><author><personname

role="last-first"><surname>McGreavy</surname> <firstname>P. D.</firstname></personname></author>
and <author><personname role="first-last"><firstname>A. N.</firstname> <surname>McLean</surname></
personname></author>, <pubdate>2007</pubdate>. “<title>Roles of learning theory and ethology in
equitation</title>.”</bibliomset> <bibliomset relation="journal"><title><emphasis role="italic">Journal of
Veterinary Behavior</emphasis></title>, <volumenum>2</volumenum> (<issuenum>4</issuenum>), <pagenums>108–
18</pagenums>.</bibliomset></bibliomixed>

Note that the volumenum and issuenum MUST surround the number only, and not include text55
and that, if the journal title is rendered in italic, an emphasis MUST be present and typically that
includes all of the title content.56 In addition, any quotes surrounding an article title MUST be
outside the title (see example in Section 16.7.4, “Chapter in edited book” above).57

It is also very unlikely that a journal article item will contain a publishername; if such occurs, it is
likely an ERROR.58

Here, the pubdate includes a month:

<bibliomixed xml:id="bibl19" role="article"><bibliomset relation="article"><author><personname role="first-

last"><firstname>Martin</firstname> <othername role="initials">W.</othername> <surname>Walsh</surname></
personname></author>, ‘<title>The Proletarian Carnival of Fo's <emphasis role="italic">Non si paga!</
emphasis></title>’.</bibliomset> <bibliomset relation="journal"><title><emphasis role="italic">Modern
Drama</emphasis></title>, vol. <volumenum>28</volumenum>, no. <issuenum>2</issuenum>, <pubdate>June 1985</
pubdate>, pp. <pagenums>211–22</pagenums>.</bibliomset></bibliomixed>

16.8.3. Journal article with URL

<bibliomixed xml:id="bibl24" role="article"><bibliomset relation="article"><author><personname role="last-
first"><surname>Austen</surname> <firstname>Gillian</firstname></personname></author>, ‘<title>Self-
portraits and Self-presentation in the work of George Gascoigne</title>’</bibliomset>, <bibliomset
relation="journal"><title><emphasis role="italic">Early Modern Literary Studies</emphasis></title>, vol.
<volumenum>14</volumenum>, no. <issuenum>1</issuenum> (Special Issue 18: <pubdate>May, 2008</pubdate>),
2.1–34, URL: <link xlink:href="http://purl.oclc.org/emls/14-1/article1.htm"><uri>http://purl.oclc.org/
emls/14-1/article1.htm</uri></link></bibliomset></bibliomixed>

16.8.3.1. Journal (or book) item with DOI

If a DOI is present, it may not be presented as a URL. Even so, all DOIs in bibliographic references
MUST be encoded as external links, which means that the DOI resolver URL may need to be added in
the @xlink:href (but not in the text):59
50
Tested in Schematron: bibliomset-journal
51
Tested in Schematron: title-emphasis
52
Tested in Schematron: article-not-part, article-not-book, article-journal, article-article
53
Tested in Schematron: article-article-2, journal-article
54
Tested in Schematron: article-editor
55
Tested in Schematron: volume-issue-numeric
56
Tested in Schematron: title-emphasis
57
Tested in Schematron: bib-title-start-quote, bib-title-end-quote
58
Tested in Schematron: pubname-in-article
59
Tested in Schematron: doi-href

122
 Bibliographies and components

<bibliomixed role="article" xml:id="b-0000292"><bibliomset relation="article"

xml:id="b-0000293"><author><personname role="last-first"><surname>Cutas</surname><firstname
role="initials">D.</firstname></personname></author>, (<pubdate>2011</pubdate>) ‘<title>On Triparenting:
Is having three committed parents better than having only two?</title>’</bibliomset>, <bibliomset
relation="journal"><title><emphasis role="italic">Journal of Medical Ethics</emphasis></title> doi: <link
xlink:href="http://dx.doi.org/10.1136/jme.2011.043745">10.1136/jme.2011.043745</link></bibliomset></
bibliomixed>

See also Section 15.6, “DOI links”

16.8.3.2. Magazine
Treated exactly as an academic journal, though here there is a full date:

<bibliomixed xml:id="bibl20" role="article"><bibliomset relation="article"><author><personname role="first-

last"><firstname>Charles</firstname> <surname>Mann</surname></personname></author>, ‘<title>Fo No-
Show Doesn't Mean No Fo Show</title>’.</bibliomset> <bibliomset relation="journal"><title><emphasis
role="italic">Village Voice</emphasis></title>, <pubdate>17–23 December 1980</pubdate></bibliomset>.</
bibliomixed>

16.8.3.3. Newspaper item

Items in newspapers (and magazines) may not necessarily have an author:

<bibliomixed xml:id="f-4" role="article"><bibliomset relation="article">‘<title>The Uneventful Event</

title>’</bibliomset> <bibliomset relation="journal"><title><emphasis role="italic">Irish Times</emphasis></
title> <pubdate>February 18, 1956</pubdate>.</bibliomset></bibliomixed>

Text strings bounded by single quotes suggest an article of some sort.60

16.8.3.4. Implied author (journals)

Exactly as with books, the @condition MUST be used. This item was from a works list (“Works of
Dario Fo”):

<bibliomixed xml:id="bibl23" role="article"><bibliomset relation="article"><author

condition="hidden"><personname role="first-last"><firstname>Dario</firstname> <surname>Fo</surname></
personname></author> ‘<title>Dialogue with an Audience</title>’ (trans. Tony Mitchell)</bibliomset>,
<bibliomset relation="journal"><title><emphasis role="italic">Theatre Quarterly</emphasis></title>, vol.
<volumenum>9</volumenum>, no. <issuenum>35</issuenum>, <pubdate>Autumn 1979</pubdate>, pp. <pagenums>11–
6</pagenums></bibliomset></bibliomixed>

See also Section 14.6, “Conditional processing with @condition”

16.8.3.5. Book reviews

Sometimes a book review in a journal will include details of the book under review. In such cases, the
book’s details just need to go in a bibliomisc, and the book name and author DO NOT need to be
marked up:

<bibliomixed role="article" xml:id="ba-9781472541673-0001775"><bibliomset

relation="article"><author><personname role="last-first"><surname>Russell</surname><firstname
role="initials">R.L.</firstname></personname></author> (<pubdate>1979</pubdate>). &#x201C;<title
xml:id="ba-9781472541673-0001776">Speech acts, conversational sequencing, and rules</title>&#x201D;
<bibliomisc role="description">(Review of the book <emphasis role="italic">Therapeutic Discourse</
emphasis>, by W. Labov and D. Fanshel)</bibliomisc></bibliomset>. <bibliomset relation="journal"><title
xml:id="ba-9781472541673-0001778"><emphasis role="italic">Contemporary Sociology</emphasis></title>,
<volumenum>8</volumenum>, <pagenums>176&#x2013;9</pagenums></bibliomset>.</bibliomixed>

60
Tested in Schematron: bibliomixed-other-test

123
 Bibliographies and components

16.9. Unpublished
The number of “unpublished” and “other” bibliomixed items is usually relatively small, so if a
large proportion of them are so tagged it suggests that many of them may be mis-categorised.61 The
word “unpublished” in a bibliomixed can be a useful clue for some of them.62

<bibliomixed role="unpublished" xml:id="ba-9781849664622-0006563"><author><personname role="last-

first"><surname>Hurwitz</surname><firstname>D.</firstname></personname></author> (<date>1983</
date>), &#x2018;<title xml:id="ba-9781849664622-0006564">Broadcast “ratings”</title>: <subtitle
xml:id="ba-9781849664622-0006565">The rise and development of commercial audience research and measurement
in American broadcasting</subtitle>&#x2019;, <bibliomisc role="description">Unpublished doctoral
dissertation</bibliomisc>, <address xml:id="ba-9781849664622-0006566"><city>Urbana</city>, <state>IL</
state></address>: <orgname>University of Illinois</orgname></bibliomixed>

Note also the use of orgname rather than publishername,63 and date rather than pubdate.

16.9.1. Thesis
Note the use of date, rather than pubdate, and the presence of the text “PhD”:64

<bibliomixed xml:id="bibl25" role="unpublished"><author><personname role="first-last"><firstname>Suzanne</

firstname> <surname>Cowan</surname></personname></author>, ‘<title>The Militant Theatre of Dario Fo</
title>’, <bibliomisc role="description">PhD Thesis</bibliomisc>, <orgname>University of Minnesota</
orgname>, <date>1977</date>.</bibliomixed>

16.9.2. Personal communications

If a reference includes the text “personal communication”, it MUST also be marked as an
unpublished item:65

<bibliomixed role="unpublished" xml:id="b-0006789"><author><personname role="last-first"><surname>McNair</

surname><firstname>I.</firstname></personname></author> (<date>2000</date>), <title>Personal
communication</title>.</bibliomixed>

16.9.3. Interviews
Unpublished interviews may also appear in a bibliography.66 Note that these too have a date rather
than pubdate, and use bibliomisc[@role=description] for the general contextual details.

<bibliomixed role="unpublished" xml:id="b-ack001246"><author><personname role="last-first"><surname>Fayez</

surname><firstname>Baha El Din</firstname></personname></author>. <date>2009</date>. <title>Head
of Pharmaceutical Sector, National Institute for Research and Technology</title>. <bibliomisc
role="description">Interview</bibliomisc>, <date>3 February 2009</date>.</bibliomixed>

16.9.4. Conference papers, other meetings and reports

Note that the conference name does need to be marked up, ie use of DocBook’s confgroup is
REQUIRED in this context. Note that almost all bibliographic items that include a confgroup will be
‘unpublished’67 (though occasionally a biblio item for a published book may also note a conference
from which it was drawn).

<bibliomixed role="unpublished" xml:id="bi1"><author><personname role="last-first"><surname>Bairner</

surname> <firstname>A.</firstname></personname></author>, <author><personname role="last-

61
Tested in Schematron: proportion-unpublished-other
62
Tested in Schematron: possible-unpublished
63
Tested in Schematron: unpublished-publishername
64
Tested in Schematron: unpublished-pubdate, possible-unpublished-2
65
Tested in Schematron: possible-unpublished-3
66
Tested in Schematron: possible-unpublished-4
67
Tested in Schematron: confgroup-present

124
 Bibliographies and components

first"><surname>Curry</surname> <firstname>G.</firstname></personname></author> and <author><personname

role="last-first"><surname>Malcolm</surname> <firstname>D.</firstname></personname></author> (<date>2007</
date>), ‘<title>Ireland’s Other National Sport? Irishness and the Cricket World Cup 2007</title>’, paper
presented at <confgroup><conftitle>North American Society for the Sociology of Sport Annual Meeting</
conftitle></confgroup>, <address><city>Pittsburgh</city></address>, <confgroup><confdates>Oct-Nov. 2007</
confdates></confgroup>.</bibliomixed>

Note that there are two confgroup wrappers in there because confgroup does not allow text as a
direct child node.68

Here is a second example:

<bibliomixed role="unpublished" xml:id="b-0002159g"><author><personname role="first-last"><firstname>Li</

firstname><surname>Wuwei</surname></personname></author>'s Keynote speech ‘<title>Towards City of
Creativity</title>’ at <confgroup><conftitle>Shanghai Creative Industries International Forum</conftitle>
<confdates>2008</confdates></confgroup>, <address><city>Shanghai</city></address></bibliomixed>

Finally, here is confgroup used for minutes of a meeting, and note also that it uses biblioid for the
document reference number (which would also be used for documents from archives):

<bibliomixed role="unpublished" xml:id="b-ack000806"><author><orgname>WTO (World Trade Organization)</

orgname></author>. <date>2000b</date>. <title>World Trade Organization Council for Trade-Related Aspects
of Intellectual Property Rights</title>. <date>2000</date>. <confgroup><conftitle>Minutes of Meeting</
conftitle></confgroup>. <biblioid class="other" otherclass="refNo">IP/C/M/28</biblioid>, <date>21–22
September 2000</date>.</bibliomixed>

Implementation note: conftitle and related elements are not handled in the DocBook XSL

16.10. Email messages

Email messages may sometimes be cited in a bibliography. These MUST have @role=message, and
MUST NOT contain elements such as volumenum, publishername etc.69

Smith, J. Re: Biodiversity management. [email] Message to Brown, J. Sent 12 January 2013.

<bibliomixed role="message" xml:id="mg1"><author><personname role="last-first"><surname>Smith</surname>

<firstname role="initials">J.</firstname></personname></author>, <title>Re: Biodiversity Management</
title>. [email] <title>Message to Brown, J.</title>. Sent <date>12 January 2013</date>.</bibliomixed>

16.11. Web sites

The presence of a URL in a bibliographic reference does not mean that it is to be treated as a website;
many such items are books and journals that are available on the internet (see examples above in
Section 16.7.14, “Online version of a text” and Section 16.8.3, “Journal article with URL”). This section
details other materials that are to be found on the web, including blogs and other documents.

16.11.1. Article on web with access date

The date on which the author accessed a website MUST be marked with date as in the example
below.70 If the link url is fllowed by the access date in brackets, there MUST be a space between
them.71

Note that this can be distinguished from a book online (@role=monograph) since it just has an
article title (in single quotes in this case) and no other title.
68
Tested in Schematron: possible-conference, which identifies conference-like words in a title
69
Tested in Schematron: possible-message, biblio-message
70
Tested in Schematron: accessed-date, possible-access-date
71
Tested in Schematron: possible-missing-space3

125
 Bibliographies and components

<bibliomixed role="website" xml:id="b-0004008"><author><personname role="last-first"><surname>Whittaker</

surname> <firstname role="initials">B.</firstname></personname></author> (<pubdate>2002</pubdate>)
'<title>Islam and the British press after September 11</title>' <link xlink:href="http://www.al-bab.com/
media/articles/bw020620.htm"><uri>http://www.al-bab.com/media/articles/bw020620.htm</uri></link> (accessed
<date role="accessed">14 October 2008</date>).</bibliomixed>

16.11.2. Minimal web site reference

The least a website reference needs is a title and a link:72

<bibliomixed role="website" xml:id="ba-9781472544247-0002984"><title>AAQUA</title> (<pubdate>n.d.</

pubdate>), Available at <link xlink:href="http://www.aaqua.org"><uri>http://www.aaqua.org</uri></link>
[<date role="accessed">28 May 2011</date>].</bibliomixed>

Here is a slightly longer one, with the website name marked with publishername:

<bibliomixed role="website" xml:id="ba-9781472544247-103426">‘<title>Domain Name System</title>’,

<publishername>Wikipedia</publishername>, <pubdate>12 February 2009</pubdate>. Available at <link
xlink:href="http://www.en.wikipedia.org/wiki/Domain_name_system"><uri>http://en.wikipedia.org/wiki/
Domain_name_system</uri></link> [accessed <date role="accessed">3 May 2011</date>]</bibliomixed>

16.11.3. Music
This particular example is from a web source so can be treated as any other web resource:

<bibliomixed xml:id="bibl26" role="website"><author><personname role="last-first"><surname>Kramme</surname>

<firstname>Joel</firstname> <othername>I.</othername></personname></author>, ‘<title>A Country Masque
for Hodge Trillindle and His Zweet Hort Malkyn: The Dramatic Elements of Thomas Ravenscroft’s “Enamoring”
Section of the Harmonies from A Briefe Discourse, 1614</title>’, <link xlink:href="http://www.ickingmusic-
archive.org/scores/ravenscroft/enamouring.html#Lyrics"><uri>www.ickingmusic-archive.org/scores/ravenscroft/
enamouring.html#Lyrics</uri></link> (n.d.)</bibliomixed>

16.12. Legal references

Ref: §1.65, §1.66, §1.67

For legal items in a bibliography, ie cases, statutes etc, the bibliomixed element MUST be used. The
@role attribute must be set to an appropriate value from the list below:

1. case

2. legislation

An item marked “legislation” includes statutes, Acts, treaties, EU Directives, Regulations, Orders
and any other statutory instrument.

Within a legal citation, only light markup of the component parts is REQUIRED, at most a title, date
and some reference number, and possibly a URL. It is normally unlikely that they contain an author.

In most books it is unlikely that there will be many legal references, so a high proportion of them can
suggest that some items may be incorrectly marked up.73

16.12.1. Cases
<bibliomixed xml:id="bibl27a" role="case"><title><emphasis role="italic">Leeds Teaching Hospital NHS Trust
v A and B</emphasis></title> [<date>2003</date>] <bibliomisc role="legalRef">1 FLR 412</bibliomisc>.</
bibliomixed>

72
Tested in Schematron: bibliomixed-website
73
Tested in Schematron: proportion-case-legislation

126
 Bibliographies and components

The bibliomisc[@role=legalRef] is a general container for any identifier, and could even
contain the relevant court:

<bibliomixed xml:id="bibl27b" role="case"><title><emphasis role="italic">Blood and another v UK</

emphasis></title> [<date>1 March 2003</date>] <bibliomisc role="legalRef">High Court (unreported)</
bibliomisc>.</bibliomixed>

If a bibliomisc[@role=legalRef] occurs in a biblio item it MUST be a

bibliomixed[@role=legislation | case].74

Note that, though most cases have a “v” within them, some may begin “Re”:

<bibliomixed xml:id="bibl28b" role="case"><title><emphasis role="italic">Re D (A Child) (IVF treatment)</

emphasis></title> [<date>2001</date>] <bibliomisc role="legalRef">1 FLR 972</bibliomisc>.</bibliomixed>

It is an ERROR to mark up cases with other biblio constructs.75

<bibliomixed role="case" xml:id="b-001223">Cairo Court. <date>2004a</date>. Decision of Cairo Court

of First Instance, <bibliomisc role="legalRef">case no. 43/2004</bibliomisc>, <title><emphasis
role="italic">Pfizer vs Memphis Pharmaceutical and Chemicals (MPCI) and Delta Pharma Pharmaceutical
Company (DPPC)</emphasis></title>, issued 19 May 2004.</bibliomixed>

16.12.2. Legislation and other statutory instruments

This is about as simple as it gets:

<bibliomixed xml:id="bibl27c" role="legislation"><title>Equality Act 2010</title>.</bibliomixed>

A Regulation may have a longer title and a number:

<bibliomixed xml:id="bibl27e" role="legislation"><title>Human Fertilisation and Embryology Authority

(Disclosure of Donor Information) Regulations 2004</title> (<bibliomisc role="legalRef">SI 2004/1511</
bibliomisc>).</bibliomixed>

This reference to an Order also includes a reference to a specific article/section:

<bibliomixed xml:id="bibl27h" role="legislation"><title>Value Added Tax (Buildings and Land) Order 2010</
title>, <bibliomisc role="legalRef">SI 2010/485, art 4(2)</bibliomisc></bibliomixed>

This EU Directive reference doesn’t obviously have a title,76 so only the reference number has been
tagged:

<bibliomixed xml:id="bibl27f" role="legislation">Directive <bibliomisc role="legalRef">92/12/EC</

bibliomisc> on the mutual enforcement of tax debts</bibliomixed>

whereas this one has a couple of reference numbers and a date:

<bibliomixed xml:id="bibl27g" role="legislation">Directive <bibliomisc role="legalRef">2006/112/EC</

bibliomisc> of <date>28 November 2006</date> on the common system of value added tax (Principal VAT
Directive) 2006 <bibliomisc role="legalRef">OJ L347/1</bibliomisc></bibliomixed>

A legislation item can also include such things as Agreements, Treaties, etc:77
74
Tested in Schematron: legalref-present
75
Tested in Schematron: v-present, biblioentry-collab-vs and related tests
76
Presence of titles in non-legal items tested in Schematron: non-legal-biblio-title
77
Tested in Schematron: possible-legislation

127
 Bibliographies and components

<bibliomixed role="legislation" xml:id="b-000784"><title>EU-Egypt Association Agreement</title>.

Signature 25 June 2001, entered into force <date>1 June 2004</date>. <link xlink:href="http://
www.ec.europa.eu/external_relations/egypt/aa/06_aaa_en.pdf"><uri>http://ec.europa.eu/external_relations/
egypt/aa/06_aaa_en.pdf</uri></link>.</bibliomixed>

Or, additionally:

<bibliomixed role="legislation" xml:id="b-000804">WTO (World Trade Organization). <date>2001</date>.

<title><emphasis role="italic">Declaration on the TRIPS Agreement and Public Health</emphasis></title>.
<bibliomisc role="legalRef">WT/MIN (01)/DEC/W/2</bibliomisc>. <confgroup><conftitle>WTO Doha Ministerial
Conference</conftitle></confgroup>, 4th Sess. <link xlink:href="http://www.who.int/medicines/areas/policy/
tripshealth.pdf"><uri>http://www.who.int/medicines/areas/policy/tripshealth.pdf</uri></link>.</bibliomixed>

16.13. Recordings
A recording MUST take @role=recording, and the artist encoded using
othercredit[@otherclass=artist] (ie NOT author) (and not that orgname is used for
bands). It should also contain a date and title:78

<bibliomixed role="recording" xml:id="b-9781609032227-e25"><othercredit class="other"

otherclass="artist"><personname role="last-first"><surname>Bennett</surname> <firstname>Tony</
firstname></personname></othercredit>. '<title>Cold Cold Heart</title>.' CBS 330037. <emphasis
role="italic"><date>1951</date></emphasis>: USA.</bibliomixed>
<bibliomixed role="recording" xml:id="b-9781609032227-e35"><othercredit class="other"
otherclass="artist"><orgname>Bearfoot Bluegrass</orgname></othercredit>. <title><emphasis
role="italic">Back Home</emphasis></title>. CD-GLAC-7235 707541723527. <emphasis
role="italic"><date>2004</date></emphasis>: USA. (<link xlink:href="http://
www.bearfootbluegrass.com"><uri>www.bearfootbluegrass.com</uri></link>)</bibliomixed>

16.14. Films
A film MUST take @role=film, and MUST include a title and MAY include a date:79

<bibliomixed role="film" xml:id="b-9781609032227-e30"><title><emphasis role="italic">Applause</emphasis></

title>, dir. Rouben Mamoulian. <date>1929</date>. USA. 80 mins. Musical Drama. Non-original music by Jay
Gorney, E.Y. Harburg, E. Ray Goetz, Pete Wendling, Joe Young.</bibliomixed>

16.15. Other items

There are relatively few items that should be tagged as @role=other. Normally, if there is some
sort of title and a date, the chances are that it will fall into one of the other categories, though odd
reports etc may need to be “other”.80 If an item with @role=other contains publishername or
volumenum, for instance, the chances are that it should be one of the other bibliomixed types.81

16.15.1. Reports and organisation names

<bibliomixed xml:id="bibl27" role="other"><author><orgname>Arts Council England</orgname></author>,
‘<title>Economic impact study of UK theatre</title>’, April <pubdate>2004</pubdate>.</bibliomixed>

Implementation note: orgname is not handled in the DocBook XSL

78
Tested in Schematron: artist-required, recording-date, recording-title, poss-recording
79
Tested in Schematron: film-date, film-title, poss-film
80
Tested in Schematron: bibliomixed-other-test
81
Tested in Schematron: bibliomixed-other-issue1, bibliomixed-other-issue2

128
 Bibliographies and components

16.15.2. Play performances, radio broadcasts etc

<bibliomixed xml:id="b-0003108" role="other"><title>The Winters Tale</title> (<date>11 August 2009</date>),
William Shakespeare, dir. Michael Boyd, perf. Royal Shakespeare Company, Courtyard Theatre Stratford,
programme.</bibliomixed>

16.15.3. DVDs
Note how the performers’ names don’t need to be marked up and that bibliomisc is used for many of
the components:

<bibliomixed role="other" xml:id="ba-9781472543356-0002167"><author><personname role="last-

first"><surname>Bourne</surname><firstname>Matthew</firstname></personname></author>
(<bibliomisc role="description">choreographer</bibliomisc>) (<pubdate>1992</pubdate>), <title
xml:id="ba-9781472543356-0002168"><emphasis role="italic">Nutcracker</emphasis></title>. <bibliomisc
role="description">Performed by Alan Vincent, Etta Murfitt, and the cast of New Adventures</bibliomisc>
<date>2002</date>. <bibliomisc role="description">DVD</bibliomisc>, <publishername>Warner Vision
International</publishername>, <bibliomisc role="description">released 2003</bibliomisc>.</bibliomixed>

16.16. Inline bibliographic references

Most often, bibliographic references occur in specific bibliographic sections in which they are
displayed as separate block list items. However, occasionally a book may have bibliographic
references inline within a paragraph. For example, this text has no bibliography other than this:

which includes some complexity, and it is worth reviewing the markup in detail:

<para xml:id="b-9012785">For selections from these and other earlier critical responses, see <bibliolist
xml:id="b-9002785" role="inline"><bibliomixed role="monograph" xml:id="b-9002752"><editor><personname
role="first-last"><firstname>Brian</firstname> <surname>Vickers</surname></personname></editor>
(ed.), <title><emphasis role="italic">Shakespeare: The Critical Heritage</emphasis></title> 6 vols
(<publishername>Routledge</publishername>, <pubdate>1976-96</pubdate>); </bibliomixed> <bibliomixed

129
 Bibliographies and components

role="monograph" xml:id="b-9992034"><author><personname role="first-last"><firstname>Jonathan</

firstname> <surname>Bate</surname></personname></author>, <title><emphasis role="italic">The Romantics
on Shakespeare</emphasis></title> (<publishername>Penguin</publishername>, <pubdate>1992</pubdate>)</
bibliomixed></bibliolist>. Useful starting-points for criticism of particular plays, genres, or
performances are: the Oxford Shakespeare Topics series, edited by Peter Holland and Stanley Wells;
the Cambridge Companions to Shakespeare. On the comedies, see <bibliolist xml:id="b-9002786"
role="inline"><bibliomixed role="monograph" xml:id="b-9091752"><author><personname role="first-
last"><firstname>Kiernan</firstname> <surname>Ryan</surname></personname></author> <title><emphasis
role="italic">Shakespeare Comedies</emphasis></title>, (<publishername>Palgrave</publishername>,
<pubdate>2009</pubdate>)</bibliomixed></bibliolist>). For adventurous and accessible new thinking about
Shakespeare, see Continuum's series of original ‘minigraphs’, <emphasis role="italic">Shakespeare Now!</
emphasis> (ed. Ewan Fernie and Simon Palfrey).</para>
<para xml:id="b-9012753">There is an ever-expanding amount of textual and critical material online. A
convenient gateway to this abundance is the reference site Mr. William Shakespeare and the Internet.
This and many other sites are conveniently listed at <link xlink:href="http://www.shakespeare.bham.ac.uk/
resources"><uri>www.shakespeare.bham.ac.uk/resources</uri></link>. For the RSC's archive catalogue and
database see <link xlink:href="http://www.shakespeare.org.uk/main/3/313"><uri>www.shakespeare.org.uk/
main/3/313</uri></link>. For Shakespeare productions 1960–2000 see <link xlink:href="http://ahds.ac.uk/
performingarts/designingshakespeare"><uri>http://ahds.ac.uk/performingarts/designingshakespeare</uri></
link></para>
<para xml:id="b-9065754">On the First Folio, see <bibliolist xml:id="b-9002788" role="inline"><bibliomixed
role="monograph" xml:id="b-9002754"><author><personname role="first-last"><firstname
role="initials">W.W.</firstname> <surname>Greg</surname></personname></author>, <title><emphasis
role="italic">The Shakespeare First Folio</emphasis></title> <publishername>Oxford University Press</
publishername>, <pubdate>1955</pubdate></bibliomixed></bibliolist>). On the actors, see <bibliolist
xml:id="b-9002789" role="inline"><bibliomixed role="monograph" xml:id="b-9882752"><author><personname
role="first-last"><firstname>Andrew</firstname> <surname>Gurr</surname></personname></
author>, <title><emphasis role="italic">The Shakespeare Company, 1594–1642</emphasis></title>
(<publishername>Cambridge University Press</publishername>, <pubdate>2004</pubdate>); </
bibliomixed><bibliomixed role="monograph" xml:id="b-9002702"><author><personname role="first-
last"><firstname>Tiffany</firstname> <surname>Stern</surname></personname></author>, <title><emphasis
role="italic">Rehearsal from Shakespeare to Sheridan</emphasis></title> (<publishername>Oxford University
Press</publishername>, <pubdate>2000</pubdate>).</bibliomixed></bibliolist></para>

Points to note:

• Inline references MUST be within a bibliolist[@role=inline]82

• Punctuation between items within a list MUST be included

• Not all items have enough components to require bibliographic markup (the three examples are
book series, not individual titles)

• Some items are only external links.

Implementation note: bibliolist[@role=inline] is not handled in the DocBook XSL

However, if there is a separate bibliography, either in the back of the book or at the end of the chapter,
items mentioned in the text MUST be linked to them rather than being encoded inline. For example,
the following is WRONG:

<para xml:id="id0199">John Gielgud, who praised Stanislavski’s ‘practical wisdom’ in his preface to
<bibliolist role="inline" xml:id="g5"><bibliomixed xml:id="hg6" role="monograph"><author><personname
role="first-last"><firstname>Sonia</firstname> <surname>Moore</surname></personname></author>’s
<title><emphasis role="italic">The Stanislavski System</emphasis></title> (<publishername>Viking
Press</publishername>, <pubdate>1965</pubdate>); and </bibliomixed> <bibliomixed xml:id="d4"
role="monograph"><author><personname role="first-last"><firstname>Michael</firstname> <surname>Redgrave</
surname></personname></author>, who called himself ‘a disciple of Stanislavsky’ in his autobiography
(<title><emphasis role="italic">In My Mind’s Eye</emphasis></title>, <publishername>Weidenfeld &amp;
Nicolson</publishername>, <pubdate>1983</pubdate>)</bibliomixed></bibliolist>.</para>

It MUST be marked up as follows:

<para xml:id="id0199">John Gielgud, who praised Stanislavski’s ‘practical wisdom’ in his preface to Sonia
Moore’s <link role="bib" linkend="bibl11"><emphasis role="italic">The Stanislavski System</emphasis></
link> (Viking Press, 1965); and Michael Redgrave, who called himself ‘a disciple of Stanislavsky’ in his
autobiography (<link role="bib" linkend="bibl12"><emphasis role="italic">In My Mind’s Eye</emphasis></
link>, Weidenfeld &amp; Nicolson, 1983).</para>

82
Tested in Schematron: inline-bibliolist

130
 Bibliographies and components

It is also an ERROR for there to be punctuation at the end of the last bibliomixed AND for the text
after the bibliolist to start with punctuation.83

Furthermore, an inline bibliolist MUST have a space between it and any preceding word.84 The
following is an ERROR:

See also<bibliolist role="inline" xml:id="b-9781408174654-0000216"><bibliomixed role="monograph"

xml:id="b-9781408174654-0000217"><author><personname role="first-last"><firstname>James</firstname>
<othername role="middle-initials">L.</othername> <surname>Calderwood</surname></personname></author>,
<title xml:id="b-9781408174654-0000218"><emphasis role="italic">Shakespearean Metadrama</emphasis></title>
(<address xml:id="b-9781408174654-0000219"><city>Minneapolis</city></address>, <pubdate>1971</pubdate>);</
bibliomixed></bibliolist>

16.17. Abbreviated forms

Some works may include an abbreviated form of a reference, the expansion of which may well be at
the beginning of the bibliography. For example:

Brooks, C. (1977) ‘The heroic impulse in the Odyssey’, CW70, 455-6.

The expanded form MUST be included within the bibliomixed as well as the displayed form, each
with a different @condition:

<bibliomixed role="article" xml:id="ki9"><bibliomset relation="article"><author><personname role="last-

first"><surname>Brooks</surname> <firstname>C.</firstname></personname></author> (<pubdate>1977</pubdate>)
‘<title>The heroic impulse in the <emphasis role="italic">Odyssey</emphasis></title>’,</bibliomset>
<bibliomset relation="journal"><title condition="hidden"><emphasis role="italic">Classical World</
emphasis></title><glossterm linkend="CW" condition="display"><emphasis role="italic">CW</emphasis></
glossterm> <volumenum>70</volumenum>, <pagenums>455–6</pagenums>.</bibliomset></bibliomixed>

See also Section 14.6, “Conditional processing with @condition”.

Implementation note: This is not supported in DocBook XSL

16.18. Annotated bibliographies

Occasionally, bibliographic items may have notes in them by the author about the work. If
the annotation text runs on after the bibliographic reference, it can be contained within the
bibliomixed, but if, as here, it follows it:

this REQUIRES that the entire bibliography in which this occurs be within a general container
element (eg chapter and sections) and the bibliographic references contained within
bibliolist/bibliomixed, so that they can be interleaved with paras:
83
Tested in Schematron: bibliomixed-punc
84
Tested in Schematron: possible-missing-space4

131
 Bibliographies and components

<section xml:id="ba4">
<info xml:id="ba5">
<title xml:id="ba6">Further Reading</title>
</info>
<bibliolist xml:id="bl2">
<bibliomixed role="monograph" xml:id="ba7"><author><personname role="last-first"><surname>Abbott</
surname> <firstname>H. P.</firstname></personname></author> (<pubdate>1973</pubdate>), <title><emphasis
role="italic">The Fiction of Samuel Beckett: Form and Effect</emphasis></title>. <address><city>Berkeley</
city></address>: <publishername>University of California Press</publishername>.</bibliomixed>
</bibliolist>
<para xml:id="bl3">Abbott’s introduction to Beckett’s prose ranges from the early fiction through the
major novels: <emphasis role="italic">Murphy</emphasis>, <emphasis role="italic">Watt</emphasis>,
<emphasis role="italic">Molloy</emphasis>, <emphasis role="italic">Malone Dies</emphasis>, <emphasis
role="italic">The Unnamable</emphasis>, <emphasis role="italic">How It Is</emphasis>. He also gives
important attention to <emphasis role="italic">Texts for Nothing</emphasis> and the neglected <emphasis
role="italic">Mercier and Camier</emphasis>. An analysis of what Abbott calls ‘imitative form’, the book
looks at how the form of the fiction works particular effects on the reader.</para>

16.19. Non-permitted content of bibliographic

items
A small number of elements MUST NOT be used within a bibliomixed (though they are valid
within the DocBook Publishers schema):

• biblioid: If the content is a URI encode as a link;85

• publisher: This element does not permit PCDATA between components, so use publishername
etc directly where needed;86

85
Tested in Schematron: bibliomixed-biblioid
86
Tested in Schematron: bibliomixed-publisher

132
Chapter 17. Names
Ref: §1.92, §1.93, §1.94, §1.95

It is not necessary to mark up person or organisation names within paragraph text. Names MUST
be correctly marked up when they occur within structured content such as front material and
bibliographic entries.1 The names of people must be marked up using the personname element. The
names of organisations must be marked up using the orgname element.

Personal name must be marked up using the structured field variant of the personname element.
That is, it may only have element children, not text. A personname MUST also have a @role.2

The orgname element has no internal structure and must contain text only.

[Add instructions on Spanish, Asian names etc]

17.1. Initials in biblio names

The default Bloomsbury style for initials within bibliographical references is to include full stops.
However, occasionally, some book styles may require that no stops are used, either for the book as a
whole, or (for edited books) for specific chapters. If this is so, the following MUST be included in the
book metadata (in book/info or {chunk}/info):

<biblioid class="other" otherclass="biblioType">initials-without-stops</biblioid>

This will ensure that the regular tests for stops in bibliographies are switched off, and a few others
applied instead.3

This can also take the value ‘initials-with-stops’, though that is the assumed default value.

17.2. Overview of name markup

The following table sets out examples of how personal names must be marked up.

Name Markup
John Smith <personname role="first-last" ><firstname>John</
firstname> <surname>Smith</surname></personname>
Mr. John Smith <personname role="first-last" ><honorific>Mr.
</honorific> <firstname>John</firstname>
<surname>Smith</surname></personname>
J. Smith <personname role="first-last" >< first name
role='initials'>J </othername> <surname>Smith</
surname></personname>
John Robert Smith <personname role="first-last" ><firstname>John</
firstname> <othername role='middle'>Robert</
othername> <surname>Smith</surname></personname>
John R. Smith <personname role="first-last" ><firstname>John</
firstname> <othername role='middle-initials'>R </
othername> <surname>Smith</surname> </personname>

1
Tested in Schematron: personname-components
2
Tested in Schematron: personname-role-present
3
Tested in Schematron: biblioType-test; firstname-one-char-2; firstname-stop-3; firstname-stop-4

133
 Names

Name Markup
The Honourable J.R. Smith the <personname role="first-last" > <honorific>The
Third Honourable</honorific> < first name
role='initials'>J. R </othername>
<surname>Smith</surname> <lineage>the Third</
lineage></personname>
Mitford, Rev. J. <personname role="last-first"><surname>Mitford</
surname> <honorific>Rev.</honorific> <firstname
role="initials">J.</firstname></personname>
W.N. Price, Jr <personname role="first-last"><firstname
role="initials">W.N.</firstname> <surname>Price</
surname> <lineage role="comma-before" >Jr</
lineage></personname>
John K. Smith III <personname role="first- last"><firstname >
John </firstname> < other name role=" middle-
initials"> K. </firstname> <surname> Smith </
surname> <lineage> III </lineage></personname>

The values that may be used in the @role attributes of the various name elements are:

Element Value Indicates

firstname initials If the name consists only of
surname and initials this must
be used to mark the initials.
All initials must be marked up
within a single firstname
element.
othername middle If an individual middle name
is given, it is indicated with
this value. Multiple middle
names must be marked up using
multiple elements.

Note that names with an

othername and no firstname are
WRONGa
othername middle-initials If middle initials are given they
must be marked up with this
value. Multiple middle initials
must be marked up within a
single othername element.
lineage comma-before Since punctuation is not
permitted by the content
model of personname, if
a comma is required to be
displayed before the content
of lineage (“W.N. Price, Jr”)
this attribute MUST be used.
[Clarify requirement if used
within personname[@role=last-
first]]
a
Tested in Schematron: othername-no-firstname

134
 Names

17.3. Specific name encoding issues

The element givenname MUST NOT be used; use firstname instead.4

Spaces within a firstname normally suggest that there are multiple name components that should
be marked up separately.5

Names given as initials must use either firstname[@role=initials] or

othername[@role=middle-initials] depending on their place in the name, and must end with
a full stop.6 If punctuation occurs within a firstname that does not have @role=initials, it is an
ERROR.7

Double-barrelled surnames MUST be included within a single surname; full stops are rarely allowed
in surnames;8 and multiple surnames within a personname is an ERROR.9

Furthermore, it is unusual for a personname ONLY to contain a surname;10 if that is the case, it is
likely that the item may be a short form reference that simply needs to be a link to the full reference
elsewhere. Usually, only ancient authors (eg “Plato” and “Aristotle”) havea single name, which
MUST be contained within surname (even though it is semantically incorrect).

When initials occur in a name, either firstname[@role=initials] or

othername[@role=middle-initials] MUST be used.11

It is an ERROR for a single character or full stops to occur within such elements without the @role,
and there MUST NOT be an additional stop in untagged text after the name,12 ie the following is
WRONG (but see also Section 17.1, “Initials in biblio names”):

<bibliomixed role="monograph" xml:id="ba-9781472548375-0001173"><author><personname role="last-

first"><surname>Williams</surname> <firstname role="initials">J.</firstname></personname></
author>. <title xml:id="ba-9781472548375-0001174"><emphasis role="italic">The Politics of
Sleep: Governing (Un)consciousness in the Late Modern Age</emphasis></title> (<address
xml:id="ba-9781472548375-0001175"><city>Basingstoke</city></address>: <publishername>Palgrave Macmillan</
publishername>, (<pubdate>2011</pubdate>)</bibliomixed>

17.3.1. Confusion between surnames and firstnames

Markup of bibliographic references can be hard, and they include much subtlety, depending on the
bibliographic citation style the book author has used, even assuming such style has been applied
consistently. For example, it is not unusual to have a mixture of names with either surnames or
firstnames first:

Surname1, Firstname1, surname2, firstname2, and surname3, firstname3 (2002) ‘article title’ in
surname4, firstname4 and firstname5 and surname5 (eds.) Book Title, Place: Publisher

In such cases it can be hard to programmatically determine which is the surname and which the
firstname(see examples in Section 32.6.2, “Firstname/surname issues”).13
4
Tested in Schematron: givenname-not-allowed
5
Tested in Schematron: space-firstname
6
Tested in Schematron: name-initials
7
Tested in Schematron: stop-firstname, comma-firstname
8
Tested in Schematron: surname-with-stop
9
Tested in Schematron: multiple-surnames
10
Tested in Schematron: surname-only
11
Tested in Schematron: firstname-one-char, firstname-stop
12
Tested in Schematron: firstname-stop-2
13
Tested in Schematron: surname-is-firstname

135
 Names

17.3.2. Lineage and honorific

Note that text strings such as “Jr”, “Sr”, “II”, “III”, and “IV” MUST be within a lineage element,
and not captured within other name components.14

The honorific element typically includes such content preceding the name such as “Sir” or for
other designations after the name;15 it is very unusual for it to include “Dr” or other academic titles
on the title pages of academic books. The example below shows a honorific after the name:

<personname role="first-last">
<firstname>Arthur</firstname>
<surname>Madigan</surname>
<honorific>S.J.</honorific>
</personname>

17.3.3. Other name mark-up issues

In bibliographic items etc, especially in footnotes, names may sometimes be given in a possessive
form (“in John Smith’s book Book title(Cambridge: 2010)...”, in which case, the apostrophe MUST
NOT be included within the surname:16

<bibliomixed role="unpublished" xml:id="ba-9781849666565-0002159g"><author><personname

role="first-last"><firstname>Li</firstname><surname>Wuwei</surname></personname></author>'s
Keynote speech ‘<title xml:id="ba-9781849666565-0002033g">Towards City of Creativity</title>’ at
<confgroup><conftitle>Shanghai Creative Industries International Forum 2008</conftitle></confgroup>,
<address xml:id="ba-9781849666565-0002034g"><city>Shanghai</city></address></bibliomixed>

Implementation note: othername and lineage processing in DocBook XSL needs

modification. Needs to support @role=comma-before for lineage and display both in
bibliographies

14
Tested in Schematron: jr-present, sr-present, II-present, III-present, IV-present
15
Tested in Schematron: honorific-start, honorific-end. Typical post-nominal abbreviations that should be in honorific
include: (Hon); BA; B.A.; BDS; B.D.S.; BEd; B.Ed.; BEng; B.Eng.; BSc; B.Sc.; Bart; Bart.; Bt; Bt.; CBE; C.B.E.; CH; C.H.; DD; D.D.;
DLitt; D.Litt.; DPhil; D.Phil.; Esq; Esq.; FBA; F.B.A.; FRCP; F.R.C.P.; FRCS; F.R.C.S.; FRS; F.R.S.; Kt; Kt.; LLB; LL.B.; LLD; LL.D.;
MA; MBA; M.B.A.; MBE; M.B.E.; MD; M.D.; MEP; M.E.P.; MEd; M.Ed.; MLitt; M.Litt.; MP; M.P.; MRCP; M.R.C.P.; MRCS;
M.R.C.S.; MSP; M.S.P.; MSc; M.Sc.; MSci; M.Sci.; OM; O.M.; OSB; O.S.B.; PhD; Ph.D.; QC; Q.C.; SJ; S.J. In addition, some text
strings such as “Dir.” should not be in honorific (honorific-dir)
16
Tested in Schematron: surname-apos1 surname-apos2

136
Chapter 18. Footnotes, endnotes and
other notes
Ref: §1.75, §1.76, §1.77, §1.78

NOTE: This differs from the previous instructions

The footnote element MUST be used for all note types, ie:

Note type @role

Foot notes (at page foot) none
End of chapter notes end-ch-note
Back of book notes end-bk-note
End of paragraph notes end-para-note
Marginal notes margin1 | margin2

All notes marked with a number, letter or symbol (for example with *, †; or ‡) MUST be marked up
using footnote elements. Footnotes and notes must be inserted into the text at the point of first
reference to the note. The symbol (or numeric marker) MUST be replaced by the footnote element,
which MUST contain the content of the note.

The @role attribute MUST be used if the note is to be rendered other than at the foot of the page in
print. If a note is to be rendered at the end of the chapter then the @role attribute must be given the
value ‘end-ch-note’1 and if a note is to be rendered at the end of the book then the @role attribute
must be given the value ‘end-bk-note’.2 If a note is to be placed after a paragraph (as in some
legal books) the @role attribute must be given the value ‘end- para -note’. See Section 18.2.1,
“End of chapter notes”, Section 18.2.2, “End of book notes” and Section 18.2.3, “End of paragraph notes” for
placement of these notes.

Notes in the margins (and marginal line numbers) MUST take the @role values ‘margin1 |
margin2’. See Section 18.3, “Marginal notes” for more details.

DocBook convention is to auto-generate numeric labels for footnotes and end notes. However, in the
following cases a footnote MUST have a @label:

1. When the footnote uses a symbol or letter and is separate from the regular numeric flow of the
rest of the notes. This primarily affects actual footnotes at the foot of the page, or may affect notes
in tables.

2. For retrospective data conversion where a single note has a value that is not in the (alpha)numeric
sequence, ALL footnotes in the work MUST have their values stored within @label(eg the
numbering sequence runs... 34, 35, 35A, 36,...), so that the original footnote numbering can be
preserved.

3. Works where the footnotes were originally numbered per page must also have all the numbers
stored as @label, ie the first note on each page is numbered “1”

Note also that it is an ERROR if a footnote is the only content of a para3 , and if a footnote is within a
link.4
1
Tested in Schematron: end-ch-note-footnote, missing-processing-instruction2, end-ch-notes-item
2
Tested in Schematron: missing-processing-instruction, duplicate-end-bk-notes, end-bk-notes-item
3
Tested in Schematron: footnote-para
4
Tested in Schematron: footnote-link

137
 Footnotes, endnotes
and other notes

18.1. Notes content

Note content can be quite variable, depending on the authorial style and MAY require links to other
(normally bibliographic) items, or MAY include full bibliographic references themselves.5

18.1.1. Note with link to bibliography

The note appears as:

1. See Knowlson (323–24) on Beckett’s turn to French.

This is a non-standard reference to the bibliographic item, so requires a link:

<footnote xml:id="fn-1" role="end-bk-note"><para xml:id="fn-2">See <link role="bib"

linkend="bibl2">Knowlson</link> (323–24) on Beckett’s turn to French.</para></footnote>

This is a similar item:

2. Colin Duckworth ‘The Making of Godot’: 89.

where this is a short form reference to a contribution in a book, so the text in the title (“The Making of
Godot”) would be within the link.

Here is a similar example, pointing to the back of book bibliography:

<footnote xml:id="ba-9781408163023-5002788" role="end-bk-note" label="2"><para

xml:id="ba-9781408163023-5000123">As quoted in Cole Lesley, <link role="bib"
linkend="ba-9781408163023-5003097"><emphasis role="italic">The Life of Noël Coward</emphasis></link>
(London: Penguin Books, 1978), p. 149.</para></footnote>

18.1.2. Note with a bibliographic reference

If the note uses the standard short form reference for a bibliographic item, then link MUST be used
as elsewhere:

<footnote role="end-bk-note" xml:id="b-0001916"><para xml:id="b-0001917">Test Match Special is the BBC's

radio coverage of international cricket. For an analysis of its importance in constructing understandings
of cricket, see <link role="bib" linkend="b-0003989">Jones 2004</link>.</para></footnote>

18.1.3. Notes with a bibliographic item

Some bibliographic items mentioned in a note are not included in the (back of book) reference list, so
MUST have full bibliographic markup applied. For example:

3. ‘The Uneventful Event’ Irish Times February 18, 1956.

would be encoded as:

<footnote xml:id="f-1" role="end-ch-note"><bibliolist xml:id="f-3"><bibliomixed xml:id="f-4"

role="article"><bibliomset relation="article">‘<title>The Uneventful Event</title>’</bibliomset>
<bibliomset relation="journal"><title><emphasis role="italic">Irish Times</emphasis></title>
<pubdate>February 18, 1956</pubdate>.</bibliomset></bibliomixed></bibliolist></footnote>

5
Tested in Schematron: possible-link-biblio-1, possible-link-biblio-2, possible-link-biblio-3,
possible-link-biblio-4

138
 Footnotes, endnotes
and other notes

In the preceding example the footnote contains only the bibliographic reference, so its direct child
can be a bibliolist(but NOT with @role=inline, which is an ERROR, since that can only occur
within a para).6

In contrast, if the text contains more than just the biblio reference the bibliolist MUST also be
within a para, and consequently also have @role=inline.

<footnote role="end-bk-note" xml:id="b-0000083"><para xml:id="b-0000084">For an interesting account

of just such a &#x2018;disciplinary&#x2019; politics of sleep, see <bibliolist xml:id="b-0000085"
role="inline"><bibliomixed role="monograph" xml:id="b-0000087"><author><personname role="first-
last"><firstname>Simon</firstname> <surname>Williams</surname></personname></author>, <title
xml:id="b-0000087"><emphasis role="italic">The Politics of Sleep: Governing (Un)consciousness in
the Late Modern Age</emphasis></title> (<address xml:id="b-0000088"><city>Basingstoke</city></
address>: <publishername>Palgrave Macmillan</publishername>, <pubdate>2011</pubdate>).</bibliomixed></
bibliolist> This includes sections on what Williams calls &#x2018;fast&#x2019; capitalism, and on the
&#x2018;biomedicalization&#x2019; of sleep. </para></footnote>

18.1.4. Ibids, loc cits and op cits in footnotes

This footnote has very little content, and the “Ibid” just needs to be a link to the corresponding item
in the back of book bibliography (or in another footnote, if that is where it was referenced). In
addition, an alt element MUST also be included containing the author and title of the referenced
item,7 which can then be used for alt or title text in a processing application:

<footnote xml:id="ba-9781408163023-5002791" role="end-bk-note" label="5"><para

xml:id="ba-9781408163023-5000126"><link role="bib" linkend="ba-9781408163023-5003097"><alt>Cole Lesley,
The Life of Noël Coward</alt><emphasis role="italic">Ibid.</emphasis></link>, p. 65.</para></footnote>

Implementation note: alt does not appear to be supported in this context in standard
DocBook XSL

18.1.5. A footnote sequence

This is a good example of a bibliographic reference in a footnote and various forms of subsequent
reference to it thereafter. Note that the note also has text that continues after the bibliographic item:

<footnote xml:id="ba-9781408163023-5002789" role="end-bk-note" label="3"><para

xml:id="ba-9781408163023-5000124"><bibliolist role="inline"><bibliomixed xml:id="fn3"
role="monograph"><author><personname role="first-last"><firstname>Sean</firstname> <surname>O'Casey</
surname></personname></author>, <title><emphasis role="italic">The Green Crow</emphasis></title>
(<address><city>New York</city></address>: <publishername>George Braziller</publishername>,
<pubdate>1956</pubdate>), p. 98</bibliomixed></bibliolist>. In ‘Coward Codology: 1’, O'Casey says: "The
truth is, of course, that Noël Coward hasn't yet even put his nose into the front rank of second-class
dramatists, let alone into the front rank of first-class dramatists".</para></footnote>

A later footnote also refers to the same work, but in a somewhat abbreviated form (no publisher
details or date, so this requires a link back to the preceding reference:

<footnote xml:id="ba-9781408163023-5002796" role="end-bk-note" label="10"><para

xml:id="ba-9781408163023-5000133">Sean O'Casey, <link role="bib" linkend="fn3"><emphasis role="italic">The
Green Crow</emphasis></link>, p. 112.</para></footnote>

Finally, the next note is just an Ibid, which points back to the first full reference and has the alt text:

<footnote xml:id="ba-9781408163023-5002797" role="end-bk-note" label="11"><para

xml:id="ba-9781408163023-5000134"><link role="bib" linkend="fn3"><alt>Sean O'Casey, The Green Crow</
alt><emphasis role="italic">Ibid.</emphasis></link>, p. 92.</para></footnote>

6
Tested in Schematron: inline-bibliolist-footnote
7
Tested in Schematron: alt-required

139
 Footnotes, endnotes
and other notes

18.1.6. Further examples

In this set of end of chapter notes there is no corresponding bibliography, so all the full forms of the
references appear herein at some point:

note 2 starts off with text, followed by single reference (bibliomixed) within an inline
bibliolist; note 3 is a full bibliomixed(in this case a website); notes 4-6 need to be links back
to the bibliomixed in note 3, etc.

However, in this example we have something which is superficially the same:

140
 Footnotes, endnotes
and other notes

but all of the references in the notes are in fact listed in a back of book bibliography as well. In this
case the title of the reference MUST be a link(“Rene Wellek, Concepts of Criticism(New Haven, CT:
Yale University Press, 1963)”) pointing to the relevant bibliomixed, ie references in footnotes
should only be marked up in bibliomixed if there is no corresponding item in the bibliography for
it to point to.

[Link to an abbreviated form]

1 Adorno, GS 11:32. (Notes to Literature)- ET: Vol. 1, p. 22.

18.1.7. Incorrect footnote markup

Not all citations in footnotes need be marked up. In this example the content is more discursive and
illustrative, and so just needs to be marked up as plain text with formatting:

In 1592 a Latin translation of the prototypal such work, the Characters of Theophrastus
of Lesbos (371–287 BC), was published. There followed Joseph Hall's Characters of Virtues
and Vices1608, The Man in the Moon1609, Thomas Overbury's Characters 1614, John Earle's
Microcosmographie1628

ie, the following is WRONG. We do not need such extreme markup in such cases:

<footnote xml:id="b-9005762">
<para xml:id="b-1200823">In 1592 a Latin translation of the prototypal such work, the <emphasis
role="italic">Characters</emphasis> of Theophrastus of Lesbos (371–287 BC), was published.
There followed <bibliolist xml:id="b-9002779" role="inline"><bibliomixed role="monograph"
xml:id="b-9800016"><author><personname><firstname>Joseph</firstname><surname>Hall</surname></
personname></author>'s <title>Characters of Virtues and Vices</title> <pubdate>1608</pubdate>,
<title>The Man in the Moon</title> <pubdate>1609</pubdate>, <author><personname><firstname>Thomas</
firstname><surname>Overbury</surname></personname></author>'s <title>Characters</title> <pubdate>1614</
pubdate>, <author><personname><firstname>John</firstname><surname>Earle</surname></personname></author>'s
<title>Microcosmographie</title> <pubdate>1628</pubdate>. </bibliomixed></bibliolist></para>

141
 Footnotes, endnotes
and other notes

</footnote>

18.2. Note placement

Implementation note: Placement of end chapter and end book notes as described herein is not
supported in DocBook XSL.

Required handling is for the note refs to be links to the end notes, which are displayed at the
end of the chapter/chunk/book as in the print.

Bob Stayton on the docbook mailing list noted:

1. “You'll need to mark all the elements that you want handled in a special way with role
attributes.

2. You should process those special elements with templates in a mode different from the
default, applying templates in that mode.

3. You will need to include empty templates that match on those elements with those roles, but
in default mode (no mode attribute) to prevent them from being processed normally along
with other text.

4. You'll need to customize certain DocBook templates to place the special text, triggering
processing of them in the new modes. For example, customize the book template to call
a template named something like "process.endnotes" and placed at the end of the book
template to trigger end note processing there.”

18.2.1. End of chapter notes

The notes that MUST be placed at the end of a chapter (footnote[@role=end-ch-note]) are not
necessarily the very last item to appear within a chapter chunk. Therefore, a processing instruction
MUST be included within the text to indicate where the notes section must be inserted.8 Such PI
MAY also include the value of the section title for the notes if one is required though markup or
Unicode character references are NOT PERMITTED within the PI 'title'9 :

world in which the tide of faith was already retreating...</para>

</section>
<?insert item="end-ch-notes" title="Notes"?>
<bibliography xml:id="en11">
<info xml:id="en12">

<title xml:id="en13">Bibliography</title>
</info>
<bibliomixed role="article" xml:id="en14"><bibliomset relation="article"><author><personname role="last-
first"><surname>Weinstock</surname> <firstname>D.J.</firstname></personname></author> (<pubdate>1981</
pubdate>), ‘<title>“Say not we are on a darkling plain”: Clough’s response to “Dover Beach”</title>’,</
bibliomset> <bibliomset relation="journal"><title><emphasis role="italic">Victorian Poetry</emphasis></
title>, <volumenum>19</volumenum>.</bibliomset></bibliomixed>

However, if there is no title for the notes section, or if there is other content in the notes section, the PI
MUST simply call in the list of notes within a correctly-structured division of text, and MUST have a
@role:10

<section xml:id="notes" role="notes">

8
Tested in Schematron: ch-insert-missing
9
Tested in Schematron: pi-markup, ampersand-in-pi-insert
10
Tested in Schematron: possible-notes-section

142
 Footnotes, endnotes
and other notes

<info xml:id="notes1">
<title xml:id="notes2">Notes</title>
</info>
<para xml:id="notes3">Introductory paragraph before the end chapter notes, etc</para>
<?insert item="end-ch-notes"?>
</section>

Note that the following, with a 'Notes' section/info/title and a title in the PI is WRONG (all
structurally equivalent notes sections in a book must be handled similarly, but it is most likely that the
insert PI simply needs to be like that in the previous example):11

<section xml:id="b-9780857854049-0000158">
<info xml:id="b-9780857854049-0000159"><title xml:id="b-9780857854049-0000160">Notes</title></info>
<?insert item="end-ch-notes" title="Notes"?>
</section>

A section[@role=notes] MUST include at least one end-ch-notes processing instruction, and

it is an ERROR if an end-ch-notes PI is present but there are no corresponding footnotes in the
chapter.12

It is also an ERROR if an end-ch-notes PI is present within a footnote.13

18.2.2. End of book notes

Notes sections at the end of a book also need a placeholder. Typically, this will be a chapter within
the back matter, which MUST have pagenums and a pdf file reference, and MUST have a @role.14

As with the end of chapter notes, a processing instruction MUST call in the list of notes, where
“chunk” has the value of the chunk @xml:id of the notes to be included (ie chapter by chapter).15

A chapter [@role=notes] MUST include at least one end- bk -notes processing instruction16
, and the chunk IDs in the processing instruction MUST point to a valid chunk id in the data.17

Note that the remark element is included with standard content simply so that the file will parse,
otherwise the chapter would not have any valid content.

<chapter xml:id="backnotes" role="notes">

<info xml:id="bn1">
<title xml:id="bn">Notes</title>
<pagenums>123–134</pagenums>
<mediaobject xml:id="id0046y">
<imageobject xml:id="id0047z"><imagedata fileref="filename.pdf" format="application/pdf"/></imageobject>
</mediaobject>
</info>
<remark xml:id="bn3" condition="hidden">Placeholder for back of book note content</remark>
<?insert item="end-bk-notes" chunk="ch1" title="Introduction"?>
<?insert item="end-bk-notes" chunk="ch2" title="<emphasis role='italic'>Waiting for Godot</emphasis> and
<emphasis role='italic'>Endgame</emphasis>"?>
<?insert item="end-bk-notes" chunk="ch3" title="Conclusion"?>
</chapter>

The value of the ‘title’ string in the processing instruction MUST match that as it appears on the
printed page where the notes are to be inserted.18

Some examples of books in which this occurs are included below:

11
Tested in Schematron: end-ch-notes-title, notes-pi-title
12
Tested in Schematron: end-ch-notes-missing, processing-instruction-issue
13
Tested in Schematron: end-ch-notes-in-footnote
14
Tested in Schematron: possible-notes-section
15
Tested in Schematron: bk-insert-missing
16
Tested in Schematron: end-bk-notes-missing
17
Tested in Schematron: end-bk-notes-missing
18
Tested in Schematron: insert-pi-title, insert-pi-title2

143
 Footnotes, endnotes
and other notes

Implementation note: Default numbering style must be to start from 1 within each chunk, as
called.

18.2.3. End of paragraph notes

Some legal texts contain notes placed at the end of the paragraph in which they are referenced.

These texts contain numbered paragraphs, which use the formalpara container element. Such notes
MUST have a @role='end-para-note' and the placement is determined by the location of an
insert PI.19

<formalpara xml:id="b-9781234567897-fp2.9">

19
Tested in Schematron: end-para-notes-item, para-insert-missing, end-para-note-footnote

144
 Footnotes, endnotes
and other notes

<info xml:id="q1">
<title xml:id="q2">2.9</title>
</info>
<para xml:id="q3">The law relating to the circumstances in which minority shareholders may maintain
an action on behalf of their company in the face of opposition from the management and majority
shareholders has, over the years, attracted a great deal of comment and discussion.<footnote label="1"
role="end-para-note" xml:id="q4"><para xml:id="q5">See the so called rule in <bibliolist role="inline"
xml:id="q6"><bibliomixed role="case" xml:id="q7"><emphasis role="italic">Foss v Harbottle</emphasis>
(1843) 2 Hare 461</bibliomixed></bibliolist>.</para></footnote> While the courts have been prepared
to assist shareholders to bring derivative actions based on the company’s cause of action against
persons who have seemingly engaged in fraud and misappropriation of the company’s property, there
has been uncertainty as to what amounts to fraud and what can be regarded as corporate property.
For example, some of the cases involving allegations of equitable fraud include misconduct, such
as the taking of a secret profit, in circumstances where there is no dishonesty in the common law
sense.<footnote label="2" xml:id="q8" role="end-para-note"><para xml:id="q9">See <bibliolist role="inline"
xml:id="q10"><bibliomixed xml:id="q11" role="case">Armitage v Nurse [1998] Ch 241 at 252</bibliomixed></
bibliolist>. Millett LJ stated that equitable fraud included ‘breach of fiduciary duty, undue influence,
abuse of confidence, unconscionable bargains and fraud in powers’. See also for an early discussion
of this <bibliolist xml:id="q12" role="inline"><bibliomixed xml:id="q13" role="article"><bibliomset
relation="article"><author><personname role="first-last"><firstname role="initials">B.</firstname>
<surname>Rider</surname></personname></author> ‘<title>Amiable Lunatics and the Rule in Foss v
Harbottle</title>’ (<pubdate>1978</pubdate>)</bibliomset> <bibliomset relation="journal"><title><emphasis
role="italic">Cambridge Law Journal</emphasis></title> <volumenum>270</volumenum></bibliomset></
bibliomixed></bibliolist>. In <bibliolist role="inline" xml:id="q14"><bibliomixed xml:id="q15"
role="case"><emphasis role="italic">Item Softwear (UK) Ltd v Fassihi</emphasis> [2005] 2 BCLC 91</
bibliomixed></bibliolist>, it was held that a director is under a duty derived from his obligation
of loyality to disclose to his company his own wrongdoing even if it does not amount to fraudulent
misconduct. The dishonest failure to do this, might well render the law of fraud relevant. See <emphasis
role="bold">6.14</emphasis>.</para></footnote>...</para>
<?insert item="end-para-notes"?>
</formalpara>

Implementation note: This placement is not supported in standard DocBook XSL. The default
numbering style must be to start from 1 within each formalpara.

See also Section 14.1.3, “Formal paragraphs” and Section 32.16.5, “Numbered paragraphs”.

18.3. Marginal notes

Marginal notes are likely to be rare in most content, but where they occur the footnote element
MUST be used to store them. The footnote element MUST also be used to store a line number as
displayed in the margin.

Two values of @role are allowed: margin1and margin2. These are to indicate to which series
of marginal notes a specific item belongs. Note that this does not mean ‘left’ or ‘right’ since the
placement is dependent on the processing application. For example, if a work has both line numbers
and some authorial textual notes in the margin, all of the former would be margin1 and the latter
margin2.

See also Section 24.3.4, “More complex poems, and line numbers”

<line xml:id="po64">&#160;&#160;&#160;&#160;Thou hast bound bones and veins in me,

fastened me flesh, <footnote role="margin1" xml:id="po65"><para xml:id="po66">5</para></
footnote><footnote role="margin2" xml:id="po67"><para xml:id="po68">Marginal note text</para></footnote></
line>

Implementation note: This is not supported in DocBook XSL. These footnotes MUST NOT be
included in the auto-generated numbered sequence that is used for other footnotes; indeed, they
MUST NOT have an auto-generated number. If a number marker is required in the text, that
MUST be provided by the @label only, though in many cases (and especially where used for
line numbers) @label is NOT REQUIRED.

145
Chapter 19. Lists
Lists are (usually) block items, and should be siblings of para. It is usually an ERROR for a list to be
the sole child of a para element, other than in the abstract(the content model of which does not
allow them). 1

It MAY be an error if there is only a single list item.2

Generally, the only occasion when it is permissible (and REQUIRED) that lists occur within
paragraphs is where the sentence continues after the list:

<para xml:id="id0076">Sometimes it may be necessary to have a list within a paragraph, such as here:
<itemizedlist xml:id="id0077">
<listitem xml:id="id0078"><para xml:id="id0079">Item 1</para></listitem>
<listitem xml:id="id0080"><para xml:id="id0081">Item 2</para></listitem>
</itemizedlist>
which only makes sense if the sentence continues after the list. Otherwise, the lists must be siblings of
the paras.</para>

See also Section 10.8, “Glossaries and abbreviations lists”.

19.1. Simple lists

A simplelist in DocBook is for those list blocks that do not have titles, bullets, numbering, or
multi-paragraph items. This list type MUST be used in such cases. A simplelist MUST NOT be
used for poetry (for which use the poetry element).

<simplelist>
<member>Item 1</member>
<member>Item 2</member>
<member>Item 3</member>
</simplelist>

Here’s a good example of material that would need a simplelist:

19.2. Unordered (bulleted) lists

Lists with bullets MUST use itemizedlist. Note that these lists (and orderedlist) may contain
multiple paragraphs with a list item and lists may be nested.3

<itemizedlist xml:id="id0060">
<listitem xml:id="id0061"><para xml:id="id0062">First item</para></listitem>

1
Tested in Schematron: list-para-test
2
Tested in Schematron: single-list-item and single-list-item-2
3
Presence reported in Schematron: nested-list

146
 Lists

<listitem xml:id="id0063"><para xml:id="id0064">Second item</para>

<para xml:id="id0065">Second para of item 2</para>
</listitem>
<listitem xml:id="id0066"><para xml:id="id0067">Third item</para></listitem>
</itemizedlist>

The style of the bullet can be controlled to a limited extent, by using the @mark attribute, which
normally takes values of disc (default), square and circle:4

<itemizedlist xml:id="id0077" mark="square">

However, @mark=none is permissible for occasions when what would otherwise be a simplelist
has a title, or if any of the list items contain multiple para s, or nested lists etc. See also the worked
example in Section 32.7.1, “A simple list with title, columns and notes”.

See also DocBook documentation and examples:

http://www.sagehill.net/docbookxsl/Itemizedlists.html

Implementation note: The @mark appears to have partial supported in DocBook XSL

Implementation note: Display of list titles when they are within info is not supported in
DocBook XSL

19.3. Ordered (numbered) lists

EXCEPT FOR LEGAL TEXTS (see Section 32.16.6, “Numbered lists in legal books”), for numbered lists,
orderedlist MUST be used:

<orderedlist xml:id="id0069">
<listitem xml:id="id0070"><para xml:id="id0071">First item</para></listitem>
<listitem xml:id="id0072"><para xml:id="id0073">Second item</para></listitem>
<listitem xml:id="id0074"><para xml:id="id0075">Third item</para></listitem>
</orderedlist>

DocBook also supports more complex numbering patterns and options, such as continuation of
numbering:5

<itemizedlist xml:id="id0077">
<listitem xml:id="id0078"><para xml:id="id0079">Item 1</para></listitem>
<listitem xml:id="id0080"><para xml:id="id0081">Item 2</para></listitem>
</itemizedlist>
<para xml:id="id0082">The list is then followed by any other content. It may also end a chapter and a new
one start. If the next list includes the continuation attribute then the numbering will continue the
sequence:</para>
<orderedlist continuation="continues" xml:id="id0086">
<listitem xml:id="id0087"><para xml:id="id0088">Item 3</para></listitem>
<listitem xml:id="id0089"><para xml:id="id0090">Item 4</para></listitem>
<listitem xml:id="id0091"><para xml:id="id0092">Item 5</para></listitem>
</orderedlist>

In addition, the numbering style can be set to be other than Arabic,6 items can be forced to start with
a particular number (and note that the value is a number, irrespective of the numeration type),7 and
when there are nested lists, they may inherit the parent numbering:8
4
Tested in Schematron: list-mark
5
Presence reported in Schematron: continuation-present
6
Presence reported in Schematron: numeration-present
7
Presence reported in Schematron: startingnumber-present
8
Presence reported in Schematron: inheritnum-present

147
 Lists

<orderedlist xml:id="id0077g" numeration="loweralpha" startingnumber="3">

<listitem xml:id="id0078g">
<para xml:id="id0079g">Item 1</para>
</listitem>
<listitem xml:id="id0080g">
<para xml:id="id0081g">Item 2</para>
<orderedlist xml:id="id0082g" numeration="lowerroman" inheritnum="inherit">
<listitem xml:id="id0083g">
<para xml:id="id0084g">Sub-item</para>
</listitem>
<listitem xml:id="id0085g">
<para xml:id="id0086g">Sub-item</para>
</listitem>
</orderedlist>
</listitem>
</orderedlist>

Ordered lists and itemized lists may also be nested together.

See also the DocBook documentation:

• http://www.docbook.org/tdg5/publishers/5.1b3/en/html/orderedlist.html

• http://www.sagehill.net/docbookxsl/Orderedlists.html

19.4. Variable lists

The other list type is the variablelist, which can be used for lists where there are chronologies
(for example) and for numbered lists in legal books (see Section 32.16.6, “Numbered lists in legal
books”). The variablelist MUST not be used for glossaries, for which glossary and glosslist
are available. In addition, variablelist is PREFERRED for list-like content rather than the table
elements (though there may be complex lists for which a table is easier to use).

<variablelist>
<info><title xml:id="pti-0">Film production</title></info>
<varlistentry>
<term xml:id="pt-001">1899</term>
<listitem xml:id="pl-001"><para xml:id="pp-001">First films shot and screened in Korea by Burton Holmes</
para></listitem>
</varlistentry>
<varlistentry>
<term xml:id="pt-002">1903</term>
<listitem xml:id="pl-002"><para xml:id="pp-002">First public film screening announced in a newspaper
(<emphasis role="italic">Hwangsong sinmun</emphasis>)</para></listitem>
</varlistentry>
<varlistentry>
<term xml:id="pt-003">1903</term>
<listitem xml:id="pl-003"><para xml:id="pp-003">Tongdaemun Motion Picture Studio, the first motion picture
theater in Korea, opens</para></listitem>
</varlistentry>
</variablelist>

Note that a variable list may contain multiple terms for each entry.9 See http://
www.sagehill.net/docbookxsl/Variablelists.html, and also for further information about
variablelist formatting and indentation: it is assumed that all variablelists will be formatted
as tables (ie with terms and entrys on the same line); if this is not the case for a specific list, follow
the instructions as described using the relevant DocBook processing instructions.

See also Section 10.8, “Glossaries and abbreviations lists”.

9
Tested in Schematron: multi-terms

148
Chapter 20. Tables
There are two sorts of table in DocBook:

• A table is a table with a title

• An informaltable is a table without a title

It is an ERROR to have a table with an empty title element.1 A title in the print edition will
usually be preceded by “Table n” etc. As with Chapter and Part titles, the string “Table n” MUST
NOT be encoded in the title,2 but the alphanumeric value of n MUST be captured as @label.

It is important that all style information as used in the print MUST be retained, ie table, row, column
and cell borders, vertical alignment, column widths, etc all match exactly the format in the book.

Further examples can be seen in: http://www.sagehill.net/docbookxsl/Tables.html

This is the default informaltable style, ie with no attributes controlling borders and layout:

<informaltable xml:id="id0116">
<tgroup cols="2">
<thead>
<row><entry xml:id="id0117">Column 1</entry><entry xml:id="id0118">Column 2</entry></row>
</thead>
<tbody>
<row><entry xml:id="id0119">Item 1</entry><entry xml:id="id0120">1</entry></row>
<row><entry xml:id="id0121">Item 2</entry><entry xml:id="id0122">2</entry></row>
<row><entry xml:id="id0123">Item 3</entry><entry xml:id="id0124">3</entry></row>
</tbody>
</tgroup>
</informaltable>

The number of entrys in a row MUST be equal to the cols value in tgroup,3 apart from where
there are column and row spans.

In the following example, setting @colsep to “0” switches off the column separator, the @frame
value adds a border on the top and bottom of the table as a whole, and @rowheader treats the first
column as the row header, which is important for accessibility:

<informaltable colsep="0" frame="topbot" pgwide="0" rowheader="firstcol" xml:id="id0126">

<tgroup cols="2">
<thead>
<row><entry xml:id="id0127">Column 1</entry><entry xml:id="id0128">Column 2</entry></row>
</thead>
<tbody>
<row><entry xml:id="id0129">Item 1</entry><entry xml:id="id0130">1</entry></row>
<row><entry xml:id="id0131">Item 2</entry><entry xml:id="id0132">2</entry></row>
<row><entry xml:id="id0133">Item 3</entry><entry xml:id="id0134">3</entry></row>
</tbody>
</tgroup>
</informaltable>

This next example spans the entire page width (@pgwide), with no column separators, frame on the
sides, and only one row separator under the first body row. It also uses @colwidth to control the
relative widths of the two columns:

<informaltable colsep="0" frame="sides" pgwide="1" rowheader="firstcol" rowsep="0" xml:id="id0136">

<tgroup cols="2">
<colspec colwidth="35"></colspec>
<colspec colwidth="25"></colspec>
<thead>

1
Tested in Schematron: impermissible-empty-element
2
Tested in Schematron: table-in-label
3
Tested in Schematron: row-cols-count

149
 Tables

<row><entry xml:id="id0137">Column 1</entry><entry xml:id="id0138">Column 2</entry></row>

</thead>
<tbody>
<row rowsep="1"><entry xml:id="id0139">Item 1</entry><entry xml:id="id0140">1</entry></row>
<row><entry xml:id="id0141">Item 2</entry><entry xml:id="id0142">2</entry></row>
<row><entry xml:id="id0143">Item 3</entry><entry xml:id="id0144">3</entry></row>
</tbody>
</tgroup>
</informaltable>

Now we have a table with no column or row separators, frame on the bottom, and one cell that spans
two rows (which means that tbody/row[2] only has one entry within it):4

<informaltable colsep="0" frame="bottom" pgwide="0" rowheader="firstcol" rowsep="0" xml:id="id0146">

<tgroup cols="2">
<colspec colwidth="35" colname="col1"></colspec>
<colspec colwidth="25" colname="col2" align="right"></colspec>
<thead>
<row><entry xml:id="id0147">Column 1</entry><entry xml:id="id0148">Column 2</entry></row>
</thead>
<tbody>
<row><entry morerows="1" xml:id="id0149">Item 1</entry><entry xml:id="id0150">1</entry></row>
<row><entry xml:id="id0151">2</entry></row>
<row><entry xml:id="id0152">Item 3</entry><entry xml:id="id0153">3</entry></row>
</tbody>

</tgroup>
</informaltable>

Now here is a table with cells that span multiple rows and columns:5

<informaltable frame="all" xml:id="id0155">

<tgroup cols="2">
<colspec colwidth="35" colname="col1"></colspec>
<colspec colwidth="25" colname="col2"></colspec>
<thead>
<row><entry xml:id="id0156">Column 1</entry><entry xml:id="id0157">Column 2</entry></row>
</thead>
<tbody>
<row><entry morerows="1" xml:id="id0158">Item 1</entry><entry xml:id="id0159">1</entry></row>
<row><entry xml:id="id0160">2</entry></row>
<row><entry namest="col1" nameend="col2" xml:id="b-id0161">3</entry></row>
</tbody>
</tgroup>
</informaltable>

This is a table (ie not an informal one), which has a tfoot, alt and caption as well. Note that the
tfoot content appears before the tbody in the content model. In practice, it is unlikely that any alt
content will be available.

<table xml:id="id0163">
<info xml:id="id0164"><title xml:id="id0165">A simple table</title></info>
<alt>This is the content of the alt element</alt>
<tgroup cols="2">
<thead>
<row><entry xml:id="id0166">Column 1</entry><entry xml:id="id0167">Column 2</entry></row>
</thead>
<tfoot>
<row><entry xml:id="id0168">Foot</entry><entry xml:id="id0169">Content</entry></row>
</tfoot>
<tbody>
<row><entry xml:id="id0170">Item 1</entry><entry xml:id="id0171">1</entry></row>
<row><entry xml:id="id0172">Item 2</entry><entry xml:id="id0173">2</entry></row>
<row><entry xml:id="id0174">Item 3</entry><entry xml:id="id0175">3</entry></row>
</tbody>
</tgroup>
<caption xml:id="id0176"><para xml:id="id0177">The is the content of the caption, which is inside a
paragraph</para></caption>
</table>

4
Presence reported in Schematron: table-row-col-att
5
Tested in Schematron: namest-present, nameend-present, nameend-present-2, namest-and-end, col-span-
test, namest-required

150
 Tables

Implementation note: CALS table alignment mechanisms are not supported in DocBook XSL

20.1. Table placement

Tables and informaltables MUST NOT occur within a paragraph. The same rules apply as for figure
placement. See Section 21.4, “Image placement”.

151
Chapter 21. Figures and images
Ref: §1.52, §1.53, §1.54, §1.55

NOTE: This differs slightly from the previous instructions

Block images MUST be marked up within a mediaobject element, almost invariably within a
figure or informalfigure.1 Images that are not within the body of the book, eg title page logo,
are most likely NOT to require a containing figure or informalfigure element (see Section 7.5.8,
“Imprint logo”). Inline images MUST be marked up within a inlinemediaobject element (see
Section 23.3, “More complex equations”). The image itself MUST be marked up using an imageobject
element2 containing at least one imagedata element. The @fileref attribute MUST be used to
store a reference to the relative location of the image file, with the following options:

• /pdfs: for the chunk pdfs3

• /images: for all image content4

The imageobject element MUST contain one imagedata element for each format provided. An
imageobject MUST contain an image in a web format, ie it is an ERROR if only a print format (eps/
tiff) is present.5 If multiple image formats are provided then multiple imagedata elements MUST
be present with an appropriate @ outputformat value.6 (See also Section 14.7, “@outputformat”.)
The @format attribute7 must contain the MIME type appropriate to the file referenced by @fileref
attribute, eg:8

Name MIME type File extension(s)

Adobe Portable Document application/pdf .pdf
Format
Graphics Interchange Format image/gif .gif
JPEG image image/jpeg .jpeg |.jpg
Portable Network Graphics image/png .png
Tagged Image File Format image/tiff .tiff |.tif

<mediaobject xml:id='b-0111'>
<imageobject>
<imagedata fileref='images/example.png' outputformat='web' format='image/png'/>
</imageobject>
<imageobject>
<imagedata fileref='images/example.tiff' outputformat='print' format='image/tiff'/>
</imageobject>
</mediaobject>

Ordinarily a block image will be contained within a figure or informalfigure. These containers
provide a limited number of attributes for controlling the layout and alignment of the image display.

Please note the following important difference:

1
Tested in Schematron: mediaobject-required
2
Tested in Schematron: imageobject-required
3
Tested in Schematron: pdf-dir
4
Tested in Schematron: images-dir
5
Tested in Schematron: only-non-web-image, non-web-image-format
6
Tested in Schematron: outputformat-required, outputformat-imagedata
7
Tested in Schematron: imagedata-format-required
8
Tested in Schematron: imagedata-mime-type, pdf-file-extension, png-file-extension, tiff-file-
extension, gif-file-extension, jpg-file-extension

152
 Figures and images

• A figure is a displayed image with a title

• An informalfigure is a displayed image without a title (though it MAY contain a caption)9

It is an ERROR to have a figure with an empty title element.10 A title in the print edition will
usually be preceded by “Figure n” etc. As with Chapter and Part titles, the string “Figure n” MUST
NOT be encoded in the title,11 but the alphanumeric value of n MUST be captured as @label.

21.1. Image display

DocBook makes available a number of attributes for the control of the display of images and other
media objects. For example, it is possible to use imagedata/@align to control the left/right/centre
alignment of the image.

See also the details in the DocBook documentation.

21.2. Image captions

Note that titles and captions should not be confused. A title is likely to have a “Figure n”
label, and titles are most often above the figure, and in a different font style. A caption is normally
below the figure containing relatively expansive text and less prominent. For this reason, an
informalfigure can have a caption, but it should not be captured as a figure’s title. Such
captions are often used for source and attribution information about the figure. For example, the
following figure:

would be an informalfigure, with the following caption:

9
Presence reported in Schematron: figure-present
10
Tested in Schematron: impermissible-empty-element
11
Tested in Schematron: figure-in-label

153
 Figures and images

<caption xml:id="id0031">
<para xml:id="casp001">Michelangelo Merisi da Caravaggio (1571-1610) <emphasis role="italic">The Conversion
of St Paul</emphasis>, 1601 (oil on canvas). <phrase role="source">Santa Maria del Popolo, Rome, Italy/
Bridgeman Art Library.</phrase></para>
</caption>

If a figure is encoded with a very long title, it is possible that some of its content may need to
belong in a caption.12

The boundary between what constitutes a figure title and what is a caption is arguably a bit
vague, but in a case like this, where we have some text that all runs on, is fairly long, doesn’t have
components that are especially typographically distinct as a “title”, and also includes permissions
information (example includes WRONG markup):

<figure label="D" xml:id="ba-9781472543356-0000082cc"><info xml:id="ba-9781472543356-0000083cc"><title

xml:id="ba-9781472543356-0000084cc"><link linkend="ba-9781472543356-0001991"><emphasis
role="italic">Oliver Twist</emphasis>, Classics Illustrated</link> (2008, pp. 8&#x2013;9). &#x00A9;2013
First Classic Inc. All Rights Reserved. By Permission of Jack Lake Productions Inc.</title></info>
<mediaobject xml:id="ba-9781472543356-0000085cc"><imageobject
xml:id="ba-9781472543356-0000086cc"><imagedata fileref="images/figd.jpg" format="image/jpeg"/></
imageobject></mediaobject></figure>

then, this is more likely a caption than a title. In which case the containing element need to be an
informalfigure.

Revised (CORRECT) markup:

<informalfigure label="D" xml:id="ba-9781472543356-0000082cc">

<mediaobject xml:id="ba-9781472543356-0000085cc"><imageobject
xml:id="ba-9781472543356-0000086cc"><imagedata fileref="images/figd.jpg" format="image/jpeg"/></
imageobject></mediaobject>
<caption xml:id="ba-9781472543356-0000083cc"><para xml:id="ba-9781472543356-0000084cc"><link
linkend="ba-9781472543356-0001991"><emphasis role="italic">Oliver Twist</emphasis>, Classics Illustrated</
link> (2008, pp. 8–9). ©2013 First Classic Inc. All Rights Reserved. By Permission of Jack Lake Productions
Inc.</para></caption></informalfigure>

These are often spotted via the warning mentioned in the preceding footnote:

Description: The figure title is 141 characters long, should some of it be in a caption? check element with
id "ba-9781472543356-0000082cc"

21.3. Image sources

Often an image may have a distinct source description to indicate where the image is from, or
to include a copyright statement. Sometimes these simply run on in the figure caption after the
descriptive text:

<caption xml:id="id0031">
<para xml:id="casp001">Michelangelo Merisi da Caravaggio (1571-1610) <emphasis role="italic">The Conversion
of St Paul</emphasis>, 1601 (oil on canvas). <phrase role="source">Santa Maria del Popolo, Rome, Italy/
Bridgeman Art Library.</phrase></para>
</caption>

Or they may be presented in a different font, size or location compared with the rest of the caption
content, in which case they MUST be within a distinct para:13

<caption xml:id="ij86f">
<para xml:id="fc86k">In 2002, a replica of the “Leave It to Beaver house” is again seen on Colonial Street,
this time cast as part of a middle-class African-American neighborhood, “Nellyville, U.S.A.,” in the music
video for Nelly’s single, “Dilemma.” Featuring R&amp;B singer Kelly Rowland as new to the established,

12
Tested in Schematron: figure-title-length
13
Tested in Schematron: source-in-caption

154
 Figures and images

vibrant suburban neighborhood, she and her mother (Patti Labelle) move into the Cleaver’s old home across
the street from rapper-resident Nelly.</para>
<para xml:id="ygtf6" role="source">© 2002, Universal Records</para>
</caption>

21.4. Image placement

Block images (and tables and sidebars) MUST NOT occur within a para.14 They may occasionally
appear in such a location within the flow of text in a book, but this is solely due to the print layout
around page breaks. In such circumstances, the figure or informalfigure MUST be placed after
the para in which it falls (though see some exceptions below), and an anchor element used to mark
the location of the figure in the print edition. Note that the figure or informalfigure MUST also
include a @xlink:href pointing back to the anchor:15

<para xml:id="b-9780857854117-0000424">Important to a chronicle of New York fashion are the couture

designs of Charles James. While James is perhaps best remembered for his extravagant eveningwear
(his so-called Clover dress of 1953 is composed of thirty pattern pieces and layers of fabric (<link
linkend="b-9780857854117-0002132" role="bib">Martin 1997</link>: 53)), he was also capable of stunning
simplicity. The Museum does have examples of James’s elaborate eveningwear but the garment representing
him in the gallery is a late 1930s coat, which is the model of restraint (<link linkend="b-9780857854117-
figure-5.1" role="figure">Figure 5.1</link>). The Museum acquired the coat in 1978. It came with two
Charles James evening bodices, one James evening dress and several accessories from Miss Philippa Barnes
<anchor role="objectPointer" xml:id="b-9780857854117-d1e3212"/>
<?page value="73"?>
of West Malling, Kent and formed part of the Beaton collection. Regrettably there exists no information
about the donor in the papers relating to the acquisition. I chose the coat for expedience: it was one of
the few James pieces that needed no conservation in order to be displayed.</para>
<informalfigure label="5.1" xml:id="b-9780857854117-figure-5.1" xlink:href="b-9780857854117-d1e3212"
xlink:role="objectPointer">
<mediaobject xml:id="b-9780857854117-0000425">
<imageobject xml:id="b-9780857854117-0000426">
<imagedata format="image/jpeg" outputformat="web" fileref="images/image009.jpg"/>
</imageobject>
</mediaobject>
<caption xml:id="b-9780857854117-0000427">

If an image really must be placed in a para, it MUST be in an inlinemediaobject.

Note also that block images MUST NOT be between a para and an attribution in a
blockquote.16

21.5. Image alt text

Important
This section is now DEPRECATED from Schematron version 7. The instructions for alt
text given in Chapter 34, Accessibility should be followed instead.

Note the difference between the caption (the default behaviour of which is to appear below the
image) and textobject/phrase, which is not used in print but is the OPTIONAL means of
creating HTML alt text.

<figure label="A" xml:id="b-figa">

<info>
<title>Leonardo DiCaprio in Baz Luhrman's film version of <emphasis role="italic">Romeo and Juliet</
emphasis></title>
</info>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="images/romeo_juliet.jpg"/>

14
Tested in Schematron: object-in-para
15
Tested in Schematron: anchor-role, anchor-id, object-role, object-id, object-target-id, impermissible-
href-location
16
Tested in Schematron: object-in-blockquote

155
 Figures and images

</imageobject>
<textobject>
<phrase>Picture of Leonardo DiCaprio kissing Claire Danes</phrase>
</textobject>
<caption>
<para>This scene is at the end of the film</para>
</caption>
</mediaobject>
</figure>

The informalfigure example shows that @valign can be used, and it can also have a
textobject/phrase for alt text, or a caption. This example also shows how long descriptions
for accessibility can be added to mediaobject s, also using the textobject, but NOT within a
phrase.[Practically it is unlikely that we will be able to support this editorially]

<informalfigure xml:id="b-fig1">
<mediaobject>
<imageobject>
<imagedata align="left" valign="bottom" fileref="images/virtuousCircle.png"/>
</imageobject>
<textobject>
<phrase>Diagram illustrating film programming connections</phrase>
</textobject>
<textobject>
<formalpara>
<info>
<title>The virtuous circle in film programming</title>
</info>
<para>The diagram shows that, as film programming improves, it enhances audience development, which can
in turn promote community engagement and participation. That, in turn, can help support film education
activities, which feeds into the programming.</para>
</formalpara>
</textobject>
<caption>
<para>Film programming, audience development, community engagement, and film education are all connected.</
para>
</caption>
</mediaobject>
</informalfigure>

21.6. Plate sections

Plate sections MUST be represented in the data and MUST be placed at the point at which they occur
in the printed book. They MUST be enclosed within a sidebar[@role=plateSection], which
contains all the images within the plates within figure or informalfigure, as appropriate.

<para xml:id="s3">Schelling's connections to psychoanalysis are conceptually clear. He developed a theory

of the unconscious as a set of pre-personal drives that matches the contours of Freud's account. <sidebar
role="plateSection" xml:id="sb-1"><informalfigure xml:id="sb-3"><mediaobject xml:id="sb-4"><imageobject
xml:id="sb-5"><imagedata fileref="images/sb-fig1.jpg" format="image/jpeg"/></imageobject><caption
xml:id="sb-6"><para xml:id="sb-7">The Tory candidate addresses an election meeting in Bethnal Green, June
1945</para></caption></mediaobject></informalfigure></sidebar><?page value="23"?>Canonical works like
Hartmann's groundbreaking <emphasis role="italic">Philosophy of the Unconscious</emphasis> acknowledge the
centrality of Schelling's contribution here.</para>

See also Chapter 26, Sidebars

156
Chapter 22. Other media content
22.1. Video
22.1.1. Embedded video
Where the expected rendering behaviour is that a video be displayed embedded (e.g. online, in a
player directly embedded in the current web page) this markup MUST be used:

<mediaobject xml:id='b-9781350970809-a123'>
<videoobject xlink:show="embed">
<videodata fileref="123456789" role="brightcoveID" classid="somePlayerID"
xml:id="b-9781350970809-b456"/>
</videoobject>
</mediaobject>

where

• @xlink:show indicates the embedding behaviour expected from the renderer;

• @fileref contains an ID within a given ID space (for example, a media store);

• @role identifies the ID space referred to;

• @classid optionally specifies the player ID; a default player should be used if absent.

22.1.2. Reference by ID
For video assets held by Bloomsbury (we will instruct where this is the case), include the asset ID in
the xlink:href of a phrase[@role='videoID'], as follows:1

<phrase role="videoID"
xlink:role="http://docbook.org/xlink/role/olink"
xlink:href="5987882506001">Jean Paul Gaultier SS 1988 (B0370)</phrase>

Here, the rendering expectation is that a URL for the asset will either be constructed on export from
the CMS where the XML resides, for use by the platform, or directly by the target platform itself.

22.2. Audio
Audio content may also be included using the reference by ID mechanism described in Section 22.1.2,
“Reference by ID”.

22.2.1. Reference by ID
In the case of audio content assets held by Bloomsbury (we will instruct where this is the case),
phrase[@role='audioID'] should be used to include the asset ID:2

<phrase role="audioID"
xlink:role="http://docbook.org/xlink/role/olink"
xlink:href="4595718792345">The Sound of Silence</phrase>

As for video assets, the rendering expectation is that a URL for the asset will either be constructed on
export from the CMS for use by the platform, or directly by the target platform itself.
1
Tested in Schematron: video-rule-1
2
Tested in Schematron: audio-rule-1

157
Chapter 23. Equations
23.1. Equation basics
The DocBook equation container elements are:1

Element Usage
Equation Displayed equations with titles
informalequation Displayed equations without titles
inlineequation Inline equations

They can all contain one of:

Item Usage
mathphrase For simple equations that can be represented
with text, numbers, symbols, superscripts and
subscripts
mml: MathML markup for more complex equations
Media objects Graphics of the equation, often in multiple
formats for different outputs

As with other elements for which formal and informal versions are available, equations can be
referenced by link s, and the auto-generated numbering scheme can be overridden using @label.

23.2. Simple equations

If mathphrase is adequate for displaying the equation, then only that need be provided:

<para xml:id="id0211">Here are a variety of equation options. First a mathphrase within an inlineequation:
<inlineequation xml:id="eq1"><mathphrase xml:id="eq2">E = mc<superscript>2</superscript></mathphrase></
inlineequation>, and the text can just follow on.</para>

And mathphrase can be used for display equations, as well as inline:

<para xml:id="eq3">Or, we can have an informal equation, also with mathphrase:</para>

<informalequation xml:id="eq4">

<mathphrase xml:id="eq5">x<superscript>n</superscript> + y<superscript>n</superscript> ≠ z<superscript>n</

superscript> # n ≠ 2</mathphrase>
</informalequation>

23.3. More complex equations

For more complex equations which cannot be rendered with mathphrase, multiple options MUST
be provided,2 and must include all of the following:3

• MathML

• Image for web rendering

1
Presence reported in Schematron: eqn-present
2
Tested in Schematron: missing-eqn-sibling-1, missing-eqn-sibling-2
3
Tested in Schematron: multi-format-eqns

158
 Equations

• Image for print rendering

[Need to specify image specification, including baseline etc, font etc) SVG?]

Two equation containers MUST be provided: one for processing by a MathML tool
(@condition=mathml); and the other for an image renderer (@condition=non-mathml),4
UNLESS the title bears a metadata flag indicating that it targets the Bloomsbury Collections platform
(see Section 7.5.11, “Other biblioids”), in which case only non-MathML equations are required.5 Only
one of these elements MUST be used in the output processing. These values of @condition are only
permissible on the following elements:6

• equation

• informalequation

• inlineequation

In addition, the images MUST contain versions for both print and web usage:

<informalequation xml:id="eq13" condition="mathml">

<mml:math xmlns="http://www.w3.org/1998/Math/MathML" display="block">
<mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mo>&#x222B;</mml:mo>
<mml:mrow>
<mml:mi>D</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mo>&#x2207;&#x22C5;</mml:mo>
<mml:mi>F</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mi>d</mml:mi>
<mml:mrow>
<mml:mi>V</mml:mi>

</mml:mrow>
</mml:mrow>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mo>&#x222B;</mml:mo>
<mml:mrow>
<mml:mo>&#x2202;</mml:mo>
<mml:mi>D</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mtext>&#x2009;</mml:mtext>
<mml:mi>F</mml:mi>
<mml:mo>&#x22C5;</mml:mo>
<mml:mi>n</mml:mi>
</mml:mrow>
<mml:mi>d</mml:mi>
<mml:mi>S</mml:mi>
</mml:mrow>
</mml:mrow>
</mml:math>
</informalequation>
<informalequation xml:id="eq13a" condition="non-mathml">
<mediaobject xml:id="eq14">
<imageobject xml:id="eq15">
<imagedata xml:id="eq16" outputformat="web" fileref="images/equation1.png" format="image/png"
align="center"/>
</imageobject>
<imageobject xml:id="eq15a">
<imagedata xml:id="eq16q" outputformat="print" fileref="images/equation1.tiff" format="image/tiff"
align="center"/>

4
Tested in Schematron: eqn-condition-required
5
Tested in Schematron: no-mathml-on-BC-platform
6
Tested in Schematron: math-condition-attribute

159
 Equations

</imageobject>
</mediaobject>
</informalequation>

The same approach MUST also be adopted for inline complex equations, and note that mml:math
within an inlineequation MUST have @display=’inline’.7 (In practice most inline equations
should be able to be rendered within mathphrase):

<para xml:id="eq17">Next, we can have an inline equation <inlineequation condition="mathml" xml:id="eq21">

<mml:math display="inline"> <mml:mrow>
<mml:mi>cos</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mi>&#x3B8;</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>&#x3C6;</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mo>=</mml:mo>
<mml:mi>cos</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mi>&#x3B8;</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mi>cos</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>

<mml:mi>&#x3C6;</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>sin</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mi>&#x3B8;</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mi>sin</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mi>&#x3C6;</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow></mml:math></inlineequation>
<inlineequation xml:id="iee9" condition="non-mathml">
<inlinemediaobject xml:id="eq18">
<imageobject xml:id="eq19">
<imagedata outputformat="web" fileref="images/equation2.png" format="image/png"/>
</imageobject>
<imageobject xml:id="eq19a">
<imagedata outputformat="print" fileref="images/equation2.tiff" format="image/tiff"/>
</imageobject>
</inlinemediaobject></inlineequation> with text following on, and shows how hard it will be to get the
baseline correct so it sits neatly in the text.</para>

See also Section 14.6, “Conditional processing with @condition”

Implementation note: Conditional processing of equations is not supported in DocBook XSL

23.4. equations
In some cases, equations in LaTeX are also required.
7
Tested in Schematron: inline-math-attribute

160
 Equations

Important
Bloomsbury will advise if this is the case.

Where biblioid[@role='otherclass'][@otherclass='latexEquations'] is set to 1

(see Section 7.5.11, “Other biblioids”), element mathphrase with a role value of latex MUST be
supplied,8 in addition to the other required non-MathML formats, e.g.

<informalequation condition='non-mathml'><mathphrase role='latex'>...</mathphrase></informalequation>

8
Tested in Schematron mathphrase-latex

161
Chapter 24. Blockquotes, epigraphs,
poetry and drama
This section describes the various block extracts and related elements.

Note that quote (for inline quotations) is NOT REQUIRED in this instance of DocBook.

Implementation note: Processing and display of the DocBook Publishers poetry and drama
components is not supported in DocBook XSL (though blockquote and epigraphs are)

24.1. Blockquotes
Whereas epigraphs are quotations at the beginning of a chapter or section (see next section), a
blockquote is any other displayed text set apart from the main flow, usually indented relative to
the main text. If a blockquote occurs as the first element in a chunk or section it should almost
certainly be an epigraph.1

Typically, a blockquote will contain one or more paragraphs:

<blockquote xml:id="sb6"><para xml:id="sb7">We are the leading partner in a Government project which
enables students to learn through hands-on experience. Through practise and primary engagement with
research, students build and improve their critical skills...</para></blockquote>

However, a blockquote may also contain poetry or drama, and may also include an attribution:

<blockquote xml:id="gk5a">
<attribution>Archilochus fr. 48.5-7 W</attribution>
<poetry xml:id="gk6">
<line xml:id="gk7">τροφὸ.ς κατ.[&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; ἐσμυριχμένας κόμην</line>
<line xml:id="gk8">καὶ στῆθος, ὡς ἂν καὶ γέρων ἠράσσατο.</line>
<line xml:id="gk9">ὦ Γλαῦκ.[</line>
</poetry>
</blockquote>

Note the use of the attribution element rather than para[@role=right].2

24.2. Epigraphs
Ref: §1.12, §1.86, §1.87, §1.88

NOTE: This differs markedly from the previous instructions

Chunks MAY begin with one or more epigraph (a phrase, quotation, or poem that is set at
the beginning of a document or component, usually inset or typographically distinct from the
surrounding text).3

Such content MUST be marked up within an epigraph element (NOT a blockquote, which is for
quoted text within the body of the content), and will be the first element(s) within the content chunk.
Note also that the DocBook schema REQUIRES that the attribution is the first element within the
epigraph, irrespective of where it appears in the print edition. However, the DocBook stylesheets
include a parameter to allow for the placement of the attribution after the epigraph text, if required:

<chapter xml:id="b-chapter-001">

1
Tested in Schematron: possible-epigraph
2
Tested in Schematron: possible-attribution
3
Tested in Schematron: para-before-epigraph

162
 Blockquotes, epigraphs,
poetry and drama

<info xml:id="b-0000109">
<title xml:id="b-0000110">Introduction</title>
<subtitle xml:id="b-0000111">Globalizing cricket</subtitle>
</info>
<epigraph>
<attribution>Sir Laurence Olivier</attribution>
<para><emphasis role="italic">I have often thought of how much better a life I would have had, what a
better man I would have been, how much healthier an existence I would have led, had I been a cricketer.</
emphasis></para>
</epigraph>
<epigraph>
<attribution>Robert Mugabe</attribution>

<para><emphasis role="italic">Cricket civilizes people and creates good gentlemen. I want everyone to play
cricket in Zimbabwe; I want ours to be a nation of gentlemen.</emphasis>
</para>
</epigraph>
<epigraph>
<attribution>Bill Bryson</attribution>
<para><emphasis role="italic">It is not true that the English invented cricket as a way of making all other
human endeavours look interesting and lively; that was merely an unintended side effect. I don't wish to
denigrate a sport that is enjoyed by millions, some of them awake and facing the right way, but it is an
odd game.</emphasis>
</para>
</epigraph>
<para>Cricket polarizes opinion. To some it holds quasi-religious status; to others it is a point of
fun. Despite their obvious devotion, some (particularly English) cricket spectators are remarkably
impassive. Inextricably linked to what defines Englishness, cricket is also venerated by those who have
publicly and vigorously fought against imperial oppression. It has the aura of a genteel game which builds
character, yet it is amongst the most injurious sports played in the United Kingdom (<link role="bib"
linkend="b-0003848">Smith 2012</link>)....</para>

The attribution MAY take @role (left | right | center), if required. Note the use of the
attribution element rather than para[@role=right].4

24.3. Poetry
Ref: §1.89, §1.90

Poetry in the text may occur within a blockquote or epigraph, or neither. A poem must be placed
within a blockquote or epigraph if it is so quoted and (usually) inset relative to the usual flow
of text.5 It will certainly require a parent blockquote or epigraph if it has an attribution.6

24.3.1. Simple poem

A simple poem may also REQUIRE the use of non-breaking spaces (“&#160;”) to create the correct
indentation for each line:

<poetry xml:id="po5">
<line xml:id="po6">The languages, especially the dead,</line>
<line xml:id="po7">&#160;&#160;&#160;The sciences, and most of all the abstruse,</line>
<line xml:id="po8">The arts, at least all such as could be said</line>
<line xml:id="po9">&#160;&#160;&#160;To be the most remote from common use,</line>
<line xml:id="po10">In all these he was much and deeply read:</line>
<line xml:id="po11">&#160;&#160;&#160;But not a page of anything that’s loose,</line>
<line xml:id="po12">Or hints continuation of the species,</line>
<line xml:id="po13">Was ever suffer’d, lest he should grow vicious.</line>
</poetry>

Note also that content in brackets at the end of the last line of a poem is almost certainly an attribution
and MUST be marked up accordingly,7 ie the following is WRONG:

<poetry xml:id="b-9781408174654-0000456">
<linegroup xml:id="b-9781408174654-0000457">
<line xml:id="b-9781408174654-0000458">the midnight bell</line>
<line xml:id="b-9781408174654-0000459">Did, with his iron tongue and brazen mouth,</line>

4
Tested in Schematron: possible-attribution
5
Tested in Schematron: drama-poetry-parent
6
Presence reported in Schematron: poetry-drama-present
7
Tested in Schematron: line-attribution

163
 Blockquotes, epigraphs,
poetry and drama

<line xml:id="b-9781408174654-0000460">Sound one into the drowsy race of night.</line>

<line xml:id="b-9781408174654-0000461">(3.2.47-9)</line>
</linegroup>
</poetry>

and MUST be encoded as:

<blockquote xml:id="b-9781408174654-0000454">
<attribution xml:id="b-9781408174654-0000455">(3.2.47-9)</attribution>
<poetry xml:id="b-9781408174654-0000456">
<linegroup xml:id="b-9781408174654-0000457">
<line xml:id="b-9781408174654-0000458">the midnight bell</line>
<line xml:id="b-9781408174654-0000459">Did, with his iron tongue and brazen mouth,</line>
<line xml:id="b-9781408174654-0000460">Sound one into the drowsy race of night.</line>
</linegroup>
</poetry>
</blockquote>

24.3.2. Poem with verses

Where there are verses, they MUST be grouped using linegroup:

<poetry xml:id="po17">
<linegroup xml:id="po18">
<line xml:id="po19">Juan was taught from out the best edition,</line>
<line xml:id="po20">Expurgated by learned men, who place</line>
<line xml:id="po21">Judiciously, from out the schoolboy’s vision,</line>
<line xml:id="po22">The grosser parts; but, fearful to deface</line>
<line xml:id="po23">Too much their modest bard by this omission,</line>
<line xml:id="po24">And pitying sore his mutilated case,</line>
<line xml:id="po25">They only add them all in an appendix,</line>
<line xml:id="po26">Which saves, in fact, the trouble of an index;</line>
</linegroup>
<linegroup xml:id="po27">
<line xml:id="po28">For there we have them all &#x2018;at one fell swoop,&#x2019;</line>
<line xml:id="po29">Instead of being scatter’d through the pages;</line>
<line xml:id="po30">They stand forth marshall’d in a handsome troop,</line>
<line xml:id="po31">To meet the ingenuous youth of future ages,</line>
<line xml:id="po32">Till some less rigid editor shall stoop</line>
<line xml:id="po33">To call them back into their separate cages,</line>
<line xml:id="po34">Instead of standing staring all together,</line>
<line xml:id="po35">Like garden gods – and not so decent either.</line>
</linegroup>
</poetry>

24.3.3. Line formatting

If there are centred devices, line[@role=center] MUST be used (note that non-breaking space
characters MUST be used to separate multiple asterisks, else the downstream processing will
compress all normal space characters to a single one as part of its white space handling):

<poetry xml:id="po37">
<linegroup xml:id="po38">
<line xml:id="po39">He sat in a wheeled chair, waiting for dark,</line>
<line xml:id="po40">And shivered in his ghastly suit of grey,</line>
<line xml:id="po41">Legless, sewn short at elbow. Through the park</line>
<line xml:id="po42">Voices of boys rang saddening like a hymn,</line>
<line xml:id="po43">Voices of play and pleasure after day,</line>
<line xml:id="po44">Till gathering sleep had mothered them from him.</line>
<line role="center" xml:id="b-9781474208482-0007719">*&#160;&#160;&#160;&#160;*&#160;&#160;&#160;&#160;*</
line>
<line xml:id="po46">About this time Town used to swing so gay</line>
<line xml:id="po47">When glow-lamps budded in the light-blue trees</line>
<line xml:id="po48">And girls glanced lovelier as the air grew dim,</line>
<line xml:id="po49">— In the old times, before he threw away his knees.</line>
<line xml:id="po50">Now he will never feel again how slim</line>
<line xml:id="po51">Girls' waists are, or how warm their subtle hands,</line>
<line xml:id="po52">All of them touch him like some queer disease.</line>
</linegroup></poetry>

164
 Blockquotes, epigraphs,
poetry and drama

24.3.4. More complex poems, and line numbers

The DocBook model does not provide a full-featured semantic model for poetry (or drama),
so more complex works may require slightly creative use of the linegroup and line
elements to achieve the appropriate formatting. In the following example linegroup/
line[@role=center] is used for all canto/stanza divisions, and marginal line numbers are
achieved with a footnote[@role=margin1]:

<poetry xml:id="po54">
<line role="center" xml:id="po55"><emphasis role="italic">To the happy memory of five Franciscan Nuns
exiles by the Falk Laws drowned between midnight and morning of Dec. 7th. 1875</emphasis></line>
<linegroup xml:id="po56">
<line role="center" xml:id="po57">PART THE FIRST</line>
</linegroup>
<linegroup xml:id="po58">
<line role="center" xml:id="po59">1</line>
<line
xml:id="po60">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;THOU
mastering me</line>
<line xml:id="po61">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;God! giver of
breath and bread;</line>
<line xml:id="po62">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;World’s strand, sway of the sea;</line>
<line xml:id="po63">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Lord of living
and dead;</line>
<line xml:id="po64">&#160;&#160;&#160;&#160;Thou hast bound bones and veins in me, fastened me flesh,
<footnote role="margin1" xml:id="po65"><para xml:id="po66">5</para></footnote></line>
<line xml:id="po67">&#160;&#160;&#160;&#160;And after it almost unmade, what with dread,</line>
<line xml:id="po68">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Thy doing: and dost thou touch me
afresh?</line>
<line xml:id="po69">Over again I feel thy finger and find thee.</line></linegroup>
<linegroup xml:id="po70">
<line role="center" xml:id="po71">2</line>
<line
xml:id="po72">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;I
did say yes</line>

<line xml:id="po73">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;O at lightning

and lashed rod;<footnote role="margin1" xml:id="po74"><para xml:id="po75">10</para></footnote></line>
<line xml:id="po76">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Thou heardst me truer than tongue
confess</line>
<line xml:id="po77">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Thy terror, O
Christ, O God;</line>
<line xml:id="po78">&#160;&#160;&#160;&#160;Thou knowest the walls, altar and hour and night:</line>
<line xml:id="po79">&#160;&#160;&#160;&#160;The swoon of a heart that the sweep and the hurl of thee trod</
line>
<line xml:id="po80">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Hard down with a horror of
height:<footnote role="margin1" xml:id="po81"><para xml:id="po82">15</para></footnote></line>
<line xml:id="po83">And the midriff astrain with leaning of, laced with fire of stress.</line>
</linegroup></poetry>

which would render as follows:

165
 Blockquotes, epigraphs,
poetry and drama

24.3.5. Poem with epigraph

In this instance, the poem has a title, as well as a quoted text at its start (epigraph):

<poetry xml:id="po85">
<info xml:id="po86"><title xml:id="po87">The Show</title></info>

<epigraph xml:id="po88"><attribution>W.B. YEATS</attribution>

<linegroup xml:id="po89">
<line xml:id="po90">&#x201C;We have fallen in the dreams the ever-living</line>
<line xml:id="po91">Breathe on the tarnished mirror of the world,</line>
<line xml:id="po92">And then smooth out with ivory hands and sigh&#x201D;.</line></linegroup>
</epigraph>
<linegroup xml:id="po93">
<line xml:id="po94">My soul looked down from a vague height, with Death,</line>
<line xml:id="po95">As unremembering how I rose or why,</line>
<line xml:id="po96">And saw a sad land, weak with sweats of dearth,</line>
<line xml:id="po97">Grey, cratered like the moon with hollow woe,</line>
<line xml:id="po98">And pitted with great pocks and scabs of plagues.</line>
<line xml:id="po99">Across its beard, that horror of harsh wire,</line>
<line xml:id="po100">There moved thin caterpillars, slowly uncoiled.</line>
<line xml:id="po101">It seemed they pushed themselves to be as plugs</line>
<line xml:id="po102">Of ditches, where they writhed and shrivelled, killed.</line>
</linegroup></poetry>

24.4. Drama
The text of dramatic works in the text may occur within a blockquote or epigraph, or neither. A
dramatic work must be placed within a blockquote or epigraph if it is so quoted and (usually)
inset relative to the usual flow of text.8
8
Tested in Schematron: drama-poetry-parent. Presence reported in Schematron: poetry-drama-present

166
 Blockquotes, epigraphs,
poetry and drama

The dialogue element MUST be contained within a drama.

24.4.1. Simple dramatic text

In this instance the format style is to have the speaker’s name on the line before the text of the speech
(@role=line-below-speaker), and there is an inline stage direction:9

<drama xml:id="dr-019">
<dialogue xml:id="dr-020" role="line-below-speaker">
<linegroup xml:id="dr-021"><speaker xml:id="dr-022">BEATRICE</speaker>
<line xml:id="dr-023">Oh, there&#x2019;s one above me, sir. [<emphasis role="italic">Aside</emphasis>] For
five days past</line>
<line xml:id="dr-024">To be recall'd! Sure, mine eyes were mistaken;</line>
<line xml:id="dr-025">This was the man was meant me. That he should come</line>
<line xml:id="dr-026">So near his time, and miss it!</line>
</linegroup>
</dialogue>
</drama>

24.4.2. Line following speaker in dramatic text

In contrast with the preceding example, in this book the required style for layout is to have the speech
text following straight after the speaker name, and there is also a stage direction on its own line:

<drama xml:id="dr-005">
<dialogue xml:id="dr-006" role="line-follows-speaker">
<linegroup xml:id="dr-007"><speaker xml:id="dr-008">THERIDAMAS.</speaker> <line xml:id="dr-009">Then now,
my lord, I humbly take my leave.</line></linegroup>
<linegroup xml:id="dr-010"><speaker xml:id="dr-011">MYCETES.</speaker> <line xml:id="dr-012">Theridamas,
farewell ten thousand times.</line>
<line xml:id="dr-013"><emphasis role='italic'>[Exit THERIDAMAS.]</emphasis></line>
<line xml:id="dr-014">Ah, Menaphon, why stay'st thou thus behind,</line>
<line xml:id="dr-015">When other men press forward for renown?</line>
<line xml:id="dr-016">Go, Menaphon, go into Scythia,</line>
<line xml:id="dr-017">And foot by foot follow Theridamas.</line>
</linegroup></dialogue></drama>

24.4.3. Split lines

Where the formatting of the lines follows on from the previous line (to preserve the metre of the
verse):

Katherina

Mov'd, in good time! Let him that mov'd you hither

Remove you hence. I knew you at the first

You were a movable.

Petruchio

Why, what's a movable?

Katherina

A joint-Stool.

Petruchio

Thou hast hit it. Come, sit on me.

9
Note that phrase role='stageDirection' is deprecated for drama excerpts (by Schematron
stageDirectionDeprecated), but see Section 24.4.5, “Screenplay excerpts” and note, for allowed usage.

167
 Blockquotes, epigraphs,
poetry and drama

These MUST be indicated using an appropriate @role on line:10

<dialogue xml:id="b-9000394">
<linegroup xml:id="b-9000598">
<speaker xml:id="b-9002870">Katherina</speaker>
<line xml:id="b-9001167">Mov'd, in good time! Let him
that mov'd you hither</line>
<line xml:id="b-9001168">Remove you hence. I knew you at
the first</line>
<line role="partInitial" xml:id="b-9001169">You were a
movable.</line>
</linegroup>
<linegroup xml:id="b-9000599">
<speaker xml:id="b-9002871">Petruchio</speaker>
<line role="partFinal" xml:id="b-9001170">Why, what's a
movable?</line>
</linegroup>
<linegroup xml:id="b-9000600">
<speaker xml:id="b-9002872">Katherina</speaker>
<line role="partInitial" xml:id="b-9001171">A
joint-Stool.</line>
</linegroup>
<linegroup xml:id="b-9000601">
<speaker xml:id="b-9002873">Petruchio</speaker>
<line role="partFinal" xml:id="b-9001172">Thou hast hit
it. Come, sit on me.</line>
</linegroup>
</dialogue>

Permissible values of @role are:

Value Usage
partInitial The first line in any split line group
partMedial Any intermediate line(s) in a split line group
partFinal The final line in any split line group

24.4.4. More complex dramatic work

In this example there are marginal line numbers and a song:

<drama xml:id="dr-029">
<dialogue xml:id="dr-039">
<linegroup xml:id="dr-031">
<speaker xml:id="dr-031a"><person><personname><emphasis role="smallcaps">livia</emphasis></personname></
person></speaker><line xml:id="dr-032">[<emphasis role="italic">Aside</emphasis>.]: I am as dumb to any
language now</line>
<line xml:id="dr-033">But love's, as one that never learn'd to speak.</line>
<line xml:id="dr-034">I am not yet so old, but he may think of me.</line>
<line xml:id="dr-035">My own fault, I have been idle a long time;</line>
<line xml:id="dr-036"><footnote role="margin1" xml:id="dr-036a"><para xml:id="dr-036b">140</para></
footnote>But I'll begin the week, and paint to-morrow,</line>
<line xml:id="dr-037">So follow my true labour day by day.</line>
<line xml:id="dr-038">I never thriv'd so well as when I us'd it.</line>
<poetry xml:id="dr-039a">
<info xml:id="dr-040"><title xml:id="dr-041"><emphasis role="smallcaps">the song</emphasis> [<emphasis
role="italic">sung by</emphasis> <emphasis role="smallcaps">isabella</emphasis>]</title></info>
<line xml:id="dr-042">What harder chance can fall to woman,</line>
<line xml:id="dr-043">Who was born to cleave to some man, </line>
<line xml:id="dr-044">Than to bestow her time, youth, beauty,</line>
<line xml:id="dr-045">Life's observance, honour, duty,</line>
<line xml:id="dr-046">On a thing for no use good,</line>
<line xml:id="dr-047">But to make physic work, or blood</line>
<line xml:id="dr-048">Force fresh in an old lady's cheek?</line>
<line xml:id="dr-049"><footnote role="margin1" xml:id="dr-036d"><para xml:id="dr-036c">150</para></
footnote>She that would be</line>
<line xml:id="dr-050">Mother of fools, let her compound with me.</line>
</poetry>
</linegroup>
<linegroup xml:id="dr-051">

10
Tested in Schematron: part-initial, part-medial, part-final

168
 Blockquotes, epigraphs,
poetry and drama

<speaker xml:id="dr-052"><person><personname><emphasis role="smallcaps">ward</emphasis></personname></

person></speaker> <line xml:id="dr-053">[<emphasis role="italic">While she sings</emphasis>.]: Here's a
tune indeed ; pish ! I had rather hear one</line>
<line xml:id="dr-054">ballad sung i' th' nose now, of the lamentable drowning of fat sheep and</line>
<line xml:id="dr-055">oxen, than all these simpering tunes play'd upon cat's guts, and sung by</line>
<line xml:id="dr-056">little kitlings.</line>
</linegroup>
</dialogue>
</drama>

24.4.5. Screenplay excerpts

Occasionally, titles (especially monographs on cinema-related topics) may include short excerpts of
dialogue from screenplays. These MUST be captured as drama, with a role of screenplay. In the
example below, drama contains two dialogue elements separated by an informalfigure. The
first dialogue has a title.

<blockquote xml:id="b-9780571343713-1002297">
<drama xml:id="b-9780571343713-1002298" role="screenplay">
<dialogue role="line-below-speaker" xml:id="b-9780571343713-0002317">
<info xml:id="b-9780571343713-0002314a">
<title xml:id="b-9780571343713-0002314">3. MEDIUM SHOT – GIRL</title>
</info>
<linegroup xml:id="b-9780571343713-0002318">
<line xml:id="b-9780571343713-0002319" role="stageDirection">The <emphasis role="smallcaps">girl</
emphasis>, taking initiative at once, is already snatching up his trousers that are on a chair, picking up
his watch from the table beside the bed.</line>
</linegroup>
</dialogue>
<informalfigure xml:id="b-9780571343713-1002347">
<mediaobject xml:id="b-9780571343713-1002348">
<imageobject xml:id="b-9780571343713-1002349">
<imagedata fileref="images/sn4.jpg" format="image/jpeg"/>
</imageobject>
</mediaobject>
</informalfigure>
<dialogue role="line-below-speaker" xml:id="b-9780571343713-1002317">
<linegroup xml:id="b-9780571343713-0002320">
<speaker xml:id="b-9780571343713-0002321">Boy’s voice</speaker>
<line xml:id="b-9780571343713-0002322" role="stageDirection">(<emphasis role="italic">overscene,
continuing</emphasis>)</line>
<line xml:id="b-9780571343713-0002323">I thought it was this afternoon.</line>
<line xml:id="b-9780571343713-0002324">Camera pans back with the <emphasis role="smallcaps">girl</emphasis>
as she thrusts the trousers into the <emphasis role="smallcaps">boy</emphasis>’s hands and gives him his
watch.</line>
</linegroup>
<linegroup xml:id="b-9780571343713-0002325">
<speaker xml:id="b-9780571343713-0002326">GIRL</speaker>
<line xml:id="b-9780571343713-0002327">No. I told you I changed it. It’s at ten-fifteen. We’ve got twenty
minutes.</line>
</linegroup>
</dialogue>
</drama>
</blockquote>

Note
Note the use of line role='stageDirection' here to capture the stage direction.

24.5. Incorrect block markup

Where there are multiple lines within a quote of some sort, it is WRONG to mark them all up as
separate paras as in the following example. This should have used a linegroup.11 Note also the
incorrect URL markup in the footnote:

<blockquote xml:id="b-0002538">
<para xml:id="b-0002539">Cricket</para>
<para xml:id="b-0002540">as explained to a foreign visitor</para>

11
Tested in Schematron: possible-poem

169
 Blockquotes, epigraphs,
poetry and drama

<para xml:id="b-0002541">There are two sides</para>

<para xml:id="b-0002542">one out in the field and one in.</para>
<para xml:id="b-0002543">Each player that's in the side that's</para>
<para xml:id="b-0002544">in goes out and when he's out he</para>
<para xml:id="b-0002545">comes in and the next player</para>
<para xml:id="b-0002546">goes in until he's out</para>
<para xml:id="b-0002547">When they are all out the side</para>
<para xml:id="b-0002548">that's out comes in and the side that's</para>
<para xml:id="b-0002549">been in goes out and tries to get those coming in out</para>
<para xml:id="b-0002550">Sometimes you get players still in and not out.</para>
<para xml:id="b-0002551">When both side have been</para>
<para xml:id="b-0002552">in and out including the not outs</para>
<para xml:id="b-0002553">That's the end of the game</para>
<para xml:id="b-0002554">Howzat!<footnote role="end-bk-note" xml:id="b-0002555"><para
xml:id="b-0002556">http://www.shopatlords.com/?page=shop&amp;pid=3071&amp;cid=149</para></footnote></para>
</blockquote>

170
Chapter 25. Interviews, questions/
answers
Occasionally, a book may include text which takes the form of an interview, where paragraphs are
preceded by the name of the person speaking (for instance). For such content, the dialogue element
MUST NOT be used. Instead, these MUST utilise the specific DocBook Q&A elements, with the
label to contain the name of the speaker:

<qandaset xml:id="qa1a">
<qandaentry xml:id="qa1b">
<question>
<label><emphasis role="italic">Interviewers</emphasis>:</label>
<para xml:id="qa1">During the last ten years, following the controversial popularity of <emphasis
role="italic">Sopyonje</emphasis>, you emerged as the most prominent film director in Korea. How has this
recognition affected your sensibility as a filmmaker?</para>
</question>
<answer>
<label><emphasis role="italic">Im Kwon-Taek</emphasis>:</label>
<para xml:id="qa2">Since the 1980s, I have been considering my films with these matters in mind...</para>
</answer>
</qandaentry>
</qandaset>

For further examples and behaviour of the stylesheets, see http://www.sagehill.net/

docbookxsl/QandASetsHTML.html

Implementation note: Default DocBook behaviour is to add a ToC for the Q&As; this must be
suppressed in the XSLT. Automatic styling for label must also be turned off (see http://
www.sagehill.net/docbookxsl/QandAtoc.html).

171
Chapter 26. Sidebars
The DocBook spec defines a sidebar as “A portion of a document that is isolated from the main
narrative flow.” This may be a block of text in a box, or similar feature.

In addition, sidebars MAY be used as a container for plate sections. See Section 21.6, “Plate sections”

Other content that is like a sidebar are procedures, which are also typically set apart from the main
flow of a text and probably typographically distinct. For such features, see Chapter 27, Steps and
procedures.

26.1. Simple sidebars

The following page provides an example of regular sidebars:

This is a relatively complex-looking layout, though can easily be modelled as follows:

<chapter xml:id="si1" label="3">

<info xml:id="si2">
<title xml:id="si3">Theory in focus</title>
<pagenums>9–10</pagenums>
<biblioid class="doi">10.5040/9781234567096.0003</biblioid>
<mediaobject xml:id="id0046mad">
<imageobject xml:id="id0047mad"><imagedata fileref="filename.pdf" format="application/pdf"/></imageobject>
</mediaobject>
</info>
<epigraph xml:id="si4"><para xml:id="si5">Men make their own history, but they do not make it just as they
please; they do not make it under circumstances chosen by themselves, but under circumstances directly
encountered, given, and transmitted from the past.<footnote xml:id="si6" label="1"><para xml:id="si7">Karl
Marx, &#x2018;The Eighteenth Brumaire of Louis Bonaparte&#x2019;, in <emphasis role="italic">Karl Marx:
Selected Writings</emphasis>, ed. David McLellan (New York and Oxford: Oxford University Press, 1977), p.
300.</para></footnote></para></epigraph>

172
 Sidebars

<sidebar xml:id="si8">
<info xml:id="si9"><title xml:id="si10">Objective</title></info>
<para xml:id="si11">To establish and analyse the key theoretical concepts necessary for understanding new
historicism and cultural materialism</para>
</sidebar>
<section xml:id="si12">
<info xml:id="si13">
<title xml:id="si14">Clifford Geertz: Culture, thick description and local knowledge</title>
</info>
<sidebar xml:id="si15">
<info xml:id="si16"><title xml:id="si17">Summary</title></info>
<itemizedlist xml:id="si18">
<listitem xml:id="si19"><para xml:id="si20">Anti-humanism versus essentialist humanism</para></listitem>
<listitem xml:id="si21"><para xml:id="si22">Clifford Geertz’s definition of culture</para></listitem>
<listitem xml:id="si23"><para xml:id="si24">&#x2018;Thick description&#x2019;</para></listitem>
<listitem xml:id="si25"><para xml:id="si26">&#x2018;Local knowledge&#x2019;</para></listitem>
<listitem xml:id="si27"><para xml:id="si28">Criticisms of Geertz</para></listitem>
<listitem xml:id="si29"><para xml:id="si30">Summary of Geertz’s theory</para></listitem>
</itemizedlist>
</sidebar>
<para xml:id="si31">In Chapter 2, I surveyed the main currents of Shakespeare criticism from 1904 to
the 1970s. One of the most obvious differences between the critics we looked at in that chapter and the
new...</para>

If a book contains differently-styled sidebars, each sidebar type can take a different @role:

• sidebar1

• sidebar2

• sidebar3

• sidebar9

NOTE: values sidebar4 to sidebar9 should only be used for exceptional cases, and MUST NOT be
used without prior authorisation from Bloomsbury.

This second example is a more typical text box:

in which the sidebar is inserted directly in the para at the point at which it occurs in the text. Note
also that the “label” text is within the title since sidebar does not support an @label attribute:

173
 Sidebars

which is supported by a Higher Education Academy grant (also see <link role="bib"
linkend="bibl6">Hammerstein 1999</link>, and see <emphasis role="bold"><link role="xref"
linkend="sb2">Chapter 3</link></emphasis>). He argues that involving students
<sidebar xml:id="sb2">
<info xml:id="sb3"><title xml:id="sb4">Vignette 11 University of Lincoln &#x2018;Students as
Producers&#x2019;</title></info>
<para xml:id="sb5">The University of Lincoln describes the initiative as follows:</para>
<blockquote xml:id="sb6"><para xml:id="sb7">We are the leading partner in a Government project which
enables students to learn through hands-on experience. Through practise and primary engagement with
research, students build and improve their critical skills...

26.2. Semantic sidebars in textbooks

Alternatively some books may have standard sidebar (or section) types; most often this occurs
in textbook-type content, and the styling of these sections may be distinct from the regular chapter
sections. In these cases the following @role values should be used, if possible:

@role value Usage

overview-objectives Sections and sidebars that describe or summarise
the chapter, or its learning objectives for the
student, often title @overview’, ‘Objectives’ or
some such
terms Sections or sidebars that contain a list of key
terms that have been introduced in the chapter.
The terms themselves should be in a glosslist
and (if defined elsewhere) link through to their
definitions
exercises-activities Sections or sidebars that contain questions, tests
and exercises for a student

Implementation note: The sidebars may need some light styling, and for each @role type

26.3. Embedded articles

Very occasionally, a content chunk may contain a sidebar which is effectively a discrete article in
its own right. Most often this will be within an article element within a reference work, and the
embedded article is simply a shorter, related article which needs to be represented as a sidebar.

In such cases, it MUST take @role=embeddedArticle.

See also the Section 9.5.6.3, “Article Groups” in Section 9.5.6, “Article components (dictionary-type
content)”, where sections may be used for sub-articles.

26.4. Sidebar placement

Sidebars MUST NOT occur within a paragraph. The same rules apply as for figure placement. See
Section 21.4, “Image placement”.

174
Chapter 27. Steps and procedures
Occasionally, some books may contain features which are best described as a procedure, with
numbered or un-numbered steps. Typically, they will be typographically distinct from the
surrounding text, and can be thought of as a special type of sidebar. Most often these occur in specific
sorts of textbooks with a more practical dimension, eg Designing and Patternmaking for Stretch Fabrics:

The following example has the images removed for clarity:

<procedure xml:id="pr1">
<info xml:id="pr2"><title xml:id="pr3">Making a marker for cutting</title></info>
<step xml:id="pr4">
<para xml:id="pr5">Once you have a final pattern and fabric ready, it is time to lay out the pattern
pieces, make a marker, and cut out your garment. All garments, including first samples, should be cut out
using a marker. A marker is a tracing of the pattern on special marking paper that has printed lines and/
or numbers used for lining up the grainline.</para>
<para xml:id="pr6">Preparing the marker paper:</para>
<simplelist xml:id="pr7">
<member xml:id="pr8">Draw a line across the top edge of the marker 1" below the cut edge. This is in case
the fabric, which will be underneath, is not straight.</member>
<member xml:id="pr9">Draw a line 1/2" in from the sides of the marker paper. This is so that the selvedge
will not be in the final garment.</member>
<member xml:id="pr10">All markers waste 1" of fabric at each end of the marker, and 1/2" on each side.</
member>
</simplelist>
</step>
<step xml:id="pr11">
<para xml:id="pr12">Tracing the pattern pieces:</para>
<para xml:id="pr13">Trace all the pattern pieces (right side up), making sure to include every notch and
any drill marks.</para>
</step>
</procedure>

Implementation note: Default DocBook styling is for each step to be numbered; downstream
applications should support a slightly different rendering relative to base text, and support
[new method for suppressing numbering]

175
Chapter 28. Examples
As with tables and figures, examples can occur either with or without a title, for which the example
and informalexample elements MUST be used, respectively.

As with other numbered blocks, if the label "Example 1" is required, the "1" is stored as @label on
the containing element. Note that @label on informalexample is an extension of DocBook.

<informalexample xml:id="b-9781849664554-01" label="1">

<para xml:id="b-9781849664554-02">Text</para>
</informalexample>

Implementation note: Default DocBook XSL does not support @label on informalexample

176
Chapter 29. Indexes and index terms
Ref: §1.70, §1.71, §1.72, §1.73, §1.74

If a book has an index, the terms MUST be marked up inline rather than as entities in themselves.
The terms MUST be positioned at the location in the text where they occur AND include an index
element to indicate the correct location of the index within the work.1

29.1. Index chunk

As with all content chunks, an index MUST include a title, pagenums and pdf file reference.

<index xml:id="b-0002163">
<info xml:id="b-0002163a">
<title xml:id="b-0002163b"><?page value="127"?>Index</title>
<pagenums>127–129</pagenums>
<mediaobject xml:id="b-ind-001">
<imageobject xml:id="b-ind-002">
<imagedata fileref="pdfs/9781849666565.0009.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
</index>

If the index includes some introductory text, this MUST be included, most likely as a para:

<index xml:id="b-0000707">
<info xml:id="b-0000708">
<title>Index</title>
<pagenums>129&#x2013;131</pagenums>
<mediaobject xml:id="b-0000710">
<imageobject xml:id="b-0000711"><imagedata fileref="pdfs/9781472541697.0007.pdf" format="application/pdf"/
></imageobject>
</mediaobject>

</info>
<para xml:id="b-0000712">Although there is some overlap, this index generally omits entries for material
that is easily found under a heading or sub-heading shown in the table of contents.</para>

An index MUST be included within the back matter.2

29.2. Multiple indexes

A book MAY have multiple indexes (eg General Index and Name Index), in which case, each MUST
have a @type,3 which MUST match the @type attributes on the indexterms: 4

<index type="NameIndex">
<info xml:id="b-1001702-index1">
<title xml:id="b-4001702">Name Index</title>

If there are multiple index @types, where an indexterm has @class=endofrange (see next
section) such indexterm does NOT REQUIRE @type (since it is implied by the corresponding
indexterm[@class=startofrange]).5

1
Tested in Schematron: index-missing, indexterms-missing
2
Tested in Schematron: index-not-back
3
Tested in Schematron: missing-index-type
4
Tested in Schematron: wrong-index-type
5
Tested in Schematron: type-endofrange

177
 Indexes and index terms

29.3. Types of index terms

An indexterm identifies text that is to be placed in the index, and is placed in the flow of the
document where the index should point.

An indexterm can mark either a single point or a range, and MUST have a @class to indicate such
type.6 Terms can be up to three levels: primary, secondary and tertiary:

He believes that education is about the transmission of facts, which he confounds with knowledge<indexterm
class="singular" type="SubjectIndex" xml:id="b-0000511"><primary>knowledge</primary><secondary>as
commodity</secondary></indexterm>.

Index terms can also have ranges, but such ranges MUST NOT be within a itermset,7 they MUST
start before they end,8 have a start and end point,9 and MUST NOT occur within footnotes.10 The
@zone attribute is NOT TO BE USED in this instance of DocBook.11

And, of course, in the hands of those who describe and manipulate &#x2018;the student experience<indexterm
class="startofrange" type="SubjectIndex" xml:id="b-0000620"><primary>authority</primary><secondary>and
experience</secondary></indexterm>&#x2019;, it really does have nothing whatsoever to do with this.
...
Such a transaction is anathema to the very idea of experience itself: it denies experience while promising
to provide it.<indexterm class="endofrange" startref="b-0000620"/></para>

If an index term should be alpha-sorted differently from its content (eg ‘Mac’ surnames), the
@sortas MUST be used:

<indexterm class="singular"><primary sortas="Macmillan, John">McMillan, John</primary></indexterm>

Furthermore, if some index terms are more important than others (usually rendered in bold in an
output format), use @significance:

<indexterm class="singular" significance="preferred">

<primary>Aristotle</primary>
<secondary><emphasis role="italic">De Anima</emphasis></secondary>
</indexterm>

29.4. Positioning of index terms

Most indexterms MUST occur in the text at the point at which they should be referenced so that the
index can be programmatically constructed. The DocBook documentation includes useful background
on positioning of indexterms.12

To avoid downstream processing issues with whitespace, there MUST NOT be any space between
the term and the indexterm.

In addition, indexterms MUST NOT be between block elements, ie in practice all indexterms
MUST be within:13

• attribution

• emphasis
6
Tested in Schematron: indexterm-class-missing
7
Tested in Schematron: itermset-with-range
8
Tested in Schematron: end-before-start
9
Tested in Schematron: no-end-range
10
Tested in Schematron: range-in-footnote-1, range-in-footnote-2
11
Tested in Schematron: zone-present
12
See http://www.docbook.org/tdg5/publishers/5.1b3/en/html/indexterm.singular.html
13
Tested in Schematron: indexterm-location

178
 Indexes and index terms

• entry

• itermset

• line

• member

• para

Occasionally,indexterms MAY appear within an index, but ONLY for retrospective data
conversion projects, if that approach is approved by Bloomsbury.

An indexterm MUST NOT appear within a title.14 If a term needs to be so placed, it MUST be
within an itermset within the division’s info. An indexterm is not permitted in an abstract,
either.15

29.5. Cross references within an index

29.5.1. “see” in index
Cross references within an index (“see other term”) can be constructed using the see element within
an indexterm. The target of the see MUST be another primary term.16 Since these do not have a
referent point in the text, they must be placed into an itermset in the info element of the chapter
that contains the term referred to.17

<itermset xml:id="b-0000025">
<indexterm class="singular" xml:id="b-0000026"><primary>financial shock 2008–9</primary><see>Great
Recession</see></indexterm>
<indexterm class="singular" xml:id="b-0000027"><primary>recession</primary><see>Great Recession</see></
indexterm>
</itermset>

Note that, if a see reference is included within a book, it is an error to use the same primary term in
another index item.18 For example, given the following indexterms:

<indexterm><primary>Extensible Markup Language</primary> <see>XML</see></indexterm>

<indexterm><primary>Extensible Markup Language</primary><secondary>definition of</secondary></indexterm>

There is no way to construct a logical index because an entry in the index should never have both a
see and other content.

29.5.2. “see also” in index

A “see also” cross reference can be created using a seealso element. The target of the seealso
MUST be another primary term.19

<itermset xml:id="b-0000275">
<indexterm class="singular" xml:id="0000276"><primary>leisure</primary><seealso>play</seealso></indexterm>
</itermset>

14
Tested in Schematron: indexterm-in-title
15
Tested in Schematron: abstract-indexterm
16
Tested in Schematron: see-seealso-target
17
Tested in Schematron: see-in-itermset
18
Tested in Schematron: see-mismatch
19
Tested in Schematron: see-seealso-target

179
Chapter 30. Elements we might not
need
At the present time it is unlikely that the following elements will be required at all, so their occurrence
is likely to be an error.1 If the data is likely to require one of these elements, please contact the
publisher.

acronym area
areaset areaspec artpagenums
bibliocoverage biblioentry biblioref bibliorelation
bibliosource citebiblioid citetitle collab
contractnum contractsponsor givenname literal
optional orgdiv
productname productnumber quote simpara
simplesect stepalternatives substeps
task taskprerequisites taskrelated tasksummary
trademark wordasword xref

1
Tested in Schematron: non-required-elements

180
Chapter 31. Schematron
This accompanying Schematron includes several hundred tests, most of which are cross-referenced
within this text, the main exceptions being numerous DocBook standard tests for element positions,
eg equation not allowed within equation etc.

In addition, the following tests are applied to report Information for each book to support spot checks
and additional QA:

• Title of the book [title-value]

• If a previous title is present [previous-title]

• If a series has a previous title value [series-prev-title]

• If an @xml:lang other than English is used at all [non-english-text]

• If the book is Open Access [open-access]

• If a contributor statement is present [contrib-statement-present]

• The proportion of unpublished and other bibliomixed items (if any) [proportion-unpub-other]

• The proportion of legal and case bibliomixed items (if any) [proportion-case-leg]

• If tables are present [table-present]

• If text marked “smaller”, “larger”, “sans-serif” or “serif” is used [rare-emph-present]

• If an insert PI is present [insert-present]

• If associated Online Resources are available [hasOnlineResources-info]

• If column PIs are present [columns-present]

• If line break PIs are present [line-break-present]

• If @condition is present (other than on remark) [condition-present]

• If a bibliomixed contains otherEdition, originalLang or translation components [other-editions-etc]

• If nested lists occur [nested-list]

• If orderedlist attributes are present [continuation-present, numeration-present, startingnumber-

present, inheritnum-present]

• If row and col span attributes are present in table [table-row-col-att]

• If a figure or informalfigure are present [figure-present]

• If an equation is present [eqn-present]

• If poetry or drama is present [poetry-drama-present]

• The value of @label, when present [label-value]

• If @outputformat is present [outputformat-present]

• If a book is marked as a work of fiction [fiction-info]

• If a book is marked as requiring chapter numbering suppression [chapter-numeration-info]

181
 Schematron

• If a sidebar is present [sidebar-present]

• If indexterms are present within an index [index-with-terms]

• If a snapshot-article or sub-article are present [snapshot-article, sub-article]

182
Chapter 32. Worked examples
32.1. Front matter
32.1.1. Title page and contributors

<info>
<title>Brecht, Music and Culture</title>
<authorgroup>
<author><personname role="first-last"><firstname>Hans</firstname><surname>Eisler</surname></personname></
author>
<othercredit class="other" otherclass="other"><personname role="first-last"><firstname>Hans</
firstname><surname>Bunge</surname></personname><contrib>in Conversation with</contrib></othercredit>
</authorgroup>
<bibliomisc role="contributorStatement">Hans Eisler in Conversation with Hans Bunge</bibliomisc>
<authorgroup>
<othercredit class="other" otherclass="editorTranslator"><personname role="first-last"><firstname>Sabine</
firstname><surname>Berendse</surname></personname>

<contrib>Edited and translated by</contrib></othercredit>

<othercredit class="other" otherclass="editorTranslator"><personname role="first-last"><firstname>Paul</
firstname><surname>Clements</surname></personname></othercredit>
</authorgroup>

32.1.2. Book lists

Notes:

183
 Worked examples

• On the half title verso

<cover role="halfTitleVerso" xml:id="b-0000022a">

<para xml:id="b-0000023">Also Available From Bloomsbury</para>
<simplelist xml:id="l1">
<member xml:id="b-0000024"><emphasis role="italic">Blanchot and Literary Criticism</emphasis>, Mark
Hewson</member>
<member xml:id="b-0000025"><emphasis role="italic">Deconstruction without Derrida</emphasis>, Martin
McQuillan</member>
<member xml:id="b-0000025a"><emphasis role="italic">Derrida</emphasis>, Simon Morgan Wortham</member>
<member xml:id="b-0000025b"><emphasis role="italic">Encountering Derrida</emphasis>, Edited by Simon Morgan
Wortham and Allison Weiner</member>
<member xml:id="b-0000025c"><emphasis role="italic">Jean-Luc Nancy</emphasis>, Edited by Benjamin
Hutchens</member>
<member xml:id="b-0000025d"><emphasis role="italic">Jean-Luc Nancy and the Question of Community</
emphasis>, Ignaas Devisch</member>
</simplelist></cover>

Commentary:

1. This is distinct from a series list (“Also Available”) so has@role=halfTitleVerso

2. The centering in the print is assumed to be handled by the print style template so does not need to
be reproduced here

3. The list of books is a list, not separate paragraphs, so needs to be grouped together in a
simplelist. These do not need to be in a bibliolist, which is only required for book lists that
need full biblio markup, ie bibliographies

32.1.3. CIP block

Notes:

• On title verso

<legalnotice xml:id="b-0000020a" role="CIP">

<para xml:id="b-0000026"><emphasis role="bold">Library of Congress Cataloging-in-Publication Data</
emphasis></para>
<simplelist xml:id="l2">
<member xml:id="b-0000027">Wortham, Simon.</member>
<member xml:id="b-0000028">The poetics of sleep : from Aristotle to Nancy / Simon Morgan Wortham.</member>
<member xml:id="b-0000029">p. cm.</member>
<member xml:id="b-0000030">Includes bibliographical references (p.) and index.</member>
<member xml:id="b-0000031">ISBN 978-1-4411-2476-0 (hardcover) -- ISBN 978-1-4411-6962-4 (ebook pdf) -- ISBN
978-1-4411-8081-0 (epub) 1. Sleep. 2. Dreams. I. Title.</member>
<member xml:id="b-0000032">BF1071.W67 2013</member>
<member xml:id="b-0000033">128&#x2019;.4--dc23</member>
<member xml:id="b-0000034">2012028312</member>
</simplelist>
</legalnotice>

Commentary:

1. The entire CIP block is in a legalnotice with @role=CIP

2. The CIP data is treated as a simplelist

3. The centering of the content is assumed to be handled by the print style template so is not needed
here

184
 Worked examples

32.2. Parts, chunks and labels

32.2.1. Unusual part structure and labels
This book (Background Noise: Perspectives on Sound Art, by Brandon LaBelle) is divided into numbered
parts and represented as such in the table of contents, but the presentation on the page is slightly
unusual. Here are pages 195 and 197:

Notes:

• The ‘normal’ heading “Part 5” does not actually appear (though it does on the table of contents)

• The part title page contains some quotes

• The following chapter doesn’t have a regular label

The proposed markup for this would be as follows:

<part xml:id="pt5" label="5">

<info xml:id="pt5-1">
<title xml:id="py1-2">Soundmarks: Environments and Aural Geography</title>
<pagenums>195–196</pagenums>
<biblioid class="doi">10.5040/9781609032229.part-005</biblioid>
<mediaobject xml:id="if1">

<imageobject xml:id="if2"><imagedata fileref="pdfs/9781609032229.part-005.pdf" format="application/pdf"/></

imageobject>
</mediaobject>

185
 Worked examples

</info>
<partintro xml:id="pt5-2">
<epigraph xml:id="e1">
<attribution role="right"><emphasis role="smallcaps">R. Murray Schafer</emphasis></attribution>
<para xml:id="ep1" role="center"><emphasis role="italic">Sounds cannot be known the way sight can be
known...</emphasis></para>
</epigraph>
</partintro>
<chapter xml:id="cp5" role="labelOverRide" label="Introduction to Part 5">
<info xml:id="cp5-1">
<title xml:id="cp5-2">Soundmarks: Environments and Aural Geography</title>
<pagenums>197–200</pagenums>
<biblioid class="doi">10.5040/9781609032229.009</biblioid>
<mediaobject xml:id="if3">
<imageobject xml:id="if4"><imagedata fileref="pdfs/9781609032229.009.pdf" format="application/pdf"/></
imageobject>
</mediaobject>
</info>
<para xml:id="cp1-10">The works of sound installation seek out a specificity of sound in which location and
listening intersect. The place of sound becomes as much a...</para>
</chapter>
</part>

Commentary:

1. This is part 5, so the @label value is included, even though the style of the print edition is to omit
it

2. The pagenums for the part title page are just for this page and the following blank one, not the
entire part

3. The quotes on the part title page MUST be contained within a partintro

4. The quotes are both epigraphs, since they occur at the beginning of the chunk; blockquote
would not be correct in this context

5. The attribution occurs first in the data, even though it may appear after the quote in the
rendered form; indeed, the DocBook default behaviour is to place it after the quote, though that
can be controlled in the DocBook customisation layer

6. The attribution takes a @role to indicate the alignment; DocBook default behaviour is to left
align an attribution

7. The dash before the name in the attribution should not be included, since that is a template
style

8. The name is styled as small caps

9. The centering of the epigraph paragraphs is controlled with @role

10.The content of the epigraph is styled with emphasis. There could be a case for the styling of
both this and the previous item to be implied by the template style

11.The next section starts a new page which is stylistically (and structurally) identical to a chapter
elsewhere in the book, so is contained within a chapter

12.The default labelling and numbering style for parts, chapters etc is “[element name] @label” if a
@label is present, so typically <chapter label="1"> would have a label “Chapter 1” or “1”
before the title (depending on the style template). In this case, the text “Introduction to Part 5” is
in the same style as “Chapter 13” which follows it. Therefore, that text is included as the @label,
but also includes the @role=labelOverRide to indicate that this chapter has non-standard
@label behaviour

13.The opening word has a drop cap in the print, but that is not replicated in the XML

186
 Worked examples

32.2.2. More unusual structure and labels

Notes:

• This book is organised into “Sections” which contains numbered “Ideas”, each of which happens to
occupy a single page

• The book’s table of contents lists all the Ideas as if they were chapters

<part xml:id="h1" label="Section 1" role="labelOverRide">

<info xml:id="h2">
<title xml:id="h3">Birth — 11 months</title>
<pagenums>1</pagenums>

187
 Worked examples

<biblioid class="doi">10.5040/9781609032229.0006</biblioid>
<mediaobject xml:id="h4">
<imageobject xml:id="h5"><imagedata fileref="pdfs/9781609032229.0006.pdf" format="application/pdf"/></
imageobject>
</mediaobject>
</info>
<partintro xml:id="h6">
<para xml:id="h7">While generally happy to be looked after by anyone who is competent, warm and caring,
newborn and very young babies already show...</para>
</partintro>
<chapter xml:id="h8" label="Idea 1" role="labelOverRide">
<info xml:id="h9">
<title xml:id="h10">Snug as a Bug</title>
<pagenums>2</pagenums>
<biblioid class="doi">10.5040/9781609032229.0007</biblioid>
<mediaobject xml:id="ha4">
<imageobject xml:id="ha5"><imagedata fileref="pdfs/9781609032229.0007.pdf" format="application/pdf"/></
imageobject>
</mediaobject>
</info>
<informaltable xml:id="h11" frame="none">
<tgroup cols="3">

<colspec colname="col1" colnum="1" align="left" colsep="0" colwidth="2*"/>

<colspec colname="col2" colnum="2" align="left" colsep="0" colwidth="1*"/>
<colspec colname="col3" colnum="3" align="left" colsep="0" colwidth="2*"/>
<thead>
<row rowsep="1"><entry xml:id="h12">Focus</entry><entry xml:id="h13">Group size</entry><entry
xml:id="h14">Preparation/Resources</entry></row>
</thead>
<tbody>
<row rowsep="0"><entry xml:id="h15">Self-confidence and Self-esteem</entry><entry xml:id="h16">Individual</
entry><entry xml:id="h17">A light baby blanket or wrap</entry></row>
<row><entry xml:id="h18">Behaviour and Self-control</entry><entry xml:id="h19"></entry><entry
xml:id="h20"></entry></row>
</tbody>
</tgroup>
</informaltable>
<para xml:id="h21">Babies gain physical, psychological and emotional comfort...</para>
<itemizedlist xml:id="h22" mark="disc">
<listitem xml:id="h23"><para xml:id="h24">With the baby's limbs loosely contained...</para></listitem>
<listitem xml:id="h25"><para xml:id="h26">Make a little joke...</para></listitem>
</itemizedlist>
<sidebar xml:id="h27" role="sidebar1">
<info xml:id="h28"><title xml:id="h29">Safety note</title></info>
<mediaobject xml:id="hb4">
<imageobject xml:id="hb5"><imagedata fileref="images/9781609032229.0001.png" format="image/png"/></
imageobject>
</mediaobject>
<para xml:id="h30">Avoid cellular blankets for this game in case small fingers become caught in the
holes.</para>
</sidebar>
</chapter>
</part>

Commentary
The Section is encoded as a part with “Section 1” as its @label and, because it is a non-
standard label, must have @role=labelOverRide
The pagenums for the Section 1 introductory text just takes the page it occupies
Its text is encoded within partintro
Then the Idea content is within a chapter, with “Idea 1” as its @label and because it is a non-
standard label, must take @role=labelOverRide
The Idea occupies a single page, which is recorded in pagenums
The first item of text is a simple table, using informaltable and @frame=none
The header of which has a row below, so has @rowsep=1
Other rows do not have a separator so need @rowsep=0
The Safety Note is styled differently so can be placed in a sidebar (in this case with
@role=sidebar1 so all such Notes can be styled the same)
The Safety Note icon is encoded as a mediaobject directly in the text; it is not a figure or
informalfigure since it is simply serving as an icon; its position is to be controlled by the
downstream style template

188
 Worked examples

32.2.3. Slightly complex chapter opener style

Note:

• What is the title?

<chapter xml:id="qk1" label="Conversation 1" role="labelOverRide">

<info xml:id="qk2">
<title xml:id="qk3"><emphasis role="italic">14 Ways of Describing Rain</emphasis> – Meetings between Brecht
and Arnold Schoenberg, Charlie Chaplin and Thomas Mann – Brecht and Music</title>
<subtitle xml:id="qk4">9 April 1958<footnote xml:id="qk5" label="6"><para xml:id="qk6">Hans Bunge writes:
&#x2018;The recording of the conversation during our first meeting on 9 April 1958 was inadvertently
deleted due to a technical mistake. The text before you is a reconstruction from memory of the first
conversation on the basis of prepared written questions. This recording took place on 2 May 1958.&#x2019;
The only passage preserved on tape is a discussion about a title change to Brecht&#x2019;s song &#x2018;In
Praise of Communism&#x2019;. With Brecht&#x2019;s knowledge, Eisler changed it to &#x2018;In Praise of
Socialism&#x2019;. Eisler remarks that the title of a song is not the important issue, although Brecht
would certainly not have allowed him to change it to &#x2018;In Praise of Reformism&#x2019;. The passage
has not been included in this edition.</para></footnote></subtitle>
<titleabbrev>Conversation 1, 9 April 1958</titleabbrev>

Commentary:

1. Note use of @role=labelOverRide; see elsewhere in this document for further description of its
use.

2. It makes most sense to make "14 Ways of Describing Rain" etc the title since it is in bigger type
than the date

3. which means the date is in a subtitle and contains a footnote

4. Include @label on all the footnotes since they are numbered sequentially throughout the book;
the only occasion when you don't need to add @label to footnotes is when they are numbered 1-n
within a single chapter.

5. There is a titleabbrev too, which is where you can store the running head since it is not
necessarily straightforward to generate it from the text.

189
 Worked examples

32.2.4. Non-sequential heading style

Very occasionally, a chapter may have, say, a level 2 heading which is not preceded by a level 1
heading. Since the heading level is determined by the section depth, how do you achieve this?

Here is an example:

190
 Worked examples

Within the style of this book, the heading “Beyond Cultural Industries” is level 1, and “Integrated
development” is level 2. This can only be achieved using the floating bridgehead element with
appropriate @renderas:

</figure>

China reached 1.13 billion including 300 million landline users and 830 million
mobile phone users. Broadband users increased to 110 million in 2010.<footnote
xml:id="ba-9781849666565-0000854"><para xml:id="ba-9781849666565-0000855"><bibliolist
role="inline" xml:id="ba-9781849666565-0002048zz"><bibliomixed role="website"
xml:id="ba-9781849666565-0002049yy"><author><orgname>Statistics from the Ministry of Industry and
Information Technology of P.R.China</orgname></author>. <title><emphasis role="italic">China Daily</
emphasis></title>, <pubdate>29 June 2010</pubdate>. <link xlink:href="http://www.chinadaily.com.cn/
hqgj/jryw/2010-06-29/content_512367.html"><uri>http://www.chinadaily.com.cn/hqgj/jryw/2010-06-29/
content_512367.html</uri></link> [accessed <date role="accessed">8 March 2011</date>]</bibliomixed></
bibliolist>.</para></footnote></para>
<bridgehead renderas="sect2" xml:id="ba-9781849666565-0000867">Integrated development</bridgehead>
<para xml:id="ba-9781849666565-0000868">In a 2002 research paper I identified three development trends of
modern industries: industrial clusters, industrial convergence and industrial ecology.

32.2.5. Chapter Outlines and Abstracts

Some of the Bloomsbury design templates include chapter outlines and abstracts. At first sight, these
could both adopt a sidebar element, but that is not correct.

191
 Worked examples

The Chapter Outline is only a table of contents. As such it can be generated entirely from the XML
structure, should it be required, so MUST NOT have a separate representation in the data.1

The Abstract MUST be within an abstract element in the chunk info, and take
@role=authorAbstract:

<chapter label="8" xml:id="ba-9781472552914-ch08">

<info xml:id="ba-9781472552914-0001164">
<title xml:id="ba-9781472552914-0001165"><?page value="165"?>Challenges for the International Aid System</
title>
<author>
<personname role="first-last"><firstname>Alan</firstname><surname>Smith</surname></personname>
</author>
<pagenums>165&#x2013;176</pagenums>
<biblioid class="doi">10.5040/9781472552914.ch-008</biblioid>
<mediaobject xml:id="ba-9781472552914-0001166">
<imageobject xml:id="ba-9781472552914-0001167"><imagedata fileref="pdfs/9781472552914.ch-008.pdf"
format="application/pdf"/></imageobject>
</mediaobject>
<abstract role="authorAbstract" xml:id="ba-9781472552914-0001193">
<para xml:id="ba-9781472552914-0001194" role="fullOut">This chapter identifies a number of significant
developments in the global environment that have influenced international aid over the past decade and
reflects on their implications for the provision of education for IDPs. These include arguments for the
inclusion of education as part of a humanitarian response, changes to the global security environment,
and the implications of UN involvement in peacebuilding. It argues that there is a lack of understanding
around the roles education may play in the wake of crisis, as well as the contexts in which people are
internally displaced.</para>
</abstract>
</info>
<section xml:id="ba-9781472552914-0001197">
<info xml:id="ba-9781472552914-0001196"><title xml:id="ba-9781472552914-0001195">Introduction</title></
info>
<para xml:id="ba-9781472552914-0001198" role="fullOut">When the cold war ended, there was an aspiration
that the international aid agenda might be driven by humanitarian goals to eliminate poverty rather
than be limited by tensions in international relations. This aspiration is reflected in the Millennium
Development Goals (MDGs) and the central importance of education to human development was emphasized by
the <?page value="166"?>

1
Tested in Schematron: remove-chapter-outline

192
 Worked examples

32.3. Chapters with appendices etc

Occasionally, chapters or other chunks may have relatively unusual structures for which at first sight
there are standard semantic elements, but which aren’t valid in the schema.

193
 Worked examples

Notes:

• This would ordinarily be a normal chapter with sections, bibliography and then notes (see
Section 18.2.1, “End of chapter notes”), but the material at the end (the appendix) causes issues since
the schema does not permit appendix within a chapter

194
 Worked examples

<chapter label="1" xml:id="ba-9781849664530-chapter-001">

<info xml:id="ba-9781849664530-0000343">
<title xml:id="ba-9781849664530-0000344"><?page value="11"?>The Terrible Simplifiers:</title>
<subtitle xml:id="ba-9781849664530-0000345">Common Origins of Financial Crises and Persistent Poverty in
Economic Theory and the New &#x2018;1848 Moment&#x2019;</subtitle>
<pagenums>11–38</pagenums>
<biblioid class="doi">10.5040/9781849664530.ch-001</biblioid>
<mediaobject xml:id="ba-9781849664530-ch1-001">
<imageobject xml:id="ba-9781849664530-ch1-002">
<imagedata fileref="pdfs/9781849664530.ch-001.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
<author><personname role="first-last"><firstname>Erik</firstname><othername role="middle-initials">S.</
othername><surname>Reinert</surname></personname></author>
</info>
<-- Content omitted for clarity -->
<?page value="29"?>
<section xml:id="ba-9781849664530-0000668">
<info xml:id="ba-9781849664530-0000669">
<title xml:id="ba-9781849664530-0000670">Conclusion: Towards &#x2018;An 1848 Moment&#x2019; when Empirical
Knowledge Matters Again</title>
</info>
<-- Content omitted for clarity -->
</section>
<?page value="33"?>
<section xml:id="ba-9781849664530-0000800">
<info xml:id="ba-9781849664530-0000801">
<title xml:id="ba-9781849664530-0000802">References</title>
</info>
<bibliolist xml:id="bl1"><bibliomixed role="monograph"
xml:id="ba-9781849664530-0000803"><author><personname role="last-first"><surname>Buchanan</
surname><firstname>James</firstname></personname></author> (<pubdate>1979</pubdate>).
<title xml:id="ba-9781849664530-0000804"><emphasis role="italic">What Should Economists
Do?</emphasis></title> <publishername>Liberty Press</publishername>, <address
xml:id="ba-9781849664530-0000805"><city>Indianapolis</city></address>.</bibliomixed>
<-- Content omitted for clarity -->
</bibliolist></section>
<?page value="36"?>
<?insert item="end-ch-notes" title="Notes"?>
<?page value="37"?>
<section label="Appendix I" role="labelOverRide" xml:id="ba-9781849664530-appendix-001">
<info xml:id="ba-9781849664530-0000988">
<title xml:id="ba-9781849664530-0000989">Frank Graham's Theory of Uneven Development</title>
</info>
<para xml:id="ba-9781849664530-0000990">Increasing and diminishing returns in international trade: a
numerical example</para>
<-- Content omitted for clarity -->
</section>
</chapter>

Commentary:

1. The chapter contains regular sections

2. However, because it ends with an appendix, all of the child units MUST be within a section,
even if a more semantically correct element would normally be used (such as here, where
bibliography would be more typical)

3. Consequently, the group of bibliomixed elements within the section must be in a

bibliolist to be valid

4. The Notes section is called in using the processing instruction in the usual way

5. And finally, the appendix is included as a section, though it needs @role="labelOverRide"

32.4. Glossary
Many glossaries occur as chunks at the beginning or end of books; alternatively, they may occur at the
end of a chapter or as part of an appendix etc. In such cases, the glossary MAY be a child element
of a chunk, or the glossary content may simply be within a glosslist. This example illustrates how
general layout is not encoded within the glossary elements:

195
 Worked examples

Notes:

• The styling in print is simply to run on

• There is an internal cross reference

<glossentry xml:id="consideration">
<glossterm><emphasis role="bold">consideration</emphasis></glossterm>
<glossdef xml:id="g4"><para xml:id="g6">something of value offered in order to persuade another party to
enter a <link role="xref" linkend="contract"><emphasis role="smallcaps">contract</emphasis></link>.</
para></glossdef>
</glossentry>
<!-- Text omitted for clarity -->
<glossentry xml:id="contract">
<glossterm><emphasis role="bold">contract</emphasis></glossterm>
<glossdef xml:id="g7"><para xml:id="g8">a legally enforceable agreement.</para></glossdef>
</glossentry>

Commentary:

1. Term IDs can use the term itself, if that makes it easier to construct internal cross references

2. The definition is within a para, even though in this case the print edition renders it as following on
from the term

3. Internal cross references are explicitly linked

4. Small caps of the cross-referenced terms is also marked up

32.5. Linking
32.5.1. Short-form bibliographic references
All bibliomixed should usually be referenced at least once in the text. Sometimes it can be difficult
to find the referring string in the text, and these examples illustrate some of the issues.

Here, the author is mentioned, but the date of the article cited is right at the end of the following
blockquote:

Baroness Tessa Blackstone, Vice-Chancellor of the University of Greenwich, commented in the short debate in
the House of Lords:</para>
<blockquote xml:id="ba-9781849666459-0000112">
<para xml:id="ba-9781849666459-0000113">No-one could have predicted that such a review would double the
fees then proposed and assume that the public funding of 80 per cent of undergraduate tuition would be
abandoned. Nor would anyone have predicted that this review would be based on a commitment to the free
market that is so extreme that it abandons, to quote Sir Peter Scott, a much respected vice-chancellor and
former member of the HEFCE board, &#x2018;the very idea of a public system of higher education, built with
such care and effort since Robbins&#x2019;. (<link role="bib" linkend="ba-9781849666459-0002171">2010</
link>)</para>

196
 Worked examples

</blockquote>
which then references the following bibliomixed:
<bibliomixed role="article" xml:id="ba-9781849666459-0002171"><bibliomset relation="article"
xml:id="ba-9781849666459-0002172"><author><personname role="last-first"><surname>Blackstone</
surname><honorific>Baroness</honorific></personname></author> (<pubdate>2010</pubdate>),
&#x2018;<title xml:id="ba-9781849666459-0002173">House of Lords Debate, 27 October 2010</
title>&#x2019;</bibliomset>, <bibliomset relation="journal" xml:id="ba-9781849666459-0002174"><title
xml:id="ba-9781849666459-0002175"><emphasis role="italic">Hansard</emphasis></title>, <address
xml:id="ba-9781849666459-0002176"><city>London</city></address>: <publishername>Hansard</publishername>.
col. 1238. Available at: <link xlink:href="http://www.publications.parliament.uk/pa/ld201011/ldhansrd/
text/101027-0001.htm#10102762000053"><uri>http://www.publications.parliament.uk/pa/ld201011/ldhansrd/
text/101027-0001.htm#10102762000053</uri></link> [<date role="accessed">27 July 2011</date>].</
bibliomset></bibliomixed>

Here is a similar example:

each vice-chancellor and pro-vice chancellor in the UK should be obligated to read and reflect on Boulton
and Lucas's words on the societal role of the university:</para>
<blockquote xml:id="ba-9781849666459-0001056">
<para xml:id="ba-9781849666459-0001057">Universities are not just supermarkets for a variety of public
and private goods that are currently in demand, and whose value is defined by their <?page value="73"?
>perceived aggregate financial value. We assert that they have a deeper, fundamental role that permits
them to adapt and respond to the changing values and needs of successive generations, and from
which the outputs cherished by governments are but secondary derivatives. To define the university
enterprise by these specific outputs, and to fund it only through metrics that measure them, is to
misunderstand the nature of the enterprise and its potential to deliver social benefit. (<link role="bib"
linkend="ba-9781849666459-0002192">2008</link>: 17)</para>
</blockquote>

Alternatively, the author’s name and the date to be linked may simply be some distance away in the
same paragraph:

In 2010 George Monbiot wrote: &#x2018;Through networking, confidence, unpaid internships, and
most importantly attendance at top universities, the privately educated upper middle classes run
politics, the civil service, the arts, the city, law, medicine, big business, the armed forces,
even, in many cases, the protest movements challenging these powers&#x2019; (<link role="bib"
linkend="ba-9781849666459-0002625">2010</link>).

32.5.2. Same work in multiple bibliomixeds

Resolving links to their correct bibliomixed target can sometimes be problematical, especially for
some edited books. This is typically more complex if each chapter has its own bibliography (or
includes citations in footnotes), whether at the end of the chapter or grouped in chapter units at the
back of the book.

For example:

Chapter 1: The beginnings of Rome

Joan Smith and Emily Brown
Some text here, which includes a reference to Cornell (1995) and then continues...
Bibliography
Cornell, T.J. (ed.) (1995) The Beginnings of Rome: Italy and Rome from the Bronze Age to the Punic Wars (c.
1000-264 BC). London: Routledge.
Chapter 2: The later republic
Roger White and James Black
Some text here, which also includes a reference to Cornell (1995) and then continues...
Bibliography
Cornell, T.J. (ed.) (1995) The Beginnings of Rome: Italy and Rome from the Bronze Age to the Punic Wars (c.
1000-264 BC). London: Routledge.

The short form reference in each chapter MUST link to the correct target for that chapter. It is an
ERROR if the short form references for a particular chapter resolve to the bibliomixed for that
book but belonging to the bibliography of another chapter. In such a case, there will be lots of
warnings of unresolved bibliomixed items, which MUST be checked.2

2
See in Schematron: bibliomixed-referenced

197
 Worked examples

32.6. Bibliographies
32.6.1. Inconsistent biblio style
This warning highlights a case where there is an inconsistent style in a bibliography. Typically a
bibliography is ordered by the surname of the first-named author, and this test identifies if there is a
mixture of such items.3

Description: Not all of the biblio items have the same personname @role style [first-last=1 / last-
first=56]

However, how do you find where the problem might be?

So, to find the odd one out, use these two XPath queries:

• bibliomixed/element()/personname[1][@role='first-last']

• bibliomixed/bibliomset[1]/element()/personname[1][@role='first-last']

The first one doesn’t retrieve any results, but the second one identifies the incorrect item. Note that in
this case there is just one personname[@role=first-last] as the first name in the bibliography,
whereas all others are last-first:

<bibliomixed role="contribution" xml:id="ba-9781472543370-0001337"><bibliomset

relation="part"><author><personname role="first-last"><firstname>Bart</firstname><surname>Moore-
Gilbert</surname></personname></author> &#x2018;<title xml:id="ba-9781472543370-0001338">Postcolonialism
and the &#x201C;the Figure of the Jew&#x201D;: Caryl Phillips and Zadie Smith</title>&#x2019;</
bibliomset>, in <bibliomset relation="book"><title xml:id="ba-9781472543370-0001339"><emphasis
role="italic">The Contemporary British Novel</emphasis></title>. edited by <editor><personname
role="first-last"><firstname>James</firstname><surname>Acheson</surname></personname></
editor> and <editor><personname role="first-last"><firstname>Sarah</firstname><othername
role="middle-initials">C. E.</othername><surname>Ross</surname></personname></editor>. <address
xml:id="ba-9781472543370-0001340"><city>Edinburgh</city></address>: <publishername>Edinburgh University
Press</publishername>, <pubdate>2005</pubdate>, pp.<pagenums>106&#x2013;17</pagenums>.</bibliomset></
bibliomixed>

which then just needs to be modified as follows:

<bibliomixed role="contribution" xml:id="ba-9781472543370-0001337"><bibliomset

relation="part"><author><personname role="last-first"><surname>Moore-Gilbert</surname><firstname>Bart</
firstname></personname></author> &#x2018;<title xml:id="ba-9781472543370-0001338">Postcolonialism
and the &#x201C;the Figure of the Jew&#x201D;: Caryl Phillips and Zadie Smith</title>&#x2019;</
bibliomset>, in <bibliomset relation="book"><title xml:id="ba-9781472543370-0001339"><emphasis
role="italic">The Contemporary British Novel</emphasis></title>. edited by <editor><personname
role="first-last"><firstname>James</firstname><surname>Acheson</surname></personname></
editor> and <editor><personname role="first-last"><firstname>Sarah</firstname><othername
role="middle-initials">C. E.</othername><surname>Ross</surname></personname></editor>. <address
xml:id="ba-9781472543370-0001340"><city>Edinburgh</city></address>: <publishername>Edinburgh University
Press</publishername>, <pubdate>2005</pubdate>, pp.<pagenums>106&#x2013;17</pagenums>.</bibliomset></
bibliomixed>

32.6.2. Firstname/surname issues

As a result of automated conversion processes, sometimes names that are likely to be first names are
tagged as surname. The test4 for this is isn’t completely infallible, since some names are used as both
first names and surnames, but it is a good indicator to check if some of the biblio markup is wrong.

The warning is:

3
See in Schematron: mixed-personname-style
4
See in Schematron: surname-is-firstname

198
 Worked examples

Description: Should the surname element be a firstname? Its content = Kevin, + also check sibling firstname
element and that parent personname[@role] is correct

For example, these three were highlighted:

<bibliomixed role="contribution" xml:id="ba-9781472543356-0001489"><bibliomset

xml:id="ba-9781472543356-0001490" relation="part"><author><personname role="last-
first"><surname>Wetmore</surname><firstname>Kevin</firstname></personname></author> <pubdate>2009</
pubdate>, &#x2018;<title xml:id="ba-9781472543356-0001491">&#x201C;The amazing adventures of
superbard&#x201D;: Shakespeare in comics and graphic novels</title>&#x2019;</bibliomset>, in
<bibliomset xml:id="ba-9781472543356-0001492" relation="book"><editor><personname role="last-
first"><surname>Jennifer</surname><firstname>Hulbert</firstname></personname></editor>,
<editor><personname role="last-first"><surname>Kevin</surname><firstname role="initials">J.</
firstname></personname></editor> <editor><personname role="last-first"><surname>Wetmore</surname></
personname></editor> and <editor><personname role="last-first"><surname>Robert</surname><firstname
role="initials">L.</firstname><othername role="middle">York</othername></personname></editor> (eds),
<title xml:id="ba-9781472543356-0001493"><emphasis role="italic">Shakespeare and Youth Culture</
emphasis></title>. <address xml:id="ba-9781472543356-0001494"><city>Houndmills</city></address>:
<publishername>Palgrave</publishername>, pp. <pagenums>171&#x2013;98</pagenums>.</bibliomset></
bibliomixed>

And notice also that there is a name in the middle with only a surname (which also generates a
warning).

Compare with the print layout, where it is much clearer

Wetmore, Kevin (2009), ‘“The amazing adventures of superbard”: Shakespeare in comics and
graphic novels’, in Jennifer Hulbert, Kevin J. Wetmore and Robert L. York (eds), Shakespeare and
Youth Culture. Houndmills: Palgrave, pp. 171–98.

Correct markup, in which all the components that have been modified in some way are highlighted:

<bibliomixed role="contribution" xml:id="ba-9781472543356-0001489"><bibliomset

xml:id="ba-9781472543356-0001490" relation="part"><author><personname role="last-first"><surname>Wetmore</
surname><firstname>Kevin</firstname></personname></author> <pubdate>2009</pubdate>, &#x2018;<title
xml:id="ba-9781472543356-0001491">&#x201C;The amazing adventures of superbard&#x201D;: Shakespeare in
comics and graphic novels</title>&#x2019;</bibliomset>, in <bibliomset xml:id="ba-9781472543356-0001492"
relation="book"><editor><personname role="first-last"><firstname>Jennifer</firstname><surname>Hulbert</
surname></personname></editor>, <editor><personname role="first-last"><firstname>Kevin</
firstname><othername role="middle-initials">J.</othername><surname>Wetmore</surname></personname></
editor> and <editor><personname role="first-last"><firstname>Robert</firstname><othername
role="middle-initials">L.</othername><surname>York</surname></personname></editor> (eds),
<title xml:id="ba-9781472543356-0001493"><emphasis role="italic">Shakespeare and Youth Culture</
emphasis></title>. <address xml:id="ba-9781472543356-0001494"><city>Houndmills</city></address>:
<publishername>Palgrave</publishername>, pp. <pagenums>171&#x2013;98</pagenums>.</bibliomset></
bibliomixed>

32.6.3. Sibling elements of bibliomset

Within a bibliomixed, if it contains bibliomsets there should not normally be any other child
elements of the bibliomixed. The only possible exception is if some general note about the
bibliographical item follows it.

In this example, the editors of the book must be in the bibliomset[@relation=book] (the
following example includes INCORRECT markup):

<bibliomixed role="contribution" xml:id="ba-9781472543356-0001489"><bibliomset

xml:id="ba-9781472543356-0001490" relation="part"><author><personname role="last-first"><surname>Wetmore</
surname><firstname>Kevin</firstname></personname></author> <pubdate>2009</pubdate>, &#x2018;<title
xml:id="ba-9781472543356-0001491">&#x201C;The amazing adventures of superbard&#x201D;:
Shakespeare in comics and graphic novels</title>&#x2019;</bibliomset>, in <editor><personname
role="first-last"><firstname>Jennifer</firstname><surname>Hulbert</surname></personname></editor>,
<editor><personname role="first-last"><firstname>Kevin</firstname><othername role="middle-initials">J.</
othername><surname>Wetmore</surname></personname></editor> and <editor><personname role="first-
last"><firstname>Robert</firstname><othername role="middle-initials">L.</othername><surname>York</
surname></personname></editor> (eds), <bibliomset xml:id="ba-9781472543356-0001492" relation="book"><title

199
 Worked examples

xml:id="ba-9781472543356-0001493"><emphasis role="italic">Shakespeare and Youth Culture</

emphasis></title>. <address xml:id="ba-9781472543356-0001494"><city>Houndmills</city></address>:
<publishername>Palgrave</publishername>, pp. <pagenums>171&#x2013;98</pagenums>.</bibliomset></
bibliomixed>

The following is the CORRECT version:

<bibliomixed role="contribution" xml:id="ba-9781472543356-0001489"><bibliomset

xml:id="ba-9781472543356-0001490" relation="part"><author><personname role="last-first"><surname>Wetmore</
surname><firstname>Kevin</firstname></personname></author> <pubdate>2009</pubdate>, &#x2018;<title
xml:id="ba-9781472543356-0001491">&#x201C;The amazing adventures of superbard&#x201D;: Shakespeare in
comics and graphic novels</title>&#x2019;</bibliomset>, in <bibliomset xml:id="ba-9781472543356-0001492"
relation="book"><editor><personname role="first-last"><firstname>Jennifer</firstname><surname>Hulbert</
surname></personname></editor>, <editor><personname role="first-last"><firstname>Kevin</
firstname><othername role="middle-initials">J.</othername><surname>Wetmore</surname></personname></
editor> and <editor><personname role="first-last"><firstname>Robert</firstname><othername
role="middle-initials">L.</othername><surname>York</surname></personname></editor> (eds),
<title xml:id="ba-9781472543356-0001493"><emphasis role="italic">Shakespeare and Youth Culture</
emphasis></title>. <address xml:id="ba-9781472543356-0001494"><city>Houndmills</city></address>:
<publishername>Palgrave</publishername>, pp. <pagenums>171&#x2013;98</pagenums>.</bibliomset></
bibliomixed>

The test5 for this generates the following warning:

Description: Biblio item contains editor element that is not in a bibliomset, which is very unusual. Is
that correct?

32.7. Lists
32.7.1. A simple list with title, columns and notes

Notes:
5
See in Schematron: element-not-bibliomset

200
 Worked examples

• At first sight, this looks like section headings and footnotes, but that is not the case

<itemizedlist xml:id="j4" mark="none">

<info xml:id="j2">
<title xml:id="j3">New and climbing<link role="xref" linkend="o10">*</link></title>
</info>
<?break type="column-start"?>
<listitem xml:id="j5"><para xml:id="o1">Northwestern University</para></listitem>
<listitem xml:id="j6"><para xml:id="o2">Queens College [CUNY]</para></listitem>
<listitem xml:id="j7"><para xml:id="o3">Rutgers University of Newark</para></listitem>
<listitem xml:id="j8"><para xml:id="o4">University of Colorado</para></listitem>
<listitem xml:id="j9"><para xml:id="o5">University of Georgia</para></listitem>
<?break type="column"?>
<listitem xml:id="j10"><para xml:id="o6">University of Massachusetts at Boston</para></listitem>
<listitem xml:id="j11"><para xml:id="o7">University of New Hampshire</para></listitem>
<listitem xml:id="j12"><para xml:id="o8">University of Wyoming</para></listitem>
<listitem xml:id="j13"><para xml:id="o9">Virginia Tech University</para></listitem>
<?break type="column-end"?>
</itemizedlist>
<!-- Second list omitted for clarity -->

<para xml:id="o10">* Date of program initiation: Queens College [CUNY], 2007; Rutgers University of Newark,
2007;...</para>

Commentary:

1. The text could in principle be modelled as two sections, though since all the notes have
to be in a para, that would result in the notes not belonging in the section to which they
belonged, so it makes most sense for this to be treated as a list; and importantly, this is an
itemizedlist[@mark=none] because it has a title

2. The notes are not footnotes as they simply appear in the text below the lists, so are simply
captured as paras, with a link

3. Processing instructions are used for column markers

4. This means that items that run over two lines in print are encoded within a single listitem

5. The link target is includes the note label (asterisk) in the text

32.8. Tables
32.8.1. A relatively simple table

201
 Worked examples

Notes:

• Table at the foot of a page, mid paragraph

• Different column widths

<para xml:id="t1">While the reasons for such differences are not well understood, one possible explanation
lies in the distance the
<table xml:id="t2" label="2.1" frame="topbot">
<info xml:id="t3">
<title xml:id="t4">Average slave mortality in the Middle Passage, 1590–1867C</title>
</info>
<?dbhtml table-width="80%"?>
<?dbfo table-width="80%"?>
<tgroup cols="3">
<colspec align="left" colnum="1" colname="col1" colwidth="1*"/>

<colspec align="char" char="." charoff="20" colnum="2" colname="col2" colwidth="1.5*"/>

<colspec align="right" colnum="3" colname="col3" colwidth="1*"/>
<thead>
<row><entry xml:id="t5">Period</entry><entry xml:id="t6" align="center">Mean percentage of deaths</
entry><entry xml:id="t7" align="center">Ships in sample</entry></row>
</thead>
<tbody>
<row><entry xml:id="t8">1590–1699</entry><entry xml:id="t9">20.3</entry><entry xml:id="t10">401</entry></
row>
<row><entry xml:id="t11">1700–1749</entry><entry xml:id="t12">15.8</entry><entry xml:id="t13">1091</
entry></row>
<row><entry xml:id="t14">1750–1807</entry><entry xml:id="t15">12.0</entry><entry xml:id="t16">2571</
entry></row>
<row><entry xml:id="t17">1808–1829</entry><entry xml:id="t18">8.8</entry><entry xml:id="t19">1350</entry></
row>
<row><entry xml:id="t20">1830–1867</entry><entry xml:id="t21">11.5</entry><entry xml:id="t22">553</entry></
row>
</tbody>
</tgroup>
<caption xml:id="t23"><para xml:id="t24"><emphasis role="italic">Source</emphasis>: Herbert S. Klein,
<emphasis role="italic">The Atlantic Slave Trade</emphasis>, Cambridge, 1999, p. 138.</para></caption>
</table>
<?page value="23"?>enslaved Africans had to travel...</para>

Commentary:

1. Table placed where it occurs on the page within the para

2. The label “TABLE 2.1” is assumed to be autogenerated and triggered by the presence of @label.
Style of the “TABLE 2.1” label is a design template issue, not to be captured in the data

3. The @frame attribute gives a reasonable amount of control of the table borders and should reflect
what is required in the print edition. Here the option is to have a top and bottom rule

4. Table width MUST be specified using both the processing instructions (for HTML and pdf output)
as illustrated (see Bob Stayton DocBook XSL: The Complete Guide)

5. The number of columns MUST be specified, since this helps downstream processing

6. There is a colspec for each column

7. Column alignment is controlled via @align, and can be overridden at the row and entry level as
well

8. The colspec MUST have a @colnum

9. It is prudent to add a @colname, though these are only used for spans

10.The column width is controlled with @colwidth, and MUST take relative values only

11.Column alignment on a particular character requires use of @char and @charoff

202
 Worked examples

12.The table head MUST be in a thead. The style of the head in print is controlled via design
template and is not encoded in the data

13.An entry can take a different @align to override that specified in the colspec

14.The rowsep adds a border to the bottom of the row, though the last row does not need one since
table[@frame=topbot]

15.The source data at the foot of the table is in caption; it MUST NOT be in tfoot

16.There is a page break processing instruction after the table

32.8.1.1. A more complex table

This is a table with column and row spans, and much else.

Notes:

• There are notes in the table with their targets at the bottom of the page

203
 Worked examples

• The borders are significant and add clarity to the content so MUST be encoded

• There are several spans

<table label="3.1" frame="all" xml:id="b542" pgwide="1">

<info xml:id="b541"><title xml:id="b542">India – key demographics</title>
</info>
<tgroup cols="5">
<colspec colnum="1" colname="col1" colsep="0" colwidth="1.2*" />
<colspec colnum="2" colname="col2" colsep="0" colwidth="1.2*" />
<colspec colnum="3" colname="col3" colsep="0" colwidth="1.3*" />
<colspec colnum="4" colname="col4" colsep="0" colwidth="1*" />
<colspec colnum="5" colname="col5" colsep="0" colwidth="1*" />
<tbody>
<row xml:id="b551" rowsep="1">
<entry xml:id="b552" morerows="5"><para xml:id="b553">Population<link role="xref"
linkend="b545"><superscript>a</superscript></link></para></entry>
<entry xml:id="b554"><para xml:id="b555">Persons</para></entry>

<entry xml:id="b556" align="left" namest="col3" nameend="col5"><para xml:id="b557">1,028,737,436</para></

entry>
</row>
<row xml:id="b560" rowsep="0">
<entry xml:id="b562"><para xml:id="b563">Males</para></entry>
<entry xml:id="b564" align="left" namest="col3" nameend="col5"><para xml:id="b565">532,223,090</para></
entry>
</row>
<row xml:id="b568" rowsep="1">
<entry xml:id="b570"><para xml:id="b571">Females</para></entry>
<entry xml:id="b572" align="left" namest="col3" nameend="col5"><para xml:id="b573">496,514,346</para></
entry>
</row>
<row xml:id="b576" rowsep="1">
<entry xml:id="b578" namest="col2" nameend="col5"><para xml:id="b579">Rural–urban distribution<link
role="xref" linkend="b546"><superscript>b</superscript></link></para></entry>
</row>
<row xml:id="b582" rowsep="0">
<entry xml:id="b584"><para xml:id="b585">Rural</para></entry>
<entry xml:id="b586" align="char" char="." namest="col3" nameend="col5"><para xml:id="b587">72.2%</para></
entry>
</row>
<row xml:id="b590" rowsep="1">
<entry xml:id="b592"><para xml:id="b593">Urban</para></entry>
<entry xml:id="b594" align="char" char="." namest="col3" nameend="col5"><para xml:id="b595">27.8%</para></
entry>
</row>
<row xml:id="b598" rowsep="1">
<entry xml:id="b599" morerows="6"><para xml:id="b600">Literacy rate<link role="xref"
linkend="b547"><superscript>c</superscript></link></para></entry>
<entry xml:id="b601" />
<entry xml:id="b602"><para xml:id="b603">Persons</para></entry>
<entry xml:id="b604"><para xml:id="b605">Males</para></entry>
<entry xml:id="b606"><para xml:id="b607">Females</para></entry>
</row>
<row xml:id="b608" rowsep="0">
<entry xml:id="b610"><para xml:id="b611">Total</para></entry>
<entry xml:id="b612" align="char" char="."><para xml:id="b613">64.8%</para></entry>
<entry xml:id="b614" align="char" char="."><para xml:id="b615">75.3%</para></entry>
<entry xml:id="b616" align="char" char="."><para xml:id="b617">53.7%</para></entry>
</row>
<row xml:id="b618" rowsep="0">
<entry xml:id="b619"><para xml:id="b620">Rural</para></entry>
<entry xml:id="b621" align="char" char="."><para xml:id="b622">58.7%</para></entry>
<entry xml:id="b623" align="char" char="."><para xml:id="b624">70.7%</para></entry>
<entry xml:id="b625" align="char" char="."><para xml:id="b626">46.1%</para></entry>
</row>
<row xml:id="b627" rowsep="1">
<entry xml:id="b628"><para xml:id="b629">Urban</para></entry>
<entry xml:id="b630" align="char" char="."><para xml:id="b631">79.9%</para></entry>
<entry xml:id="b632" align="char" char="."><para xml:id="b633">86.3%</para></entry>
<entry xml:id="b634" align="char" char="."><para xml:id="b635">72.9%</para></entry>
</row>
<row xml:id="b636" rowsep="1">
<entry xml:id="b638" align="left"><para xml:id="b639">Mobile phone users</para></entry>
<entry xml:id="b640" align="left" namest="col3" nameend="col5"><para xml:id="b641">827 million<link
role="xref" linkend="b548"><superscript>d</superscript></link> (April 2011)</para></entry>
</row>
<row xml:id="b644" rowsep="1">
<entry xml:id="b646"><para xml:id="b647">Internet users</para></entry>
<entry xml:id="b648" align="left" namest="col3" nameend="col5"><para xml:id="b649">42,000,000<link
role="xref" linkend="b549"><superscript>e</superscript></link> (September 2008)</para></entry>

204
 Worked examples

</row>
<row xml:id="b652" rowsep="0">
<entry xml:id="b654"><para xml:id="b655">Graduates</para></entry>
<entry xml:id="b656" align="left" namest="col3" nameend="col5"><para xml:id="b657">48.7 million (2005)<link
role="xref" linkend="b550"><superscript>f</superscript></link></para></entry>
</row>
</tbody>

</tgroup>
<caption xml:id="c1">
<para xml:id="b545"><superscript>a</superscript> &#x2018;Census Data 2001: India at a Glance:
Population&#x2019;, <!-- Text omitted for clarity -->
</para>
<para xml:id="b546"><superscript>b</superscript> <!-- Text omitted for clarity -->
</para>
<para xml:id="b547"><superscript>c</superscript> <!-- Text omitted for clarity -->
</para>
<para xml:id="b548"><superscript>d</superscript> <!-- Text omitted for clarity -->
</para>
<para xml:id="b549"><superscript>e</superscript> <!-- Text omitted for clarity -->
</para>
<para xml:id="b550"><superscript>f</superscript> <!-- Text omitted for clarity -->
</para>
</caption>
</table>

Commentary:

1. Table has @frame=all which adds borders to all four sides

2. The @pgwide makes the table occupy the full width of the page

3. Use of @colsep=0 to ensure that no column borders are added

4. Small variations in relative @colwidth

5. This table does not have a thead, since there isn’t a row that serves that purpose

6. The @rowsep is used on all the rows to determine if a border should be below it or not

7. The @morerowsspecifies how many extra rows the cell must span

8. The content of the cells is in a para, which can be useful for controlling aspects of the alignment
and other features of the content

9. The note has an explicit link to its target in the caption

10.The note reference is in a superscript

11.The cell at row 1, col 3 spans three columns using the @namest and @nameend, the values of
which MUST match the corresponding colspec[@colname] (alternatively, you can use a
spanspec at the top of the table and reference that)

12.Where the is a row span using @morerows, the rows below MUST have a correspondingly
reduced number of entrys

13.The @rowsep=0 ensures that there is no border below a row

14.A small number of empty entrys may be necessary

15.The notes are all separate paras in the caption, with the para[@xml:id] being the target of the
link[@linkend]

16.The label of the note is encoded in the data within a superscript, with a space afterwards

32.9. Appendices
Appendices can often contain a rag-bag of content which has irregular layout and structure. Some
examples are given below.

205
 Worked examples

32.9.1. Lists and spacing 1

Notes:

• Some odd layouts in the second section

<appendix xml:id="m1" label="A">

<info xml:id="m2">
<title xml:id="m3">Resources for students</title>
<pagenums>195–210</pagenums>
<mediaobject xml:id="m4">
<imageobject xml:id="m5"><imagedata fileref="pdfs/9781609032229.0005.pdf" format="application/pdf"/></
imageobject>
</mediaobject>
</info>
<section xml:id="m6">
<info xml:id="m7">
<title xml:id="m8">Semester-long CBL projects</title>
</info>
<para xml:id="m9">I've included three full semester-long CBL projects...</para>
</section>
<section xml:id="m10">
<info xml:id="m11">

<title xml:id="m12">Community-based learning projects</title>

</info>
<itemizedlist xml:id="m13" mark="none">

206
 Worked examples

<listitem xml:id="m14"><para xml:id="m15"><emphasis role="bold">Student</emphasis>: Danielle Merola</

para></listitem>
<listitem xml:id="m16"><para xml:id="m17"><emphasis role="bold">Project Title</emphasis>: The Sense
Journals</para></listitem>
<listitem xml:id="m18"><para xml:id="mi1"><emphasis role="bold">Community Partner Details</emphasis>:</
para>
<itemizedlist xml:id="m19" mark="none">
<listitem xml:id="m20"><para xml:id="m21">Mr. Bearden</para></listitem>
<listitem xml:id="m22"><para xml:id="m23">(Winegard Elementary, fourth grade)</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para xml:id="m24" role="spaceBefore"><emphasis role="bold">Project Overview</emphasis>: To incorporate the
five sense lessons (sight, smell, sound...</para>
<para xml:id="m25" role="spaceBefore"><emphasis role="bold">Project Goals</emphasis>: I would ideally like
these students to come out of the class...</para>
</section>
</appendix>

Commentary:

1. The first block is effectively a nested list, for which we have to use itemizedlist with
@mark=none

2. Subsequent paragraphs are full out and separate from their siblings, so have
@role=spaceBefore

32.9.2. Lists and spacing 2

Notes:

• Groups of text

<section xml:id="r1">
<info xml:id="r2">
<title xml:id="r3">Week Six: The makings of character #3: Talk to me—character dialogue</title>
</info>
<simplelist xml:id="r4">
<member xml:id="r5">Teacher: Eric Fershtman</member>
<member xml:id="r6">Location: Lakeside Behavioral Healthcare, Orlando, FL</member>
</simplelist>
<simplelist xml:id="r7">
<member xml:id="r8"><emphasis role="bold">Warm-up exercise:</emphasis> (5 minutes)</member>

<member xml:id="r9">At the top of our page we'll complete the prompt:...</member>
</simplelist>
</section>

Commentary:

1. In this instance there are no nested lists, so each group can be accommodated within a
simplelist

207
 Worked examples

32.9.3. Lists and spacing 3

Notes:

• A nested list with significant groupings

<appendix xml:id="y1" label="C">

<info xml:id="y2">

<title xml:id="y3">Additional resources for teachers and students</title>

<pagenums>211–222</pagenums>
<mediaobject xml:id="y4">
<imageobject xml:id="y5"><imagedata fileref="pdfs/9781609032229.0006.pdf" format="application/pdf"/></
imageobject>
</mediaobject>
</info>
<section xml:id="y6">
<info xml:id="y7">
<title xml:id="y8">Websites and links to creative writing in the community projects</title>
</info>
<section xml:id="y9">
<info xml:id="y10">
<title xml:id="y11">Nonprofit organizations and alliances</title>
</info>
<itemizedlist xml:id="y12" mark="none">

208
 Worked examples

<listitem xml:id="y13"><para xml:id="y14">826 National</para>

<itemizedlist xml:id="y15" mark="none">
<listitem xml:id="y16"><para xml:id="y17"><link
xlink:href="http://826national.org"><uri>http://826national.org</uri></link></para>
<para xml:id="y18">826 National is a nonprofit organization that provides strategic leadership,...</para>
</listitem>
</itemizedlist>
</listitem>
<listitem xml:id="y19"><para xml:id="y20">Teachers &amp; Writers Collaborative</para>
<itemizedlist xml:id="y21" mark="none">
<listitem xml:id="y22"><para xml:id="y23"><link xlink:href="http://twc.org"><uri>http://twc.org</uri></
link></para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</section>
</section>
</appendix>

Commentary:

1. All Level 2 headings in this book are italicised so we don’t need to capture that style information in
the title

2. All the data in list can be modelled with the project name as the top level item, and the child
components within a nested list, with the uri in one para and and other information in a sibling
para within the same listitem (ie rather than treat the uri and following para as separate
listitems, which effectively ungroups their relationship)

32.10. Complex and unusual layouts

See also Section 32.14, “Heavily-designed books”

209
 Worked examples

32.10.1. Different fonts in fiction

Notes:

• This looks a bit unusual, but is remarkably simple

<para xml:id="f4"><emphasis role="italic"><emphasis role="sans-serif">hi dylan, itz amir here. r u goin 2

skool 2 mor?</emphasis></emphasis> Amir always started his texts with telling me who they were from even
though I'd told him a billion times that <emphasis role="italic">No Sleep Till Brooklyn</emphasis> meant
that I knew it was him. I even played his message tone to him. He was some man, Amir was.</para>
<para xml:id="f5"><emphasis role="sans-serif">probs, dont want 2 tho</emphasis></para>
<para xml:id="f6"><emphasis role="italic"><emphasis role="sans-serif">dont worry about MM</emphasis></
emphasis></para>

Commentary:

1. Font differences are encoded using emphasis[@role]. Note that this starts both italic and sans-
serif, and that the question mark is included within the span

2. Each line of the conversation is in a para

3. Some may only contain one emphasis

4. Others contain multiple emphasis elements

210
 Worked examples

32.10.2. Linguistic example 1

Notes:

• Numbered examples, and cross references to them

<para xml:id="l4">... is not surprising. The negative marker does not scope either over the N-word or its
copy as shown in (<link role="xref" linkend="l5">61</link>).</para>
<orderedlist xml:id="l5" startingnumber="61">
<listitem xml:id="l7a"><para xml:id="l8">[TP personn [vP <emphasis role="line-through">personn</emphasis>
le [TP mo pa ale]]]</para></listitem>
</orderedlist>

Commentary:

1. Where there are numbered examples, the cross references to them throughout the text are linked

2. We have used orderedlist here. The example element has not been used because that is for
more formal examples with titles. However, the default DocBook behaviour for orderedlist
numbering is to have just the number followed by a stop (“61.”); the output can be changed in
the DocBook customisation layer so it could be rendered as “(61)”. Consequently, it would also be
permissible to mark this up as an informaltable with two cells, one for the number and one for
the content. See also the next example.

3. With orderedlist, it is possible to specify the starting number, or if the numeration continues
from the previous orderedlist, an alternative is to use @continuation="continues"

4. For strike-through, the emphasis element has been used with an appropriate @role

32.10.3. Linguistic example 2

Notes:

• Alignment of the components is essential

• Also includes a list

<orderedlist xml:id="l10" startingnumber="33">

<listitem xml:id="l11">
<orderedlist numeration="loweralpha" xml:id="b-9781474208482-0009475">
<listitem xml:id="l13">

<informaltable xml:id="l14" frame="none">

<tgroup cols="5">
<colspec colnum="1" colname="col1" colwidth="1*" align="left" />

211
 Worked examples

<colspec colnum="2" colname="col2" colwidth="1*" align="left" />

<colspec colnum="3" colname="col3" colwidth="1*" align="left" />
<colspec colnum="4" colname="col4" colwidth="5*" align="left" />
<colspec colnum="5" colname="col5" colwidth="2*" align="left" />
<tbody>
<row><entry xml:id="l15">li</entry><entry xml:id="l16">kapav</entry><entry xml:id="l17">marsse</
entry><entry xml:id="l18">aster.</entry><entry xml:id="l18b">(root)</entry></row>
<row><entry xml:id="l19">he</entry><entry xml:id="l20">can</entry><entry xml:id="l21">walk</entry><entry
xml:id="l22" namest="col4" nameend="col5">now</entry></row>
<row><entry xml:id="l23" namest="col1" nameend="col5">&#x2018;He can walk now&#x2019;</entry></row>
</tbody>
</tgroup>
</informaltable>
</listitem>
<listitem xml:id="l13a">
<informaltable xml:id="l14a" frame="none">
<tgroup cols="5">
<colspec colnum="1" colname="col1" colwidth="1*" align="left" />
<colspec colnum="2" colname="col2" colwidth="1*" align="left" />
<colspec colnum="3" colname="col3" colwidth="1*" align="left" />
<colspec colnum="4" colname="col4" colwidth="5*" align="left" />
<colspec colnum="5" colname="col5" colwidth="2*" align="left" />
<tbody>
<row><entry xml:id="l15a">li</entry><entry xml:id="l16a">kapav</entry><entry xml:id="l17a">dan</
entry><entry xml:id="l18hb">lakaz.</entry><entry xml:id="l18ba">(epistemic)</entry></row>
<row><entry xml:id="l19a">he</entry><entry xml:id="l20a">possible</entry><entry xml:id="l21a">in</
entry><entry xml:id="l22a" namest="col4" nameend="col5">house</entry></row>
<row><entry xml:id="l23a" namest="col1" nameend="col5">&#x2018;It&#x2019;s possible he is in the
house&#x2019;</entry></row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</orderedlist>
</listitem>
</orderedlist>

Commentary:

1. As in the previous example, we have used orderedlist for the example, though it could have
been contained within an informaltable; for a given book, the approach adopted for all such
examples MUST be the same; it would not be right to mix the two

2. There are two examples, numbered “a” and “b”, so we need another orderedlist within the top-
level one, this time with @numeration=lower-alpha to specify the numbering style

3. Then, within each listitem, the layouts are managed within an informaltable, which has all
the row and cell borders switched off

4. Note the various relative @colwidths

5. The second row in each item has a final entry with a column span; since there aren’t any borders
on the cells it would have been permissible to have an empty entry following it instead

6. However, the third row of each listitem must have a column span since its content runs across
the table underneath the content above

7. The second listitem starts and will trigger the automatic numeration (“b.”)

212
 Worked examples

32.11. Poetry
32.11.1. Marginal line numbers, spacing and translation

Notes:

• The text is indented (ie it is a quotation)

• It has very specific layout requirements

• There is a marginal line number

• There is a translation

<para xml:id="q1">In place of the biblical "Song of the Sea" we find the following injunction to the
Israelites, and to his listening and reading audience:</para>
<blockquote xml:id="q2">
<poetry xml:id="q3">
<line xml:id="q4">Wile nu gelæstan&#160;&#160;&#160;&#160;&#160;&#160;þæt he lange gehet</line>
<line xml:id="q5">mid aðsware,&#160;&#160;&#160;&#160;&#160;&#160;engla Drihten,</line>
<line xml:id="q6">in fyrndagum&#160;&#160;&#160;&#160;&#160;&#160;fæderyncynne,<footnote role="margin1"
xml:id="b-9781474208482-0009553"><para xml:id="q8">560</para></footnote></line>
<!-- Text omitted for clarity -->
</poetry>
<para xml:id="q9">The Lord of Angels wishes to fulfill now what He had promised long ago in days of old to
our forefathers...</para>
<!-- Text omitted for clarity -->
</blockquote>
<para xml:id="q10">The passage reiterates the terms of the Sinai Covenant (updated...</para>

Commentary:

1. The text is inset relative to the margin since it is quoted, so is in a blockquote. If this chapter only
contained poetry (ie was not quoted), there would not be a blockquote container

2. There is a light smattering of Unicode for the special characters

213
 Worked examples

3. Unicode non-breaking space characters are used for standard gaps and spaces within text

4. The footnote[@role=margin1] is used for all marginal line numbers. If there were marginal
notes on both sides of the page @role=margin2 would be used for the second series of notes. The
assumption is that no traditional footnote or endnote numbering is automatically generated with
these values of @role

5. The translation text is still within the blockquote container since it is indented and is part of the
quoted text

32.12. References
32.12.1. Archive list
A bibliographic section may sometimes contain a list of archives which have been consulted,
in addition to the books and journals. The contents of such a list are not bibliographic items in
themselves, so bibliomixed MUST NOT be used for this content.

Notes:

• There are two sections in the References chunk: Archival Sources, and then Secondary Sources, the
latter containing the books and journals

• Each archive group starts with the name of the archive, and then the following lines list the
collections referenced from that archive

<chapter xml:id="ba-9781849662932-bibliography-0008">
<info xml:id="ba-9781849662932-0015154">
<title xml:id="ba-9781849662932-0015155"><?page value="358"?>References</title>
<pagenums>358–384</pagenums>
<biblioid class="doi">10.5040/9781472544216.0008</biblioid>
<mediaobject xml:id="ba-9781849662932-0008-001">
<imageobject xml:id="ba-9781849662932-0008-002">
<imagedata fileref="pdfs/9781472544216.0008.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<section xml:id="ba-9781849662932-0015157">
<info xml:id="ba-9781849662932-0015158">
<title xml:id="ba-9781849662932-0015159">Archival Sources</title>

</info>
<para xml:id="ba-9781849662932-0015156">Archives are listed below. Reference details for particular archive
documents are given in the footnotes only.</para>
<itemizedlist xml:id="il1" mark="none">

214
 Worked examples

<info xml:id="il2"><title xml:id="il3">Archiv für die Geschichte der Soziologie in Österreich, Universität
Graz:</title></info>
<listitem xml:id="il4"><para xml:id="il5">Else Frenkel-Brunswik Papers</para></listitem>
<listitem xml:id="il6"><para xml:id="il7">Interview Collection</para></listitem>
<listitem xml:id="il8"><para xml:id="il9">Marie Jahoda Papers</para></listitem>
<listitem xml:id="il10"><para xml:id="il11">Paul F. Lazarsfeld, Microfilms</para></listitem>
</itemizedlist>
<itemizedlist xml:id="ba-9781849662932-0015162" mark="none">
<info xml:id="il12"><title xml:id="il13">Columbia University, Rare Book and Manuscript Library, New York:</
title></info>
<listitem xml:id="il14"><para xml:id="il15">Paul F. Lazarsfeld Papers</para></listitem></itemizedlist>
<!-- Text omitted for clarity -->
</section>
<section xml:id="ba-9781849662932-0015180"><info xml:id="ba-9781849662932-0015181"><title
xml:id="ba-9781849662932-0015182">Secondary Sources</title>
</info>
<bibliolist xml:id="bl1">
<bibliomixed role="monograph" xml:id="ba-9781849662932-0015183"><editor><personname role="last-
first"><surname>Abb</surname><firstname>Gustav</firstname></personname></editor> (ed.) (<pubdate>1930</
pubdate>), <title xml:id="ba-9781849662932-0015184"><emphasis role="italic">Aus fünfzig Jahren
deutscher Wissenschaft. Die Entwicklung ihrer Fachgebiete in Einzeldarstellungen</emphasis></title>,
<address xml:id="ba-9781849662932-0015185"><city>Berlin</city></address>: <publishername>de Gruyter</
publishername>.</bibliomixed>

Commentary:

1. Because the section “Archival Sources” does not contain any bibliographic items (bibliomixed)
the schema does not permit the container element to be a bibliodiv. Therefore, because this
bibliography contains mixed content (ie lists AND bibliographic references) the container element
for the chunk as a whole has to be within a chapter NOT a bibliography so that the necessary
elements are available.

2. This now allows us to use sections for each of the major divisions within the chunk

3. Each archive list needs to be within an itemizedlist, and can take @mark=none, and the
archive name can be within a title in the list

4. The actual bibliography follows in the next section

5. This means that the biblio items have to be contained within a bibliolist

32.13. Page break placement

32.13.1. Page breaks and back-of-book/end-of-chapter
notes
Occasionally a warning such as this may be encountered:

Description: Problem with numbering of page break markers [in chunk

9781849662192.0006.pdf]: at page 241; preceding page no = 237; following page no =

Because back of book and end of chapter notes are placed where the note is called, this means that
there is often no place to put these page breaks that is strictly accurate, since page break markers are
NOT permitted in footnote elements (since it will overly complicate the other tests). So, for this
example:

215
 Worked examples

the page break markers are placed before the corresponding processing instruction insertion point,
which may mean in this case that some page break markers are missing:

<chapter xml:id="ba-9781849662192-backnotes" role="notes">

<info xml:id="ba-9781849662192-backnotes1">
<title xml:id="ba-9781849662192-backnotes2"><?page value="237"?>Notes</title>
<pagenums>237&#x2013;264</pagenums>
<biblioid class="doi">10.5040/9781849662192.0006</biblioid>
<mediaobject xml:id="ba-9781849662192.0006-001">
<imageobject xml:id="ba-9781849662192.0006-002">
<imagedata fileref="pdfs/9781849662192.0006.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<remark xml:id="ba-9781849662192-backnotes3" condition="hidden">Placeholder for back of book note content</
remark>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-009" title="Introduction"?>
<?page value="241"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-001" title="Chapter One"?>
<?page value="245"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-002" title="Chapter Two"?>
<?page value="249"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-003" title="Chapter Three"?>
<?page value="251"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-004" title="Chapter Four"?>
<?page value="255"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-005" title="Chapter Five"?>
<?page value="257"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-006" title="Chapter Six"?>
<?page value="259"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-007" title="Chapter Seven"?>

<?page value="262"?>
<?insert item="end-bk-notes" chunk="ba-9781849662192-chapter-008" title="Conclusion"?>
</chapter>

32.13.2. Footnotes and page breaks

As mentioned in the previous section, page break markers are not allowed in footnote elements. So,
for this example:

216
 Worked examples

it is incorrect for the page break to be placed here:

<para xml:id="ba-9781472542069-0000364" role="fullOut">When laughter is invited or made

relevant as one of a range of possible responses, second laughter routinely gets treated
as affiliative or aligning (<link linkend="ba-9781472542069-1212627">Clarke and Wilkinson,
2009</link>; <link linkend="ba-9781472542069-1212789">O&#x2019;Donnell-Trujillo and Adams,
1983</link>; <link linkend="ba-9781472542069-1212790">Osvaldsson, 2004</link>; <link
linkend="ba-9781472542069-1212846">Schenkein, 1972</link>; <link linkend="ba-9781472542069-1212872">Vöge,
2010</link>).<footnote role="end-ch-note" xml:id="b-9781474208482-0009692"><para
xml:id="ba-9781472542069-0000404">Stivers (2008) distinguishes between aligning and affiliating in
storytelling. Aligned responses support the &#x201C;structural asymmetry of the storytelling activity:
that a <?page value="22"?>storytelling is in progress and that the teller has the floor until story
completion&#x201D; (p. 34). Disaligned responses &#x201C;undermine this asymmetry by competing for the
floor or failing to treat a story as either in progress &#x2013; or at story completion &#x2013; as
over&#x201D; (p. 34). Affiliation concerns the stance taken in the telling. With an affiliative response,
&#x201C;the hearer displays support of and endorses the teller&#x2019;s conveyed stance&#x201D; (p. 35).</
para></footnote>

The marker MUST be placed after the notes insertion point:

<para xml:id="ba-9781472542069-0000398">The chapters that follow reflect the progression we have adopted
in this review chapter. We began with a micro-level focus on laughs themselves, attending to their
commonalities and their varieties. We considered their placements: freestanding, within turns at talk
in different locations, or following talk. We have given considerable attention to laugh sequences
including laughables, laugh invitations, shared laughter, and resistance. We have discussed the ways
that laugh sequences contribute to displays of alignment or resistance, affiliation or disaffiliation.
Finally, attention has been given to the ways that laughter plays a part in the construction of contexts
and identities. Through the organization of laughter, people show themselves to be participating in
different kinds of events and settings. Whether conceived of in terms of institutional role, individual
difference, gender, or nationality, who we are is in no small measure built out of small moments
of laughter&#x2014;distinctively produced, precisely placed, systematic, and specific in what it
accomplishes.</para>
</section>
<?insert item="end-ch-notes" title="Notes"?>
<?page value="22"?>
</chapter>
<part label="1" xml:id="ba-9781472542069-0000406">
<info xml:id="ba-9781472542069-0000175v">
<title xml:id="ba-9781472542069-0000176v"><?page value="23"?>Varieties of Laughter</title>

217
 Worked examples

32.14. Heavily-designed books

At first sight, books that have complex page layouts and designs can appear difficult to fit into
the DocBook model. However, once the layout template has been factored out, the content is often
surprisingly simple, though may need some thinking through to appreciate this. If it is not obvious
how particular features should be modelled in the data, please contact Bloomsbury.

32.14.1. Part divider with quote

<part label="I"><info> <title>Idea</title></info><partintro><epigraph><attribution>Coco Chanel</

attribution><para>&#x2018;Fashion is not something that exists in dresses only. Fashion is in the sky, in
the street, fashion has to do with ideas, the way we live, what is happening.&#x2019;</para></epigraph>...

Commentary

1. Note that the attribution is always the first element (if present) in an epigraph, irrespective of
where it is actually placed in the layout.

218
 Worked examples

32.14.2. Subsequent part content

These are the pages following on from the previous example, and complete the partintro.

<mediaobject><imageobject><imagedata contentwidth="450" fileref="images/fa.jpg" format="image/jpeg&#x201C;/

></imageobject></mediaobject><section><info> <title>Idea / Process</title></info><para><emphasis
role="bold">idea:</emphasis></para><itemizedlist> <listitem><para><emphasis role="bold">a personal opinion
or belief</emphasis></para></listitem> <listitem><para><emphasis role="bold">a thought to be presented as
a suggestion</emphasis></para></listitem> <listitem><para><emphasis role="bold">an impression or knowledge
of something</emphasis></para></listitem> <listitem><para><emphasis role="bold">a concept that exists
in the mind only</emphasis></para></listitem> <listitem><para><emphasis role="bold">a mental image that
reflects reality</emphasis></para></listitem></itemizedlist><para>An idea is the catalyst that begins any
project. The origin...</para><para>Finding the right idea is one thing but...</para></section></partintro>

Commentary:

• The image will also require an @outputformat to determine that it is for web use, and note that it
has a @contentwidth to specify the display width in pixels

219
 Worked examples

32.14.3. Content chunks

This is the style of the main content chunks within each part, and follows on from the previous
example. The header at the top of page 21 provides pointers for the related chunks about the same
piece of work in the other parts of the book. Similarly, the Process box on page 20 summarises the
keywords relating to the chunk in bold, and includes the keywords for the related items from the
other chunks in a lighter font.

The background image on page 20 is decorative only and is not included in the XML.

<chapter>
<info>
<title>Hope for the Future</title>
<subtitle>An investigation into movement and dance, using zero-waste and sustainable methods.</subtitle>
<othername class="other" otherclass="contributor"><personname role="first-last"><firstname>Janelle</
firstname><surname>Abbott</surname></personname></author>
</info>
<sidebar>
<info>
<title>Process</title></info>
<informaltable frame="none"colsep="0" rowsep="0">...</>
</sidebar>
<para>This was Janelle’s final project within her &#x2018;Concepts&#x2019; course during her third year of
study in pursuit of her BFA degree in Fashion Design at Parsons The New School for Design.</para>

Commentary:

1. The chunk title is taken from the right hand page, but the subtitle is on the left

2. The name is not strictly the author of the text, though is the subject of the discussion and the author
of the design works, so othername is used

3. The Process block is set apart from the text in a sidebar. If there are multiple sidebars in a book
that have different semantic function, they can be differentiated using @role

220
 Worked examples

4. The items within the Process sidebar are just a list; and simplelist is adequate for each of the
three columns (so, the informaltable has one row, containing three cells, each of which contains
a simplelist)

32.14.4. Chunk content

Again, this follows on from the text in the previous example, and is regular text with some figures:

<section><info> <title>Where did the idea come from?</title></info><para>Janelle&#x2019;s project began

when her instructor played a song in class...</para> <figure label="1&#x201D;><info><title>1 / 2 / 3
Brush stroke images</title></info><para>Janelle used brush strokes to make connections between....</
para><mediaobject><imageobject><imagedata fileref="images/f1.jpg" format="image/jpeg" contentwidth="350" /
></imageobject></mediaobject></figure><informalfigure label="2&#x201D;><mediaobject><imageobject><imagedata
fileref="images/f2.jpg" format="image/jpeg" contentwidth="275" /></imageobject></mediaobject></
informalfigure>

Commentary:

1. There is only one title for all three figures on the page, so that is contained within a figure//
title, and the other images are just contained within informalfigure, each with @label

2. All images have @contentwidth

32.14.5. Print-specific content

Where books have content that only works in a print context (eg pictures of page layouts elsewhere
within the book) or references to page numbers, alternative versions MUST be provided in the data
for non-print usage. For example:

<sidebar xml:id="sw122323" role="sidebar1">

<para xml:id="dffggf"><emphasis role="bold"> <phrase outputformat="print">Turn to page 84 to see</
phrase> <phrase outputformat="web">See also</phrase> <link linkend="a2">PART II (Concept)</link>

221
 Worked examples

of this project, or <phrase outputformat="print">page 148 for</phrase> <link linkend="a3">PART III

(Design)</link>.</emphasis></para>
</sidebar>

Commentary:

1. The phrase elements ( , ) have been added to enable the switching off of print-
only content for online usage, and some new textual content has been added (within
phrase[@outputformat=web] ), so that the text makes sense for online usage

2. The target section titles are links ( , )

3. For new books it is preferable if the text can be authored in such a way as to be format-neutral

32.15. Geographers Biobibliographical Studies

This series has over thirty volumes and each contains a number of articles about individuals who are
significant in the history of geography as a discipline. As such, they are fairly standard monographs
but include a small number of other features:

1. Series data

2. Cross references to other books in the series

3. Implied authors in the bibliography

32.15.1. Series data

All books in the series MUST have the book title &#x2018;Geographers Biobibliographical
Studies&#x2019;, followed by a volumenum, together with a corresponding series block:

<book role="fullText" xml:id="b-9781234567897" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://

www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<info xml:id="a1">
<title xml:id="a2">Geographers Biobibliographical Studies</title>
<volumenum>32</volumenum>
<!-- Authors here -->
<biblioset role="series" xml:id="a0">
<title role="series" xml:id="s1">Geographers: Biobibliographical Studies</title>
<volumenum role="series">32</volumenum>

</biblioset>

32.15.2. Cross references to other books in the series

Each chapter MAY contain one or more cross references to chapters in other books in the
series. These MUST be constructed as links using olink. This REQUIRES that all chapters
in the books in this series MUST use the chunk IDs as provided by Bloomsbury (see file
GeographersSeriesIDs.xlsx).

Typically, such cross references are flagged in the text:

During the first decade of his publishing career extending from 1882 to 1892, de Margerie
placed his articles, critical notes and reviews almost exclusively in geological journals, but
in 1894 he was invited by Paul Vidal de la Blache (Geographers Vol. 12) to join the editorial
board of the fledgling Annales de Géographie in place of the colonial geographer Marcel
Dubois (Geographers Vol. 30) who had been its co-founder in 1891. Lucien Gallois, a disciple and
colleague of Vidal’s, also joined the board in 1894 and was an obvious choice (Claval 1998, 80)
(on Gallois, see Geographers Vol. 24).

222
 Worked examples

The cross-linking REQUIREMENT is that the following MUST be linked:

1. The volume number in the explicit cross reference; and

2. The first occurrence of the name in the chapter

Where the targetdoc is the target book ID, and the targetptr is the target chunk ID:

<para xml:id="k8">During the first decade of his publishing career extending from 1882 to 1892, de Margerie
placed his articles, critical notes and reviews almost exclusively in geological journals, but in 1894 he
was invited by <olink type="otherBook" targetdoc="b-9780987654321" targetptr="b-9780987654321-001">Paul
Vidal de la Blache</olink> (<emphasis role="italic">Geographers</emphasis> Vol. <olink type="otherBook"
targetdoc="b-9780987654321" targetptr="b-9780987654321-001">12</olink>) to join the editorial
board of the fledgling <emphasis role="italic">Annales de Géographie</emphasis> in place of
the <?page value="36"?>colonial geographer <olink type="otherBook" targetdoc="b-9780987654321"
targetptr="b-9780987654322-002">Marcel Dubois</olink> (<emphasis role="italic">Geographers</emphasis>
Vol. <olink type="otherBook" targetdoc="b-9780987654321" targetptr="b-9780987654322-002">30</
olink>) who had been its co-founder in 1891. <olink type="otherBook" targetdoc="b-9780987654321"
targetptr="b-9780987654323-003">Lucien Gallois</olink>, a disciple and colleague of Vidal’s, also
joined the board in 1894 and was an obvious choice (<link role="bib" linkend="bl2">Claval 1998</link>,
80) (on Gallois, see <emphasis role="italic">Geographers</emphasis> Vol. <olink type="otherBook"
targetdoc="b-9780987654321" targetptr="b-9780987654323-003">24</olink>).</para>

Note that some explicit cross references may include multiple items, so their preceding instances may
be earlier in the paragraph than expected:

<para xml:id="p9">Over the years, de Margerie contributed numerous book reviews to the <emphasis
role="italic">Annales de Géographie</emphasis>, including commentaries on the doctoral monographs
of some of Vidal’s immediate disciples such as <olink type="otherBook" targetdoc="b-9780987654321"
targetptr="b-9780933654321-001">Emmanuel de Martonne</olink> (1873–1955), who researched the
physiography of the Transylvanian Carpathians, and <olink type="otherBook" targetdoc="b-9780987654321"
targetptr="b-9780923654321-005">Antoine Vacher</olink> (1873–1919), who analysed the physical geography
of the province of Berry in central France (De Margerie <link role="bib" linkend="v10">1908a</
link>, <link role="bib" linkend="v15">1909</link>) (on de Martonne and Vacher, see <emphasis
role="italic">Geographers</emphasis> Vols <olink type="otherBook" targetdoc="b-9780987654321"
targetptr="b-9780933654321-001">12</olink> and <olink type="otherBook" targetdoc="b-9780987654321"
targetptr="b-9780923654321-005">31</olink>, respectively).</para>

In addition, books in the series MAY include implicit cross references to named individuals who are
included in subsequent volumes in the series. These will obviously not have any explicit reference,
so as much as possible the first occurrence in any chunk of any name matching one of the list in the
accompanying spreadsheet MUST also be made into a olink.

Implementation note: olink is not supported in DocBook XSL and will need specific handling;
it may have loader implications, since a book in the series could link to any other book in the
series.

See Section 15.8, “Links to other books”.

32.15.3. Implied authors in bibliographies

The bibliographies for each chapter will typically include a list of works by the subject of the chapter.
In which case, typically such author is not named in the bibliographic items and MUST be added as
an implied author. Note also in this example that this particular bibliography adopts an unusual style
as a two-column list, with the year in the first column, and the biblio item in the second:

Selected Bibliography of Works of Emmanuel de Margerie

1908a‘Albert de Lapparent’, Annales de Géographie 17, 344–7.

1909‘La géographie physique du Berry,’ Annales de Géographie 18, 390–406.

223
 Worked examples

This REQUIRES the use of a variablelist, with each biblio item to be within the listitem, and
include an implied pubdate as well as author:

<section xml:id="sec10" label="3">

<info xml:id="sec11">
<title xml:id="sec12">Selected Bibliography of Works of Emmanuel de Margerie</title>
</info>
<variablelist xml:id="v1">
<varlistentry xml:id="v6">
<term xml:id="v7">1908a</term>
<listitem xml:id="v8"><bibliolist xml:id="v9"><bibliomixed role="article"
xml:id="b-9781474208482-0009855"><bibliomset relation="article"><author condition="hidden"><personname
role="first-last"><firstname>Emmanuel</firstname><surname>de Margerie</surname></personname></
author><pubdate condition="hidden">1908</pubdate>&#x2018;<title>Albert de Lapparent</title>&#x2019;</
bibliomset>, <bibliomset relation="journal"><title><emphasis role="italic">Annales de Géographie</
emphasis></title> <volumenum>17</volumenum>, <pagenums>344–7</pagenums></bibliomset>.</bibliomixed></
bibliolist></listitem>
</varlistentry>
<varlistentry xml:id="v11">
<term xml:id="v12">1909</term>
<listitem xml:id="v13"><bibliolist xml:id="v14"><bibliomixed role="article"
xml:id="b-9781474208482-0009860"><bibliomset relation="article"><author condition="hidden"><personname
role="first-last"><firstname>Emmanuel</firstname><surname>de Margerie</surname></personname></
author><pubdate condition="hidden">1909</pubdate>&#x2018;<title>La géographie physique du Berry</
title>,&#x2019;</bibliomset> <bibliomset relation="journal"><title><emphasis role="italic">Annales de
Géographie</emphasis></title> <volumenum>18</volumenum>, <pagenums>390–406</pagenums></bibliomset>.</
bibliomixed></bibliolist></listitem>
</varlistentry>
</variablelist>
</section>

See also the sub-section ‘Section 16.7.10, “Implied authors (books)”’ in Section 16.7, “Books”.

32.16. Hart and Bloomsbury legal texts

32.16.1. Legal content type
All legal books MUST contain a biblioid[@otherclass=legalContentType] with one of the
permitted values. See Section 7.5.11, “Other biblioids”.

32.16.1.1. Looseleaf content

Looseleaf content MUST be identified in the volume metadata using the markup <biblioid
class="other" otherclass="legalBPrOLooseleaf">1</biblioid>.

Note
Bloomsbury will advise where this is the case.

32.16.2. More strict ID rules

With the legal texts it is very useful in the preparation of the data to have predictable IDs for several
elements, especially numbered parts and chapters, and formalparas. See Section 5.2.3, “IDs for chunks”
and Section 5.2.6, “IDs for formal paragraphs”.

32.16.3. Law stated at date

Most legal works other than case reports should contain a ‘Law as stated at’ date. These MUST be
included in book/info,6 and should be displayed in the book metadata block on the site:

<date role="lawStatedAt">10 October 2005</date>

6
Tested in Schematron: lawstatedate-missing

224
 Worked examples

If a date for this field has not been supplied, please contact Bloomsbury.

32.16.4. Legal contents

Legal works tend to include formal tables of cases, statutes, international treaties etc, which are cross
referenced to the relevant location in the book.

See Section 10.5, “Tables of cases and statutes”.

The main issue with these is that they are structurally more complex than may at first appear,
especially tables of statutes which have sophisticated layout requirements, with implied content, as in
the following example. Note how the ‘s’ of the section numbers align, but if the ‘s’ is omitted, then the
number aligns, and if that is omitted then the subsection aligns:

This is achieved using nested variablelists and @condition=hidden:

<variablelist xml:id="djdu7">
<varlistentry>
<term xml:id="jfu7">Access to Justice Act 1999</term>
<listitem xml:id="kfi8s">
<variablelist xml:id="dod93">
<varlistentry>
<term xml:id="fe66d">s 6(8)</term>
<listitem xml:id="dlod93">
<para xml:id="dkd63">
<link linkend="fp1-01" role="xref">1.01</link>
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term xml:id="fkfi8">Alcoholic Liquor Duties Act 1979</term>
<listitem xml:id="kfi8ss">
<para xml:id="d973">
<link linkend="fp1-01" role="xref">1.01</link>
</para>
<variablelist xml:id="dsy36n">
<varlistentry>
<term xml:id="ssk3">s 8</term>
<listitem xml:id="d9d9d">
<para xml:id="dkdd9s">
<link linkend="fp1-01" role="xref">1.01</link>
</para>
</listitem>
</varlistentry>
<varlistentry>

225
 Worked examples

<term xml:id="dkddu"><phrase condition="hidden">s 8</phrase>(4)</term>

<listitem xml:id="did83">
<para xml:id="dd98">
<link linkend="fp1-02" role="xref">1.02</link>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term xml:id="d84jsa"><phrase condition="hidden">s</phrase> 10</term>
<listitem xml:id="djdu7s">
<para xml:id="ksi83a">
<link linkend="fp1-01" role="xref">1.01</link>

</para>
</listitem>
</varlistentry>
<varlistentry>
<term xml:id="dkdid84s"><phrase condition="hidden">s 10</phrase>(4)</term>
<listitem xml:id="ddkd9ssa">
<para xml:id="s9slq">
<link linkend="fp1-01" role="xref">1.01</link>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term xml:id="ddkddj53"><phrase condition="hidden">s</phrase> 11</term>
<listitem xml:id="ddd8756l">
<para xml:id="dld0987">
<link linkend="fp1-02" role="xref">1.02</link>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term xml:id="shs73p"><phrase condition="hidden">s 11</phrase>(3)</term>
<listitem xml:id="ploki48">
<para xml:id="dodd9">
<link linkend="fp1-01" role="xref">1.01</link>
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
</variablelist>

Implementation note: The fine rendering of this is not supported in DocBook XSL.

32.16.5. Numbered paragraphs

Most legal monographs have numbered paragraphs to facilitate cross referencing. These may be in a
variety of styles, though are usually placed in the margin on the page. The number of the para MUST
be included in the info/title, and any heading within the paragraph simply marked as bold (or
whatever the heading style is):

<formalpara xml:id="bp-9781234567890-fp1.01">
<info xml:id="djdid">
<title xml:id="lk98">1.01</title>
</info>
<para xml:id="dj87"><emphasis role="bold">Subject matter of the book.</emphasis> The subject matter of this
book is the rules governing the voluntary inter vivos assignment of contractual rights. Such transactions
involve the transfer of a contractual right from the owner (assignor) to the transferee (assignee).
The person bound to perform the correlative obligation is either (in the case of a debt) the debtor or
(in the case of some other contractual performance obligation) the obligor. Assignments of contractual
rights form an important area of commercial practice. Despite this, in terms of legal publications, the
assignment of contractual rights is an area that has received little attention. Recently it was described
as &#x201C;undeveloped&#x201D;.</para>
</formalpara>

Implementation note: DocBook XSL renders the title inline; if a marginal position is required a
front end change will be required.

226
 Worked examples

See Section 14.1.3, “Formal paragraphs”, and Section 18.2.3, “End of paragraph notes”.

32.16.6. Numbered lists in legal books

Numbered lists in legal texts can be unusually complex, with many levels of nesting and
(importantly) irregular numeration that cannot be handled using regular orderedlist/
@startingnumber. For example, note the item '(6A)' in the following example:

In addition, the formatting of the numbering is often very important since it may need to exactly
follow the style of published legislation, ie surrounded by brackets in the example above.

For this reason, legal books (those with a biblioid[@otherclass=legalContentType]) MUST

use variablelist to encode these numbered lists, with the numeration captured in the data in a
term exactly as it must appear:7

<variablelist>
<varlistentry>
<term>(5)</term>
<listitem>
<para>References in sections 404 to 404B to a relevant firm include—</para>
<variablelist>
<varlistentry>
<term>(a)</term>
<listitem>
<para>a person who was at any time a relevant firm but has subsequently ceased to be one; and</para>
</listitem>
</varlistentry>

<varlistentry>
<term>(b)</term>
<listitem>
<para>a person who has assumed a liability (including a contingent one) incurred by a relevant firm in
respect of a failure by the firm to comply with a requirement applicable to the carrying on by it of any
activity.</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>

7
Tested in Schematron: legal-lists

227
 Worked examples

<term>(6)</term>
<listitem>
<para>References in those sections to the carrying on of an activity by a relevant firm are, accordingly,
to be read in that case with the appropriate modifications.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>(6A)</term>
<listitem>
<para>References in sections 404 and 404E to an &#x201C;electronic money issuer&#x201D; are references to a
person mentioned in paragraph (a), (b), (c), (d), (h) or (i) of the definition of &#x201C;electronic money
issuer&#x201D; in regulation 2(1) of the Electronic Money Regulations 2011.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>(7)</term>
<listitem>
<para>If the Authority varies a permission or authorisation of a person so as to impose requirements on
the person to establish and operate a scheme which corresponds to, or is similar to, a consumer redress
scheme, the provision that may be included in the permission or authorisation as varied includes—</para>
<variablelist>
<varlistentry>
<term>(a)</term>
<listitem>
<para>provision imposing requirements on the person corresponding to those that could be included in rules
made under section 404; and</para>
</listitem>
</varlistentry>
<varlistentry>
<term>(b)</term>
<listitem>
<para xml:id="b-9781474201124-0021468">provision corresponding to section 404B.</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
</variablelist>

32.16.7. Case Reports

A volume of Case Reports MUST be identified using book/info/
biblioid[@otherclass='legalContentType'] = 'cases'. Most of the semantic markup
can be identified from the styles in the source. See the accompanying 'Bloomsbury Legal Case
Reports: Style mapping', which is available from Bloomsbury if required.

See also: Section 14.13, “Notes”

<chapter xml:id="b-9781849664554-001">
<info xml:id="b-9781849664554-0000097">

<title xml:id="b-9781849664554-0000098"><?page value="65"?><phrase role="caseName">Re X and others

(deprivation of liberty) (nos 1 and 2)</phrase></title>
<pagenums>65–118</pagenums>
<biblioid class="doi">10.5040/9781849664554.001</biblioid>
<biblioid class="other" otherclass="courtCode">CA</biblioid>
<biblioid class="other" otherclass="shortCourtName">CA</biblioid>
<biblioid class="other" otherclass="decisionDate">2015-06-15</biblioid>
<biblioid class="other" otherclass="shortCaseName">Re X</biblioid>
<biblioid class="other" otherclass="caseCitation">[2016] 1 FCR 65</biblioid>
<mediaobject xml:id="b-9781849664554-chapter-001c">
<imageobject xml:id="b-9781849664554-chapter-001d">
<imagedata fileref="pdfs/9781849664554.001.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<para xml:id="b-9781849664554-0000099a" role="caseNumber">[2015] EWCA Civ 599</para>
<para xml:id="b-9781849664554-0000099" role="court">Court of Appeal, Civil Division</para>
<para xml:id="b-9781849664554-0000100" role="panel">Moore-Bick VP, Black and Gloster LJJ</para>
<para xml:id="b-9781849664554-0000101" role="hearingDate">16 June 2015</para>
<para xml:id="b-9781849664554-0000102" role="catchwords">
<emphasis role="italic">Procedure – Court of Protection – Decision – Appellate jurisdiction – President
of Court of Protection delivering judgments containing general guidance on procedure in deprivation
of liberty cases – Procedural issues not being live in cases before President – Whether President
having jurisdiction – Whether Court of Appeal having jurisdiction to hear appeals – Meaning of
&#x2018;decision&#x2019; – Mental Capacity Act 2005, s 53(1), Court of Protection Rules 2007, SI
2007/1744.</emphasis>

228
 Worked examples

</para>
<note xml:id="b-9781849664554-0000103a" role="facts"><para xml:id="b-9781849664554-0000103">In order
to address an anticipated increase in the number of cases involving authorisations of deprivation of
liberty (&#x2018;DoL&#x2019;) under the Mental Capacity Act 2005 following the Supreme Court’s decision
in <emphasis role="italic">P v Cheshire West and Chester Council, P v Surrey CC</emphasis> [2014] 2 FCR
71, and the practical and procedural implications of that decision,... guaranteed by art 5<footnote
xml:id="b-9781849664554-0000103b" label="a"><para xml:id="b-9781849664554-0000103c">Article 5, so far as
material, is set out at <link linkend="b-9781849664554-0000114g" role="xref">[31]</link>, below.</para></
footnote> of the European Convention for the Protection of Human Rights and Fundamental Freedoms 1950...</
para></note>
<note xml:id="b-9781849664554-0000104a" role="holding">
<para xml:id="b-9781849664554-0000104"><emphasis role="bold">Held</emphasis> – Upon a proper construction
of the 2005 Act and the 2007 Rules, and considering the general context of applications under the Act,
those responsible for drafting s 53(1) had not intended the word &#x2018;decision&#x2019; to have the
special, wider meaning for which the parties contended...</para></note>
<bridgehead renderas="sect1" xml:id="b-9781849664554-0000108c">Cases referred to</bridgehead>
<bibliolist xml:id="b-9781849664554-0000108d">
<bibliomixed role="case" xml:id="b-9781849664554-0000108e"><emphasis role="italic">A (A Patient) (Court of
Protection: Appeal), Re</emphasis> [2013] EWCA Civ 1661, [2014] 1 WLR 3773.</bibliomixed>
<bibliomixed role="case" xml:id="b-9781849664554-0000108f"><emphasis role="italic">A-G v Lord Hotham</
emphasis> (1827) 3 Russ 415.</bibliomixed>
</bibliolist>
<note xml:id="b-9781849664554-0000109" role="history">
<bridgehead renderas="sect1" xml:id="b-9781849664554-0000109b">Appeals</bridgehead>
<para xml:id="b-9781849664554-0000109c">AC, GS and the Law Society of England and Wales appealed from
two judgments of the President of the Court of Protection, Sir James Munby, of 7 August 2014 (<emphasis
role="italic">Re X (deprivation of liberty) (no 1)</emphasis> [2014] EWCOP 25, [2015] 2 FCR 15, [2015] 2
All ER 1154) and 16 October 2014 <emphasis role="italic">Re X (deprivation of liberty) (no 2)</emphasis>
[2014] EWCOP 37, [2015] 2 FCR 28, [2015] 2 All ER 1165). The Secretary of State for Health and the
Secretary of State for Justice also appeared and the Official Solicitor intervened. The facts are set out
in the judgment of Black LJ.</para>
</note>
<para xml:id="b-9781849664554-0000110" role="legalRepresentation"><emphasis role="italic">Nathalie
Lieven QC</emphasis> and <emphasis role="italic">Katie Scott</emphasis> (instructed by <emphasis
role="italic">Irwin Mitchell LLP</emphasis>) for AC and GS.</para>
<para xml:id="b-9781849664554-0000110d" role="judgmentDate">16 June 2015. The following judgments were
delivered.</para>
<note xml:id="b-9781849664554-0000110e" role="judgment">
<para xml:id="b-9781849664554-0000110f" role="judgmentBy">Black LJ.</para>
<formalpara xml:id="b-9781849664554-0000110g"><info xml:id="b-9781849664554-0000110h">
<title xml:id="b-9781849664554-0000110i">[1]</title>
</info><para xml:id="b-9781849664554-0000110j">This appeal concerns the practice and procedure to be
adopted in applications to the Court of Protection in deprivation of liberty cases...</para></formalpara>
<bridgehead xml:id="b-9781849664554-0000110k" renderas="sect1">The process leading to the President’s
judgments</bridgehead>
<formalpara xml:id="b-9781849664554-0000111g"><info xml:id="b-9781849664554-0000111h">
<title xml:id="b-9781849664554-0000111i">[4]</title>
</info><para xml:id="b-9781849664554-0000111j">In view of the unusual path that matters took in front of
the President, I need to look in a little detail at what occurred before him.</para></formalpara>
<bridgehead xml:id="b-9781849664554-0000112k" renderas="sect2">(a) The President’s description of the
process</bridgehead>
<formalpara xml:id="b-9781849664554-0000112g"><info xml:id="b-9781849664554-0000112h">
<title xml:id="b-9781849664554-0000112i">[5]</title>
</info><para xml:id="b-9781849664554-0000112j">A good starting point is the President’s own description of
the exercise upon which he was engaged....&#x2019;</para>
</blockquote>
</formalpara>
<bridgehead xml:id="b-9781849664554-0000114k" renderas="sect2">(c) Section 53 Mental Capacity Act 2005</
bridgehead>
<formalpara xml:id="b-9781849664554-0000114g"><info xml:id="b-9781849664554-0000114h">
<title xml:id="b-9781849664554-0000114i">[31]</title>
</info><para xml:id="b-9781849664554-0000114j">I start with the parties’ proposed answer to the
jurisdiction question, namely s 53 of the MCA 2005. This sets out the rights of appeal in cases under the
Act...</para></formalpara>
<note xml:id="b-9781849664554-0000112l" role="disposition"><para
xml:id="b-9781849664554-0000112m"><emphasis role="italic">Order accordingly</emphasis></para></note>
</note>
</chapter>

Commentary:

1. A Case Report MUST be within a chapter, but MUST NOT use @label

2. The case name is within the chapter/info/title, and the case name MUST be in a
phrase[@role='caseName']

3. Various metadata components MAY be identified in the chapter/info. Note that the
decisionDate MUST be in ISO date format

229
 Worked examples

4. The first few paragraphs of content MAY also be identified with a semantic @role. The
catchwords (keywords) are typically italicised before the main body of the content

5. The first main section of the text comprises the Facts of the Case, and should be identifiable from
the source; it is contained within a note[@role='facts']

6. Likewise the holding section typically starts with the word 'Held' in bold, and should also be
within a semantic note[@role='holding']

7. Note that if note elements are included within a Case Report the section element MUST NOT
be used to model the headings and their content (since it is not permitted in the content model).
Consequently, if there are any headings in the content (either as a direct child of the chapter, or
within a note, they MUST be marked up using bridgehead and the correct @renderas value

8. All cases in the bibliography MUST be encoded as bibliomixed[@role='case']

9. Paragraphs marking up the legalRepresentation and judgmentDate MAY also be necessary

10.Each judgment should be in its own note[@role='judgment']

11.And the name of the judge delivering it within a para[@role='judgmentBy']

12.Numbered paragraphs within a Case Report MUST use the formalpara element

13.The final disposition can be marked up with note[@role='disposition']

Implementation note: DocBook XSL does not handle any chapter/info/biblioid content,
so if this is required to be displayed or handled in any way it will need additional support.

Furthermore, the default DocBook XSL handling of note will need to be amended, and the
para elements with these case-specific @role values MAY require special styling (eg full-out
and bold)

32.16.8. Annotated legislation

A volume of annotated legislation MUST be identified using book/info/
biblioid[@otherclass='legalContentType'] = &#x2018;legislation&#x2019;.
Most of the semantic markup can be identified from the styles in the source. See the accompanying
'Bloomsbury Annotated Legislation: Style mapping', which is available from Bloomsbury if required.

See also: Section 5.2.7, “IDs for annotated legislation”, Section 14.13, “Notes”

<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"

xml:lang="en" xml:id="b-9781782257004" role="fullText">
<info xml:id="b-9781782257004-d1e4">
<title xml:id="b-9781782257004-d1e6">Tax Acts: 2016</title>
<!--Content omitted for clarity-->
<biblioid class="other" otherclass="legalContentType">legislation</biblioid>
<biblioid class="other" otherclass="legalJurisdiction">ie</biblioid>
</info>
<chapter xml:id="PCTA1927">
<info xml:id="b-9781782257004-d1e868">
<title xml:id="b-9781782257004-d1e870">Provisional Collection of Taxes Act 1927</title>
<pagenums>12–13</pagenums>
<biblioid class="doi">10.5040/9781782257004.004</biblioid>
<biblioid class="other" otherclass="legalDivType">statute</biblioid>
<mediaobject xml:id="b-9781782257004-004c">
<imageobject xml:id="b-9781782257004-004d">
<imagedata fileref="pdfs/9781782257004.004.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<para xml:id="b-9781782257004-d1e874">(1927 Number 7)</para>
<variablelist xml:id="b-9781782257004-d1e877">

230
 Worked examples

<varlistentry xml:id="b-9781782257004-d1e879vle"><term xml:id="b-9781782257004-d1e879term">1</

term><listitem xml:id="b-9781782257004-d1e879">
<para xml:id="b-9781782257004-d1e884"><link role="xref" linkend="PCTA1927s1">Definitions</link></para>
</listitem></varlistentry>
<varlistentry xml:id="b-9781782257004-d1e888vle"><term xml:id="b-9781782257004-d1e888term">2</
term><listitem xml:id="b-9781782257004-d1e888">
<para xml:id="b-9781782257004-d1e893"><link role="xref" linkend="PCTA1927s2">Certain resolutions to have
statutory effect</link></para>
</listitem></varlistentry>
<varlistentry xml:id="b-9781782257004-d1e897vle"><term xml:id="b-9781782257004-d1e897term">3</
term><listitem xml:id="b-9781782257004-d1e897">
<para xml:id="b-9781782257004-d1e902"><link role="xref" linkend="PCTA1927s3">Application of general taxing
enactments</link></para>

</listitem></varlistentry>
</variablelist>
<section xml:id="PCTA1927s1" label="1">
<info xml:id="b-9781782257004-d1e970">
<title xml:id="b-9781782257004-d1e975">Definitions</title>
<biblioid class="other" otherclass="legalDivType">section</biblioid>
</info>
<para xml:id="b-9781782257004-d1e979">In this Act—</para>
<para xml:id="b-9781782257004-d1e982">the expression <emphasis role="bold">&#x201C;Committee on
Finance&#x201D;</emphasis> means the Committee on Finance of Dáil Éireann when and so long as such
Committee is a committee of the whole House;</para>
<para xml:id="b-9781782257004-d1e988">[the expression <emphasis role="bold">&#x201C;new tax&#x201D;</
emphasis> when used in relation to a resolution under this Act means a tax which was not in force
immediately before the date on which the resolution is expressed to take effect or, where no such date is
expressed, the passing of the resolution by Dáil Éireann;]<superscript>1</superscript></para>
<para xml:id="b-9781782257004-d1e996">the expression <emphasis role="bold">&#x201C;permanent tax&#x201D;</
emphasis> means a tax which was last imposed without any limit of time being fixed for its duration;</para>
<para xml:id="b-9781782257004-d1e1003">the expression <emphasis role="bold">&#x201C;temporary tax&#x201D;</
emphasis> means a tax which was last imposed or renewed for a limited period only;</para>
<para xml:id="b-9781782257004-d1e1009">the expression <emphasis role="bold">&#x201C;normal
expiration&#x201D;</emphasis> when used in relation to a temporary tax means the end of the limited period
for which the tax was last imposed or renewed;</para>
<para xml:id="b-9781782257004-d1e1015">[the word <emphasis role="bold">&#x201C;tax&#x201D;</emphasis>
means any customs duty, excise duty, income tax, value-added tax, capital gains tax, corporation
tax, gift tax, inheritance tax, residential property tax, stamp duty, parking levy[, local property
tax]<superscript>2</superscript> or any other levy or charge for the purposes of this Act, for the benefit
of the Exchequer.]<superscript>3</superscript></para>
<note role="annotations" xml:id="b-9781782257004-d1e1028bh1a">
<bridgehead renderas="sect3" xml:id=""b-9781782257004-d1e1028bh1">Amendments</bridgehead>
<para xml:id="b-9781782257004-d1e1034"><superscript>1</superscript> Definition of &#x201C;new tax&#x201D;
substituted by FA 2002, s 139(<emphasis role="italic">a</emphasis>) with effect from 25 March 2002.</para>
<para xml:id="b-9781782257004-d1e1042"><superscript>2</superscript> Inserted by Finance (Local Property
Tax) Act 2012, s 159(1) with effect from 1 January 2013 (by virtue of the Finance (Local Property Tax) Act
2012).</para>
<para xml:id="b-9781782257004-d1e1047"><superscript>3</superscript> Definition of &#x201C;tax&#x201D;
substituted by FA 2010, s 160 with effect from 3 April 2010.</para></note>
</section>
</chapter>
</book>

Commentary:

1. Annotated legislation volumes MUST have legalContentType=legislation8

2. The jurisdiction for the legislation MUST be included in legalJurisdiction9

3. Each statute or other legal instrument (Statutory Instrument, Regulation, Order, Directive etc)
MUST be within a chapter. This means that all layers in the book hierarchy above it MUST be
in parts.10 Note that the @xml:id does not follow the usual standard format, but instead adopts
a unique abbreviation for the item. These values will be supplied by Bloomsbury and should be
enforced in the schematron

4. A statute chapter REQUIRES a legalDivType=statute

5. Typically, a statute starts with a table of content listing all the sections in the Act. This MUST
reflect accurately the structure and content of the Act, and each heading MUST be a link to the
corresponding section
8
Tested in Schematron: legislation-required
9
Tested in Schematron: jurisdiction-required, jurisdiction-values, jurisdiction-location
10
Tested in Schematron: legislation-chapter

231
 Worked examples

6. The internal structure of an Act or other legal instrument MUST be modelled using sections,
with a predictable @xml:id starting with the chapter/@xml:id, and ending with the section/
@label. In between there will be a text string determined by the value of the legalDivType (in
this case 's', since it is a legalDivType=section)

7. The legalDivType=section indicates that this section is a Section in the Act. Other possible
values include chapter or part, which also informs the ID structure, eg 'TCA1997pt8ch4'11

8. The notes section at the end of a Section MUST be wrapped in a note[@role=annotations]

9. Headings within the note MUST be encoded as bridgehead[@renderas=sect3]

Implementation note: The default DocBook XSL handling of note will need to be amended

32.17. Biology and natural history works with

taxonomic content
The content of some books is organised taxonomically and are not broken into conventional ‘chapter’
chunks. This may take the form of a book on birds, in which each content chunk is about a different
species (see the simple example in Section 14.11, “Natural history and biology content”). In other cases,
the structure of the book may follow the deeply-nested biological taxonomy, as in the following
example from The Mammals of Africa:

In practice, there may be up to thirteen nested layers of content within the taxonomic tree within the
content:

1. Class: Mammalia

2. Supercohort: Afrotheria

3. Cohort: Paenungulata

4. Order: Hyracoidea

5. Family Procaviidae

6. Genus: Dendrohyrax

7. Species: Dendrohyrax arboreus

Each such layer in the tree is called a taxon (pl: taxa). Some other taxonomic layers may also be
present in some cases, eg Super-order etc. Each such layer type (Class, Order, Genus, Species, etc) is
called the Taxon Rank.

[If other Taxon Ranks are required (eg Divisions for plants), please contact Bloomsbury to ensure the
necessary changes are made to the schematron]

It is proposed that the species content is encoded as a DocBook chapter, and all the parent content
as part[partintro].

Sample data is is available.

32.17.1. Structure of chunks

In this book, each content chunk typically has the following features:
11
Tested in Schematron: legislation-divisions, legislation-divisions-location, legislation-section,
legislation-label

232
 Worked examples

1. A title comprising:

a. Taxon Rank (“Family”)

b. Taxon Name (“Elephantidae”) (ie the Latin/scientific name)

c. English name

2. A reference giving the taxonomic authority, ie an abbreviated form of the bibliographic details of
when the taxon was first described

3. It may contain a short table listing its child taxa

4. It then contains regular paragraphs, sections, bibliographic short form references (to be linked to
their full forms in the bibliography), images etc

5. And finishes with the names of the authors of the chunk

A species chunk is slightly different:

233
 Worked examples

1. It does not explicitly contain a Taxon Rank (ie “Species”)

2. It may contain one or more additional English names (in brackets)

3. It usually includes a subtitle containing French and German names for the animal

4. An image of the animal may appear before the heading

32.17.2. High-level data requirements

1. Each taxon division MUST be a content chunk

2. The implicit hierarchy of the content MUST be explicitly represented in the structure of the parts.
This is best assessed by looking at the book’s table of contents, and remembering that sibling
nodes should have the same Taxon Rank

3. A species-level chunk MUST be captured as a chapter, and each parent chunk as a part

4. The corresponding pdf of the chunk MUST only include the text and images for that chunk, ie it
MUST blank out the content from any preceding or following chunk on the page

5. Some additional markup is REQUIRED, as detailed in the following section

32.17.3. Biology-specific markup

The following additional mark-up is REQUIRED:

<chapter xml:id="b-9781234567897-0001">
<info xml:id="akya8">

234
 Worked examples

<title xml:id="strsi"><phrase role="taxonName"><emphasis role="italic">Loxodonta africana</emphasis></

phrase> <phrase role="taxonEnglish">Savanna Elephant</phrase> (<phrase role="taxonEnglish">African Bush
Elephant</phrase>)</title>
<subtitle xml:id="djd8d">Fr. <foreignphrase role="taxonForeign" xml:lang="fr">Elephant d’Afrique</
foreignphrase>; Ger. <foreignphrase role="taxonForeign" xml:lang="de">Afrikanischer Elefant</
foreignphrase></subtitle>
<authorgroup>
<author>
<personname role="first-last">
<firstname>Joyce</firstname>
<surname>Poole</surname>
</personname>
</author>
<author>
<personname role="first-last">
<firstname>Paula</firstname>
<surname>Kahumbu</surname>
</personname>
</author>
<author>
<personname role="first-last">
<firstname>Ian</firstname>
<surname>Whyte</surname>
</personname>
</author>
</authorgroup>
<pagenums>181–194</pagenums>
<biblioid class="doi">10.5040/9781234567897.0013</biblioid>
<biblioid class="other" otherclass="taxonRank">species</biblioid>
<mediaobject xml:id="ofrgb">
<imageobject xml:id="ogf10b">
<imagedata fileref="pdfs/9781234567897.0013.pdf" format="application/pdf"/>
</imageobject>
</mediaobject>
</info>
<para xml:id="kfiss" role="taxonAuthority"><emphasis role="italic">Loxodonta africana</emphasis>
Blumenbach, 1797. Handb. Naturgesch., 5th Ed., p. 125. Restricted to the Orange River, South Africa, by
Pohle (1926).</para>
<-- Insert header image here -->
<section xml:id="juu">
<info xml:id="loi86">
<title xml:id="hdjd84">Taxonomy</title>
</info>
<para xml:id="dkdi98">The colonial era brought a profusion of claims of different races of
African elephants (see genus profile). Ansell (1974) recognized four subspecies within his
<emphasis role="italic">africana</emphasis> section (see also Laursen &amp; Bekoff 1978, Spinage
1994), but their validity is doubtful. Shoshani (2005) recognized a single monotypic species.
Synonyms: <emphasis role="italic">angolensis</emphasis>, <emphasis role="italic">berbericus</
emphasis>, <emphasis role="italic">capensis</emphasis>, <emphasis role="italic">cavendishi</
emphasis>, <emphasis role="italic" >cornaliae</emphasis>, <emphasis role="italic">hannibali</
emphasis>, <emphasis role="italic">knochenhaueri</emphasis>, <emphasis role="italic">mocambicus</
emphasis>, <emphasis role="italic">orleansi</emphasis>, <emphasis role="italic">oxyotis</emphasis>,
<emphasis role="italic">peeli</emphasis>, <emphasis role="italic">pharaohensis</emphasis>,
<emphasis role="italic">rothschildi</emphasis>, <emphasis role="italic">selousi</emphasis>,
<emphasis role="italic">toxotis</emphasis>, <emphasis role="italic">typicus</emphasis>, <emphasis
role="italic">zukowskyi</emphasis>. Chromosome number: 2n = 56; the normal karyotype has 25 acrocentric/
telocentric and two metacentric/submetacentric autosomal pairs. The X chromosome is a large submetacentric;
the Y chromosome is small and acrocentric (Hungerford et al. 1966, Wallace 1978, Houck et al. 2001).</
para>

1. The content of title and subtitle has granular content to encode the taxon name and other
language variants. For chunks other than species, the taxon rank MUST also be marked up (see
accompanying sample data)

2. The taxonName must ONLY include the taxon name; it MUST NOT include terminal
punctuation or other names. For species, typically this will be ONLY the portion in italics, and
MUST NOT include the authority name which often follows the taxon name. If this is not clear,
please request further examples

3. The authors of the chunk are listed in the chunk info, not at the end of the chunk

4. The pagenums will generate overlapping page ranges [the schematron may need to be improved to
avoid false positives in this context]

5. There is a new biblioid that is REQUIRED, which records the taxon rank, even in those cases
where (like here) it is not explicitly recorded in the title

235
 Worked examples

6. If there is an image that appear above the title, it MUST be placed as the first element after the
taxon authority

7. The first para of most chunks takes a new @role to indicate that it is a bibliographical reference
for the authority who first described the taxon.

Implementation note: Special formatting may be required for taxon name, taxon rank, taxon
authority etc, and linking to external biological databases could be supported

236
Chapter 33. Series names
The following list is the definitive list of all Bloomsbury series names. This list will be added to
as new series are created. If a book has a series name that is not included herein, please contact
Bloomsbury immediately.

10 Minute Spelling Tests 100 Great Recipes

100 Ideas for Teachers 100 Ideas for the Early Years
100% New Developing Literacy 100% New Developing Mathematics
101 Drills 101 Essential Lists
101 Things 1 KBW on
21st Century Genre Fiction 21st Century Music Practices
21st Century Turning Points 33 1/3
33 1/3 Brazil 33 1/3 Europe
33 1/3 Japan 33 1/3 Oceania
50 Fantastic Things 50 Fantastic...
50 Ways to Improve Your... 69 series
A & C Black Assembly Packs A & C Black Mini-musicals
A & C Black Musical Licences A & C Black Musicals
A & C Black Whiteboard Songs A Court of Thorns and Roses
A Criminal History of Britain A Good Country
A Konrad Simonsen Thriller A Lesson For Every Day
A Maggie Brooklyn Mystery A Modern History of Politics and Violence
A Newbery Honor book A Perfect Chemistry Novel
A Robyn Hoodlum Adventure A Spike Sanguinetti Novel
A User's Guide to... Series A Whole Nother Story
A World View of Social Issues ABC-CLIO Literary Companion
ABC-CLIO Supreme Court Handbooks Abigail Iris
Abitare Annuals Abnormal Psychology
Abracadabra Brass Abracadabra Guitar
Abracadabra Piano Abracadabra Recorder
Abracadabra Strings Abracadabra Strings Beginners
Abracadabra Woodwind ACB Originals
Access to Knowledge Accredited Institutions of Postsecondary
Education
Ace Place ACE/Praeger Series on Higher Education
Across the Aisle Across the Curriculum: Geography
Across the Curriculum: Science Active Every Day
Activity Books For Boys Activity Books For Girls
Adlard Coles Book of Adlard Coles Manuals
Adlard Coles Maritime Classics Adult Learning, Literacy and Social Change
Advances in Applied Developmental Psychology Advances in Applied Linguistics
Advances in Behavioral Economics Advances in Child Development Within Culturally
Structured Environments
Advances in Communication and Culture Advances in Comparative Psychology
Advances in Digital Language Learning and Advances in Discourse Processes
Teaching
Advances in Experimental Philosophy Advances in Foreign and Second Language
Pedagogy
Advances in Infancy Research Advances in Instructed Second Language
Acquisition Research
Advances in Organization Development Advances in Sociolinguistics
Advances in Stylistics Advances in Teacher Education
Advances in Visual Cognition Adventures Abroad
Adventures of a Young Sailor Aerospace Management & Law
Aesthetics and Contemporary Art Affirming Catholicism
Africa in Focus African American Religious Thought and Life

237
 Series names

African Special Bibliographic Series Aga and Range Cookbooks

Air Campaign Air Vanguard
Aircraft of the Aces Akimbo
Alfred Kropp All Things
Almond Press Individual Titles Also Known As
Alternate Takes: Critical Responses to Popular Alternative | Education
Music
Alternative Energy American Ethnic Experience
American Film Institute Monograph Series American History through Music
American Interest Group Politics American Political Landscape Series
American Popular Culture American Popular Culture Through History
American Religious Cultures American Schools of Oriental Research Excavation
Reports
American Schools of Oriental Research American Social and Political Movements
Monographs
American Subcultures America's Freedoms
America's Natural Places An Araminta Spookie Adventure
An explorefaith.org Book An I.Q book
An Unofficial Gamer’s Adventure Anatomy
Anatomy of The Ship Ancient Commentators on Aristotle
Ancients in Action Anglican Association of Biblical Scholars Study
Series
Anglo-Catalan Society Anglo-Russian Affinities
Animal Tales Animals on the Edge
Animals Sticker Activity Books Animation: Key Films/Filmmakers
Annabelle Unleashed Annotated Bibliographies of Serials: A Subject
Approach
Anthrozoos Applications in Scientific Photography
Applied Theatre Approaches to Digital Game Studies
ARBA and Index Archaeological Histories
Archaeology of Medieval Britain Architecture and Culture
Architecture Exchange: Engagements with Architecture in the Age of Artificial Intelligence
Contemporary Theory and Philosophy
Arctic Governance Arden Critical Companions
Arden Early Modern Drama Arden Early Modern Drama Guides
Arden Performance Companions Arden Shakespeare
Arden Shakespeare and Theory Arden Shakespeare Dictionaries
Arden Shakespeare Handbooks Arden Shakespeare Insights
Arden Shakespeare Intersections Arden Shakespeare Library
Arden Shakespeare Studies in Language and Arden Shakespeare The State of Play
Digital Methodologies
Arden Student Guides Arden Student Skills: Language and Writing
Arden Studies in Early Modern Drama Arnold History of Britain
Arnold History of Europe Arnold Readers in History
Arnold Student Reference Art Express
Art in Translation Art Reference Collection
Artist Questions Answered Artists of an Era
Artists of the American Mosaic Artist's Workshop
Asia in Focus Asian Cinema
Assembly Today Assembly Tomorrow
Assessing Pupils' Progress Association of Social Anthropologists Monographs
Athlete vs. Mathlete Athlone Contemporary European Thinkers
Athlone French Poets Athlone Publications in Egyptology & Ancient
Near Eastern Studies
Athlone Renaissance Library Audition Speeches
Author Research Series Baby & Beyond
Backstage Baseball's All-Time Greatest Hitters
Basics Advertising Basics Animation

238
 Series names

Basics Architecture Basics Creative Photography

Basics Design Basics Fashion Design
Basics Fashion Management Basics Filmmaking
Basics Graphic Design Basics Illustration
Basics Interactive Design Basics Interior Architecture
Basics Interior Design Basics Landscape Architecture
Basics Marketing Basics of Sculpture
Basics of the Hard Sciences Basics of the Social Sciences
Basics Photography Basics Product Design
Basics Textile Design Basics Typography
Battleground Series Battles and Leaders of the American Civil War
BCP Egyptology BCPaperbacks
Bedside, Bathtub & Armchair Companions Berg European Studies
Berg French Studies Berg Monographs in German Literature
Berg New Media Bertolt Brecht
Best Handwriting Beta Phi Mu Monograph Series
Beyond Criticism BFI Film Classics
BFI Film Stars BFI Modern Classics
BFI Screen Guides BFI Silver
Bible and Literature Bible and Postcolonialism
Biblical Guides Biblical Languages: Greek
Biblical Languages: Hebrew Biblical Seminar
Bibliographies and Indexes in Afro-American and Bibliographies and Indexes in American History
African Studies
Bibliographies and Indexes in American Literature Bibliographies and Indexes in Anthropology
Bibliographies and Indexes in Asian Studies Bibliographies and Indexes in Economics and
Economic History
Bibliographies and Indexes in Education Bibliographies and Indexes in Ethnic Studies
Bibliographies and Indexes in Geography Bibliographies and Indexes in Gerontology
Bibliographies and Indexes in Law and Political Bibliographies and Indexes in Library and
Science Information Science
Bibliographies and Indexes in Mass Media and Bibliographies and Indexes in Medical Studies
Communications
Bibliographies and Indexes in Military Studies Bibliographies and Indexes in Philosophy
Bibliographies and Indexes in Popular Culture Bibliographies and Indexes in Psychology
Bibliographies and Indexes in Religious Studies Bibliographies and Indexes in Science and
Technology
Bibliographies and Indexes in Science Fiction, Bibliographies and Indexes in Sociology
Fantasy, and Horror
Bibliographies and Indexes in the Performing Arts Bibliographies and Indexes in Women's Studies
Bibliographies and Indexes in World History Bibliographies and Indexes in World Literature
Bibliographies and Indexes on Sports History Bibliographies of American Notables
Bibliographies of Battles and Leaders Bibliographies of British Statesmen
Bibliographies of the Presidents of the United Bibliographies of the States of the United States
States
Bibliographies of World Leaders Big Picture
Big6 Information Literacy Skills Binah: Studies in Jewish History, Culture, and
Thought
Bio-Bibliographies in Afro-American and African Bio-Bibliographies in American Literature
Studies
Bio-Bibliographies in Art and Architecture Bio-Bibliographies in Economics
Bio-Bibliographies in Law and Political Science Bio-Bibliographies in Music
Bio-Bibliographies in Sociology Bio-Bibliographies in the Performing Arts
Bio-Bibliographies in World Literature Bio-Critical Sourcebooks on Musical Performance
Biographical Companions Biographies of Disease
Biography and Autobiography Biotechne: Interthinking Art, Science and Design
Birds of Africa Birdwatcher's Guides
Birmingham University Semitic Study Aids Birmingham War Studies

239
 Series names

Black Atlantic Black Cats

Black History Lives Black Literary and Cultural Expressions
Black Magic Black's Nature Guides
Black's New Testament Commentaries Black's Sketchbooks
Bloomsbury Academic Collections: Biblical StudiesBloomsbury Academic Collections: Economics
Bloomsbury Academic Collections: English Bloomsbury Academic Collections: Japan
Literary Criticism
Bloomsbury Academic Collections: Philosophy Bloomsbury Adaptation Histories
Bloomsbury Advances in Critical Discourse Bloomsbury Advances in Religious Studies
Studies
Bloomsbury Advances in Semiotics Bloomsbury Advances in Translation
Bloomsbury Aesthetics Bloomsbury Ancient Comedy Companions
Bloomsbury Classics in Linguistics Bloomsbury Comics Studies
Bloomsbury Companions Bloomsbury Contemporary American Thinkers
Bloomsbury CPD Library Bloomsbury Critical Education Series
Bloomsbury Critical Introductions to Bloomsbury Critical Introductions to
Contemporary Epistemology Contemporary Metaphysics
Bloomsbury Critical Introductions to Linguistics Bloomsbury Curriculum Basics
Bloomsbury Discourse Bloomsbury Education Handbooks
Bloomsbury Educational Editions Bloomsbury Egyptology
Bloomsbury Ethics Bloomsbury Family Law
Bloomsbury Gender and Education Bloomsbury Handbooks
Bloomsbury Handbooks in Religion Bloomsbury Higher Education Research
Bloomsbury History of Philosophy Bloomsbury Intelligence Studies
Bloomsbury Library of Educational Thought Bloomsbury New Media Series
Bloomsbury Perspectives on Children's Literature Bloomsbury Philosophy Dictionaries
Bloomsbury Political Philosophy Bloomsbury Research Handbooks in Asian
Philosophy
Bloomsbury Research in Political Philosophy Bloomsbury Research Methods
Bloomsbury Research Methods for Education Bloomsbury Research Skills for History
Bloomsbury Revelations Bloomsbury Shinto Studies
Bloomsbury Sources in Ancient History Bloomsbury Studies in American Philosophy
Bloomsbury Studies in Ancient Philosophy Bloomsbury Studies in Black Religion and
Cultures
Bloomsbury Studies in Central and East European Bloomsbury Studies in Classical Reception
History
Bloomsbury Studies in Contemporary North Bloomsbury Studies in Continental Philosophy
American Fiction
Bloomsbury Studies in Critical Poetics Bloomsbury Studies in Global Ethics
Bloomsbury Studies in Jewish Thought Bloomsbury Studies in Material Religion
Bloomsbury Studies in Military History Bloomsbury Studies in Modern Architecture
Bloomsbury Studies in Philosophy Bloomsbury Studies in Philosophy of Religion
Bloomsbury Studies in Religion and Popular Bloomsbury Studies in Religion, Space and Place
Music
Bloomsbury Studies in the Aristotelian Tradition Bloomsbury Studies in the City
Bloomsbury Studies in Theoretical Linguistics Bloomsbury Studies in Translation
Bloomsbury Studies in World Philosophies Bloomsbury Topics in Contemporary North
American Literature
Body In Action Bolt Action
Books of Bayern Brain, Behavior, and Evolution
Brief Histories Britain and Europe
British Film Guides British Institute of Persian Studies
British Screen Stories British Studies in Applied Linguistics
British Theatre Companies: From Fringe to Building Partnerships Series
Mainstream
Business Business on a Shoestring
Business, Culture and Change Busy Practitioner
Cambridge Yearbook of European Legal Studies Camera Craft

240
 Series names

Campaign Campaign for Learning

Carrying on in Key Stage 1 Cartoon History
Celebrations Centennial Psychology Series
Ceramics Handbooks Chameleons
Changing Issues in the Family Character Studies
Chatham House Papers Check Your Vocabulary
Child Psychology and Mental Health Childhood and Youth: Studies in History and
Culture
Childhood in America Children and Youth: History and Culture
Children's and Young Adult Literature Reference Chillers
China and International Economic Law China Statistics Series
China Studies: Studies in Chinese History and Choices
Civilization
Christian Mission & Modern Culture Christmas Maths
Chronologies in American History Church Dogmatics
Ciné-File French Film Guides Cinema and Society
Civic Discourse for the Third Millennium CIVICUS Global Study of Civil Society
Civil Justice Systems Classic Commentaries
Classic Criticism Classic Folk and Fairy Tales
Classic Reprint Series Classical Diaspora
Classical Dramatists Classical Essays
Classical Inter/Faces Classical Life and Letters
Classical Literature and Society Classical Receptions in Twentieth-Century Writing
Classical Studies Classical World
Classmates Classroom Starters and Plenaries
Clifford Chance Lectures Clio Companions
Coastal Guides from the Air Cognition and Computing
Cognition and Literacy Collected Works of M.A.K. Halliday
Colour Graffix Colour Jets
Colouring Activity Books Columbia London Law Series
Combat Combat Aircraft
Comix Communication and Information Science
Communication: The Human Context Communications Law
Companion to the Qumran Scrolls Companions to Celebrated Musicians
Companions to Greek and Roman Tragedy Comparative Genocide
Comparative Islamic Studies Comparative Media, Communication and Culture
Compass Series Complementary and Alternative Medicine
Complete Guides Computers, Privacy and Data Protection
Conflict and Today's Congress Constellations
Constitutional Systems of the World Constitutional Systems of the World: Thematic
Studies
Constitutionalism in Asia Constitutionalism in Latin America and the
Caribbean
Construction Newsletter Consumer Health Information Source Book
Consumer Health USA Contemporary American Ethnic Issues
Contemporary Anarchist Studies Contemporary Applied Linguistics
Contemporary Christian Culture Contemporary Christian Insights
Contemporary Classics in Children's Literature Contemporary Controversies
Contemporary Critical Perspectives Contemporary Debates
Contemporary Dramatists Contemporary Education Issues
Contemporary Ethical Issues Contemporary European Studies
Contemporary Food Studies: Economy, Culture Contemporary Issues in Education Studies
and Politics
Contemporary Issues in Museum Culture Contemporary Language Education
Contemporary Language Studies Contemporary Legal Issues
Contemporary Military, Strategic, and Security Iss Contemporary Practices in Alternative Process
Photography Series

241
 Series names

Contemporary Psychology Contemporary Studies in Cognitive Science and

Technology
Contemporary Studies in Comm Culture Info Contemporary Studies in Corporate Law
Contemporary Studies in Information Contemporary Studies in International Political
Management, Policies, and Services Communication
Contemporary Studies in Linguistics Contemporary Studies in Linguistics and
Education
Contemporary Studies in Second Language Contemporary Studies in Social and Policy Issues
Learning in Education: The David C. Anch
Contemporary Studies in Technical Contemporary Thinkers Reframed
Communication
Contemporary Turkey Contemporary Urban Studies
Contemporary World Cities Contemporary World Issues
Contemporary Youth Issues Contexts
Contextualizing Art Markets Continuum Advances in Religious Studies
Continuum Advances in Semiotics Continuum Advances in Translation
Continuum Biblical Studies Continuum Classic Texts
Continuum Contemporaries Continuum Contemporary American Thinkers
Continuum Critical Introductions to Linguistics Continuum Discourse
Continuum Education Handbooks Continuum Empirical Studies in Education
Continuum Ethics Continuum Histories
Continuum Icons Continuum Impacts
Continuum Intelligence Studies Continuum Library of Educational Thought
Continuum Literary Studies Continuum One Hundreds
Continuum Philosophy Dictionaries Continuum Reception Studies
Continuum Renaissance Drama Guides Continuum Research Methods
Continuum Resources in Religion and Political Continuum Shakespeare Dictionaries
Culture
Continuum Shakespeare Studies Continuum Studies in American Philosophy
Continuum Studies in Ancient Philosophy Continuum Studies in British Philosophy
Continuum Studies in Classical Reception Continuum Studies in Continental Philosophy
Continuum Studies in Eastern Philosophies Continuum Studies in Educational Research
Continuum Studies in Jewish Thought Continuum Studies in Lifelong Learning
Continuum Studies in Philosophy Continuum Studies in Philosophy of Religion
Continuum Studies in Political Philosophy Continuum Studies in Religion and Political
Culture
Continuum Studies in Research in Education Continuum Studies in the City
Continuum Studies in Theoretical Linguistics Continuum Studies in Translation
Contributions in Afro-American and African Contributions in American History
Studies: Contemporary Black Poets
Contributions in American Studies Contributions in Asian Studies
Contributions in Comparative Colonial Studies Contributions in Criminology and Penology
Contributions in Drama and Theatre Studies Contributions in Drama and Theatre Studies: Lives
of the Theatre
Contributions in Economics and Economic History Contributions in Ethnic Studies
Contributions in Family Studies Contributions in Intercultural and Comparative
Studies
Contributions in Labor Studies Contributions in Latin American Studies
Contributions in Legal Studies Contributions in Librarianship and Information
Science
Contributions in Medical Studies Contributions in Military Studies
Contributions in Philosophy Contributions in Political Science
Contributions in Psychology Contributions in Women's Studies
Contributions to the Study of Aging Contributions to the Study of American Literature
Contributions to the Study of Anthropology Contributions to the Study of Art and Architecture
Contributions to the Study of Childhood and Contributions to the Study of Computer Science
Youth

242
 Series names

Contributions to the Study of Education Contributions to the Study of Mass Media and
Communications
Contributions to the Study of Music and Dance Contributions to the Study of Popular Culture
Contributions to the Study of Religion Contributions to the Study of Religion:
Christianity and the HolocaustÑCore Issues
Contributions to the Study of Science Fiction and Contributions to the Study of World History
Fantasy
Contributions to the Study of World Literature Controversies in Science
Controversies in the Study of Religion Convergence Series
Conway Classics Conway Compass
Conway Maritime Modeller's Series Conway Plan Portfolios
Conway's History of Sail Conway's History of the Ship
Conway's Merchant Marine & Maritime History Conway's Naval History After 1850
Conway's Plan Portfolio Conway's Ship Modelling
Conway's Ship Types Cookbooks for Students
Copenhagen International Seminar Copy and Cut
Copyright Series Core Tax Annuals
Cornerstone on... Corporations That Changed the World
Corpus and Discourse Course Companions in the History of Medicine
Crackers Craft Workshop
Crash Course Create Your Own
Creating Corporate Cultures Creative Careers
Creative Core Creative Painting
Crime in Popular Culture Crime, Media, and Popular Culture
Criminal Justice History Criminal Justice, Delinquency, and Corrections
Criminal Law Library Criminal Practice
Critical Adventures in New Media Critical and Primary Sources
Critical Companions Critical Companions to Popular Contemporary
Writers
Critical Companions to Popular Contemporary Critical Pedagogy Today
Writers--ON LINE
Critical Performances Critical Perspectives in Social Theory
Critical Perspectives on Culture and Society Critical Perspectives on Language, Mobility and
International Education
Critical Political Studies Critical Powers
Critical Research in Material Culture Critical Responses in Arts and Letters
Critical Scripts Critical Stages
Critical Studies in Education and Culture Series Critical Studies in Russian Literature
Critical Theory and Contemporary Society Critiquing Religion: Discourse, Culture, Power
Cross-Cultural Perspectives on Women Cross-Cultural Statistical Encyclopedia of the
World
Crossing Ebenezer Creek Crossroads in World History
Crucible Plays Crunchbone Castle Chronicles
Cultural and Social History Cultural Context of Infancy
Cultural Histories of Cinema Cultural Histories of Design
Cultural Histories of Theatre and Performance Cultural Memory and History in Antiquity
Cultural Politics Cultural Studies in Practice
Culture and Customs of Africa Culture and Customs of Asia
Culture and Customs of Europe Culture and Customs of Latin America and the
Carib
Culture and Customs of Native Peoples in Culture and Customs of North America
America
Culture and Customs of the Middle East Culture Machine
Cultures in the American West Cultures of Consumption Series
Cultures of Early Modern Europe Cultures of the American Mosaic
Current Research in Film Curriculum Charts
Curtain Up Cut 'n Clip Series
D & T Workshop Daily Life Encyclopedias

243
 Series names

Daily Life through Artifacts Dance Divas

Dance in Dialogue Dance of Shadows
Dancing to Music Dark Hunter
Dark Lord Dark Osprey
Database Searching Series David Foster Wallace Studies
Daystar Devotions Dealing with Feelings
Debates in Archaeology Debates in World History
Debating Historical Issues in the Media of the Debating Law
Time
Decades of Modern American Drama: Playwriting Decades of Modern British Playwriting
from the 1930s to 2009
Decisions of the Arbitration Panel for In Rem Declaration
Restitution
Defences in Private Law Deleuze and Guattari Encounters
Deleuze Encounters Democracy and the News
Democracy in the World Denominations in America
Design and Culture Design and Make
Design for Social Responsibility Design Philosophy Papers
Design Your Own... Design, Histories, Futures
Designing in Dark Times Developing Citizenship
Developing French Developing History
Developing Literacy Developing Numeracy
Developing Science Developing Spanish
Developments in Clinical Psychology Devil's Advocates
Dialogues in Contemporary Psychology Series Diaries, Letters and Essays
Dictionary Classical Hebrew Digital Photography
Dino Stories Directors Handbook
Directory of U.S. Military Bases Worldwide Disability Insights and Issues
Disaster and Trauma Psychology Discographies: Association for Recorded Sound
Collections Discographic Reference
Discovering World Cultures Distinguished African Americans Series
Distinguished Asian Americans Series Distinguished Native Americans Series
Documentary and Reference Guides Documentary Reference Collections
Documents Decoded Documents in Imperial History
Documents in International Law Doing Theology
Dragon Slippers Dragonborn
DragonChild Draw Books
Drawing In Dress and Fashion Research
Dress Cultures Dress, Body, Culture
Duel Duke de Richleau
Early and Medieval Islamic World Early Years Library
Earlybirds Easier English
Ecclesiological Investigations E-design
Educate US Education and Digital Technology
Education Around the World Education as a Humanitarian Response
Education Media Yearbook Education Policy in Practice: Critical Cultural
Studies
Educational Policy in the 21st Century Edward Schillebeeckx Collected Works
Eerdmans Commentary on the Bible Eerdmans Critical Commentary
Egyptian Tales Elements of Dress
Elite Elite Performance
Ellie McDoodle Emerging Industries in the United States
Emerging Patterns of Work and Communications Emory Studies in Early Christianity
in an Information Age
Empire in Asia Empires of the World
Enchanted Sisters Encounters: Experience and Anthropological
Knowledge
Encyclopedia of Popular Music of the World Energy and Security

244
 Series names

Energy Resources, Technology, and Policy English

English Today Entertainment and Society around the World
Entrepreneurship: Principles and Practices Environmental Cultures
Environmental Degradation and Public Health Environmental History and Global Change
Epica Epworth Commentary
Essays in European Law Essential FE Toolkit
Essential FM Reports Essential Glossary
Essential Guides Essential Histories
Essential Reference Essentials of Psychology and Health
Ethnic American Voluntary Organizations Ethnic Diversity Within Nations
Ethnicity and Identity Ethnicity in Global Focus
EU Law in the Member States Europe in Focus
Europe’s Legacy in the Modern World European Academy of Legal Theory
European Academy of Legal Theory Monograph European and National Constitutional Law
Series
European Community Law European Competition Law Annual
Evergreens EX:CENTRICS
Ex:Centrics Exciting ICT
Exercise Your Way to Health Explorations in Anthropology
Explorations in World Maritime History Exploring Musical Genres
Exploring Social Issues through Literature Exploring the Constitution Series
Extreme! Eyewitness to History
Facialities: Interdisciplinary Approaches to the Factor 4
Human Face
Faerie Wars Chronicles Faith and Scholarship Colloquies
Faithful Servants Family Court Reports
Family Life through History Fashion Practice
Fashion Theory Fashion: Visual & Material Interconnections
Feasting with Fiction Feminist Companion to the Bible
Feminist Companion to the New Testament and Feminist Thought in Childhood Research
Early Christian Writings
Festivals Across the Year Field Guide To
Fighting Words Film Genres
Film Score Guides Film Studies: Bloomsbury Academic Collections
Film Theory in Practice Film Thinks
Financial Intelligence Finnish Yearbook of International Law
First Animal Encyclopedia Fitness Professionals
Fitness Trainers Fizzlebert Stump
Flashbacks Flashpoints: Global Crisis and Conflict
Fletcher Smith P.I. Focus Bible Study
Focus on the Prayer Book: An Adult Study Food Culture around the World
Food Cultures in America Food in American History
Food in Modern History: Traditions and Food Safety Newsletter
Innovations
Food Through History Food through History
Food, Culture and Society Fordham Intellectual Property Law and Policy
Annual
Foreign Intelligence Book Series Forensic Psychology
Forms of Drama Fortress
Foundations Foundations in Media
Freckleface Strawberry Freedom in the World
French Regional Studies French Studies in International Law
French Texts From Nation to Nation
Frontiers in Psychotherapy Frontiers of International Education
Frontiers of Science Series Fundamentals
Fundamentals,Required Reading Range Future Schools
Gastroenterology GCSE Student Editions
GCSE Student Guides Gender Matters in U.S. Politics

245
 Series names

Genre: A 33 1/3 Series Genreflecting Advisory Series

Geographers Geographers: Biobibliographical Studies
Geography Today German Historical Perspectives
German Library German Studies
German Texts Get Fit
Get Ready Get Set! Piano
Get them Thinking like … Getting the Buggers
Gifted Treasury Series Glass Handbooks
Global Crime and Justice Global East Asian Screen Cultures
Global Energy Law and Policy Global Exploitation Cinemas
Global Food History Global Guides to Internet Business Resources
Global Issues Global Pandemocracy
Global Security Watch Global Shakespeare Inverted
Global Sport Cultures Global Studies - Asia
Global Studies: Latin America & the Caribbean Globalizing Sport Studies
Go Facts: Animals Go Facts: Environmental Issues
Go Facts: Food Go Facts: Healthy Bodies
Go Facts: Natural Disasters Go Facts: Natural Environments
Go Facts: Oceans Go Facts: Physical Science
Go Facts: Plants Go Facts: Seasons
Go Facts: Space Go Facts: Transport
Godly Play Going Places
Good Behaviour Good Times Travel Agency
Gospel Perspectives Graffix
Grantchester Grass Roots Perspectives on American History
Great American Orators Great Debates in Law
Great Shakespeareans Great Stage Directors
Greek Tales Greek Texts
Green Guides Greenwood Band Biographies
Greenwood Biographies Greenwood Folklore Handbooks
Greenwood Guides to American Roots Music Greenwood Guides to Biomes of the World
Greenwood Guides to Business and Economics Greenwood Guides to Extreme Sports
Greenwood Guides to Fiction Greenwood Guides to Great Ideas in Science
Greenwood Guides to Historic Events 1500-1900 Greenwood Guides to Historic Events of the
Ancient World
Greenwood Guides to Historic Events of the Greenwood Guides to Literature
Medieval World
Greenwood Guides to Multicultural Literature Greenwood Guides to Science and Religion
Greenwood Guides to Shakespeare Greenwood Guides to the Animal World
Greenwood Guides to the Universe Greenwood Guides to Writing
Greenwood Icons Greenwood Introduces Literary Masterpieces
Greenwood Press Guides to Historic Events of the Greenwood Reference Volumes on American
Twentieth Century Public Policy Formation
Greenwood Technographies Gregory Sallust
Groundbreaking Scientific Experiments, Growing Up: History of Children and Youth
Inventions and Discoveries through the Ages
Guardians of Time Guidelines for Strategists
Guides for the Perplexed Guides to Asian Librarianship
Guides to Contemporary Drama Guides to Historical Events in America
Guides to Subcultures and Countercultures Guides to the Apocrypha and Pseudepigrapha
Hacks for Minecrafters Handbook of American Business History
Handbook of Comparative Economic Policies Handbooks for Educators and Parents
Handbooks of Catholic Theology Handicrafts through World History
Handwriting Today Harriet Bean
Hart Law Masters Hart Monographs in Transnational and
International Law
Hart Studies in Commercial and Financial Law Hart Studies in Comparative Public Law
Hart Studies in Competition Law Hart Studies in Constitutional Law

246
 Series names

Hart Studies in Constitutional Theory Hart Studies in European Criminal Law

Hart Studies in Information Law and Regulation Hart Studies in Law and Health
Hart Studies in Private Law Hart Studies in Security and Justice
Hart Studies on Judging and the Courts Harvard Theological Studies
Haunting Emma Have a Go English Tests
Have a Go Maths Tests Have a Go Science Tests
Headlines Healing Society: Disease, Medicine, and History
Health and Medical Issues Today Health and Psychology Sourcebooks
Health and Safety at Work Newsletter Health and Wellness in Daily Life
Helm Country Avifaunas Helm County Avifauna
Helm Field Guides Helm Identification Guides
Helm Photographic Guides Help Your Child to Succeed
Hero.com Hey Fafa!
Hip Hop in America Historian's Annotated Classics
Historical Endings Historical Explorations of Literature
Historical Facts and Fictions Historical Guides to Controversial Issues in Ameri
Historical Guides to the World's Periodicals and Historicizing Modernism
Newspapers
Histories and Sourcebooks on Combat Forces Historiography: Critical Readings
History and Politics in the 20th Century: History of American Thought
Bloomsbury Academic
History of Art and Architecture History of Crime, Deviance and Punishment
History of Emotions History of Human Spaces
History of Science History of Technology
History of the Ship History of Witchcraft and Magic in Europe
History: Bloomsbury Academic Collections Holiday Activity and Sticker Books
Hollywood History Home
Home Cultures Homework Today
Homeworms Horizon Wars
Hot Spot Histories How to Find It, How to Use It
Human Body Systems Human Evolution, Behavior, and Intelligence
Human Rights Law in Perspective Humanistic Perspectives on International
Relations
I.B.Tauris Short Histories Ideas in Action
Ideas To Go: Better Behaviour Ideas To Go: Creative Thinking
Ideas To Go: Science Experiments Ideas To Go: Self-esteem
Ideas To Go: Thinking Skills If Only...
Illuminating Modernity Illuminations Commentary Series
Imagine Living Here Impacts
Improving Comprehension Improving Punctuation and Grammar
Improving Schools In War and in Peace: U.S. Civil-Military Relations
Including Children With Inclusion
Influential Video Game Designers Information Literacy Series
Innovative Librarian's Guide Inside Diseases and Disorders
Inside Girl Inside the Ancient World
Insiders Inspirational Ideas
Instant Expert Instant Lessons for Supply Teachers
Instructional Technology Series Integrating Information and Communication
Technology
Intelligence and the Quest for Security Interiors Design, Architecture, Culture
International and Comparative Criminology International Annual of Oral History
International Critical Commentary International Development Resource Books
International Government & Politics Series International History
International Intellectual Property Law International Library of African Studies
International Library of Architecture International Library of Central Asian Studies
International Library of Historical Studies International Library of Human Geography
International Library of Iranian Studies International Library of Migration Studies

247
 Series names

International Library of the Moving Image International Library of Twentieth Century

History
International Perspectives on Curriculum Studies International Perspectives on Europe
International Perspectives on Individual International Perspectives on Mathematics
Differences Education
International Relations and the Great Powers International Relations for the 21st Century
International Screen Industries International Series on Technology Policy and
Innovation
International Studies in Populism International Studies in the Theory of Private Law
International Tax Law International Texts in Critical Media Aesthetics
International Theological Commentary Internet Projects
Interpretations Intersections of Race, Ethnicity, and Culture
Interventions Intimate Lives of the Ancient Peoples
Introduction to European Private Law Introductions in Feminist Theology
Introductions to British Literature and Culture Introductions to Theatre
Inventing the Nation Investigating Cult TV
Irish Yearbook of International Law Islam of the Global West
Ismaili Texts and Translations Isobel Key
Issues in Comparative Public Law Issues in Contemporary Religion
Issues in Curriculum Theory, Policy, and Research Issues in Phenomenology and Hermeneutics
Issues in Science and Theology Issues on Sexual Diversity and the Law
Issues through Pop Culture Italian and Italian American Studies
Ius Commune Casebooks for the Common Law of Jets
Europe
Jewellery Handbooks Jewish and Christian Text
Jewish Denominations in America John Albert Hall Lecture
Journal of Aesthetics and Phenomenology Journal of Communication Design
Journal of Immigration, Asylum and Nationality Journal of Pentecostal Theology Supplement
Law
Journal of Professional Negligence Journal of Textile Design Research and Practice
JSOT/ASOR Monographs Julian Day
Jumbo Jets Juridical Studies
Kant’s Sources in Translation Kent Critical Law
Key Concepts Key Concepts in Philosophy
Key Concepts in Religion Key Debates in Educational Policy
Key Ideas in Law Key Issues
Key Studies in Diplomacy Key Terms
Key Texts in the Anthropology of Visual and Key Thinkers
Material Culture
Key Words Keynote Studies from 'The Mariner's Mirror'
Keystones Kickstart Music
Kiki Strike KINO - The Russian and Soviet Cinema
KINOfiles Film Companion Knightley and Son
Knights' Tales Know the Game
Krefeld Historical Symposia Landmark Cases
Landmarks of the American Mosaic Language and Being
Language and Educational Processes Language and Learnig for Human Service
Professions
Late Victorian and Early Modernist Women Latin America in Focus
Writers
Latin Texts Latinos and Libraries Series
Law and Practical Reason Lawyers' Costs and Fees
Le Temps Mondial / World Time Leapfrogs
Learning Activities for Early Years Learning Through Folklore Series
Legal Theory Today Leicester History of Religions
Leicester Museum Studies Leisure, Consumption and Culture
Lesson Starters for Interactive Whiteboards Let's Talk About …

248
 Series names

Libraries Unlimited Guided Inquiry Libraries Unlimited Knowledge Management

Series
Libraries Unlimited Library Management Libraries Unlimited Professional Guides for Young
Collection
Libraries Unlimited Professional Guides in School Libraries Unlimited Series for Teaching
Librarianship Information Literacy Today
Library and Information Problem-Solving Skills Library and Information Science Text Series
Series
Library of Arctic Studies Library of Development Studies
Library of European Studies Library of Gender and Popular Culture
Library of International Relations Library of Islamic Law
Library of Islamic South Asia Library of Medieval Studies
Library of Middle East History Library of Modern Middle East Studies
Library of Modern Russia Library of Modern Turkey
Library of Ottoman Studies Library of South Asian History and Culture
Library Programs That Inspire Series Lily Dale
Lincoln Studies in Religion and Society Linguistics: Bloomsbury Academic Collections
Linkers: Art and Technology Linkers: Geography
Linkers: History Linkers: Science
Listening Hearts Listening to Music
Literacy Now Literary Genres
Literature and Culture Handbooks Literature as Windows to World Cultures
Literature Bridges to Science Series Literature Bridges to Social Studies Series
Literature of Travel, Exploration and Empire Literature, Culture, and Identity
Literatures as World Literature Literatures, Cultures, Translation
Little Activity Books Little Baby Books
Little Book of Big Ideas Little Books
Little Books at Home Little Books of Tips
Live Theory Lives and Legacies Series
Lives in Action Loretta Lawson
Lost In Lost World
LSE Monographs on Social Anthropology Luke the Interpreter
Luxury Magic Under Glass
Magnum Opus Major Conservative and Libertarian Thinkers
Major Harry Maxim Major Issues in American History
Making Histories in Museums Making Sense of Psychology
Making the Most Of Manuals Series
Mapping the World through Primary Documents Maritime Monographs & Reports
MasterClass Material Culture Directories
Material Culture of Art and Design Material Religion
Materializing Culture Mathematics, Learning, and Cognition:
Monograph Series of the Journal of Mathematics
Maths Maths Activity Books
Maths Today Media and Society Series
Mediterranea Meeting the Needs
Men-at-Arms Mental Maths
Mental Maths Every Day Mental Maths in Minutes
Mental Maths Tests Mermaid S.O.S.
Methuen Drama Agitations: Text, Politics and Methuen Drama Engage
Performances
Methuen Drama Handbooks Michel Serres and Material Futures
Middle East in Focus Milestones in Business History
Military Psychology Millie’s Misadventures
Mind Matters Miss Malarkey
Model Shipwright Modern Classics
Modern Dramatists Research and Production Modern Filmmakers
Sourcebooks
Modern Military Tradition Modern Plays

249
 Series names

Modern Sociology Modern Studies in European Law

Modern Studies in Property Law Modern Theatre Guides
Modern Wars Modernist Archives
Monkey and Robot Monographs on Infancy
Movements in the Arts Movements of the American Mosaic
Moving through History: Transportation and Multilingualisms and diversities in education
Society
Music Express Music Express Extra
Music Reference Collection Musical Steps
My Holiday To... National Archives
National Theatre Backstage Guides Nationalism & Internationalism
Native America: Yesterday and Today Native Peoples of the Americas
Nature and Human Societies Naturecraft
NDNA Need
New Approaches to Anthropological Archaeology New Approaches to International History
New Approaches to Sound, Music, and Media New Century Bible
New Century Theology New Ceramics
New Childhoods New Directions in Byzantine Studies
New Directions in Comparative and International New Directions in Computers and Composition
Education Studies
New Directions in European Writing New Directions in German Studies
New Directions in Information Management New Directions in Media
New Directions in Medieval Studies New Directions in Religion and Literature
New Directions in Social and Cultural History New Directions in Terrorism Studies
New Directions in the Anthropology of New Germany in Context
Christianity
New Horizons in Contemporary Writing New Mermaids
New Modernisms New Perspectives for English for Academic
Purposes
New Readings New Research in Museum Studies
New Technologies / New Cultures New Testament Guides
New Trends and Ideas in American Politics New Vanguard
Newspaper and Periodical History Noisy Picture Books
Nonproliferation Studies NT in Context Commentaries
Number Journey Numeracy 190
Numeracy Today Nutshell Booklets
Oathbreaker Object Lessons
Objective Measurement: Theory Into Practice Occupation in Europe
Old Testament Guides Old Testament Studies
Omega On Trial
Oñati International Series in Law and Society Only One Earth Series
Open Book Open Linguistics
Operating Grants for Nonprofit Organizations Oryx American Family Tree Series
Oryx Holocaust Series Oryx Statistical Handbooks
Osgoode Readers Osprey Games
Osprey Wargames Out of School
Outdoor Photography Outstanding Christian Thinkers
Outstanding Teaching Painting and Drawing
Paragon Issues in Philosophy Parents' Survival Guides
Parliamentary Democracy in Europe Pass Your GCSE Maths
Pass Your KS3 Maths Peace and Human Rights Education
Peddler's Pack Series Peony Pinker
People, Communication, Organization Percussion Players
Performance and Design Performance and Digital Cultures
Performance and Science: Interdisciplinary Performance Books
Dialogues
Personalizing Learning Perspectives in American Social History

250
 Series names

Perspectives on Cognitive Science Perspectives on Fundamental Processes in

Intellectual Functioning
Perspectives on Intelligence History Perspectives on Leadership in Higher Education
Perspectives on the Holocaust Perspectives on the Twentieth Century
Perspectives on Writing: Theory, Research, Practice Philosophical Filmmakers
Philosophy and Theology Philosophy, Aesthetics and Cultural Theory
Photographic Field Guides Photographic Guides
Photography and Culture Photography FAQs
Photography, History: History, Photography Photography, Place, Environment
Physical Security Piano Magic
Pig Kahuna Pirate Tales
Place to Talk Play & Culture Studies
Play Anthologies Playing the Texts
Plays and Playwrights Plays for Young People
Pocket Guides Pocket PAL
Political Arts Political Participation in America
Political Parties in Context Political Theologies
Political Theory and Contemporary Philosophy Politics and Development in Contemporary Africa
Politics and the Environment Politics Gets Personal
Politics in Latin America Politics, Culture & Society in the New Europe
Politics-Debates-Concepts Pop Goes the Decade
Popular Authors Series Popular Culture Bio-Bibliographies
Popular Culture in the Contemporary World Popular Television Genres
Poyser Monographs Poyser Natural History
Practical and Applied Psychology Practical Childcare
Practical Teaching Guides Practise Time Tables
Practitioners' Guides Praeger Applied Psychology
Praeger Security International Praeger Security International Textbook
Praeger Series in Criminology and Crime Control Praeger Series in Health Psychology
Policy
Praeger Series in Political Communication Praeger Series in Political Economy
Praeger Series in Presidential Studies Praeger Series in Transformational Politics and
Political Science
Praeger Series in War Studies Praeger Series on American Political Culture
Praeger Series on Jewish and Israeli Studies Praeger Series on the Ancient World
Praeger Series on the Early Modern World Praeger Series on the Middle Ages
Praeger Studies in American Industry Praeger Studies in Diplomacy and Strategic
Thought
Praeger Studies of Foreign Policies of the Great Praeger Studies on Ethnic and National Identities
Powers in Politics
Praeger Studies on the 21st Century Prayer and Practice Series
Primary Documents in American History and Princess Academy
Contemporary Issues
Princess Ponies Principles and Practice Series
Printmaking Handbooks Privatizing Government: An Interdisciplinary
Series
Problems in Theology Professional Development
Professional Media Practice Profiles and Pathways Series
Progress in Communication Sciences Psalms for Children Series
PSI Business Security PSI Classics of the Counterinsurgency Era
PSI Guides to Terrorist, Insurgents, and Armed PSI Reports
Groups
Psychoanalytic Horizons Psychological Dimensions to War and Peace
Psychology Briefs Psychology, Religion, and Spirituality
Public Health Public Health Issues and Developments
Publications for the Advancement of Theory and Publications in Creativity Research
History

251
 Series names

Publications of the Historian Liaison Group at the Putnam's History of Aircraft

European Community Commission
Q&A Health Guides Queering Theology
Quicksilver Qumran Literature, Hebrew-English Edition
Race and Ethnicity in Psychology Race Relations in the United States
Race, Ethnicity, Culture, and Health Racism in American Institutions
RADA Guides Radical Aesthetics-Radical Art
Radical Politics and Education Radical Thinkers in Design
Raging Earth Raid
Reaching the Standard Read On Series
Reader's Guides Reader's Guides to Musical Genres
Readers Theatre Reading Augustine
Reading Contemporary Television Reading for Literacy
Reading History Reading Rainbow
Readings: A New Biblical Commentary Real Lives
Real Stories Real World Research
Really Good Stuff Recent Trends
Recommended Reference Books Reconstructions in Early Modern History
Recorder Magic Reed's Almanac
Reeds Marine Engineering and Technology Reeds Professional
Reference Guides to Archival and Manuscript Reference Guides to Archives and Manuscript
Sources in World History Collections on Immigrant Culture
Reference Guides to National Architecture Reference Guides to National Legal Systems
Reference Guides to State History and Research Reference Guides to the State Constitutions of the
United States
Reference Guides to the United States Constitution Reference Guides to the World's Cinema
Reference Sources for the Social Sciences and Reference Sources in Science and Technology
Humanities
Reference Sources in the Humanities Reference Sources in the Social Sciences
Reflections on the Civil War Era Reflective Teaching
Reinventing Teacher Education Religion and the University
Religion in Contemporary Cultures Religion in Politics and Society Today
Religion in the Age of Transformation Religion Today
Religion, Health, and Healing Religion, Politics, and Public Life Under the aus
Religion-Economy-Politics Religious Studies: Bloomsbury Academic
Collections
Reproductive Rights and Policy Reputations
Required Reading Range Research Guides in Military Studies
Research Methods in Linguistics Resources for Teaching
Resources in Asian Philosophy and Religion Reverberations: Cultural Studies and Education
River Cottage Handbook Rockets
Roger Brook Roman Tales
Romans Romans Through History & Culture
Roots of Modern Conflict Rouleur
Roundabouts Routledge studies in sustainability
RSPB Rule of Law In Context
Russian Texts RYA
Sailmate SAIS Studies on Africa
SAQ SATs Practice
Scandals in American History Scarlet
Schizoanalytic Applications Schools of Psychological Thought
Science & Technology Almanac Science 101
Science and Society Science Buzzwords
Science Ethics and Society Science Explorers
Science Resources in the Electronic Age Science Works
Scientific Archaeology for the Third Millennium Scientific Studies of Religion: Inquiry and
Explanation
Scottish Core Tax Annuals Screen Adaptations

252
 Series names

Screen and Cinema Screen Decades

Scriptural Traces Security and the Environment
See For Yourself Select Proceedings of the European Society of
International Law
SEN in the Early Years Sensory Formations
Sensory Studies Series in Language and Ideology
Sermons That Work Setting Up Guides
Sex and Relationship Education Sex, Love, and Psychology
Sexual Medicine Shakespeare and Adaptation
Shakespeare and Language Shakespeare and Social Justice
Shakespeare and Theory Shakespeare at Stratford
Shakespeare in the Theatre Shakespeare Now!
Shakespeare Tales Shakespeare Today
Shakespeare: Bloomsbury Academic Collections Shakespeare: The Critical Tradition
Shapers of the Great American Debates Sheffield Archaeological Monographs
Sheffield Environmental and Archaeological Sheffield Excavation Reports
Research
Sheffield Studies in Aegean Archaeology Shipwright
Shire Library Shiverton Hall
Short Histories Significant Contributions to the History of
Psychology 1750-1920
Simple Maths Simple Science
Singing Express Singing Languages
Singing Phonics Singing Subjects
Six Week Workouts SLM Hot Topics
So you want to be a... SOAS Palestine Studies
SOAS Studies in Modern and Contemporary JapanSocial and Psychological Issues: Challenges and So
Social History of Africa Social Issues in American History Series
Social Justice and Psychology Social Theory and Methodology in Education
Research
Society for Old Testament Study Book List Sociocultural Studies in Educational Policy
Formation and Appropriation
Soldiers' Lives through History Solve My Problems
Songbirds Songbooks
Songsheets Soundbytes
Sounds Fun! Sourcebooks in Modern Technology
Sourcebooks on Hazards and Disasters Space School
Spacejackers Spanish Texts
Speak Out Special Educational Needs
Special Times Spelling for Literacy
Spelling Today Spiritual Directors International
Sport Commerce and Culture Sports and Games Through History
Springboard Shakespeare Springs of Wisdom
Stadium School Stage Source Books
Stanislavski Studies Star Fighters
Starting with… State, Law and Society
Steps to Success Sticker Activity Books
Sticker Storybooks Stopwatch
Storecupboard Cookbooks Stories from the American Mosaic
Story of a Drug Stravaganza
Student Companions to Classic Writers Student Editions
Student Guides to American Government and Student Guides to Business and Economics
Politics
Student Shakespeare Library Student's Guide to Landmark Congressional Laws
Studies in Antiquity & Christianity Studies in Art, Culture, and Communities
Studies in Christian Ethics Studies in Comparative Education
Studies in Early Medieval History Studies in Ethnicity, Religion and Democracy
Studies in European Law and Integration Studies in Fashion

253
 Series names

Studies in Freedom Studies in Higher Education

Studies in Historiography Studies in Human Rights
Studies in Industrial Property and Copyright Law Studies in International and Comparative Criminal
Law
Studies in International Law Studies in International Trade and Investment Law
Studies in International Trade Law Studies in Military History
Studies in Military History and International Affa Studies in Penal Theory and Penal Ethics
Studies in Population and Urban Demography Studies in Private International Law
Studies in Private International Law – Asia Studies in Psychical Research
Studies in Social Welfare Policies and Programs Studies in Sports Economics
Studies in the Early History of Britain Studies in the History of Tax Law
Studies in Theology Studies in Theology and Sexuality
Studies of the New Testament and Its World Studies of the Oxford Institute of European and
Comparative Law
Studies on the European Union Studio Companion
Studying Films Studying World Religions
Studying... Subcultural Style
Sunny Sweet Superhero School
Supporting Children Supporting Development in the Early Years
Foundation Stage
Supporting Literacy Supporting Maths
Supporting Phonics and Spelling Supporting Spelling
Supporting Writing Skills Survey of London
Suspensions: Contemporary Middle Eastern and Swedish Studies in European Law
Islamicate Thought
T&T Clark Approaches to Biblical Studies T&T Clark Cornerstones
T&T Clark Critical Readings in Biblical Studies T&T Clark Enquiries in Theological Ethics
T&T Clark Handbooks T&T Clark International Theological Commentary
T&T Clark Studies in Edward Schillebeeckx T&T Clark Studies in English Theology
T&T Clark Studies in Fundamental Liturgy T&T Clark Studies in Systematic Theology
T&T Clark Study Guides Tales of Terror
Tales of the Frog Princess Talking Images
Tauris Historical Geographical Series Teaching Assistant's Series
Teaching Young Children Tech Tools for Learning
Technologies: Studies in Culture & Theory Technology, Innovation, and Knowledge
Management
Technology, Psychology, and Health Teddybears
Teen Life around the World Teen Reads: Student Companions to Young Adult
Lite
Teens, Technology, and Libraries Telling the Time
Tempest Term Paper Resource Guides
Textile Textiles Handbooks
Textiles that Changed the World Texts and Contexts
Textual Moments in the History of Political Textures: Philosophy, Literature, Culture
Thought
The A Circuit The Academy
The Adlard Coles Classic Boat series The Age of Shakespeare
The American Dance Floor The American Family
The American Religious Experience The Arden Shakespeare Third Series
The Author and YOU The AVA Guides
The Avena Series The Beckett Manuscript Project
The Bloomsbury Companions to Contemporary The Bloomsbury History of Modern Russia Series
Filmmakers
The Bone Season The Calypso Chronicles
The Cartoon Chronicles of America The Caves
The Changing Face of War The CineTech Guides to the Film Crafts
The Criminal Lawyer The Cultural Histories Series
The Darkest Age The Decades Series

254
 Series names

The deGranville Trilogy The Design Journal

The Drake Chronicles The Entrepreneur's Guide
The Ethics of American Foreign Policy The Fairy-Tale Matchmaker
The Family in Antiquity The focal press costume topics series
The Foundation of Thanatology Series The Global Kitchen
The Global School Room The Goose Pimple Bay Sagas
The Great Cultural Eras of the Western World The Greats
The Greenwood Educators' Reference Collection The Greenwood Encyclopedia of American
Institutions
The Greenwood Encyclopedia of Black Music The Greenwood Encyclopedia of the Federal
Government
The Greenwood Historical Encyclopedia of the The Greenwood Histories of the Modern Nations
World's Political Parties
The Greenwood Press "Events That Changed The Greenwood Press "Events That Changed the
America" Series World" Series
The Greenwood Press "Literature in Context" The Greenwood Press "People Making a
Series Difference" Series
The Greenwood Press Cultures in Conflict Series The Greenwood Press Daily Life Through History
Ser
The Greenwood Press Daily Life Through History The Greenwood Press Daily Life Through History
Series Series: Daily Life in the United States
The Greenwood Press Daily Life Through History The Greenwood Press Endangered Peoples of the
Series: Nature and the Environment in Everyday World Series
Life
The Greenwood Press Using Literature to Help The Harriet Tubman Series on the African
Troubled Teenagers Series Diaspora
The History of American Journalism The History of World Literatures on Film
The IC2 Management and Management Science The Idea of Iran
Series
The Ilan Stavans Library of Latino Civilization The Individual in History
The Joshua Files The Journal of Modern Craft
The Justice Series - Putting Rights into Practice The Key Concepts
The Kibbutz Study Series The Legacy of the Great War
The Library of Episcopalian Classics The Library of Hebrew Bible/Old Testament
Studies
The Library of New Testament Studies The Library of Second Temple Studies
The Lottie Lipton Adventures The Lovegrove Legacy
The Makana Mysteries The Malichea Quest
The Manager as ... The Military Profession
The Mudcrusts The Musical Woman
The Mythic Misadventures The New Americans
The New Basics The New History of England
The New International Commentary on the New The New International Commentary on the Old
Testament Testament
The Oryx Multicultural Folktale Series The Oryx Reading Motivation Series
The Perfect Fire Trilogy The Pillar New Testament Commentary
The Pop Lit Book Club The Praeger Series on Contemporary Health and
Livi
The Praeger Series on Healing and Managing The Praeger Singer-Songwriter Collection
Injury
The Praeger Television Collection The President's Position: Debating the Issues
The Psychology of Everyday Life The Quirks
The Reception of British and Irish Authors in The Reception of Jesus in the First Three Centuries
Europe
The Rene Cassin Institute of Human Rights The Robert and Arlene Kogod Library of Judaic
Studies
The Rule of Law In Context The Russian and Soviet Cinema Series
The Seems The Selfish Crocodile

255
 Series names

The Senses and Society The Sourcebooks Shakespeare

The Story of the American Indian The Study of Sound
The Threes The Transatlantic Slave Trade: Bloomsbury
Academic Collections
The United Nations and Global Change The United Nations Series on Development
The Village The Washington Papers
The 'What is?' Research Methods Series The Wide-Awake Princess
The Wildlife Trusts The Winner's Trilogy
The WISH List The Wombles
The World's Environments Theatre Arts Workbooks
Theatre Makers Theatre Makers,Plays and Playwrights
Themes in Medieval History Themes in Religious Studies
Theology for the 21st Century Theology in Dialogue
Theoretical Issues in Cognitive Science Theory
Theory for a Global Age Series Theory for Theatre Studies
Thesaurus of Eric Descriptors Think Now
Thinkers Thinking Cinema
Thinking Media Thinking Through Theatre
Third Millennium Cataloging Threads
Throne of Glass Through Children's Literature
Through the Lens Time and Mind
TimeRiders Times Tables
Too! Books Topics and Issues in National Cinema
Topics in Musical Theatre Tough Jobs
Tough Times Toybox Science
Trade Secrets of the Professionals Trajectories: A Social-Science Commentary
Transatlantic Relations Transformation, Development and
Religionalization in Greater Asia
Transitions in Childhood and Youth Transversals: New Directions in Philosophy
Treasures From the Spiritual Classics Trolls
Trust Law International Tudor Flashbacks
Tudor Tales Tuesdays at the Castle
Turning PointsÑActual and Alternate Histories Twelve Dancing Princesses
Twilight Zone Two Horizons New Testament Commentary
Two Horizons Old Testament Commentary Ukulele Magic
Ultimate Book Guides Understanding Ancient Civilizations
Understanding China Today Understanding Fashion
Understanding Modern Nations Understanding Our Government
Understanding Our World Understanding Philosophy, Understanding
Modernism
Understanding Student Experiences of Higher Understanding the Bible and Its World
Education
Understanding the Moving Image Unicorn Princesses
Unlocking American History Urban Outlaws
Using Picture Books to Teach VAT Digest
Victorian Flashbacks Victorian Life and Times
Victorian Tales Viking Tales
Violence, Desire, and the Sacred Visual Cultures and German Contexts
Visual Dictionaries Visual Resources Series
Voices of an Era Voices of Twentieth-Century Conflict
Walter Benjamin Studies War, Culture and Society
War, Technology, and History Warrior
Weapon Weapons and Warfare
Weird Street Wenner-Gren International Symposium Series
Wet Play Today What Happened Here
What if? What's It Like to be a…?
Where to Watch Birds Whitaker's
White Wolves Non Fiction White Wolves: Adventure Stories

256
 Series names

White Wolves: Comparing Fiction Genres White Wolves: Comparing Work

White Wolves: Fairy Tales White Wolves: Familiar Settings
White Wolves: Folk Tales White Wolves: Imagined Worlds
White Wolves: Issues White Wolves: Myths and Legends
White Wolves: Playscripts White Wolves: Shakespeare Retellings
White Wolves: Stories from Different Cultures White Wolves: Stories from World Religions
White Wolves: Stories with Historical Settings White Wolves: Traditional Stories
White Wolves: World Folk Tales Who Watching
Who's Who Who's Who in…?
Why Philosophy Matters Wild Cards
Wild Things! Wild World
Wired Wired Connect
Wired Up Wired Up Connect
Wisden Sports Writing With Eyes Toward Zion
Women and Careers in Management Women and Minorities in Politics
Women and Politics Women and Religion in the World
Women and Society around the World Women in Context: Women's Writing
Women in History Women Make Cinema
Women Making History Women Who Broke the Rules
Women Writers of Color Women, Power and Politics
Women’s Roles through History Women's Psychology
Women's Roles in American History Women's Roles through History
Wonders of Nature: Natural Phenomena in Science Wooden Books
and Myth
Working in the Theatre Seminars World Bibliographical Series
World Cinema World Classics
World Englishes World Folklore Series
World History Companions World Music Series
World Mythology World of Islam
World Sports Guide World War I Tales
World War I Tales, World War II Tales World War II Flashbacks
World War II Stories World War II Tales
Writers' and Artists' Writers' and Artists' Companions
Writers Lives Writing for Literacy
Writing Handbooks Writing History
Writing on Writing Writing Research
Written Culture and Identity X-Planes
Yachting Monthly

257
Chapter 34. Accessibility
Note
This section contains new instructions as of Schematron version 7.

34.1. Alt text for images and other items

In all cases, element alt should be used to capture alt text for accessibility purposes.

This instruction applies to the following elements:

• table

• informaltable

• imageobject1

• inlinemediaobject

• equation

• informalequation

• videoobject

• audioobject

34.1.1. Example usage

Examples of this usage are shown below.

Example 34.1. Table

<table>
<title>Table title</title>
<alt>Alt text for a table with a title</alt>
<tgroup cols="2">
<tbody>
<row>
<entry>...</entry>
<entry>...</entry>
</row>
</tbody>
</tgroup>
</table>

Example 34.2. Informal table

<informaltable>
<alt>Alt text for a table without a title</alt>
<tgroup cols="2">
<tbody>
<row>
<entry>...</entry>
<entry>...</entry>
</row>
</tbody>
</tgroup>

1
only where used to represent a display image, i.e. as part of a figure or informalfigure

258
 Accessibility

</informaltable>

Example 34.3. Display images

<mediaobject>
<alt>Alt text for a display image</alt>
<imageobject>
<imagedata fileref="image.jpeg"/>
</imageobject>
</mediaobject>

Example 34.4. Inline images

<para>Here is an inline image: <inlinemediaobject>

<alt>Alt text for an inline image</alt>
<imageobject>
<imagedata fileref="image.jpeg"/>
</imageobject>
</inlinemediaobject>.</para>

Example 34.5. Equations

<equation>
<title>Equation title</title>
<alt>Alt text for an equation with a title</alt>
<mathphrase>e=mc<superscript>2</superscript></mathphrase>
</equation>

Example 34.6. Informal equations

<informalequation>
<alt>Alt text for an equation without a title</alt>
<mathphrase>e=mc<superscript>2</superscript></mathphrase>
</informalequation>

Example 34.7. Video

<mediaobject>
<alt>Alt text for a video</alt>
<videoobject>
<videodata fileref="video.mp4"/>
</videoobject>
</mediaobject>

Example 34.8. Audio

<mediaobject>
<alt>Alt text for audio</alt>
<audioobject>
<audiodata fileref="audio.mp4"/>
</audioobject>
</mediaobject>

259
Part I. Back matter
Table of Contents
Index ....................................................................................................................................... 262

261
Index
dates, 113
document reference numbers, 125
DOIs, 49, 122
Examples in bold are the primary examples. DVDs, 129
email messages, 125
et al, 118
Symbols EU Directives, 127
<para> style, 80 films, 128
@condition, 93 groups of authors, 116
@label, 74 ibids, 119
@outputformat, 19, 45, 93, 96, 221 implied authors, 118, 118, 123
@relation, 111 in <footnote>s, 138
@role, 86 inconsistent style warning, 197
@role=ancillary, 76 inline, 129
international agreements, treaties, 127
A interviews, 124
A-Z encyclopedias and dictionaries, 52 ISO 690, 112
A-Z container, 59 journal articles, 122
article DOI, 54 journal articles with URL, 122
article pagenums, 54 legal sources, 126
articles, 54 magazine articles, 123
articles that are only cross references, 55 monographs, 115
dummy entries, 55 multiple editions, 117
dummy headings, 57 newspaper articles, 123
high-level structure, 59 non-English language items, 112
inline cross references, 59 numbered volumes, 117
letter divisions, 53 online text, 120
placement of article authors, 53 op cits, 119
Abbreviations, 70, 71 orders, 127
Abstract author, 191 organisation names, 128
Acknowledgements, 69 other editions, 121
Alignment address and name blocks, 72 personal communications, 124
Anchors, 98 personal names, 113
Ancillary (back of book) content, 76 play performances, 129
Appendices in chapters, 192 publisher address, 118
Article groups, 62 radio broadcasts, 129
Article type, 61 recordings, 128
Asterisks, daggers etc, 96 regulations, 127
authorgroups, multiple, 23 reports, 128
reprinted works, 120
B series names, 120
Back matter, 76 theses, 123
Biblio author ID, 24 translators, 118
Bibliographies, 106 unpublished items, 124
<bibliomixed>, 110 untagged content, 114
<bibliomixed>/@role, 112 web sites, 125
abbreviated references, 131 Biological taxa, 232
access date, 125 Blockquotes, 162
Acts of Parliament, 126 different from epigraphs, 162
annotated bibliographies, 131 incorrect markup, 169
anonymous authors, 118 Blurbs, 37
archival content, 214 Bold text, 84
authors with single name, 120 Book reviews, 123
book reviews, 123
cases, 126 C
chapter in edited book, 116 Case regularisation, 40
classical authors, 120 Changes to the data, 35
conference papers, 124 Chapter Outline, 191

262
 Index

Chapter Outlines, 52 Examples (<example> and <informalexample>),

Chapters, 74 176
Chapters with appendices, 193 Examples @colsep, 149
Chronologies, 70, 72, 148 <?break?>, 92
Chunking, 41 <?page?>, 90
abstract, 51 <abbrev>, 71
authors, 46 <abstract>, 37
chunk elements, 41 <acknowledgements>, 69
chunks and pdfs, 40 <address>, 28, 95, 118
contributor statement, 47 <alt>, 71, 138, 138, 150
file names, 49 <anchor>, 97, 154
metadata, 46 <answer>, 169
numbering, 44, 137, 137, 158 <article>, 55
page ranges, 48 <article> with @role=articleGroup, 62
part containers and pdf file references, 49 <article> with @role=xref, 56
part divisions, 49 <attribution>, 162
pdf file reference, 48 <author>, 21
pdf filename examples, 43 <authorgroup>, 22
prelims, 65 <biblioid>, 32
titles, 44 <biblioid> with @otherclass=refNo, 125
Chunks with no titles, 46 <biblioid> with @otherclass=taxonName, 235
Citations inline, 108 <biblioid> with @otherclass=taxonRank, 97
Colophon, 65 <bibliolist>, 131
Column breaks, 92 <bibliomisc>, 21
Comments, 96 <bibliomisc> with @role=category, 60
Copyright, 30 <bibliomisc> with @role=description, 124
Cross references glossary terms, 71 <bibliomixed xml lang=’fr’>, 112
page numbers, 102, 102 <bibliomset relation =’book’>, 116
<biblioset>, 26, 32
D <blockquote>, 38, 162, 173
<bridgehead>, 38, 38, 191
Dateline (dated sign-off in preface), 72
<caption>, 150, 153, 155
Dedications, 68
<chapter>, 73, 74
Deliverables, 4
<city>, 28, 95, 118
Dictionary content, 60
<colophon>, 64, 64
Digital-only books, 20
<colspec>, 149
DOIs, 32, 49
<confdates>, 124
links, 103
<confgroup>, 124
Dramatic works, 166
<conftitle>, 124
inline stage directions, 166
<contrib>, 23
marginal line numbers, 165, 168
<copyright>, 28, 30
songs, 168
<country>, 95
split lines, 167
<cover>, 38, 38
<date>, 123
E <date> with @role=accessed, 126
Editions, 25, 27 <dedication>, 68
Editors (general, series etc), 22 <dialogue>, 166
Embedded articles, 174 <drama>, 166
Endnotes, 137 <edition>, 25
placement, 142, 142, 152, 155, 174 <editor>, 22, 116
Endorsements (in prelims), 38 <email>, 102
Epigraphs, 162 <entry> with @morerows, 149
Equations conditional processing, 158 <entry> with @nameend, 150
image formats, 158 <entry> with @namest, 150
links to, 158 <epigraph>, 162, 166, 172
MathML, 158, 158 <figure>, 155
simple, using <mathphrase>, 158 <footnote> with bibliolist, 138
Escaped entities, 4 <footnote> with link, 138

263
 Index

<footnoteref>, 102 <para> with @role=taxonAuthority, 235

<foreignphrase>, 6 <part>, 74
<foreignphrase> with @role=taxonForeign, 235 <personblurb>, 24
<formalpara>, 10, 83 <personname> in <address>, 72
<formalpara> for image accessibility, 155 <phrase> with @role = continuation, 97
<glossaentry>, 9, 10 <phrase> with @role=origin, 60
<glossary>, 70 <phrase> with @role=pronunciation, 60
<glossdef>, 70 <phrase> with @role=source, 154
<glossentry>, 70 <phrase> with @role=synonym, 60
<glosslist>, 70 <phrase> with @role=taxonEnglish, 97, 234
<glossterm>, 70, 71, 71 <phrase> with @role=taxonName, 97, 234
<holder>, 28, 30 <poetry>, 163, 168
<honorific>, 133, 136 <postcode>, 95
<imagedata>, 152 <preface>, 72
<imagedata> for pdf chunks, 48 <printhistory>, 26, 28
<imagedata> with @align, 155 <procedure>, 175
<imagedata> with @valign, 155 <pubdate>, 25, 115, 117, 118, 122, 123
<imageobject>, 152 <qandaentry>, 169
<index>, 176 <qandaset>, 169, 171
<informalexample>, 176 <question>, 169
<informalfigure>, 155 <releaseinfo> with @role=noDigitalRights, 94
<informaltable>, 148 <revhistory>, 35
<informaltable> with @colsep, 149 <revision>, 35
<informaltable> with @frame, 149 <revremark>, 35
<informaltable> with @pgwide, 149 <row> with @rowsep, 149
<informaltable> with @rowheader, 149 <section> with @linkend, 105
<informaltable> with @rowsep, 149 <section> with @role=bibliography, 57
<inlinemediaobject>, 160 <section> with @role=subArticle, 62
<issuenum>, 121 <sidebar>, 172, 173
<itemizedlist>, 79, 145, 146 <sidebar> with @role=’plateSection’, 156
<itemizedlist> with @mark, 146 <simplelist>, 146
<keyword>, 37 <speaker>, 166
<keywordset>, 37 <state>, 95, 118
<label>, 169 <step>, 175
<legalnotice>, 32 <street>, 28, 95
<line>, 163, 166 <subtitle>, 20, 44
<lineage>, 133 <superscript>, 158
<lineage> with @role=comma-before, 133 <table>, 150
<linegroup>, 163, 166 <term>, 148
<link>, 100, 108, 109, 109, 129, 173 <tfoot>, 150
<link> with @linkend, 100 <title>, 20, 44, 68
<link> with @role=relative, 76, 103 <title> with @role=keepWithNext, 58
<link> with @xlink href, 102, 120, 122 <titleabbrev>, 51
<mediaobject>, 152 <uri>, 102, 120, 122
<member>, 146 <variablelist>, 148
<olink>, 104 <varlistentry>, 148
<orderedlist>, 78, 147 <videodata>, 156
<orderedlist> with @continuation, 147 <videoobject>, 156
<orderedlist> with @inheritnum, 148 <volumenum>, 117, 121
<orderedlist> with @numeration, 148 <year>, 28, 30
<orderedlist> with @startingnumber, 148 @condition, 118, 119, 123, 131
<orgname>, 22, 128 @condition=’mathml’, 158
<otheraddr>, 28 @condition=’non-mathml’, 159
<othercredit>, 23, 24, 24 @label, 44, 74, 155
<pagenums>, 48, 120, 121, 172 @outputformat, 97, 152, 159
<para role=, 65 @role=labelOverRide, 45
<para> with @role=see, 55 @rowsep, 149
<para> with @role=source, 154 MathML, inline, 160

264
 Index

XLink, 62 examples, 176, 214

Extracts (pdf-only titles), 51 footnotes in titles, 21
Front or back matter containers, 64
F inline bibliographies, 130
Fiction, 34, 109 legal tables of contents, 226
Figures, 152 line and column breaks, 92
plate sections, 156 Line and column breaks, 92
sources in captions, 154 lineage, 136
titles and captions, difference between, 153 links between sections, 106
without titles, 153 links to files in data package, 104
File-naming, 4 links to other books, 105
Font size changes, 84 list bullet style, 147
Footnotes, 137 list title display, 147
Formal paragraphs, 10, 84 Marginal notes, 145
Front matter, 64 numbered paragraphs, 10, 226
olink, 223
OpenURL, 112
G orgname, 128
Geographers Biobibliographical Studies, 222
othername, 136
Glossaries, 70
page break markers, 92
cross references to terms in, 71
poetry and drama, 162
previous titles, 21
H revisions, 37
Half title page, 38 Rights, 94
verso, 39 Running headers and footers, 51
series data, 26
I sidebars, 174
Ibids, 119 steps and procedures, 175
IDs, 6 text direction and foreignphrase, 6
book, 8 Impression number, 65
chunks, 8 Imprints, 26
glossary, 9 Interviews, 171
Images, 152 Introductions, 73
alt text, 155 ISBNs, 32
Implementation notes, 1 formatting, 32
<emphasis>, 86 other volumes, 32
<para>, 78 ISO 639, 19
<para> with @role, 83 ISO 690, 112
abbreviated references in bibliographies, 131 Italic text, 84
annotated legislation, 232
auto-generated titles and @label, 45 K
Back of book notes numbering style, 144 Keywords, 37, 51
bibliodiv title display, 107
biology and natural history taxonomic content,
235 L
CALS table alignment, 150 Language, 19
case reports, 230 Legal texts, 84, 224
Chunk <pagenums>, 48 end of paragraph notes, 144
Chunk DOIs, 50 ID requirements, 10
Chunk pdfs, 50 numbered lists, 227
Chunk print history/sources, 51 tables of cases and statutes, 67
conftitle etc, 125 Ligatures, 6
Contributor statements, 48 Line breaks, 93
Copyright holder and responsibilities, 30 Linking additional links to footnotes, 101
Dictionary content, 64 external links, 102
End notes, 142 footnoteref, 102
End of para notes, 144 glossary links, 71
equations, 160 glossary/abbreviation links, 101

265
 Index

internal links, 100 §1.13, 44

links with generated text, 102 §1.14, 6
Lists, 146 §1.15, 7
bullet style, 146 §1.16, 8
bulleted, 146 §1.17, 7
chronologies, 148 §1.18, 7
legal numbered lists, 227 §1.19, 7
numbered, 147 §1.20, 7
numbering continuation, 147 §1.21, 3
numbering style, 147 §1.22, 4
paragraphs and, 145 §1.23, 4
simple, 146 §1.24, 4
starting number, 147 §1.25, 78
unadorned items, 146 §1.26, 84
unordered, 146 §1.27, 19
variable lists, 148 §1.28, 86
variable lists compared with tables, 148 §1.29, 86
Logo (title page), 28 §1.30, 86
§1.31, 40
M §1.32, 19
Marginal notes, 145 §1.33, 19
MathML, 158 §1.34, 19
Metadata sequence, 20 §1.35, 20
MIME types, 152 §1.36, 26
Multiple authorgroups, 23 §1.37, 26
§1.38, 21
§1.39, 21
N §1.40, 25
Name markup, 132
§1.41, 28
Natural history content, 97, 231
§1.42, 28
No print edition, 19
§1.43, 28
Notes, 98
§1.44, 28
Notes in chapters, 137
§1.45, 32
Notes in Chapters end of paragraph notes, 144
§1.46, 32
§1.47, 32
O §1.48, 32
Op. cits, 119 §1.49, 25, 26, 28, 32
Organisations as authors, 22 §1.50, 67
§1.51, 71, 73
P §1.52, 152
Page breaks, 91 §1.53, 152
Paragraphs, 79 §1.54, 152
block elements within, 79 §1.55, 152
formal, 10, 84 §1.56, 106
Parts, 74 §1.57, 106
Plate sections, 156 §1.58, 110
Poetry, 163 §1.59, 110
line indentation, 164 §1.60, 110
more complex layouts, 164 §1.61, 110
with epigraphs and title, 166 §1.62, 110
Prefaces, 72 §1.63, 110
Prefaces and forewords with authors, 72 §1.64, 110
Previous specification reference §1.02, 1 §1.65, 126
§1.03, 3 §1.66, 126
§1.09, 19 §1.67, 126
§1.10, 40 §1.68, 69
§1.11, 44 §1.69, 69
§1.12, 162 §1.70, 176

266
 Index

§1.71, 176 acknowledgements-chunk, 64

§1.72, 176 acknowledgements-present, 69
§1.73, 176 address-components, 27, 95
§1.74, 176 all-id-test, 8
§1.75, 136 alt-required, 139
§1.76, 136 ampersand, 6
§1.77, 136 anchor-id, 155
§1.78, 136 anchor-role, 155
§1.79, 98 anon-present, 118
§1.80, 98 appendix-label-issue, 45
§1.81, 98 appendix-tests, 74
§1.82, 98 arabic, 6
§1.83, 98 article-article, 122
§1.84, 98 article-article-2, 122
§1.85, 98 article-doi, 54
§1.86, 162 article-editor, 121
§1.87, 162 article-journal, 122
§1.88, 162 article-not-book, 122
§1.89, 163 article-not-part, 122
§1.90, 163 article-pagenums, 54
§1.91, 69 article-para-links, 55
§1.92, 132 article-section-role, 56
§1.93, 132 article-xref, 56
§1.94, 132 artist-required, 128
§1.95, 132 asterisk-in-name, 96
§1.96, 84 asterisk-in-text, 96
§1.97, 84 au-id-marker, 24
§1.98, 84 author-id-present, 24
§1.99, 84 author-title-space, 111
§3.1, 3 authorgroup-required-1, 22, 47
Previous titles, 21 authorgroup-required-2, 22, 47
Printing and typesetting details, 64 authorgroup-required-3, 22, 47
Procedures, 175 back-chunk, 76
Processing instructions, 97 back-matter-title, 76
dbhtml and dbfo (DocBook table formatting), bad-title-content, 116
201 bib-title-end-quote, 117, 122
end of chapter and end of book note bib-title-start-quote, 117, 122
placement, 141 biblio-id-format, 103
page breaks, 91 biblio-id-present, 103
Pronunciation, 60 biblio-message, 125
Publication date print, 25 biblioentry-collab-vs, 127
bibliomixed-address, 95
Q bibliomixed-address-space, 111
Questions/answers, 171 bibliomixed-author, 115
Quotes (in prelims), 38 bibliomixed-authorgroup, 116
bibliomixed-biblioid, 132
bibliomixed-multiple-pubdate, 116
R bibliomixed-multiple-publishernameurl, 121
Reference works, 52 bibliomixed-name, 113
Related titles prelims, 38 bibliomixed-other-issue1, 128
Revisions, 36 bibliomixed-other-issue2, 128
Rights, 94 bibliomixed-other-test, 123, 128
Roman (non-italicised) text, 84 bibliomixed-pubdate, 116
Running headers and footers, 51 bibliomixed-publisher, 132
bibliomixed-publishername-space, 111
S bibliomixed-punc, 131
Schematron tests abstract-indexterm, 109, 179 bibliomixed-referenced, 108, 197
accessed-date, 125 bibliomixed-successive-authors, 116

267
 Index

bibliomixed-successive-contributors, 111 contribution-part, 116

bibliomixed-successive-editors, 116 contribution-url, 120
bibliomixed-website, 126 contributor-in-title, 48
bibliomset-journal, 122 convert-inline-to-block, 79
bibliomset-title, 117 copyright-holder, 30
biblioset-isbns, 32 copyright-present, 30
biblioset-publisher, 26 copyright-year, 30
biblioType-test, 34, 133 country-name-test, 95
bk-insert-missing, 143 date-in-info, 41
bl-cip, 32 decision-date, 35
blurb-present, 37 dedication-in-title, 46
book-contribution, 116 display-item-but-no-hidden-sibling, 93
book-doi-isbn, 32 doi-format, 32
book-id-end, 8 doi-href, 103, 122
book-id-start, 8 doi-isbn, 32
book_metadata, 19, 21 doi-not-req, 46
bracket-following-address, 111 doi-not-required, 50
break-type, 93 doi-present, 32
break-typology, 93 drama-poetry-parent, 163, 166
bridgehead-annotations, 98 dupe-isbns, 32
bridgehead-renderas, 38 duplicate-doi, 32, 50
bridgehead-role, 38 duplicate-end-bk-notes, 137
case-biblioid-location, 35 edition-present, 25
case-id-types, 35 edition-role-present, 25
case-regularisation, 40 element-not-bibliomset, 117, 200
ch-doi-no-label, 49, 50 em-ghost, 6
ch-insert-missing, 142 email-tests, 102
chapter-label-issue, 45 emphasis-colon, 96
chapter-numeration-info, 181 emphasis-comma, 96
chapter-numeration-test, 34 emphasis-empty, 96
check-label, 74 emphasis-ldquo, 96
check-title, 45, 74 emphasis-lsquo, 96
chunk-colon, 21, 45 emphasis-rdquo, 96
chunk-doi-present, 50 emphasis-rsquo, 96
chunk-editor-present, 47 emphasis-semicolon, 96
chunk-id, 9 emphasis-stop, 96
chunk-id2, 9 empty-href, 102
chunk-pdf-present, 49 empty-link, 100
chunk-title-starts-with-number, 45 end-before-start, 178
col-span-test, 150 end-bk-notes-incorrect, 143
colophon-impressions, 65 end-bk-notes-item, 137
columns-present, 92, 181 end-bk-notes-missing, 143
comma-firstname, 135 end-bk-notes-target, 143
comment-present, 96 end-ch-note-footnote, 137
companion-flag, 28 end-ch-notes-item, 137
companion-location, 28 end-ch-notes-missing, 143
condition-present, 93, 181 end-ch-notes-title, 143
confgroup-present, 124 end-para-note-footnote, 144
conformance-required, 104 end-para-notes-item, 144
conformance-values, 104 endp-before-startp, 48
continuation-present, 147, 181 endterm-present, 101
contrib-present, 23 enforce-id-1, 9
contrib-required, 24 enforce-id-7, 10
contrib-statement-location, 47 enforce-id-8, 10
contrib-statement-present, 47, 181 epigraph-in-title, 46
contribution-book, 116 eqn-condition-required, 159
contribution-not-article, 116 eqn-present, 158, 181
contribution-not-journal, 116 et-al-present, 118

268
 Index

external-link-content, 102, 103 in-sans-bibliomset, 117

fiction-info, 181 index-missing, 177
fiction-test, 34 index-not-back, 177
figure-in-label, 153 index-with-terms, 182
figure-present, 153, 181 indexterm-class-missing, 178
figure-title-length, 154 indexterm-in-title, 179
film-date, 128 indexterm-location, 178
film-title, 128 indexterms-missing, 177
first-element-after-colophon, 64 info-after-pb, 91
first-element-after-info, 64, 65 info-before-pb, 91
first-element-front, 65 info-copyright, 30
first-last-1, 113 info-doi, 32
first-last-2, 113 inheritnum-present, 148, 181
firstname-one-char, 135 inline-bibliolist, 130
firstname-one-char-2, 133 inline-bibliolist-footnote, 139
firstname-stop, 135 inline-math-attribute, 160
firstname-stop-2, 135 insert-pi-title, 143
firstname-stop-4, 133 insert-pi-title2, 143
footnote-link, 137 insert-present, 181
footnote-para, 137 insufficient-isbns, 32
footnoteref-label, 102 invalid-pi, 97
footnoteref-target, 102 isbn-format, 32
foreignphrase-ar, 6 isbn-length, 32
foreignphrase-he, 6 isbn-present, 32
foreignphrase-lang, 6 isbn-role, 32
formalpara-title, 11 isbn-types, 32
formalpara-title2, 11 isbns-in-biblioset, 32
front-back-only, 44 isbns-role, 32
front-chunk, 64 itermset-with-range, 178
front-matter-title, 64 iv-present, 136
full-text-extract, 51 journal-article, 122
gif-file-extension, 152 jpg-file-extension, 152
givenname-not-allowed, 135 jr-present, 136
greater-than, 6 jurisdiction-location, 231
hasOnlineResources-info, 181 jurisdiction-required, 231
hasOnlineResources-test, 34 jurisdiction-values, 231
hasStudioResources-test, 34 keep-with-next, 59
hebrew, 6 keep-with-next-mediaobject, 59
holder-act, 30 keep-with-next-pagenums, 59
holder-year, 30 label-required, 32
honorific-dir, 136 label-required2, 45
honorific-end, 136 label-value, 181
honorific-start, 136 lang-attribute, 19
ibid-present, 119 lang-attribute-value, 19
ii-present, 136 last-first-1, 113
iii-present, 136 lawstatedate-missing, 224
imagedata-format-required, 152 leg-case, 98
imagedata-mime-type, 152 leg-note, 98
imageobject-required, 152 legal-contents, 67
images-dir, 152 legal-contents-links, 67
impermissible-href-location, 155 legal-lists, 227
imprint-bloomsbury-publishing, 26 legal-preface, 67
imprint-continuum, 26 legal-section-ids1, 11
imprint-count, 27 legal-section-ids3, 11
imprint-emphasis, 26 legal-toc, 67
imprint-in-biblioset, 26 legalref-present, 127
imprint-position, 26 legislation-chapter, 231
imprint-present, 26 legislation-divisions, 232

269
 Index

legislation-divisions-location, 232 no-contributor-in-book, 22

legislation-ids, 11 no-doi-back, 76
legislation-label, 232 no-doi-front, 64
legislation-required, 231 no-end-range, 178
legislation-section, 232 no-pagenums-back, 76
less-than, 6 no-pagenums-front, 64
ligature-ff, 6 no-pdf-back, 76
line-attribution, 163 no-pdf-front, 64
line-break-present, 93, 181 no-series, 25
link-conformance-1, 104 no-space-before-address, 111
link-role-required, 100 no-space-before-title, 111
link-role-version, 100 non-english-text, 19, 181
link-target-bibliomixed, 100, 108 non-legal-biblio-title, 127
link-target-figure, 100 non-matching-doi-pdf, 50
link-target-table, 100 non-permitted-otherclass, 33
link-target-title, 108 non-required-elements, 180
link-target-xref, 100 non-rtl-scripts, 6
linkend-or-href, 100, 102 non-web-image-format, 152
list-mark, 147 note-cases, 98
list-para-test, 146 note-role, 98
loc-cip, 32 notes-pi-title, 143
loc-cip2, 32 numbered-chapter-front, 64
loc-cit-present, 119 numeration-present, 148, 181
long-link-content, 101 object-id, 155
lower-case-imprint, 26 object-in-blockquote, 155
math-condition-attribute, 159 object-in-para, 155
mediaobject-not-req, 46 object-role, 155
mediaobject-required, 152 object-target-id, 155
missing-eqn-sibling-1, 158 olink-targetdoc, 104
missing-eqn-sibling-2, 158 olink-targetdoc-id1, 104
missing-index-type, 177 olink-targetdoc-id2, 104
missing-processing-instruction, 137 olink-targetdoc-id3, 104
missing-processing-instruction2, 137 olink-targetptr, 104
missing_id_rule, 7 olink-targetptr-id, 104
mixed-personname-style, 113, 198 olink-type, 104
mono-book, 116 one-in-label, 45, 74
mono-not-article, 116 only-blockquote-content, 52
mono-not-journal, 116 only-contains-nbsp, 84
mono-url, 120 only-non-web-image, 152
monograph-authors, 115 only-one-part, 44
monograph-title, 115 op-cit-present, 119
multi-format-eqns, 158 open-access, 181
multi-terms, 148 other-editions-etc, 121, 181
multiple-othercredits-1, 24 othercredit-class-required, 22
multiple-othercredits-2, 24 othername-no-firstname, 134
multiple-personblurb, 24 outputformat-attribute, 94
multiple-surnames, 135 outputformat-e-only, 20
name-bracket, 111 outputformat-imagedata, 152
name-initials, 135 outputformat-present, 181
name-order-info, 22, 47 outputformat-required, 152
nameend-present, 150 page-1-front, 64
nameend-present-2, 150 page-break-format, 91
namest-and-end, 150 page-break-pos-1, 91
namest-present, 150 page-break-pos-2, 91
namest-required, 150 page-break-pos-3, 91
nested-bibliomset, 117 page-break-sequence, 91, 92
nested-list, 146, 181 page-breaks-missing, 91
no-chs-in-part, 44 page-breaks-missing-2, 91

270
 Index

page-breaks-present, 20 possible-link-biblio-3, 138

page-no-match1, 49, 92 possible-link-biblio-4, 138
pagenums-count, 48 possible-message, 125
pagenums-e-only, 20 possible-missing-space, 95
pagenums-ndash-1, 48 possible-missing-space2, 95
pagenums-ndash-2, 48 possible-missing-space3, 125
pagenums-not-req, 46 possible-missing-space4, 131
pagenums-present, 48 possible-notes-section, 142
pagenums-sequence, 48 possible-poem, 169
pagenums-spaces, 48 possible-short-form-ref, 116
para-before-epigraph, 162 possible-unpublished, 124
para-dedication-pdfonly, 69 possible-unpublished-2, 124
para-insert-missing, 144 possible-unpublished-3, 124
para-lower-case, 79 possible-unpublished-4, 124
para-single-block, 79 prelims-subtitle, 65
part-abstract, 51 prelims-title, 65
part-article-doi, 54 previous-series, 25
part-author, 116 previous-title, 21, 181
part-contribution, 116 processing-instruction-issue, 143
part-doi-required, 50 proportion-case-leg, 181
part-editor, 116 proportion-case-legislation, 126
part-filename-no-label, 49, 50 proportion-unpub-other, 181
part-final, 168 proportion-unpublished-other, 124
part-initial, 168 pub-address-location, 27
part-label-issue, 45 pub-address-missing, 27
part-medial, 168 pub-city-content, 27
part-no-doi, 50 pub-city-missing, 27
part-no-label, 49, 50 pubdate-four-digits, 26
part-suppress-pdf, 50 pubdate-present, 26
pb-in-footnote, 92 publisher-address, 26
pb-section-title, 91 publisher-biblioset, 26
pdf-dir, 152 publisher-no-biblioset, 26
pdf-file-extension, 152 publisher-url, 28
pdf-only-extract, 51 publishername-emphasis, 27
pdf-suppress-incorrect, 50 pubname-in-article, 122
personblurb-para, 25 range-in-footnote-1, 178
personblurb-present, 24 range-in-footnote-2, 178
personname-components, 132 rare-emph-present, 181
personname-role-present, 132 recording-date, 128
phrase-in-publishername, 27 recording-title, 128
pi-markup, 142 relative-href, 104
png-file-extension, 152 relative-link-dir, 104
poetry-drama-present, 163, 166, 181-181 remove-chapter-outline, 192
poss-footnote-marker, 51 resource-required, 32
poss-front-matter, 64 revhistory-location, 36
poss-recording, 128 revision-author, 36
possible-abstract, 51 revision-revremark, 36
possible-access-date, 125 revision-sequence, 36
possible-appendix-link, 109 revisions-date-format, 36
possible-article-link, 59 role-or-class, 23
possible-attribution, 162, 163 role-or-href, 100
possible-chapter-link, 109 row-cols-count, 149
possible-conference, 125 rtl-scripts, 6
possible-edited-book, 22 schema-version-present, 34
possible-epigraph, 162 schema-version-test, 34
possible-legislation, 127 schematron-version-present, 34
possible-link-biblio-1, 138 schematron-version-test, 34
possible-link-biblio-2, 138 see-in-itermset, 179

271
 Index

see-mismatch, 179 unlinked-doi, 103

see-seealso-target, 179 unmarked-address, 27
serial-author, 121 unpublished-pubdate, 124
series, 25 unpublished-publishername, 124
series-location, 26 untagged-biblio-content, 114
series-name-list, 25 untagged-doi, 103
series-prev-title, 181 untagged-month, 113
short-biblio, 109 untagged-url, 102
short-link-text, 101 uri-check, 102
sidebar-present, 182 uri-spaces, 102
single-bibliomset, 117 v-present, 127
single-list-item, 146 volume-issue-numeric, 118, 122
single-list-item-2, 146 whitespace-in-href, 102
single-page, 48 wrong-index-type, 177
smallcaps-test, 86 xlink-testing-1, 103
snapshot-article, 182 xlink-testing-2, 103
source-in-caption, 154 xlink-testing-3, 103
space-before-bibliomset-required, 111 xml-isbn, 32
space-firstname, 135 xreflabel-not-required, 45, 74, 112
sr-present, 136 zone-present, 178
startingnumber-present, 148, 181-181 Series, 25
sub-article, 182 Geographers Biobibliographical Studies, 222
subscript, 86 Sidebars, 172
superscript, 86 Signed prefaces and forewords, 72
suppress-pdf-abstract, 50 Small caps, 84
suppress-pdf-article, 54 Species names, 97, 232
suppress-pdf-partintro, 50 Steps and procedures, 174
suppress-pdf-required, 50 Strikethrough, 84
surname-apos1, 136 Symbols note markers, 137
surname-is-firstname, 135, 198 Synonyms, 60
surname-only, 135
surname-with-stop, 135 T
suspicious-link-content, 101 Tables, 148
table-in-label, 149 borders, alignment, widths, 149
table-present, 181 cells spanning columns, 150
table-row-col-att, 150, 181 cells spanning rows, 149
taxon-rank-check, 98 footers, 150
taxon-siblings, 98 Tables of cases and statutes, 67
taxonRank-test, 98 Taxon rank, 97, 232
test-condition-attribute, 94 Textbook special sections, 173
test-linkend-attribute, 106 Timelines, 72
test-role-attribute, 86 Translators, 23
tiff-file-extension, 152
title-emphasis, 115, 117, 122, 122
title-not-all-emphasis, 21, 86
W
Word origins, 61
title-present, 21
title-required, 44
title-starts-with-list, 66
title-value, 181
title-within-info, 44
toc-list-starts-with-number, 66
toc-present, 66
toc-warning, 66
trans-in-title, 118
type-endofrange, 177
unbalanced-brackets-1, 101, 110
unbalanced-brackets-2, 101, 110
unlinked-bibliomixed-count, 108

272