Customizations from NISO JATS 1.0

TF JATS is based on the flexible Archiving & Interchange version of NISO JATS. Taylor & Francis' customizations from the standard schema include changes to both extend and subset the standard JATS XML grammar, and usage restrictions applied through tagging guidelines or validation. These customizations include:

  • Tightening models for key metadata including author names, journal and article identifiers, dates, references, article type and section headings.
  • Addition of new elements for article XML headers, issue-level XML, article status (as AMO, Final, etc), queries, and elements from TFJA DTD not found in NISO JATS.
  • OASIS CALS table model is implemented in the same namespace as other elements.
  • MathML is included using the latest version, MathML 3.
  • The namespace for TF JATS is "http://cats.informa.com/tfjats", and the namespace "http://jats.nlm.nih.gov" is used for NISO JATS elements.

The tagging guidelines contained in this documentation form an extensive list of the extensions and restrictions in TF JATS. A summary of the customizations that extend NISO JATS is given below.

The table below lists elements and attributes added in TF JATS that are not present in NISO JATS. These elements and attribute belong to the namespace "http://cats.informa.com/tfjats", and should be used with the prefix "tf".

Table 1. TF JATS Extension Elements and Attributes
TF JATS extension Description Location NISO JATS equivalent
issue-manifest Issue XML root element Issue XML none
issue-meta Issue metadata Issue XML none
issue-status Issue status information Issue XML none
toc Table of Contents Issue XML none
toc-section Subdivision of table of contents Issue XML none
toc-article Article entry in table of contents Issue XML none
schema-version Identifies the version of TF JATS used in creating an XML file

<article>
<issue-manifest>

 none, but similar to dtd-version
article-status Article status information <article-meta> none
tagger Track creation and updates to an XML file

<issue-status>
<article-status>

 none
header For Header XML projects, contains article metadata and references <article> <front>, <ref-list>
query Query inserted during production all %phrase.class; locations and <contrib> none
department Department name

<institution>
via %institution-elements;

 <named-content content-type="deptartment">
institution-name Name of an institution

<institution>
via %institution-elements;

 <named-content content-type="institution-name">
city City

<aff>
<address>
<addr-line>
<collab>
<corresp>
<publisher-loc>
<conf-loc>

via %address.class; and
via %address-line.class;

 <named-content content-type="city">
state State or Province

<aff>
<address>
<addr-line>
<collab>
<corresp>
<publisher-loc>
<conf-loc>

via %address.class; and
via %address-line.class;

 <named-content content-type="state">
postal-code Postal Code or Zip Code

<aff>
<address>
<addr-line>
<collab>
<corresp>
<publisher-loc>
<conf-loc>

via %address.class; and
via %address-line.class;

 <named-content content-type="postal-code">

Certain extensions have been created by changing element models to allow elements to appear in places where the JATS Archiving & Indexing DTD does not allow. These extensions are listed in this table.

Table 2. TF JATS Model Extensions
Description Element Model
Allow label in keyword groupings. This is useful for keyword lists that include multiple groups of keywords. nested-kwd (label?, (kwd | compound-kwd)+, nested-kwd*)
Allow address elements in conf-loc. This makes the model of conf-loc consistent with publisher-loc, and allows tagging address information in conf-loc. conf-loc (#PCDATA | %simple-text; | %address.class;)*

In addition, a large number of character entities have been added to the list of W3C ISO and MathML character entities that are included in NISO JATS. The additional character entities in TF JATS include character entities from TFJA DTD, and possibly character entities for new special characters used in Taylor & Francis content. All character entities in TF JATS are defined using the Unicode value of the character as defined by the Unicode Consortium.