<body>

Body of the Standards Document

The main textual portion of the standards document.

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 document (<adoption>) may contain several top-level components:
  • A <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
specific-use Specific Use
xml:base Base

Model Description

The following, in order:

This element may be contained in:

<standard>, <sub-part>

Example 

<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>
  <sec sec-type="scope" id="s1">
   <label>1</label>
   <title>Scope</title>
   <p>This International Standard defines the test equipment 
    and procedures to be used ...</p>
  </sec>
  <sec sec-type="norm-refs" id="s2">
   <label>2</label>
   <title>Normative references</title>
   <p>The following referenced documents are indispensable 
    for the application of ...</p>
   ...
  </sec>
  ...
 </body>
 <back>...</back>
</standard>

NISO STS 1.0 Tag Suite Components

Version of October 2017

Back to Top