<back>

Back Matter

Ancillary or supporting material not included as part of the main textual content of a standards document or adoption, for example, annexes.

Related Elements

Parts of a Standards Document: A standard <standard> may be divided into several structural components.
  • The front matter for the standards document (<front>), which may contain:
  • The body of the standard (<body>), which contains the textual and graphical content of the standards document
  • Any back matter (<back>) such as annexes and reference lists
Components of an Adoption: An adoption (<adoption>) may contain several top-level components:
  • An <adoption-front> element, which contains document-level and adoption-level metadata, possibly with notes and prose sections;
  • An optional adopting back matter element (<back>) provided by the adopting organization, which contains annexes in the local language or additional requirements or notes (Note: Some adopting organizations place all their adoption material, including adoption-specific back matter, before the standard they are adopting; others place the adoption-specific back matter after the standard being adopted. The NISO STS model for <adoption> allows either location to be used, though not both at once.);
  • The contents of the <adoption> that contain or point to the standard being adopted. This may include one or more of the following: The <std-xref> element may be particularly useful when a standards organization does not possess the XML version of the standard they are adopting, but only, for example, the PDF version. The <std-xref> element can also be used in situations where the adopting organization does not have permission to distribute the standard being adopted.
  • An optional adopting back matter element (<back>) provided by the adopting organization, which contains annexes in the local language or additional requirements or notes. (Note: Some adopting organizations place all their adoption material, including adoption-specific back matter, before the standard they are adopting; others place the adoption-specific back matter after the standard being adopted. The NISO STS model for <adoption> allows either location to be used, though not both at once.)

Attributes

id Document Internal Identifier
rid Reference to an Identifier
xml:base Base

Model Description

The following, in order:

This element may be contained in:

<adoption>, <standard>, <sub-part>

Example 1

The back matter of a standard:
<standard
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:mml="http://www.w3.org/1998/Math/MathML"
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:ali="http://www.niso.org/schemas/ali/1.0/"
  xmlns:tbx="urn:iso:std:iso:30042:ed-1"
  dtd-version="1.0"
  xml:lang="en">
 <front>...</front>
 <body>...</body>
 <back>
  <app-group>
   <app content-type="inform-annex" id="annA">...</app>
   <app content-type="norm-annex" id="annB">...</app>
  </app-group>
  <ref-list>...</ref-list>
 </back>
</standard>

Example 2

Back matter three times — once at the end of the ISO standard, once as part of the CEN adoption, and once as part of the DIN adoption:
<adoption>
 
<!-- DIN adoption of CEN standard -->
 <adoption-front>

<!-- Metadata that is the same for all of the organizations that developed or adopted
 this standard -->
  <std-doc-meta>
   <title-wrap xml:lang="de">
    <intro>Sicherheit von Maschinen</intro>
    <main>Sicherheitsbezogene Teile von Steuerungen</main>
    ...
   </title-wrap>
   <title-wrap xml:lang="en">
    <intro>Safety of machinery</intro>
    <main>Safety-related parts of control systems</main>
    ...
   </title-wrap>
   <title-wrap xml:lang="fr">
    <intro>Sécurité des machines</intro>
    <main>Parties des systèmes de commande relatives à la sécurité</main>
    ...
   </title-wrap>
   <std-ident>
    <doc-type>st</doc-type>
    <doc-number>13849</doc-number>
    <part-number>1</part-number>
    <version>n</version>
   </std-ident>
  </std-doc-meta>

  <std-meta id="profile.nat">
   <std-org>
    <std-org-abbrev>DIN</std-org-abbrev>
    <std-org-loc>Berlin</std-org-loc>
   </std-org>
   ...
  </std-meta>
  <notes>...</notes>
  <sec sec-type="foreword" specific-use="foreword.nat">
   <title>National foreword</title>
   <p>This standard includes ...</p>
   ...
  </sec>
 </adoption-front>

 <!-- CEN adopted ISO standard -->
 <adoption>
  <adoption-front>
   <std-meta id="profile.reg">
    <std-org>
     <std-org-abbrev>CEN</std-org-abbrev>
    </std-org>
    ...
   </std-meta>
   <notes>...</notes>
   ...
  </adoption-front>

  <!-- The ISO standard that was adopted by CEN and then by DIN -->
  <standard>
   <front>
    <iso-meta id="profile.int">
     <std-org>
      <std-org-abbrev>ISO</std-org-abbrev>
     </std-org>
     <content-language>en</content-language>
     <std-ref type="undated">ISO 13849-1</std-ref>
     <doc-ref>ISO 13849-1</doc-ref>
     <release-date>2006-11</release-date>
     <permissions>
      <copyright-year>2006</copyright-year>
      <copyright-holder>ISO</copyright-holder>
     </permissions>
    </iso-meta>
    <sec sec-type="intro">
     <title>Introduction</title>
     <p>The structure of safety standards ... this part of ISO
      13849.</p>
    </sec>
   </front>
   <body>
    <sec id="sec_1" sec-type="scope">
     <label>1</label>
     <title>Scope</title>
     <p id="par_1_1">This part of ISO 13849 provides ...</p>
     ...
    </sec>
   </body>
   <back>
    <app-group>
     <app id="sec_A" content-type="inform-annex">
      <label>Annex A</label>
      <annex-type>(informative)</annex-type>
      <title>Determination of required performance ...</title>
      ...
     </app>
     ...
    </app-group>
    ...
   </back>
  </standard>

  <!-- Back matter added by CEN -->
  <back>
   <app-group>
    <app id="sec_ZA" content-type="inform-annex">
     <label>Annex ZA</label>
     <annex-type>(informative)</annex-type>
     <title>Relationship between this European Standard and the Essential 
      Requirements of EU Directive 98/37/EC, amended by Directive 98/79/EC</title>
     <p id="par_ZA_1">This European Standard has been prepared ...</p>
    </app>
    ...
   </app-group>
  </back>
 </adoption>

 <!-- Back matter added by DIN -->
 <back>
  <app-group>
   <app id="sec_NA" content-type="bibl">
    <label>Annex NA</label>
    <title>Bibliography</title>
    <p><bold>Standards referred to in</bold> <xref ref-type="sec" rid="sec_2">Clause 2</xref>
    </p>
    <ref-list>
     <ref>
      <mixed-citation><std std-id="urn:iso:std:beuth:e2b8abae:::en" type="dated">IEV
       191:2002</std>, International electrotechnical vocabulary — Chapter 191:
       Dependability and quality of service; (IEC 60050-191 AMD 1:1999-03 and IEC
       60050-191 AMD 2:2002-01)</mixed-citation>
     </ref>
     ...
    </ref-list>
   </app>
  </app-group>
 </back>
</adoption>

NISO STS 1.0 Tag Suite Components

Version of October 2017

Back to Top