◇◆

<release-date> Release-Date

An important date in the life of a standard, such as the date it was first published or the date it was reinstated. The attributes @date-type and @std-type should be used to specify what event the date names.

Usage/Remarks

Date Type Attribute
@date-type is used to name events in the publishing cycle of the standards document (not in the lifecycle of the standard). Thus date types include events such as “published”, “editorial-change”, or “stabilized-maintenance”.
Standard Type Attribute
A @std-type attribute is used to name events (standards document types) in the lifecycle of the standard, such as “addenda” (which creates a new product, with a new designation that typically adds to a previous dated designation) or “amendment” (which replaces a previously published dated standard and also adds to a previous dated designation).
The original publication of a standard will carry a @date-type of “published” and a @std-type attribute of “new-standard”: 
<release-date date-type="published"
     std-type="new-standard">
Later corrections, amendments, editions, and alternate language versions for a standard will all carry this same release date naming the original publication; but they will also carry additional <release-date> elements that name the different dates on which they are published and the different types of lifecycle events they represent.
Specific Use Attribute
By design, the <release-date> element does not take an @specific-use attribute. If a date does not fit neatly into the @date-type and @std-type attributes just described, then that date should be tagged as a <meta-date> element.
Related Elements
Best Practice: In the original ISO STS Tag Set, the element <pub-date> was used to record the date on which an international standard was first published. NISO JATS has its own journal-article-based definition and attributes for the element <pub-date>. In order to avoid a conflict for organizations which have both journal articles and standards in a single data store, NISO STS Best Practice is to record the date on which a standard is published (as well as other significant dates) using the element <release-date> instead of the element <pub-date>.
Attributes
date-type
iso-8601-date
publication-format
std-type

Base Attributes

id
xml:base
Models and Context
May be contained in
<iso-meta>, <nat-meta>, <reg-meta>, <std-doc-meta>, <std-meta>, <std-xref>
Description
Text, numbers, or special characters, zero or more
Content Model
<!ELEMENT  release-date    %release-version-id-model;          >
Expanded Content Model

(#PCDATA)*

Tagged Samples
Published date inside <std-meta> 
...
<std-meta>
 ...
 <doc-ref>...</doc-ref>
 <release-date 
   iso-8601-date="2014-12-01" 
   date-type="published" 
   std-type="new-standard">2014-12-01</release-date>
 <comm-ref>...</comm-ref>
 ...
</std-meta>
...
ISO-specific, published date inside <iso-meta> 
...
<iso-meta>
 ...
 <content-language>en</content-language>
 <std-ref type="undated">ISO 2560</std-ref>
 <std-ref type="dated">ISO 2560:2009</std-ref>
 <doc-ref>ISO 2560:2009(en)</doc-ref>
 <release-date iso-8601-date="2009-05-30" 
   date-type="published">2009-05-30</release-date>
 ...  
</iso-meta>
...