ISO 15022-1:1999 証券—メッセージのスキーム（データフィールドディクショナリ）—パート1：データフィールドとメッセージのデザインルールとガイドライン | ページ 6

3.1

block of data fields

predefined and identified set of functionally related data fields related to a business concept

Note 1 to entry: A block of data fields is identified by a start of block and an end of block data field which both mention the block name, which qualifies the specific meaning of the block. The block of data fields may be repeating. A block of data fields may also include other, nested, blocks of data fields.

3.2

community of users

financial institutions sharing the same market practice and using the same message standards

3.3

component data element

simple data element which is a subordinate portion of a composite data element identified by its position within the composite data element

3.4

composite data element

data element containing two or more component data elements

3.5

data element

data elementunit of data for which the identification, description and value representation have been specified

Note 1 to entry: A data element in certain contexts is considered indivisible.

3.6

data element tag

unique identifier for a data element in an EDIFACT data elements directory (see field tag)

3.7

data field

data field consists of a field tag followed by a data item

Note 1 to entry: It is used to convey a simple data element or a composite data element which represents a unit of meaningful information.

3.8

data item

expression of a single data element or a composite data element represented in a specific format and identified by the preceding field tag

3.9

data source issuer code

string of characters used to identify the institution or market organization owning the data source scheme

3.10

data source issuer sub-code

identification of the specific data source scheme for the data source issuer

3.11

data source scheme

data source scheme consists of two sub-fields, the data source issuer code and the data source issuer sub-code, which are used in the data field tag to identify a proprietary scheme for the data item

3.12

discrete data field

data field which expresses a specific single business data item

Note 1 to entry: The field tag of a discrete data field does not need a qualifier to further define the business meaning of the data item.

3.13

field tag

unique string of characters identifying the meaning, format, and value representation of the following data item (see data element tag)

Note 1 to entry: A field tag is made up of a field type optionally followed by a qualifier and a data source scheme.

3.14

field type

unique string of characters which starts the field tag and identifies the format and value representation of the data item

Note 1 to entry: It also identifies either the meaning of the following data item (see discrete data field) or the class of the following data item (see generic data field).

3.15

generic data field

data field used to express the data of a family or class of data items of the same nature, e.g. dates, amounts

Note 1 to entry: The field tag of a generic data field contains a qualifier to specify the precise meaning of the following data item.

3.16

group of segments

identified, usually repeatable, grouping of segments

3.17

message

series of data fields and/or blocks of data fields communicated from one party to another to convey meaningful business information

Note 1 to entry: In EDIFACT, a set of segments in the order specified in an EDIFACT message directory starting with the message header and ending with the message trailer.

3.18

message code

unique string of characters identifying the message type

3.19

message descriptor

string of characters which specifies the scope of the message and the fields that may be used

Note 1 to entry: A message descriptor is made up of a message code optionally followed by a version number and a message version sub-format.

3.20

message type

identified and structured set of data items or data elements used to convey information related to a specific business scope

3.21

message version issuer code

string of characters used to identify the institution or market segment owning the message version sub-format

3.22

message version issuer sub-code

identification of the specific message version sub-format for the message version issuer

3.23

message version sub-format

message version sub-format consists of two sub-fields, the message version issuer code and the message version issuer sub-code, which are used in the message descriptor to identify a proprietary sub-format

3.24

nested segment

segment which directly relates to another segment in an identified and structured group of segments covering the requirements for a specific message type

3.25

qualified data element

data element whose precise meaning is conveyed by an associated qualifier

3.26

qualified segment

segment whose precise meaning is conveyed by an associated qualifier

3.27

qualifier

data element whose value is expressed as a code that gives specific meaning to the function of another data element, data item, or segment

3.28

repeating segment

segment which may repeat in a message as specified in the relevant message type specification

3.29

segment

predefined and identified set of functionally related data element values

Note 1 to entry: A segment starts with a segment tag and ends with a segment terminator.

3.30

segment tag

simple data element uniquely identifying a segment

3.31

separator

character(s) used for the syntactical separation of data

3.32

sequence

predefined set of data fields for documentation purposes only

3.33

simple data element

data element containing a single value

3.34

sub-field

subdivision or subordinate portion of a composite data element or of a field tag or of a message descriptor

3.35

version number

allows different versions of the message type to be supported concurrently