ISO 9735-1:2002

INTERNATIONAL ISO
STANDARD 9735-1
Second edition
2002-07-01
Electronic data interchange for
administration, commerce and transport
(EDIFACT) — Application level syntax rules
(Syntax version number: 4, Syntax release
number: 1) —
Part 1:
Syntax rules common to all parts
Échange de données informatisé pour l'administration, le commerce et le
transport (EDIFACT) — Règles de syntaxe au niveau de l'application
(numéro de version de syntaxe: 4, numéro d'édition de syntaxe: 1) —
Partie 1: Règles de syntaxe communes à l'ensemble des parties

Reference number
©
ISO 2002
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2002
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO 2002 – All rights reserved

Contents Page
Foreword.v
Introduction.vii
1 Scope .1
2 Conformance.1
3 Normative references.2
4 Terms and definitions .2
5 Service characters.13
5.1 General.13
5.2 Default service characters.13
5.3 UNA, service string advice .14
6 Character repertoires .14
7 Syntax structures .15
7.1 General.15
7.2 Interchange structure.15
7.3 Group structure .15
7.4 Message structure .15
7.5 Segment group structure.15
7.6 Segment structure .16
7.7 Segment tag structure.16
7.8 Composite data element structure .16
7.9 Simple data element structure .16
7.10 Package structure.16
8 Inclusion and exclusion.16
8.1 General.16
8.2 Determination of presence .17
8.3 Inclusion of segment groups .17
8.4 Exclusion of segment groups .17
8.5 Inclusion of segments.17
8.6 Exclusion of segments.17
8.7 Inclusion of data elements.17
8.8 Exclusion of data elements .18
9 Suppression of characters within data elements.19
9.1 General.19
9.2 Insignificant characters .19
9.3 Significant zeroes .20
9.4 Significant spaces .20
10 Representation of numeric data element values.20
11 Dependency notes.20
11.1 General.20
11.2 Dependency notes in the message specification .20
11.3 Dependency notes in the segment specification .21
11.4 Dependency notes in the composite data element specification.21
11.5 Notation for dependency notes.21
12 Segment collision prevention .22
13 Syntax release identification .22
Annex A (normative) UNA service string advice .23
Annex B (informative) Order of segments and groups of segments within a message .24
Annex C (informative) The use of anti-collision segment group UGH/UGT.27
Annex D (informative) Syntax release identification .30

iv © ISO 2002 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO
member bodies). The work of preparing International Standards is normally carried out through ISO technical
committees. Each member body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, governmental and non-governmental, in
liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
The main task of technical committees is to prepare International Standards. Draft International Standards adopted
by the technical committees are circulated to the member bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this part of ISO 9735 may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 9735-1 was prepared by Technical Committee ISO/TC 154, Processes, data elements and documents in
commerce, industry and administration in collaboration with UN/CEFACT through the Joint Syntax Working Group
(JSWG).
This second edition cancels and replaces the first edition (ISO 9735-1:1998) to which one new feature to the
EDIFACT syntax, version 4 has been added: Syntax release identification. However ISO 9735:1988 and its
Amendment 1:1992 are provisionally retained for the reasons given in clause 2.
Furthermore, for maintenance reasons the Syntax service directories have been removed from this and all other
parts of ISO 9735. They are now consolidated in a new part, ISO 9735-10.
At the time of publication of ISO 9735-1:1998, ISO 9735-10 had been allocated as a part for “Security rules for
interactive EDI”. This was subsequently withdrawn because of lack of user support, and as a result, all relevant
references to the title “Security rules for interactive EDI” have been removed in this second edition of ISO 9735-1.
Definitions from all parts of the ISO 9735 series have been consolidated and included in this part of ISO 9735.
The Introduction has also been updated to summarize the new feature and all other changes.
Together with ISO 9735-2, this part of ISO 9735 is an enhancement of ISO 9735:1988 and its Amendment 1:1992.
ISO 9735 consists of the following parts, under the general title Electronic data interchange for administration,
commerce and transport (EDIFACT) — Application level syntax rules (Syntax version number: 4, Syntax release
number: 1):
— Part 1: Syntax rules common to all parts
— Part 2: Syntax rules specific to batch EDI
— Part 3: Syntax rules specific to interactive EDI
— Part 4: Syntax and service report message for batch EDI (message type — CONTRL)
— Part 5: Security rules for batch EDI (authenticity, integrity and non-repudiation of origin)
— Part 6: Secure authentication and acknowledgement message (message type — AUTACK)
— Part 7: Security rules for batch EDI (confidentiality)
— Part 8: Associated data in EDI
— Part 9: Security key and certificate management message (message type — KEYMAN)
— Part 10: Syntax service directories
Further parts may be added in the future.
Annex A forms a normative part of this part of ISO 9735. Annexes B, C and D are for information only.

