<inline-supplementary-material> Inline Supplementary Material Metadata (deprecated)

Inline description of, and possibly a pointer to, an external file that provides supplementary (non-integral) material for the article. This element is deprecated.

Usage/Remarks

Attribute @supplemental for Included Objects

In previous versions of JATS, the element <inline-supplementary-material> was used to mark references to supplementary material, where the reference appeared within the regular flow of the text and did not have a preview image or separate caption. Current Best Practice is to replace such references with <inline-graphic>, <inline-media>, or <ext-link>, as appropriate, and identify the material as supplementary using the @supplemental flag attribute:
<inline-media supplemental="yes" .../>
Related Elements
Basic Non-text Elements — This Suite contains several elements that can describe and point to non-textual content: <graphic>, <inline-graphic>, <media>, and <inline-media>. These elements appear in the flow of the document, and the material they describe and point to is assumed to be integral to the document, unless flagged with the @supplemental attribute. “Integral” means that the object is logically necessary to the content of the document, although stored as an external file.
The elements <graphic> and <inline-graphic> contain a pointer to a still image (such as a photograph, diagram, line drawing, etc.). The elements <media> and <inline-media> contain a pointer to a non-textual object (typically a binary such as an audio clip, dataset, or animation that cannot be displayed in print)
Supplementary Material — In contrast to the four non-textual elements, <supplementary-material> and <inline-supplementary-material> always describe and point to objects that are considered to be “supplementary” (non-integral) to the content of the article. Such material may be XML material (tagged textual material such as figures, tables, and sections) or non-textual material (such as graphics, films, audio clips, datasets, or other resources). Best practice is to use <supplementary-material> descriptions only for describing objects that are too large or otherwise of a format that does not fit into an XML file. Objects that could properly be incorporated into an XML file (such as text fragments, tables, figures, and intext graphics) should be tagged using the ordinary JATS elements (such as <fig>, <table>, or <sec>) and flagged as supplementary using the @supplemental attribute.
The elements <supplementary-material> and <inline-supplementary-material> (like the <graphic>, <inline-graphic>, <inline-media>, and <media> elements) never contain the object they describe, even if it is an XML object such as a figure. They provide metadata concerning the external object, and may point to it.
The element <inline-supplementary-material> is used to mark up references to additional material, where the reference appears within the line of the text and does not have a preview image or separate caption. The <supplementary-material> element is used to describe a more complicated reference, where the description of the supplementary object resembles a figure in that it can be positioned as a floating or anchored object, may take a caption, and may use graphics or tables in the description of the object.
Attributes

Base Attributes

Namespaces

Models and Context
May be contained in
Description
Content Model
<!ELEMENT  inline-supplementary-material
                        (#PCDATA
                         %inline-supplementary-material-elements;)*  >
Expanded Content Model
(#PCDATA | alt-text | long-desc | email | ext-link | uri | bold | fixed-case
| italic | monospace | overline | roman | sans-serif | sc | strike | underline | ruby |
named-content | styled-content | sub | sup)*
Tagged Sample

Supplementary Timeline

(<ext-link> used instead of deprecated <inline-supplementary-material>)
...
  <p>Supplementary PDF file supplied by authors.</p>
  <media id="S1" supplemental="yes"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xlink:title="local_file" 
    xlink:href="1471-2105-1-1-s1.pdf"
    mimetype="application/pdf"/>
  <p>RNAPs seem to have arisen twice in evolution
  (see the <ext-link supplemental="yes" 
   xmlns:xlink="http://www.w3.org/1999/xlink"
   xlink:title="local_file" xlink:href="timeline">
   Timeline</ext-link>). The large family of multisubunit 
   RNAPs includes bacterial enzymes and archeal enzymes  
   ...
  </p>...