NISO STS Extends ISO STS
NISO STS extends ISO STS with the goal of making it better meet the needs of a wide variety of standards organizations. The ability to handle standards embedded in an adoption document, many additional JATS-based metadata elements (such as keywords and subject groupings), new ways to identify standards organizations, more complex titles for standards, and selected BITS (Book Interchange Tag Suite) structures (such as Indexes, Tables of Contents, and an XInclude mechanism) are just a few of the additions. (For a complete list, see Differences between ISO STS 1.1 and NISO STS 1.0 at niso-sts.org.)
All of the original ISO STS 1.1 elements and attributes are available as part of NISO STS.
However, in some cases NISO STS has more flexible alternatives for the ISO STS elements. Best Practice for new implementations, and new users, is to use these new structures, and existing users should consider transitioning to them. The ISO STS elements with new alternatives include:
- <release-version> — Which Best Practice replaces with <version>.
- <std-ref> — Which allows many elements inside it, but for Best Practice should be tagged as a simple string, since the elements that are allowed inside <std-ref> should more properly be tagged as part of the <std-ident>.
This element has been retained for backwards compatibility with ISO STS. For non-ISO
processing, the element <doc-ident>, and all the elements within it, have been replaced by elements within <std-meta> and <std-ident>. All the information currently inside <doc-ident> can be tagged outside of the <doc-ident> element as follows:
- <pub-date> — Use <release-date>.
- <normative-note> and <normative-example> — ISO STS uses only non-normative notes and example. NISO STS allows both normative and non-normative notes and examples.
- <normative-note> and <non-normative-note> — NISO STS introduces a new note type that ISO STS did not have, the <meta-note>. Best Practice: Notes such as superseding notes, adoption notes, and errata information notes should be tagged as <meta-note> elements. The @content-type attribute can distinguish note types; see @content-type page for a list of suggested values for meta-note types.
- <access-date> — Use <date-in-citation>.
- <time-stamp> — Use <date-in-citation>.
- <nlm-citation> — Use <std> for citations of standards, and either <element-citation> or <mixed-citation> for all other citations.