vi © ISO 2002 – All rights reserved

Introduction
This part of ISO 9735 includes the rules at the application level for the structuring of data in the interchange of
electronic messages in an open environment, based on the requirements of either batch or interactive processing.
These rules have been agreed by the United Nations Economic Commission for Europe (UN/ECE) as syntax rules
for Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) and are part of the United
Nations Trade Data Interchange Directory (UNTDID) which also includes both batch and interactive Message
Design Guidelines.
This part of ISO 9735 may be used in any application, but messages using these rules may only be referred to as
EDIFACT messages if they comply with other guidelines, rules and directories in the UNTDID. For UN/EDIFACT
messages, the message design rules for batch or interactive usage apply, as appropriate. These rules are
maintained in the UNTDID.
Communications specifications and protocols are outside the scope of this part of ISO 9735.
A previous version of ISO 9735 was published in 1988 as a single part. The current version of ISO 9735 consists of
multiple parts and incorporates enhancements to extend its application.
This part of ISO 9735 is a re-draft of corresponding sections in the previous version of ISO 9735. It consists of the
rules common to all parts of ISO 9735, and includes the definitions for all parts.
The basic syntax rules specified in this part remain unchanged from the previous version, with the exception that
the coverage of character repertoires has been extended, and two new techniques have been introduced (the
provision for “dependency notes” and the introduction of a service repetition character, to support the capability of
permitting multiple occurrences (repeats) of stand-alone and/or composite data elements). Both of these
techniques are used in other parts of the current version of ISO 9735, and are available for specification in
EDIFACT messages which utilize this International Standard.
In addition, enhancements have been made to the batch interchange; group; and message header segments
(UNB; UNG; and UNH).
Character repertoires: Because of the widening use of ISO 9735, it has become necessary to extend its coverage
to include all character repertoires covered by ISO 8859, parts 1-9; the code extension techniques covered by
ISO 2022 (with certain restrictions on its use within an interchange); and partial use of the techniques covered by
ISO/IEC 10646-1.
Dependency notes: These provide a formal notation to express relationships in EDIFACT message, segment and
composite data element specifications.
Repeating data elements: The specification of multiple occurrences of a message within a group or within an
interchange; a group within an interchange; and a segment group and/or a segment within a message, which
existed in the previous version of ISO 9735, has been extended in the current version. The additional capability for
the specification of multiple occurrences of a stand-alone data element and/or of a composite data element within a
segment has been introduced.
UNB - Interchange header segment: This segment has been enhanced to permit the identification of the service
code list directory version number; identification of the character encoding scheme; and internal sub-identification
of the sender and recipient. In addition, to conform to year 2000 requirements, the date format in this segment has
been extended.
UNG - Group header segment: This segment has been renamed and its function changed to permit one or more
message types and/or packages to be contained in the group. As a result, certain data elements, which are now
redundant, have been marked for deletion. In addition, to conform to year 2000 requirements, the date format in
this segment has been extended.
UNH - Message header segment: This segment has been enhanced to permit the identification of a message
subset; of a related message implementation guideline; and of a related scenario.
Segment collision prevention: An addition has been made to permit the prevention of collision, by use of the
UGH/UGT segment group. This technique shall be used in a message specification when it is not otherwise
possible to ensure unambiguous identification of each message segment upon receipt.
Syntax release identification: An addition has been made to permit the identification of specific releases related to
the syntax version number. This will facilitate the publication of minor changes to the standard (if required in the
future).
viii © ISO 2002 – All rights reserved

