ISO 12616-1:2021 多言語コミュニケーションをサポートする用語集—パート1：翻訳指向の用語集の基礎 | ページ 6

3.1

terminology

set of designations (3.7) and concepts (3.4) belonging to one subject field (3.2) or subject

[SOURCE:ISO 1087:2019, 3.1.11, modified — “domain” replaced with “subject field”, which is the preferred term in this document.]

3.2

subject field

domain

field of special knowledge

Note 1 to entry: The borderlines and the granularity of a subject field are determined from a purpose-related point of view. If a subject field is subdivided, the result is again a subject field.

[SOURCE:ISO 1087:2019, 3.1.4, modified — The preferred term in this document is “subject field”, instead of “domain”.]

3.3

object

anything perceivable or conceivable

Note 1 to entry: Objects can be material (e.g. ‘engine’, ‘sheet of paper’, ‘diamond’), immaterial (e.g. ‘conversion ratio’, ‘project plan’) or imagined (e.g. ‘unicorn’, ‘scientific hypothesis’).

[SOURCE:ISO 1087:2019, 3.1.1]

3.4

concept

unit of knowledge created by a unique combination of characteristics

Note 1 to entry: Concepts are not necessarily bound to particular natural languages. They are, however, influenced by the social or cultural background which often leads to different categorizations.

[SOURCE:ISO 1087:2019, 3.2.1 modified — Removed Note 2 to entry.]

3.5

individual concept

concept (3.4) that corresponds to a unique object (3.3)

Note 1 to entry: Individual concepts are represented by proper names (3.10) .

[SOURCE:ISO 1087:2019, 3.2.8]

3.6

general concept

concept (3.4) that corresponds to a potentially unlimited number of objects (3.3) which form a group by reason of shared properties

Note 1 to entry: For a general concept, it is essential that a number of corresponding objects greater than 1 can be perceived or conceived of. For example, ‘spaceship’ has been a general concept before such a material object existed, at the time when there existed only 1 such object, and later, when there existed several such objects.

[SOURCE:ISO 1087:2019, 3.2.9]

3.7

designation

representation of a concept (3.4) by a sign which denotes it in a subject field (3.2) or subject

Note 1 to entry: A designation can be linguistic or non-linguistic. It can consist of various types of characters, but also punctuation marks such as hyphens and parentheses, governed by domain-, subject-, or language-specific conventions.

Note 2 to entry: A designation can be a term (3.8) including appellations (3.9) , a proper name (3.10) , or a symbol (3.11) .

[SOURCE:ISO 1087:2019, 3.4.1; modified — Removed “designator” as a synonym. In the definition, “domain” replaced with “subject field”.]

3.8

term

designation (3.7) that represents a general concept (3.6) by linguistic means

Note 1 to entry: Terms may be partly or wholly verbal.

[SOURCE:ISO 1087:2019, 3.4.2]

3.9

appellation

term (3.8) that is applied to a group of objects (3.3) whose relevant properties are identical

[SOURCE:ISO 1087:2019, 3.4.3]

3.10

proper name

designation (3.7) that represents an individual concept (3.5)

[SOURCE:ISO 1087:2019, 3.4.4]

3.11

symbol

designation (3.7) that represents a concept (3.4) by non-linguistic means

Note 1 to entry: There are several types of symbols such as graphical symbols [ISO 3864 (all parts)] and letter symbols [ISO 80000 (all parts)].

[SOURCE:ISO 1087:2019, 3.4.5]

3.12

terminology work

terminology management

work concerned with the collection, description, processing and presentation of concepts (3.4) and their designations (3.7)

Note 1 to entry: Terminology work often aims at creating and maintaining terminological data collections (3.21) .

Note 2 to entry: Terminology work often aims at terminology planning and can involve all of concept harmonization, term harmonization, and term formation.

Note 3 to entry: Terminology work can be carried out in a systematic or an ad hoc fashion.

[SOURCE:ISO 1087:2019, 3.5.1, modified — In the definition, removed “systematic”. In Note 1 to entry, “terminology resources” replaced with “terminological data collections”. Added Note 3 to entry.]

3.13

prescriptive terminology work

terminology work (3.12) that aims at deciding on preferred usage of designations (3.7)

3.14

descriptive terminology work

terminology work (3.12) that aims at documenting designations (3.7) as they are used in contexts without favouring preferred usage

