The key procedures that a DMO shall use to maintain an OTD are:
Register Consensus Organization (see 7.2);
Add Concept (see 7.3);
Change Concept Documentation (see 7.4);
A DMO may define other procedures for its operation.
This procedure is used to add an organization to the list of consensus organizations authorized to submit terminology to an OTD. Figure 1 shows a flowchart of the procedure.
Step 1: |
An authorized official of the consensus organization submits a CORR to the secretariat of the DMO for the OTD. |
Step 2: |
The secretariat checks the CORR for completeness. If the CORR is incomplete go to step 5. |
Step 3: |
The secretariat verifies that the organization meets the requirements for a consensus organization. If the organization does not meet the requirements, go to step 5. |
Step 4: |
The secretariat records the CORR as accepted, assigns identifiers for the consensus organization and the ROCO, and updates the list of consensus organizations.Go to step 6. |
Step 5: |
The secretariat records the CORR as rejected. |
Step 6: |
The secretariat notifies the submitter of the action taken. If the CORR was accepted, the notification includes the assigned identifiers. |
Figure 1 — Procedure Register Consensus Organization
Table 1 — Times for steps for procedure Register Consensus Organization
Step | Time |
---|---|
1 |
0 |
2 |
5 |
3 |
7 |
4 |
3 |
5 |
3 |
6 |
1 |
This procedure is used to add a new concept to an OTD. Only a registered ROCO may submit a new concept. Figure 2 shows a flowchart of the procedure. Table 3 shows the time allowed for each step. In the case of steps performed by the secretariat, the time given for a step is the maximum time; the secretariat may complete the step sooner.
Step 1: |
A ROCO prepares a NCR and submits it to the secretariat of the DMO for the OTD. Table 2 shows the required content of a NCR. |
Step 2: |
The secretariat checks the NCR for completeness and that the submitter is a registered ROCO for a registered consensus organization. If the NCR is incomplete or the submitter is not a registered ROCO, go to step 6. |
Step 3: |
The secretariat issues a concept identifier and an identifier for each term, definition and image included in the NCR |
Step 4: |
The secretariat records the NCR as approved. |
Step 5: |
The secretariat adds the new concept and associated terms, definitions and images to an OTD master database. Go to step 7. |
Step 6: |
The secretariat records the NCR as rejected. |
Step 7: |
The secretariat notifies the submitter of the action taken. If the NCR was accepted, the notification includes the assigned identifiers. |
Figure 2 — Procedure Add Concept
Table 2 — Content of a NCR
Header section |
||
Element |
Number of values |
Recommended format |
Consensus organization identifier |
1 |
Organization identifier, as assigned by the secretariat under procedure Register Consensus Organization (see 7.2) |
Representative of consensus organization identifier |
1 |
Person identifier, as assigned by the secretariat under procedure Register Consensus Organization (see 7.2) |
Concept type name |
1 |
One of the following, if applicable:
|
Term section |
||
Element |
Number of values |
Recommended format |
Term content |
1 |
In accordance with ISO 22745-11 |
Originator reference string for the term |
1 |
As defined by the consensus organization |
Standard containing the term |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this standard), otherwise, local identifier assigned by the submitter (see standard section) |
Localization code of the term |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Published location of the term |
0 or more |
URL, in accordance with RFC 3986 |
Abbreviation content |
0 or 1 |
In accordance with ISO 22745-11 |
Originator reference string for the abbreviation |
0 or 1 (must be present if abbreviation content is present) |
As defined by the consensus organization |
Localization code of the abbreviation |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Standard containing the abbreviation |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this standard), otherwise, local identifier assigned by the submitter (see standard section) |
Published location of the abbreviation |
0 or more |
URL, in accordance with RFC 3986 |
Definition section |
||
Element |
Number of values |
Recommended format |
Definition content |
1 |
In accordance with ISO 22745-11 |
Originator reference string for the definition |
1 |
As defined by the consensus organization |
Standard containing the definition |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this standard), otherwise, local identifier assigned by the submitter (see standard section) |
Localization code of the definition |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Published location of the definition |
0 or more |
URL, in accordance with RFC 3986 |
Image section |
||
Element |
Number of values |
Recommended format |
Image file |
1 |
Portable Network Graphics (PNG) (attached file) (see ISO/IEC 15948) |
Originator reference string for the image |
1 |
As defined by the consensus organization |
Localization code of the image |
1 or more |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Standard containing the image |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this standard), otherwise, local identifier assigned by the submitter (see standard section) |
Published location of the image |
0 or more |
URL, in accordance with RFC 3986 |
Localization code section |
||
Element |
Number of values |
Recommended format |
Local identifier of the localization code |
1 |
Code that uniquely identifies the localization code within this NCR |
Language code |
1 |
ISO 639-1 alpha-2 code |
Country code |
1 |
ISO 3166-1 country code |
Dictionary |
1 |
ISO 690 (for printed dictionaries) or ISO 690-2 (for electronic dictionaries) |
Standard section |
||
Element |
Number of values |
Recommended format |
Local identifier of the standard |
1 |
Code that uniquely identifies the standard within this NCR |
Designator of the standard |
1 |
String that identifies the standard, according to a system defined by the consensus organization or its parent body. |
Title of the standard |
1 or more |
As defined by the consensus organization |
Uniform resource identifier (URI) for the standard |
0 or 1 |
URI, in accordance with RFC 3986 |
Version number of the standard |
0 or 1 |
As defined by the consensus organization |
Edition number of the standard |
0 or 1 |
As defined by the consensus organization |
Publication date of the standard |
1 |
ISO 8601 date code |
NOTE 1 Table 2 consists of a series of sections. Some sections can occur more than once. The number of times a section can be occur in a NCR is indicated by a line starting with "Occurrences". For example, the term section can be repeated more than once in case that the submitting organization recognizes more than one term for a concept.
NOTE 2 The local identifier of a localization code or standard is a code that uniquely identifies the localization code standard within a given NCR. It need not be unqiue outside the NCR.
NOTE 3 RFC 5141 defines a uniform resource name (URN) namespace for ISO and IEC publications. The URN syntax provides an identifier for each terminological entry within an ISO or IEC publication. ISO and IEC could use the URN syntax defined in RFC 5141 for the identifiers required in Table 2.
Table 3 — Times for steps for procedure Add Concept
Step | Time |
---|---|
1 |
0 |
2 |
5 |
3 |
5 |
4 |
5 |
5 |
5 |
6 |
3 |
7 |
1 |
This procedure is used to change the documentation of an existing concept. This includes adding a term, definition or image to an existing concept, marking a term, definition or image as deleted, or merging two concepts.
Figure 3 shows a flowchart of the procedure. Table 5 shows the time allowed for each step. In the case of steps performed by the secretariat, the time given for a step is the maximum time; the secretariat may complete the step sooner.
Step 1: |
The submitter prepares and submits a CDCR. Table 4 shows the required content of a CDCR. |
Step 2: |
The secretariat checks the CDCR for completeness. If the CDCR is incomplete, go to step 11. |
Step 3: |
The secretariat sends a request for approval (RFA) to the concept contributors for terms, definitions and images associated with the concept. |
Step 4: |
The concept contributors reply to the RFA. Negative replies must include a reason. |
Step 5: |
The secretariat compiles and distributes the results of the RFA to the concept contributors. If the result was negative, the secretariat notifies the submitter to respond to indicate the intent to continue the process. If the RFA was approved, go to step 10. |
Step 6: |
The submitter notifies the secretariat of the intent to continue the process. If the submitter does not notify the secretariat within the specified time period of the intent to continue the process, go to step 11. |
Step 7: |
The secretariat sends a ballot to the VC. |
Step 8: |
The members of the VC respond to the ballot. |
Step 9: |
The secretariat compiles and distributes the ballot results. Approval requires a simple majority of those VC members voting. If the ballot was not successful, go to step 11. |
Step 10: |
The secretariat records the CDCR as approved and makes the necessary updates to an OTD master database to implement the CDCR. Go to step 12. |
Step 11: |
The secretariat records the CDCR as rejected. |
Step 12: |
The secretariat notifies the submitter of the action taken. |
Figure 3 — Procedure Change Concept Documentation
Table 4 — Content of a CDCR
Header section |
||
Element |
Number of values |
Recommended format |
Submitting organization identifier |
0 or 1 |
Organization identifier, as assigned by the secretariat under procedure Register Consensus Organization (see 7.2) |
Submitting organization name |
0 or 1 |
|
Organization representative identifier |
0 or 1 |
Person identifier, as assigned by the secretariat under procedure Register Consensus Organization (see 7.2) |
Organization representative name |
0 or 1 |
|
Description section |
||
Element |
Number of values |
Recommended format |
Concept identifier |
1 or more (more than one only if type of change is "merge concepts") |
As assigned by the secretariat |
Type of change |
1 |
One of the following, if appropriate:
|
Description of change |
1 |
Reference OTD identifiers when referring to elements already in the OTD |
Term section |
||
Element |
Number of values |
Recommended format |
Term content |
1 |
In accordance with ISO 22745-11 |
Originator reference string for the term |
1 |
As defined by the consensus organization |
Standard containing the term |
1 |
Local identifier of the standard (see standard section) |
Localization code of the term |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Published location of the term |
0 or more |
URL, in accordance with RFC 3986 |
Abbreviation content |
0 or 1 |
In accordance with ISO 22745-11 |
Originator reference string for the abbreviation |
0 or 1 (must be present if abbreviation content is present) |
As defined by the consensus organization |
Localization code of the abbreviation |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Standard containing the abbreviation |
1 |
Local identifier of the standard (see standard section) |
Published location of the abbreviation |
0 or more |
URL, in accordance with RFC 3986 |
Definition section |
||
Element |
Number of values |
Recommended format |
Definition content |
1 |
In accordance with ISO 22745-11 |
Originator reference string for the definition |
1 |
As defined by the consensus organization |
Standard containing the definition |
1 |
Local identifier of the standard (see standard section) |
Localization code of the definition |
1 |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Published location of the definition |
0 or more |
URL, in accordance with RFC 3986 |
Image section |
||
Element |
Number of values |
Recommended format |
Image file |
1 |
Portable Network Graphics (PNG) (attached file) (see ISO/IEC 15948) |
Originator reference string for the image |
1 |
As defined by the consensus organization |
Localization code of the image |
1 or more |
As assigned by the secretariat (if the secretariat has already assigned an identifier for this localization code), otherwise, local identifier assigned by the submitter (see localization code section) |
Standard containing the image |
1 |
Local identifier of the standard (see standard section) |
Published location of the image |
0 or more |
URL, in accordance with RFC 3986 |
Localization code section |
||
Element |
Number of values |
Recommended format |
Local identifier of the language-country combination |
1 |
Code that uniquely identifies the language-country combination within this NCR |
Language of terminology |
1 |
ISO 639-1 alpha-2 code |
Country where terminology is used |
1 |
ISO 3166-1 country code |
Dictionary defining the spelling and meaning of words in the terminology |
1 |
ISO 690 (for printed dictionaries) or ISO 690-2 (for electronic dictionaries) |
Standard section |
||
Element |
Number of values |
Recommended format |
Local identifier of the standard |
1 |
Code that uniquely identifies the standard within this NCR |
Designator of the standard |
1 |
String that identifies the standard, according to a system defined by the consensus organization or its parent body. |
Title of the standard |
1 or more |
As defined by the consensus organization |
Uniform resource identifier (URI) for the standard |
0 or 1 |
URI, in accordance with RFC 3986 |
Version number of the standard |
0 or 1 |
As defined by the consensus organization |
Edition number of the standard |
0 or 1 |
As defined by the consensus organization |
Publication date of the standard |
1 |
ISO 8601 date code |
NOTE 1 Table 4 consists of a series of sections. Some sections can occur more than once. The number of times a section can be occur in a CDCR is indicated by a line starting with "Occurrences". For example, the term section can be repeated more than once in case that the submitting organization recognizes more than one term for a concept.
NOTE 2 The local identifier of a localization code or standard is a code that uniquely identifies the localization code standard within a given NCR. It need not be unqiue outside the CDCR.
Table 5 — Times for steps for procedure Change Concept Documentation
Step | Time |
---|---|
1 |
0 |
2 |
5 |
3 |
2 |
4 |
15 |
5 |
4 |
6 |
7 |
7 |
5 |
8 |
30 |
9 |
4 |
10 |
3 |
11 |
3 |
12 |
1 |