Oxford University Press BITS Typecodes

As an example, a book that contains a single, consistent style for all boxes found throughout the manuscript, or a book that contains different types of boxes all covered by other typecodes in this look, does not need to include the :Feature suffix on the Box typecode. However, if a book contains a consistent style for most boxes but also includes one or more kinds of boxes that need special styling not covered by this typecode list, then the feature suffix should be used. For each unique style, a number may be designated after the :Feature suffix, e.g. Box:Feature1, Box:Feature2, etc.

Historically at OUP Features have been used on boxes, but this model allows us to use the Feature suffix wherever needed. For instance, if a book retains a common default table structure and enumeration, but an additional table is used to contain a multi-column list, a Table:Feature1 may be used on the multi-column list to distinguish it from other items marked as just Table.

On Box:Feature in particular, a feature type (or label) might be present. This is a consistently used value that appears with the title of the feature. The Label typecode should be used for this portion of the text.

The :Feature suffix may be applied to any type of code.

Pre-Edit Rules

Features must be identified by production editors as part of the handover documentation. All features identified in the handover must be marked accordingly during the pre-edit and confirmed at copy edit.

Box Feature

Manuscript:

Typecodes Applied:

Final Design:

Table Feature

Manuscript:

Typecodes Applied:

Final Design:

BITS XPath

//boxed-text[@content-type="FT#"]
//table-group[@content-type="FT#"]
//disp-quote[@content-type="FT#"]

OxChapML XPath

//*[@role="FT#"]