3.15

terminography

terminology work (3.12) aimed at creating and maintaining terminological data collections (3.21)

[SOURCE:ISO 1087:2019, 3.5.2, modified — “terminology resources” replaced with “terminological data collections”.]

3.16

term extraction

terminology work (3.12) that involves the identification and excerption of terminological data (3.19) by searching through a text corpus (3.17)

Note 1 to entry: Terminological data (3.19) of primary interest are typically designations (3.7) , definitions and contexts.

Note 2 to entry: Term extraction is often supported by dedicated software tools.

[SOURCE:ISO 1087:2019, 3.5.6]

3.17

text corpus

corpus

collection of natural language data

Note 1 to entry: Text corpora can be used for various activities such as text analysis or terminology work (3.12) .

[SOURCE:ISO 1087:2019, 3.6.4]

3.18

candidate term

string of characters that has been collected by means of term extraction (3.16) but has not yet been selected as a text element to be documented in the terminological data collection (3.21)

3.19

terminological data

data related to concepts (3.4) and their designations (3.7)

Note 1 to entry: Common terminological data include designations (3.7) , definitions, contexts, notes to entry, grammatical labels, subject labels, language identifiers, country identifiers, and source identifiers.

[SOURCE:ISO 1087:2019, 3.6.1]

3.20

terminological entry

concept entry

ce

collection of terminological data (3.19) related to only one concept (3.4)

[SOURCE:ISO 1087:2019, 3.6.2, modified — Added “concept entry” and “CE” as preferred and admitted terms, respectively.]

3.21

terminological data collection

TDC

terminology resource

resource consisting of concept entries (3.20) with associated metadata and documentary information

[SOURCE:ISO 26162-1:2019, 3.2.4, modified — Added “terminology resource” from ISO 1087:2019, 3.7.1.]

3.22

data category

class of data items that are closely related from a formal or semantic point of view

Note 1 to entry: A data category can be viewed as a generalization of the notion of a field in a database.

Note 2 to entry: In running text, such as in this document, data category names are enclosed in forward slashes (e.g./part of speech/).

[SOURCE:ISO 26162-1:2019, 3.2.11]

3.23

terminology management system

TMS

software tool specifically designed with a metadata structure for collecting, maintaining, and accessing terminological data (3.19)

[SOURCE:ISO 1087:2019, 3.6.13]

3.24

concept orientation

principle whereby a concept entry (3.20) describes a single concept (3.4)

Note 1 to entry: When two or more different concepts (3.4) are represented by the same designation (3.7) (in the same language), this designation is considered a homograph. Such concepts (3.4) are documented in separate concept entries (3.20) .

[SOURCE:ISO 26162-1:2019, 3.2.13]

3.25

term autonomy

principle whereby all terms (3.8) in a concept entry (3.20) are considered independent sub-units and can be described using the same set of data categories (3.22)

Note 1 to entry: By analogy, this principle applies to designations (3.7) as well as other text elements.

[SOURCE:ISO 26162-1:2019, 3.2.14]

3.26

data granularity

degree of precision of data

Note 1 to entry: For example, the set of individual data categories (3.22) /part of speech/,/grammatical gender/, and/grammatical number/ provides for greater data granularity than does the single data category/grammar/.

[SOURCE:ISO 26162-1:2019, 3.2.15]

3.27

repeatability

principle whereby a data category (3.22) can be repeated within a database definition and whereby it can also be combined with other data categories

[SOURCE:ISO 26162-1:2019, 3.2.12]

3.28

data elementarity

principle whereby a data field contains only one data element

[SOURCE:ISO 26162-1:2019, 3.2.16]

3.29

terminology worker

person whose role is to perform terminology work (3.12) as an ancillary function of other professional activities

3.30

terminologist

expert who performs terminology work (3.12) as a main function of a professional activity

3.31

technical communicator

expert who defines, creates and delivers information products for the safe, efficient and effective use of products

Note 1 to entry: Products may be technical systems, software, or services.

3.32

source language

language of the content to be translated

[SOURCE:ISO 18587:2017, 3.2.2]

3.33

target language

language into which source language content is translated

[SOURCE:ISO 17100:2015, 2.3.6]

3.34

transfer comment

note in a terminological data collection (3.21) providing information on the degree of equivalence, directionality or other special features affecting equivalence between a designation (3.7) in one language and another designation in a second language