INTERNATIONAL STANDARD ISO 9735-1:2002(E)

Electronic data interchange for administration, commerce and
transport (EDIFACT) — Application level syntax rules (Syntax
version number: 4, Syntax release number: 1) —
Part 1:
Syntax rules common to all parts
1 Scope
This part of ISO 9735 specifies common syntax rules for the formatting of batch and interactive messages to be
interchanged between computer application systems. It includes the terms and definitions for all parts of ISO 9735.
2 Conformance
Whereas this part shall use a version number of “4” in the mandatory data element 0002 (Syntax version number),
and shall use a release number of “01” in the conditional data element 0076 (Syntax release number), each of
which appear in the segment UNB (Interchange header), interchanges continuing to use the syntax defined in the
earlier published versions shall use the following Syntax version numbers, in order to differentiate them from each
other and from this part:
 ISO 9735:1988: Syntax version number: 1
 ISO 9735:1988 (amended and reprinted in 1990): Syntax version number: 2
 ISO 9735:1988 and its Amendment 1:1992: Syntax version number: 3
 ISO 9735:1998: Syntax version number: 4
Conformance to a standard means that all of its requirements, including all options, are supported. If all options are
not supported, any claim of conformance shall include a statement which identifies those options to which
conformance is claimed.
Data that is interchanged is in conformance if the structure and representation of the data conforms to the syntax
rules specified in this part of ISO 9735.
Devices supporting this part of ISO 9735 are in conformance when they are capable of creating and/or interpreting
the data structured and represented in conformance with the standard.
Conformance shall be based on this part of ISO 9735, on ISO 9735-10, and at least either ISO 9735-2 or
ISO 9735-3.
When identified in this part of ISO 9735, provisions defined in related standards shall form part of the conformance
criteria.
3 Normative references
The following normative documents contain provisions which, through reference in this text, constitute provisions of
this part of ISO 9735. For dated references, subsequent amendments to, or revisions of, any of these publications
do not apply. However, parties to agreements based on this part of ISO 9735 are encouraged to investigate the
possibility of applying the most recent editions of the normative documents indicated below. For undated
references, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain
registers of currently valid International Standards.
ISO/IEC 646:1991, Information technology — ISO 7-bit coded character set for information interchange
ISO/IEC 2022:1994, Information technology — Character code structure and extension techniques
ISO/IEC 2382-1:1993, Information technology — Vocabulary — Part 1: Fundamental terms
ISO/IEC 2382-4:1999, Information technology — Vocabulary — Part 4: Organization of data
ISO 6093:1985, Information processing — Representation of numerical values in character strings for information
interchange
ISO/IEC 6429:1992, Information technology — Control functions for coded character sets
ISO/IEC 6523-1:1998, Information technology — Structure for the identification of organizations and organization
parts — Part 1: Identification of organization identification schemes
ISO 7498-2:1989, Information processing systems — Open Systems Interconnection — Basic Reference Model —
Part 2: Security Architecture
ISO/IEC 9594-8:1998, Information technology — Open Systems Interconnection — The Directory: Authentication
framework
ISO 9735-2:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 2: Syntax rules specific
to batch EDI
ISO 9735-3:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 3: Syntax rules specific
to interactive EDI
ISO 9735-10:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 10: Syntax service
directories
ISO/IEC 10646-1:2000, Information technology — Universal Multiple-Octet Coded Character Set (UCS) — Part 1:
Architecture and Basic Multilingual Plane
ISO/IEC 11770-1:1996, Information technology — Security techniques — Key management — Part 1: Framework
ITU-T Recommendation F.400/X.400:1999, Message handling system and service overview
4 Terms and definitions
For the purposes of all parts of ISO 9735, the following terms and definitions apply.
NOTE 1 When a word or phrase appears in italics within a definition, this means that a definition for this term is given in this
clause.
NOTE 2 The terms are classified alphabetically; an identifier is added at the end of each definition, in square brackets, to
facilitate the comparison between different linguistic versions. For example the English term “Alphabetic character set” is called
in French “Jeu de caractères alphabétiques”, and will not appear at the same alphabetic place in the two versions of the syntax;
the identifier in brackets nevertheless remains “[1]”.
2 © ISO 2002 – All rights reserved

