<doc-ident>

ISO-Specific Document Identification Section

The ISO-specific element <doc-ident> container element holds information which uniquely identifies this standards document for ISO purposes. Non-ISO organizations are advised to use elements directly within <std-meta> and inside <std-ident> instead.

Remarks

Best Practice: 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:
sdo
Use the <std-org> container to record the name, short name, and location for an SDO, or use the <originator> element within <std-ident>.
proj-id
Use the <proj-id> element within <std-meta>.
language
Use the <content-language> element within <std-meta>.
release-version
Use the <release-version> element within <std-meta>.
urn
Use <self-uri> element within <std-meta>.
ISO Note: This element (and thus all the elements within it) may be used only within <iso-meta>, <reg-meta>, or <nat-meta>, where they are retained for ISO use and for backwards-compatibility purposes. The sub-elements of <doc-ident> are closely related to the fields of ISO URNs as documented in RFC 5141 (from which some of the text describing them is borrowed).

Attributes

id Document Internal Identifier
xml:base Base
xml:lang Language of an Element

Model Description

The following, in order:

This element may be contained in:

<iso-meta>, <nat-meta>, <reg-meta>

Example 

...
<iso-meta>
 <title-wrap xml:lang="en">...</title-wrap>
 <doc-ident>
  <sdo>ISO</sdo>
  <proj-id>...</proj-id>
  <language>en</language>
  <release-version>IS</release-version>
  <urn>urn:iso:std:iso:2560:ed-3:v1:en</urn>
 </doc-ident>
 <std-ident>
  <originator>ISO</originator>
  <doc-type>is</doc-type>
  <doc-number>2560</doc-number>
  <edition>3</edition>
  <version>1</version>
 </std-ident>
 ...  
</iso-meta>
...

NISO STS 1.0 Tag Suite Components

Version of October 2017

Back to Top