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.
Models and Context
Text, numbers, or special characters, zero or more
<!ELEMENT release-date %release-version-id-model; >
Expanded Content Model
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> ...