Term structure from ISO 10241-1

## 4.4.3 Recording terminological data

### 4.4.3.1 General

In order to ensure uniform work methods, before recording terminological data, a coding system shall be established for such data categories as date of record, sources, and person or organization recording the data.

The terminological data for each language shall be recorded in a uniform manner.

Each term and other kind of designation shall be recorded separately with a preliminary concept identifier that is unique for the concept in question within the respective standard. The same preliminary concept identifier shall be used for synonymous terms and equivalent terms in all languages.

The data categories in 4.4.3.2, 4.4.3.3 and 4.4.3.4 shall be taken into consideration for each language when recording terminological data.

#### 4.4.3.2 Designation-related data

##### 4.4.3.2.1 General

Designation-related data comprise

⎯ term-related data, and

⎯ data related to other kinds of designations.

##### 4.4.3.2.2 Term-related data

Term-related data refer to verbal designations, including multiword and other complex terms, and can consist of letters, letter symbols, numerals, mathematical symbols, typographical signs and syntactic signs (e.g. punctuation marks, hyphens, parentheses, square brackets and other connectors or delimiters) as well as the respective character styles (i.e. fonts and bold, italic, bold italic or other style conventions) to render them.

NOTE 1 In practice, any combination of verbal and non-verbal designations can occur in scientific technical literature and technical documentation.

NOTE 2 The rules provided here for terms also apply largely to appellations. Term-related data may include the following:

a) terms:

1) verbal designations [i.e. designations (see 3.4.1.1.1) excluding graphical symbols (see 3.4.1.1.5)];

2) abbreviated forms (see 3.4.1.2.4);

3) full forms (see 3.4.1.2.3);

4) letter symbols (see 3.4.1.1.4);

5) variants (see 3.4.1.2.2);

6) equivalent terms in other languages (including a note indicating the degree of equivalence if relevant);

b) normative status (see 3.4.1.3);

c) grammatical information;

d) note(s) to entry referring to the term or any other data category under 4.4.3.2.2 a) 1) to a) 5);

e) other useful terms, such as homographs (see 3.4.1.4) and antonyms (see 3.4.1.5) (together with a brief explanation if necessary), and cross-referencing.

It may also be necessary to record usage information for terms such as language (indicated by language codes in accordance with ISO 639), script (indicated by a script code in accordance with ISO 15924), geographical usage (indicated by country codes in accordance with ISO 3166) and other secondary data categories defined in the ISO Data Category Registry (DCR) on the basis of ISO 12620.

Some of the above-mentioned usage information for terms is recorded in terminology databases but is not required to be shown in a standardized terminological entry.

NOTE 3 In IEC (which develops standards in the electrotechnology domain), the usage information related to a term's

“specific use” can be a complement to the term but is not necessarily a domain or subject as described in this part of

ISO 10241. For further information, see the IEC Supplement to the ISO/IEC Directives, Annex I, Implementation of the [1]

ISO/IEC Directives for the work on the International Electrotechnical Vocabulary (IEV) .

##### 4.4.3.2.3 Data related to non-verbal designations

Data related to non-verbal designations can include the following:

a) graphical symbols (see 3.4.1.1.5) and other non-verbal designations;

b) normative status (see 3.4.1.3);

c) note(s) to entry referring to non-verbal designations [i.e. graphical symbols (see 3.4.1.1.5)];

d) other useful information, such as homographs (together with a brief explanation if necessary) and cross-referencing.

NOTE In practice, any combination of verbal and non-verbal designations can occur in scientific technical literature and technical documentation. Thus, letters, numerals, symbols for quantities and units, mathematical symbols, typographical signs and syntactic signs rendered in the respective domain- or subject-specific conventions may be used as components of, or in combination with, graphical symbols.

#### 4.4.3.3 Concept-related data

Concept-related data may include the following:

a) domain or subject [e.g. a descriptive text (such as a committee title) or a code (such as an ICS code)];

b) definitions;

c) contexts;

d) non-verbal representations of the concept;

e) examples;

f) note(s) to entry referring to a definition, context (see 3.4.2.2), example or non-verbal representation;

g) note(s) to entry referring to an entire terminological entry (or to a given language section of a terminological entry);

h) position in concept system, if known.

Comments concerning the above-mentioned concept-related data are recorded in terminology databases but are not required to be shown in a standardized terminological entry. Therefore, they are not included in the data categories listed in 5.3.

#### 4.4.3.4 Administrative data

Administrative data may include the following:

a) preliminary concept identifier;

NOTE 1 The preliminary concept identifier is replaced by the entry number in the standardized terminological entry.

b) language codes in accordance with ISO 639, if necessary, followed by codes for geographical usage in accordance with ISO 3166 (names of countries and their subdivisions) or a script code in accordance with ISO 15924 (names of scripts);

c) date of record (and of any modification);

d) person (or organization) responsible for the terminological data;

NOTE 2 The types of responsibility (with respect to terminological data recording and maintenance of individuals to whom an identifier is usually assigned) can include originator, inputter, updater, checker, approver, user, subset owner, withdrawer, exporter, importer. (See http://www.isocat.org/interface/index.html.)

e) sources.

The issue provides ISO 10241-1 sections 4.4.3.1–4.4.3.4 but names no repository files, tests, or entry points. First determine how this repository represents terminological data and where the proposed term structure belongs. Done is not defined by the issue, so confirm the intended scope and acceptance criteria before starting.

Written by the indexing model from the issue text.