<std-ref> Standard Reference Designation
<std-ref> contains the value (as a string) of one standard reference designator, for example, “ISO 9001:2015”. This designator typically consists of an originator or SDO-abbreviated name (e.g., “ISO”) and a standard number or identifier (such as “9001”), and it may also include a year (such as “2015”) or other information that uniquely identifies a given standard.
The <std-ref> element can be used in two contexts:
- Within the metadata of a standard (inside <std-meta> or <iso-meta> or similar), the standard designation element <std-ref> names a designator for the current standard and is typically provided twice, once in dated and once in undated form.
- Outside the metadata, when a standard is mentioned within the prose of a standards document, the element <std> is used to hold the designation and other information for the standard being cited. Inside that <std> element, the element <std-ref> may be used to identify the designator of the cited standard and/or separate it from other information concerning the standard, such as the standard’s title.
Best Practice Content
Although many elements are allowed inside a <std-ref>, Best Practice is to make the content just text. For Best Practice, the elements that are allowed in <std-ref> should be tagged as part of the <std-ident> element, leaving <std-ref> as a simple string.
For Best Practice, a deep link to another standard (in which a figure, table, or similar internal structure from the other standard is the target of the link) should be tagged using the element <std> rather than by using <std-ref>.
Citing a Correction or Amendment Best Practice
When a correction or amendment is referenced, it is Best Practice to include the full reference in <std-ref>, e.g.
<std-ref>ISO/IEC 1989: 2002/Cor.3:2009</std-ref>
The several forms of reference designation (dated, short, etc.) should be distinguished using the @type attribute.
Redundant in Metadata
Strictly speaking, the standard reference designation <std-ref> that is part of the metadata of a standards document can almost always be constructed from information present in the <std-ident> element, with the insertion of appropriate spacing and separators. But even as part of the metadata, it can be convenient to have a precombined form of the identifier all together in one place.
Standard Designator Type (@type)
The @type attribute describes standard designator (for example, “dated”, “undated”, or “short”). @type has as its values a fixed list of designation types. To record a designation type that is not one of the listed types, you can use @custom-type to describe the actual type. Set the value of @type to “custom” and also use @custom-type to name type you require.
Models and Context
May be contained in
Any combination of:
- Text, numbers, or special characters
- <originator> Originator
- <doc-type> Document Type
- <doc-number> Document Number
- <part-number> Part Number of a Multipart Document
- <edition> Edition Number
- <isbn> ISBN
- <suppl-type> Supplement Type
- <suppl-number> Supplement Number
- <suppl-version> Supplement Version
- <version> Version Indicator
- <year> Year
<!ELEMENT std-ref (#PCDATA %std-ref-elements;)* >
Expanded Content Model
(#PCDATA | originator | doc-type | doc-number | part-number | edition | isbn | suppl-type | suppl-number | suppl-version | version | year)*
In metadata of standard
... <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> ...
Standard named in “Normative references” section
... <ref> <std><std-ref type="undated">ISO/IEC 17025</std-ref>, <title>General requirements for the competence of testing and calibration laboratories</title></std> </ref> ... <ref> <std><std-ref type="dated">ISO 15223‑1:2012</std-ref>, <title>Medical devices — Symbols to be used with medical device labels, labelling and information to be supplied — Part 1: General requirements</title></std> </ref> ...
Standard named in text
... <non-normative-note> <label>NOTE</label> <p>Guidance on this issue may be found in <std><std-ref type="short">EN 1006</std-ref></std> (see Bibliography [<xref rid="bib-3">3</xref>]).</p> </non-normative-note> <p>... complying with <std><std-ref type="dated">ISO 5356‑1</std-ref></std>.</p> ...
Standard named in “Bibliographic references” section
... <ref content-type="standard" id="ref3"> <label></label> <std><std-ref type="undated">EN 1006</std-ref>, <title>Advanced technical ceramics —Monolithic ceramics — Guidance on the selection of test pieces for the evaluation of properties</title></std> </ref> ... <ref content-type="standard" id="ref9"> <label></label> <std><std-ref type="undated">ISO 13399 (all parts)</std-ref>, <title>Cutting tool data representation and exchange</title></std> </ref> ...