◇◆

<processing-meta> Processing Metadata

Optional container element, used to hold the processing metadata elements, which describe processing information descriptive of the XML-tagged document (document instance).

Usage/Remarks

The Processing Metadata element (<processing-meta>) provides the opportunity to describe, in the XML, aspects of the document file itself, including (through attributes) the tag set, table model, and MathML options a document uses and (through elements) some of the modeling restrictions or extensions the document claims to follow.
Processing Metadata is not considered to be part of the content of a book, or part of the metadata for citing a book; it is metadata about how the XML is constructed — not about how the book content is structured. This metadata is information at the “file level” and thus not part of <book-meta>, but inside the book as a peer to <book-meta>.
  • The elements inside <processing-meta> name tag set extensions (superset) and restrictions (subset, secondary schema, etc.) that the XML document claims to follow. More than one restriction or extension is allowed.
  • The attributes on <processing-meta> describe the modeling choices made by this document in terms of tag set family, table model, and math tagging.
<processing-meta> Content
This optional container element is used to hold the processing metadata elements, which describe processing information descriptive of the XML-tagged document (document instance). The <processing-meta> element contains the following elements:
  • <restricted-by> — Identification of one of the guidelines or other restrictions (such as a tighter subset schema) the document claims to be following. The content of <restricted-by> may be a name such as “pmc”, “jats4r”, “sts4i”, or a URI, for example, the URL of a particular recommendation. The element is repeatable so that multiple restrictions can be claimed.
  • <extended-by> — Identification of a BITS extension or superset that the document claims to be following. The content of <extended-by> may be a name, such as “taxpub”, or a URI. The element is repeatable so that more than one extension can be claimed.
  • <custom-meta-group> — To hold other processing metadata a BITS user might want to express in the XML file.
Tag Set Identification Attributes
Since the @dtd-version attribute has never provided a complete description of which version of the tag set controls a document, several attributes were added to the <processing-meta> element to describe the version choices more fully:
@tagset-family
Which of the JATS tag set families is the basis for this document’s tag set? The value is fixed as “bits” and cannot be changed.
@table-model
Which table model is used by the tag set for this document? (e.g., “xhtml” or “oasis”)
@mathml-version
Which version of MathML is used by the tag set for this document? (e.g., “3.0” or “2.0”). In BITS, this is fixed to “3.0”.
@math-representation
A list of the (possibly many) ways mathematical expressions may be represented in this document (e.g., both MathML and TeX [“mathml tex”])

@table-model

Which table model is used by the tag set for this document? @table-model is an optional attribute; there is no default.
both
Both XHTML-inspired and OASIS CALS models are used
none
No table models are used
oasis
The OASIS XML Exchange (CALS) table model
xhtml
The XHTML-inspired table model

@mathml-version

Which version of MathML is used by the tag set for this document? (e.g., “3.0” or “2.0”). In BITS, this is fixed to “3.0”.

@math-representation

A list of the (possibly many) ways mathematical expressions may be represented in this document, for example, both MathML and TeX (“mathml tex”) or using MathML, SVG graphics, and narrative text (“mathml images plain-text”).
This attribute has an NMTOKENS value, meaning a space-separated list of values, so that a document can declare that their documents use both TeX and images, for example, or MathML, gif images, and TeX. Likely values include: 
mathml   tex   latex   images   plain-text
Related Elements
Back Matter — Books and book parts do not use the same element for their back matter. Books may contain a <book-back> element, which may contain <book-part> elements. In contrast, book parts may contain a <back> element, similar to that of journal articles, and this <back> cannot contain <book-part> elements.
Parts of a Book — A BITS <book> may be divided into several metadata components:
  1. the <processing-meta> (metadata concerning the XML file rather than the work); and
  2. the <collection-meta> (metadata concerning collections in which this book is a component); and
  3. the <book-meta> (the bibliographic information about the entire book);
and several narrative text components:
  1. the <front-matter> (the narrative front matter of a book or book part such as a Preface);
  2. the <book-body> (the textual and graphical content of the book); and
  3. any <book-back> (any ancillary information such as a glossary, reference list, or appendix).
Attributes
math-representation
mathml-version (fixed value = 3.0)
table-model
tagset-family (fixed value = bits)

Base Attributes

id
xml:base
Models and Context
May be contained in
<book>, <book-part-wrapper>
Description
The following, in order:
Content Model
<!ELEMENT  processing-meta
                        %processing-meta-model;                      >
Expanded Content Model

(restricted-by*, extended-by*, custom-meta-group*)

Tagged Sample

With MathML 3.0 and XHTML tables

<book
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:mml="http://www.w3.org/1998/Math/MathML"
  xmlns:xi="http://www.w3.org/2001/XInclude"
  xmlns:ali="http://www.niso.org/schemas/ali/1.0/"
  book-type="gov"
  dtd-version="2.1"
  indexed="yes"
  xml:lang="en">
 <processing-meta
   tagset-family="bits"
   table-model="xhtml"
   math-representation="mathml tex"
   mathml-version="3.0">...</processing-meta>
 <book-meta>...</book-meta>
 <book-body>...</book-body>
 <book-back>...</book-back>
</book>
Related Resources