Home
Books
Documentation for the IOP Publishing specific implementation of BITS 2.0 for book content
Chapters
All of a books chapters must be captured in seperate <book-part > elements within a <book-body> element.
Chapter Body
Capture the body content of a book chapter inside a <body> element as a child of the relevent <book-part>.
Statements (Theorems, Proofs, Remarks)
Capture formal statements such as theorems, proofs and remarks in a <statement> element.

Books
Documentation for the IOP Publishing specific implementation of BITS 2.0 for book content
- Root element
  The root element for a book is a <book> element.
- Book Meta
  <book-meta >is a mandatory element for all books as a container for the book level metadata.
- Front Matter
  Capture the front matter information for a book inside a <front-matter> element.
- Chapters
  All of a books chapters must be captured in seperate <book-part > elements within a <book-body> element.
  - Book-Part Meta
    <book-part-meta>is a mandatory element for all chapters as a container for the chapter level metadata.
  - Chapter Body
    Capture the body content of a book chapter inside a <body> element as a child of the relevent <book-part>.
    - Sections
      Capture sections in a <sec> element.
    - Paragraphs
      Capture paragraphs using <p> elements.
    - Figures
      Capture figures using a <fig> element
    - Video Figures
      Capture video figures using a <fig> element with a @fig-type attribute of value video.
    - Tables
      Capture tables inside a <table-wrap> element.
    - Cross-References
      Capture links internal to the book in a <xref> element.
    - Lists
      Capture Lists in a <list> element.
    - Inline Formula
      Capture inline mathematical content in a <inline-formula> element.
    - Display Formula
      Capture block mathematical content in a <disp-formula> element.
    - Boxed Text
      Capture boxed text content inside a <boxed-text> element.
    - Preformatted Text
      Capture text where spacing has to be preserved (e.g. computer code) in a <preformat> element.
    - Statements (Theorems, Proofs, Remarks)
      Capture formal statements such as theorems, proofs and remarks in a <statement> element.
  - Chapter Back
    Capture the back matter for a chapter in a <back> element.
- Back Matter
  Capture the book back matter inside a <book-back> element.
- Version and Change Log

Statements (Theorems, Proofs, Remarks)

Capture formal statements such as theorems, proofs and remarks in a <statement> element.

The statement element must contain a @content-type attribute describing the content of the statement. The suggested values for @content-type are:

exercise
theorem
lemma
proof
remark
axiom
proposition

The statement element must contain a child <label> element and may optionally contain a <title> element.

Note: Some types of statement use italic text in the output. Do not use italic tags in the XML to indicate this, the formatting must be applied for relevant statement types through the stylesheet.

If the <statement> element is cross-referenced elsewhere it must contain an @id attrtibute.

Example

<statement content-type="exercise">
  <label>Question B6</label>
  <p>(iv) does have some ambiguity. First, it is not quite clear what
  the wave function Ψ refers to; presumably <inline-formula>
    <tex-math><?CDATA ${{\rm{\Psi }}}_{1,0,0}$?>
    </tex-math>
    <mml:math overflow="scroll">
      <mml:mrow>
        <mml:msub>
          <mml:mi mathvariant="normal">Ψ</mml:mi>
          <mml:mn>1,0,0</mml:mn>
        </mml:msub>
      </mml:mrow>
    </mml:math>
    <inline-graphic xlink:href="bk978-0-7503-3851-6ch4ieqn20.gif" xlink:type="simple"/>
  </inline-formula> of the previous part. And ‘a short explanation
of your choice’ might be better as ‘justify your choice’.</p>
</statement>