4.1
alphabetic character set
character set that contains letters and/or ideograms, and may contain other graphic characters except digits [1]
4.2
alphanumeric character set
character set that contains letters, digits and/or ideograms, and may contain other graphic characters [2]
4.3
asymmetric algorithm
cryptographic algorithm employing a public key and a private key which together form an asymmetric key set [3]
4.4
attribute
characteristic of an entity [4]
4.5
authentication
See data origin authentication [5]
4.6
batch EDI
electronic data interchange in which no strong requirements exist for formalized data exchange using query and
response between the parties [6]
4.7
business
series of processes, each having a clearly understood purpose, involving more than one organization, realized
through the exchange of information and directed towards some mutually agreed upon goal, extending over a
period of time [7]
4.8
certificate
public key of a user, together with some other information, rendered unforgeable by a signature with the private key
of the certification authority which issued it [8]
[ISO/IEC 9594-8:1998, 3.3.3]
4.9
certification authority
authority trusted by one or more users to create and assign certificates [9]
[ISO/IEC 9594-8:1998, 3.3.8]
4.10
certification path
ordered sequence of certificates of objects in the Directory Information Tree which, together with the public key of
the initial object in the path, can be processed to obtain that of the final object in the path [10]
[ISO/IEC 9594-8:1998, 3.3.9]
4.11
character
member of a set of elements used for the organization, control, or representation of data [11]
[ISO/IEC 10646-1:2001, 4.6]
4.12
character repertoire
set of graphic characters of a coded character set, considered independently of its encoding [12]
4.13
code extension
techniques for the encoding of characters that are not included in the character repertoire of a given coded
character set [13]
4.14
code list
complete set of data element values of a coded simple data element [14]
4.15
code list directory
listing of identified and specified code lists [15]
4.16
coded character set
set of unambiguous rules that establishes a character set and the one-to-one relationship between the characters
of the set and their bit combinations [16]
[ISO/IEC 6429:1992]
4.17
component data element
simple data element used within a composite data element [17]
4.18
component data element separator
service character used to separate the component data elements within a composite data element [18]
4.19
composite data element
identified, named and structured set of functionally related component data elements, as described in a composite
data element specification [19]
NOTE In transfer, a composite data element is a specific ordered set of one or more component data element(s) in
conformance with a composite data element specification.
4.20
composite data element directory
listing of identified and named composite data elements with their composite data element specification [20]
4.21
composite data element specification
description of a composite data element in a composite data element directory, including the specification of the
position and status of the component data elements constituting the composite data element [21]
4.22
conditional
type of status, used in a message specification, segment specification, or composite data element specification, to
specify that a segment group, segment, composite data element, stand-alone data element or component data
element is used optionally or when the appropriate conditions occur [22]
4.23
confidentiality
property that information is not made available or disclosed to unauthorized individuals, entities or processes [23]
[ISO 7498-2:1989, 3.3.16]
4 © ISO 2002 – All rights reserved

