You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
e.g. urn:iec:std:iec:60601-1-1:::: vs urn:iec:std:iec:60601-1-1:2005-10:tr:prv:fr
2. All URIs are extensible, to - define adjuncts (such as amendment, corrigendum or interpretation sheet). - name consolidations (such as base edition plus its amendment)The adjunct string is appended to the base URI (after || or _)
EXAMPLE: Naming an adjunct (e.g. corrigendum to an amendment):
Separation between a base document and its adjuncts
When a base edition is amended, corrected or otherwise added to, the URN is constructed using that of the base edition, to which we add information on the adjunct. Two types of reference exist: either to the adjunct itself or to the consolidation of the base edition with one or more of its adjuncts.
The base edition information is separated from the adjunct information by three fields. The middle field indicates whether the reference is to a consolidation or not. If left empty, the reference is to the adjunct itself. If it contains the word "plus", it is a consolidation.
EXAMPLE: Amendment 1:1993 to IEC 60068-2-2:1974
urn:iec:std:iec:60068-2-2:1974: : : : :amd:1:1993
EXAMPLE: Consolidation of amendment 1:1993 with IEC 60068-2-2:1974
In theory, there is no limit to the number of adjuncts that are possible. In practice, when there are many adjuncts, it is advisable to either make use of an undated reference to the base edition as a whole, or to deliver content by different means, such as database standards.
Separator
Rule
Example
:
Between fields in the URN
urn:iec:std:iec:60601
-
Within field
urn:iec:std:iec-iso:60601-1-1:
#
Between URI and IDs for document elements, such as clauses, figures, etc.
urn:iec:std:iec:60601-1-1:2015-10:::#fig-1
Note on IDs
The IDs content elements used in this document and its examples are those that were used in IEC's conversion process. Outside the context of conversion excercises, the use of semantic ID naming schemes is not necessarily encouraged. This URN model can be used with other IDs.
Note on languages
Languages are listed in alphabetical order, to ensure that identical values are expressed in the same way (and at the same time, to avoid complex tables of language combinations to solve the problem)
Defining table
item
description
sdo namespace
Specific to each organisation.
content type namespace
Right now limited to "std", which means standards-type documents. Could be extended to other deliverables?
date
blank, YYYY, YYYY-MM or YYYY-MM-DD
type
For IS: can be blank or use "is". Other currently existing values: ts, tr, pas, guide, is, srd, ser (for series/all parts)
deliverable
product type
language
can be blank or use ISO language codes, can be one or many
adjunct type
currently used values: amd, cor, ish…could be extended.
Examples
Prefix = urn + sdo namespace + content type namespace
Base document identifier: header + project number + date + type + deliverable + language
Relation = relation
adjunct document information: adjunct type + adjunct number + date
component or related asset information: # or =, component id or related asset
urn
:
sdo namespace
:
content type namespace
:
header
:
project number
:
date
:
type
:
deliverable
:
language
adjunct type
:
adjunct number
:
date
# or =
component id or related asset
:
relation
:
urn
:
iec
:
std
:
iec
:
67654
:
blank
:
blank
:
prv
:
blank
:
plus
:
amd
:
1
:
2010-08
#
fig-1
urn
:
:
:
iso
:
60601-1
:
2010-03
:
ts
:
csv
:
en
:
:
amd
:
1
:
2010-12
#
sec-1
urn
:
:
:
iec-iso
:
61076-7-101
:
2010
:
tr
:
exv
:
fr
:
plus
:
cor
:
etc…
:
2010-11
#
sec-3.4
urn
:
:
:
iec-ieee
:
80004
:
2010-10-11
:
pas
:
rlv
:
ru
:
plus
:
ish
:
1
:
etc.
#
sec-4.5.6
urn
:
:
:
iec-itu
:
etc.
:
:
guide
:
cmv
:
en-fr
:
plus
:
…
:
:
#
tabl-7
urn
:
:
:
iec-astm
:
:
:
is
:
:
en-fr-ru
:
plus
:
:
:
#
anx-a
urn
ser
#
not-4.6.7-2
#
nte-3.2-1
#
etc.
=
software supplement
=
voting report
=
webpage
=
forum
The text was updated successfully, but these errors were encountered:
Rules
1. If any field is absent, leave empty
e.g.
urn:iec:std:iec:60601-1-1::::
vsurn:iec:std:iec:60601-1-1:2005-10:tr:prv:fr
2. All URIs are extensible, to - define adjuncts (such as amendment, corrigendum or interpretation sheet). - name consolidations (such as base edition plus its amendment)The adjunct string is appended to the base URI (after || or _)
EXAMPLE: Naming an adjunct (e.g. corrigendum to an amendment):
EXAMPLE: Consolidation of base edition and its amendments:
3. All values in lower-case
Separation between a base document and its adjuncts
When a base edition is amended, corrected or otherwise added to, the URN is constructed using that of the base edition, to which we add information on the adjunct. Two types of reference exist: either to the adjunct itself or to the consolidation of the base edition with one or more of its adjuncts.
The base edition information is separated from the adjunct information by three fields. The middle field indicates whether the reference is to a consolidation or not. If left empty, the reference is to the adjunct itself. If it contains the word "plus", it is a consolidation.
EXAMPLE: Amendment 1:1993 to IEC 60068-2-2:1974
EXAMPLE: Consolidation of amendment 1:1993 with IEC 60068-2-2:1974
Note on adjuncts
In theory, there is no limit to the number of adjuncts that are possible. In practice, when there are many adjuncts, it is advisable to either make use of an undated reference to the base edition as a whole, or to deliver content by different means, such as database standards.
Note on IDs
The IDs content elements used in this document and its examples are those that were used in IEC's conversion process. Outside the context of conversion excercises, the use of semantic ID naming schemes is not necessarily encouraged. This URN model can be used with other IDs.
Note on languages
Languages are listed in alphabetical order, to ensure that identical values are expressed in the same way (and at the same time, to avoid complex tables of language combinations to solve the problem)
Defining table
Examples
The text was updated successfully, but these errors were encountered: