Network Working Group J. Goodwin
Request for Comments: 5141 H. Apel
Category: Informational ISO
March 2008
A Uniform Resource Name (URN) Namespace for
the International Organization for Standardization (ISO)
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Abstract
This document describes a Uniform Resource Name Namespace
Identification (URN NID) for the International Organization for
Standardization (ISO). This URN NID is intended for use for the
identification of persistent resources published by the ISO standards
body (including documents, document metadata, extracted resources
such as standard schemata and standard value sets, and other
resources).
Goodwin & Apel Informational [Page 1]
RFC 5141 ISO URN Schema March 2008
Table of Contents
1. Introduction ....................................................2
2. Specification Template ..........................................4
2.1. Namespace ID ...............................................4
2.2. Registration Information ...................................4
2.3. Declared Registrant of the Namespace .......................4
2.4. Declaration of Structure ...................................4
2.4.1. Definition ..........................................4
2.4.2. Examples ...........................................12
2.5. Relevant Ancillary Documentation ..........................15
2.6. Identifier Uniqueness Considerations ......................15
2.7. Identifier Persistence Considerations .....................15
2.8. Process for Identifier Resolution .........................16
2.9. Rules for Lexical Equivalence .............................16
2.10. Conformance with URN Syntax ..............................17
2.11. Validation Mechanism .....................................17
2.12. Scope ....................................................17
3. Namespace Considerations .......................................17
4. Community Considerations .......................................18
5. IANA Considerations ............................................20
6. Security Considerations ........................................20
7. References .....................................................21
7.1. Normative References ......................................21
7.2. Informative References ....................................21
Appendix A. Alternative Naming Schemes ............................23
Appendix B. ABNF Definition of Namespace ID = "iso"
(Informative) .........................................24
1. Introduction
The International Organization for Standardization (ISO) was created
by international agreement in 1947. ISO is a network of the national
standards institutes of many countries, on the basis of one member
per country, with a Central Secretariat in Geneva, Switzerland, that
coordinates the system. ISO acts as a bridging organization in which
a consensus can be reached on solutions that meet both the
requirements of business and the broader needs of society, such as
the needs of stakeholder groups like consumers and users.
Further information is provided at http://www.iso.org/iso/about.htm.
The core mission of ISO is to develop technical standards
constituting technical agreements that provide the framework for
compatible technology worldwide. ISO standards contribute to making
the development, manufacturing, and supply of products and services
more efficient, safer, and cleaner. They make trade between
countries easier and fairer.
Goodwin & Apel Informational [Page 2]
RFC 5141 ISO URN Schema March 2008
Every participating ISO member institute (full members) has the right
to take part in the development of any standard that it judges to be
important to its country's economy. No matter what the size or
strength of that economy, each participating member in ISO has one
vote. ISO's activities are thus carried out in a democratic
framework where each country is on an equal footing to influence the
direction of ISO's work at the strategic level, as well as the
technical content of its individual standards. Although the ISO
standards are voluntary, the fact that they are developed in response
to market demand, and are based on consensus among the interested
parties, ensures widespread applicability of the standards.
Consensus, like technology, evolves and ISO takes account of both
evolving technology and evolving interests by requiring a review of
its standards at least every five years to decide whether they should
be maintained, updated, or withdrawn.
ISO publishes International Standards and other technical
specifications that are cited in the definitions of required or
expected practices in many industries in many nations. These
specifications contain dictionaries of standard terms, catalogues of
reference values, definitions of formal languages, formal schemata
for information capture and exchange, specifications for standard
practices, and other information resources of general use to
international trade and industry. ISO wishes to create and manage
globally unique, persistent, location-independent identifiers for
these resources.
This specification defines the syntax for URNs that identify
documents developed by the International Organization for
Standardization (ISO) in accordance with the standards development
procedures defined in the ISO/IEC Directives, Part 1 [ISODIR-1] and
the ISO supplement [ISODIR-S] and processed by the ISO Central
Secretariat. The syntax extends to identify document metadata and
resources related to these documents or otherwise associated with
them. It does not extend to products derived from these documents
and published by ISO (e.g., handbooks, compendia) or documents at or
below the Technical Committee level. Revisions of this specification
may define syntax for URNs in this namespace that identify other ISO
objects, when the ISO community defines a requirement for such
identifiers.
Goodwin & Apel Informational [Page 3]
RFC 5141 ISO URN Schema March 2008
2. Specification Template
2.1. Namespace ID
"iso"
2.2. Registration Information
Version 2.1
Date: 2007-12-13
2.3. Declared Registrant of the Namespace
J. Goodwin
ISO Central Secretariat
International Organization for Standardization (ISO)
Case Postale 56
CH-1211 Geneva 20
Switzerland
E-mail: goodwin@iso.org
2.4. Declaration of Structure
2.4.1. Definition
The Namespace Specific Strings (NSSs) of all URNs assigned by ISO
will conform to the syntax defined in Section 2.2 of [RFC2141].
The NSS has the following ABNF [RFC5234] specification:
NSS = std-nss
All URNs conforming to this specification begin the NSS with the
prefix "std:" to denote the restriction to documents developed by
the ISO standards development procedures as defined in the ISO/IEC
Directives, Part 1 [ISODIR-1] and the ISO Supplement [ISODIR-S].
Prefixes that identify ISO objects of other kinds may be defined
in future revisions of this specification.
std-nss = "std:" docidentifier *supplement *docelement
[addition]
The prefix "std:" distinguishes an . An
identifies the ISO document that is designated by the
, as extended or modified by any identified
. (An that identifies all parts of a
multipart ISO document is a special case as described under the
Goodwin & Apel Informational [Page 4]
RFC 5141 ISO URN Schema March 2008
element .) If the contains an
element, the NSS identifies a resource extracted from the ISO
document or otherwise associated with it (see below).
docidentifier = originator [":" type] ":" docnumber [":" partnumber]
[[":" status] ":" edition]
[":" docversion] [":" language]
provides the complete identification of an ISO
document. Each of its component elements is described below.
originator = "iso" / "iso-iec" / "iso-cie" / "iso-astm" /
"iso-ieee" / "iec"
is the organization (usually an international body)
from which a document emanates.
Current values:
iso = International Organization for Standardization
iec = International Electrotechnical Commission (IEC), or
Commission Electrotechnique Internationale
iso-iec = jointly developed by ISO and IEC
iso-cie = jointly developed by ISO and the Commission
Internationale d'Eclairage (CIE)
iso-astm = jointly developed by ISO and the American Society for
Testing and Materials (ASTM) International
iso-ieee = jointly developed by ISO and the Institute for
Electrical and Electronics Engineers (IEEE)
Revisions of this specification may define additional values.
type = "data" / "guide" / "isp" / "iwa" /
"pas" / "r" / "tr" / "ts" / "tta"
designates the ISO deliverable type. If the element
is not present, the classification is "international standard".
Other current values:
data = Data (document type no longer published)
guide = Guide
Goodwin & Apel Informational [Page 5]
RFC 5141 ISO URN Schema March 2008
isp = International Standardized Profile
iwa = International Workshop Agreement
pas = Publicly Available Specification
r = Recommendation (document type no longer published)
tr = Technical Report
ts = Technical Specification
tta = Technology Trends Assessment
docnumber = DIGITS
is the reference number assigned to the document by
ISO and/or IEC. An ISO document may comprise a single document,
or two or more separate parts each of which is identified by
.
partnumber = "-" 1*( DIGIT / ALPHA / "-" )
is the reference number that identifies a part of a
multipart standard.
Where it is required to refer to a multipart ISO document in its
entirety, this can be designated by omitting the
element. However, this precludes the possibility of using any
further elements except .
NOTE: The option to refer to a multipart ISO document by omitting
the element has been included to align with the
provision in the ISO/IEC Directives, Part 2, 2004 [ISODIR-2]
subclause 6.2.2 of making an undated reference to all parts of an
ISO document. It is only permissible to use this option where the
URN is referring to a multipart ISO document in its entirety.
Since the use of this option precludes the designation of the
elements and , it is implicit that the URN needs
to remain valid irrespective of any future changes to the
multipart document (see the rules for undated references given in
the ISO/IEC Directives, Part 2, 2004 [ISODIR-2] subclause
6.6.7.5.2). This shall be taken into consideration in the use
(and maintenance) of any URN specification employing this option.
Goodwin & Apel Informational [Page 6]
RFC 5141 ISO URN Schema March 2008
NOTE: In the case where the multipart document comprises different
types of ISO deliverable, the of the core part (usually
part 1) applies. See the example "Reference to a resource related
to all parts of a multipart document".
Except for the case where it is required to refer to a multipart
document in its entirety, the element is required if
the identified resource is a part of an ISO document. Otherwise,
this element is not used.
status = ( "draft" / "cancelled" ) / stage
indicates the publication status of the document. When
the element is not present, the NSS refers to a published
document. Other values:
draft = document that has not yet been accepted for
publication by international ballot
cancelled = document that has been deleted or withdrawn
stage = "stage-" stagecode ["." iteration]
indicates the stage code and iteration of the document.
stagecode = DIGIT DIGIT "." DIGIT DIGIT
is the harmonized stage code in accordance with ISO
Guide 69:1999, "Harmonized Stage Code system (Edition 2) --
Principles and guidelines for use" [ISOGUIDE69].
iteration = "v" DIGITS
is a sequential number that refers to a specific
iteration of the project's lifecycle through the designated stage.
If no is specified, the reference is to the highest
iteration available for the specified stagecode.
NOTE: In the ISO Central Secretariat project management database,
the is referred to as the "project version".
edition = "ed-" DIGITS
designates a specific edition of the document. (DIGITS
is the (sequential) edition number.) If no is
specified, the NSS refers to the latest edition.
Goodwin & Apel Informational [Page 7]
RFC 5141 ISO URN Schema March 2008
docversion = "v" (simpleversion / isoversion)
simpleversion = DIGITS
designates the version number of a document's
. It is altered by correction (corrected version;
Technical Corrigendum) or amendment (Amendment; Addendum) and is
distinct from a revision, which changes the edition number.
In the , the first version published is 1, and each
subsequent correction or amendment increases the version number by
1.
If no is specified, the reference is to the highest
version number available for the denoted .
Current values of :
1 - first version published
2 - corrected version published
isoversion = baseversion *includedsuppl
baseversion = DIGITS
includedsuppl = "-" suppltype supplnumber [ "." supplversion ]
An can be linked to a simpleversion by defining an
existing simpleversion as baseversion and listing all the
elements (corrections and amendments) incorporated
into that version.
Examples for the (internal ISO version) scheme:
1 = first version of standard
1-amd1.v1 = first version of standard incorporating first
version of Amendment 1
1-amd1.v1-amd2.v1 = first version of standard incorporating
first version of Amendment 1 and first version of Amendment 2
1-amd1.v2-amd2.v1-amd3 = first version of standard
incorporating corrected version of Amendment 1, first version
of Amendment 2, and highest version of Amendment 3
Goodwin & Apel Informational [Page 8]
RFC 5141 ISO URN Schema March 2008
1-cor3 = first version of standard incorporating highest
version of Technical Corrigendum 3
1-amd1-cor3 = first version of standard incorporating highest
version of Amendment 1 and highest version of Technical
Corrigendum 3
language = monolingual / bilingual / trilingual
monolingual = "en" / "fr" / "ru" / "es" / "ar"
bilingual = "en,fr" / "en,ru" / "fr,ru"
trilingual = "en,fr,ru"
designates the official ISO language(s), or the
language of an official translation, in which the document
(object) is processed and published by ISO (excluding languages
that constitute only specific elements of the content). The value
is one or more alpha-2 codes, each of which designates a language,
as specified in ISO 639-1 [ISO639-1]. If no language element is
specified, is assumed.
NOTE: Although [ISO639-1] recommends that language codes be
written in lowercase, this ABNF definition allows the use of
uppercase language codes because in ABNF [RFC5234], terminal
symbols defined as literal strings are explicitly
case-insensitive. This case distinction does not carry any
meaning (see Section 2.9) and it is recommended to use language
codes in lowercase. For additional information about the usage of
language tags in information objects, see [RFC4646].
supplement = ":" suppltype ":" supplnumber
[":" supplversion ] [":" language ]
suppltype = "amd" / "cor" / "add"
supplnumber = DIGITS
supplversion = "v" DIGITS
designates a technical alteration of or addition to
an ISO standard that does not result in a new or
. Each may be one of the three types,
designated by :
Goodwin & Apel Informational [Page 9]
RFC 5141 ISO URN Schema March 2008
amd = Amendment -- a document that alters and/or adds to
previously agreed upon technical provisions in an existing
ISO document; an amendment is subject to acceptance by
ballot in accordance with the ISO/IEC Directives, Part 1,
2004 [ISODIR-1] subclause 2.10.3
cor = Technical Corrigendum -- a document that corrects a
technical error or ambiguity, or updates the ISO document in
such a way that the modification has no effect on the
technical normative elements; a Technical Corrigendum is not
balloted -- see the ISO/IEC Directives, Part 1, 2004
[ISODIR-1] subclause 2.10.2
add = Addendum -- (document type no longer published) Addenda were
documents that changed (by correction, addition, or
deletion) the technical requirements of an ISO document; an
addendum was subject to acceptance by ballot in accordance
with the ISO/IEC Directives, Part 1. (Addenda are included
in this RFC because some of them are still valid.)
Supplements are numbered consecutively per ISO document, and
within each supplement type.
identifies the number of the supplement.
designates the version of a published supplement.
At present, only two versions are used in practice: when a
supplement is published, it is version 1. If that supplement is
subsequently corrected by issuing a corrected version, as
designated by the term "Corrected" on the cover page together with
a date, the corrected version is version 2.
The language of a supplement can be different from that of the
document. For example, a supplement may apply to only one of the
languages of a bilingual document. For such cases, the language
of a supplement can be identified using the element
defined above. The interpretation is the same, except that it
applies only to the supplement.
docelement = ":" ( "clause" / "figure" / "table" / "term" ) ":"
elementnumber / elementrange
*( "," elementnumber / elementrange )
elementnumber = ( ALPHA / DIGITS ) *( "." DIGITS )
elementrange = elementnumber "-" elementnumber
Goodwin & Apel Informational [Page 10]
RFC 5141 ISO URN Schema March 2008
identifies one or more numbered subdivisions of a
document. Types of numbered subdivision are specified in the ISO/
IEC Directives, Part 2 [ISODIR-2]. This RFC currently specifies
forms for reference to clauses, figures, tables, and terms only.
It does not provide for reference to subfigures. Revisions of
this specification may define additional values.
represents the selection of one or more clauses or
subclauses of the document. represents the selection of
one or more figures of the document.