4.24
control character
a character whose purpose is to effect format, to control data transmission, or to perform other control
functions [24]
NOTE A control character, altough it is not a graphic character, may have a graphic representation.
[ISO/IEC 2382-4:1999, 04.04.01]
4.25
credential
data that serves to establish the claimed identity of an entity [25]
[ISO 7498-2:1989, 3.3.17]
4.26
cryptography
discipline which embodies principles, means, and methods for the transformation of data in order to hide its
information content, prevent its undetected modification and/or prevent its unauthorized use [26]
[ISO 7498-2:1989, 3.3.20]
4.27
data
reinterpretable representation of information in a formalized manner suitable for communication, interpretation or
processing [27]
[ISO/IEC 2382-1:1993, 01.01.02]
4.28
data element
unit of data described in a data element specification [28]
NOTE There are two classes of data element: simple data elements and composite data elements.
4.29
data element directory
listing of identified, named and specified simple data elements (simple data element directory) or composite data
elements (composite data element directory) [29]
4.30
data element separator
service character used to separate from each:
 non repeating stand-alone data elements; or
 composite data elements in a segment; or
 a set of occurrences of a repeating data element; or
 a null set of occurrences of a repeating data element,
 where a set of occurrences of a repeating data element is a repeating data element having one or more of
its occurrences (up to a maximum specified number) present in a transfer; and
 where a null set of occurrences of a repeating data element is a repeating data element for which none of
its specified occurrences are present in a transfer [30]
4.31
data element specification
specification of a composite data element in a composite data element directory (composite data element
specification), or of a simple data element in a simple data element directory (simple data element specification)
[31]
4.32
data element value
specific instance of a simple data element, represented as specified in a simple data element specification and, if
the simple data element is coded, in a code list [32]
4.33
data integrity
property that data has not been altered or destroyed in an unauthorized manner [33]
[ISO 7498-2:1989, 3.3.21]
4.34
data origin authentication
corroboration that the source of data received is as claimed [34]
[ISO 7498-2:1989, 3.3.22]
4.35
data value representation
types of characters allowed (e.g. alphabetic, numeric) and conditions of length relating to the data element values
of a simple data element [35]
4.36
decimal mark
character that separates the digits forming the integral part of a number from those forming the fractional part [36]
[ISO 6093:1985, 4.1]
4.37
decipherment
reversal of a corresponding reversible encipherment [37]
[ISO 7498-2:1989, 3.3.23]
4.38
decryption
See decipherment [38]
[ISO 7498-2:1989, 3.3.24]
4.39
default service characters
set of characters used as service characters in circumstances where a different set is not defined in the service
string advice [39]
4.40
dependency identifier
identifier used in a dependency note to specify the type of dependency between the entities listed in the
dependency note [40]
6 © ISO 2002 – All rights reserved

4.41
dependency note
note used:
a) in a message specification to express relationships between segment groups or between segments;
b) in a segment specification to express relationships between data elements;
c) in a composite data element specification to express relationships between component data elements [41]
4.42
dialogue
two-way conversation between an initiator and responder within an I-EDI transaction [42]
NOTE It is formally composed of a pair of interchanges.
4.43
digital signature
data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the
data unit to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient [43]
[ISO 7498-2:1989, 3.3.26]
4.44
EDI
Electronic Data Interchange
electronic transfer from computer application to computer application of commercial or administrative transactions
using an agreed standard to structure the transaction or message data [44]
4.45
encipherment
cryptographic transformation of data (see cryptography) to produce ciphertext [45]
[ISO 7498-2:1989, 3.3.27]
4.46
encoding
representation of a character as a bit combination [46]
4.47
encryption
See encipherment [47]
[ISO 7498-2:1989, 3.3.28]
4.48
exponent mark
control character used to indicate that the character(s) that follow it are to be interpreted as an exponent [48]
NOTE “E” or “e” is the exponent mark.
4.49
filtering
process by which octets containing arbitrary bit patterns are converted to octets belonging to the character set
which the underlying syntax is capable of supporting [49]
4.50
graphic character
character, other than a control character, that has a visual representation and is normally produced by writing,
printing or displaying [50]
[ISO/IEC 2382-4:1999, 04.03.01]
4.51
group
group of messages (of one or more message types) and/or packages (each containing an object), headed by a
group header and ending with a group trailer [51]
4.52
group header
service segment heading and identifying a group [52]
4.53
group trailer
service segment ending a group [53]
4.54
hash function
(mathematical) function which maps values from a large (possibly very large) domain into a smaller range. A “good”
hash function is such that the results of applying the function to a (large) set of values in the domain will be evenly
distributed (and apparently at random) over the range [54]
[ISO/IEC 9594-8:1998, 3.3.14]
4.55
I-EDI
Interactive EDI
exchange of predefined and structured data within a dialogue, in accordance with the syntax specified in
ISO 9735-1 and ISO 9735-3 for some business purpose, between a pair of co-operating processes, in a timely
manner [55]
4.56
I-EDI transaction
instance of a scenario, consisting of one or more dialogues [56]
4.57
identifier
character or group of characters used to identify or name an item of data and possibly to indicate certain properties
of that data [57]
4.58
ideogram
〈in a natural language〉 graphic character that represents a concept and associated sound elements [58]
EXAMPLES A Chinese ideogram or a Japanese Kanji.
4.59
initiator
application which starts the dialogue and/or I-EDI transaction [59]
4.60
integrity
See data integrity [60]
4.61
interchange
sequence of messages and/or packages, of the same or of different types, starting with the interchange header (or
with the service string advice if used), and ending with the interchange trailer [61]
4.62
interchange header
service segment starting and uniquely identifying an interchange [62]
8 © ISO 2002 – All rights reserved

4.63
interchange trailer
service segment ending an interchange [63]
4.64
key
sequence of symbols that controls the operations of encipherment and decipherment [64]
[ISO 7498-2:1989, 3.3.32]
4.65
mandatory
type of status, used in a message specification, segment specification, or composite data element specification, to
specify that a segment group, segment, composite data element, stand-alone data element or component data
element shall be used at least one time [65]
4.66
message
identified, named and structured set of functionally related segments, covering the requirements for a specific type
of transaction (e.g. invoice), as described in a message specification; a message starts with a message header and
ends with a message trailer [66]
NOTE In transfer, a message is a specific ordered set of segments in conformance with a message specification.
4.67
message body
identified, named and structured set of functionally related segments, covering the requirements for a specific type
of transaction (e.g. invoice), as described in a message specification, excluding the message header and the
message trailer [67]
4.68
message directory
listing of identified and named messages each with its message specification [68]
4.69
message header
service segment starting and uniquely identifying a message [69]
4.70
message specification
description of a message in a message directory, including the specification of the position, status and maximum
number of occurrences of the segments and segment groups constituting the message [70]
4.71
message trailer
service segment ending a message [71]
4.72
message type
code identifying a type of message [72]
4.73
non-repudiation of origin
element of service allowing the originator of a message to provide the recipient(s) of the message irrevocable proof
of origin of the message and the integrity of its content. This will protect against any attempt by the originator to
subsequently revoke the message or its contents. Non-repudiation of origin is provided to the recipient(s) of a
message on a per-message basis using asymmetric encryption techniques [73]
[ITU-T F.400/X.400, Amendment 1]
4.74
numeric character set
character set that contains digits and may contain control characters and special characters but not letters [74]
[ISO/IEC 2382-4:1999, 04.01.04]
4.75
object
stream of bits grouped in octets (which may be associated with an EDIFACT message) [75]
4.76
object header
service segment starting and uniquely identifying an object [76]
4.77
object trailer
service segment ending an object [77]
4.78
organization
unique framework of authority within which a person or persons act, or are designated to act, towards some
purpose [78]
[ISO/IEC 6523-1:1998, 3.1]
4.79
package
object plus its associated header and trailer segments [79]
4.80
parent-child relationship
relationship between two entities, one (“child”) being contained within and directly subordinated to the other
(“parent”) [80]
4.81
position identifier
identifier used in a dependency note to identify an entity (segment group, segment, or data element) by its position
in the parent entity [81]
4.82
private key
〈in a public key cryptosystem〉 that key of a user's key pair which is known only by that user [82]
[ISO/IEC 9594-8:1998, 3.3.19]
4.83
public key
〈in a public key cryptosystem〉 that key of a user's key pair which is publicly known [83]
[ISO/IEC 9594-8:1998, 3.3.18]
4.84
qualifier
simple data element whose data element value, extracted from a code list, gives specific meaning to the function of
another data element or a segment [84]
4.85
release character
character indicating that the character immediately following it shall be passed to the application as received [85]
10 © ISO 2002 – All rights reserved

4.86
repeating data element
composite data element or stand-alone data element having a maximum occurrence of greater than one in the
segment specification [86]
4.87
repetition separator
service character used to separate adjacent occurrences of a repeating data element [87]
4.88
responder
application replying to an initiator [88]
4.89
scenario
formal specification of a class of business activities having the same business goal [89]
4.90
secret key
key used with symmetric cryptographic techniques and usable only by a set of specified entities [90]
[ISO/IEC 11770-1:1996, 3.18]
4.91
segment
identified, named and structured set of functionally related composite data elements and/or stand-alone data
elements, as described in a segment specification; a segment starts with the segment tag and ends with the
segment terminator [91]
NOTE In transfer, a segment is a specific ordered set of one or more composite data element(s) and/or stand-alone data
element(s) in conformance with a segment specification and the syntax rules for transfer.
4.92
segment directory
listing of identified and named segments with their segment specification [92]
4.93
segment group
identified hierarchical set of segments and/or segment groups within a message [93]
4.94
segment specification
description of a segment in a segment directory, including the specification of the position, status and maximum
number of occurrences of the data elements constituting the segment [94]
4.95
segment tag
simple data element uniquely identifying a segment, by reference to a segment directory [95]
4.96
segment terminator
service character indicating the end of a segment [96]
4.97
service character
character reserved for syntactical use; the service characters are the component data element separator, the data
element separator, the release character, the repetition separator and the segment terminator [97]
4.98
service composite data element
composite data element used in service segments [98]
NOTE A service composite data element specification contains only service simple data elements.
4.99
service data element
service simple data element or a service composite data element [99]
4.100
service message
message used to exchange service information relating to the use of EDIFACT syntax rules or security [100]
NOTE A service message specification contains only service segments.
4.101
service segment
segment used
a) in service messages;
b) to control the transfer of data [101]
NOTE A service segment specification contains only service composite data elements and/or service simple data
elements.
4.102
service simple data element
simple data element used only in service segments and/or service composite data elements [102]
4.103
service string advice
optional string of characters used at the beginning of an interchange to specify the service characters used in the
interchange [103]
4.104
simple data element
data element containing a single data element value [104]
NOTE There are two uses of a simple data element: within a composite data element (component data element); and
within a segment outside a composite data element (stand-alone data element).
4.105
simple data element directory
listing of identified and named simple data elements with their simple data element specification [105]
4.106
simple data element specification
set of attributes characterizing a simple data element in a simple data element directory [106]
4.107
special character
graphic character that is not a letter, digit, or blank character, and usually not an ideogram [107]
[ISO/IEC 2382-4:1999, 04.03.12]
4.108
stand-alone data element
simple data element used within a segment without being in a composite data element [108]
12 © ISO 2002 – All rights reserved

4.109
status
attribute of a segment, a segment group, a composite data element or a simple data element identifying the rules
for the presence or absence of the segment /data element in the usage of a message [109]
NOTE The types of status are conditional and mandatory.
4.110
string
sequence of elements of the same nature, such as characters, considered as a whole [110]
[ISO/IEC 2382-4:1999, 04.05.01]
4.111
symmetric algorithm
cryptographic algorithm employing the same value of key for both enciphering and deciphering or for both
authentication and validation [111]
4.112
threat
potential violation of security [112]
[ISO 7498-2:1989, 3.3.55]
4.113
transfer
communication of information from one partner to another [113]
4.114
trigger segment
segment starting a segme
...