 | |
 |
Distr. RESTRICTED TRADE/WP.4/R.1157/Add.3 19 September 1995 ENGLISH ONLY |
 | |
ECONOMIC COMMISSION FOR EUROPE COMMITTEE ON THE DEVELOPMENT OF TRADE Working Party on Facilitation of International Trade Procedures (Item 3 of the provisional agenda of the Meeting of Experts on Data Elements and Automatic Data Interchange(GE.1) Fifty-third session, 18-19 March 1996) | |
|
* * *
Electronic data interchange for
Part 8:
|
|
* The present document is reproduced in the form in which it was received by the secretariat.
Contents
Page
Foreword 4
Introduction 5
1 Scope 6
2 Conformance 6
3 Definitions 6
4 Hierarchical interchange structure for
associated data 7
Annex A: Service
directories for associated data 9
Annex B: Object exchange examples 21
Foreword
(Foreword to be added)
In this Part 8, annex A forms an integral part of this
International Standard.
Introduction
This International Standard 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.
These syntax rules 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 UNTDID.
Communications specifications and protocols are outside the scope of
this standard.
UN/EDIFACT CD 9735 consists of eight parts:
UN/EDIFACT CD 9735-1 - Syntax rules
common to both batch and interactive EDI
UN/EDIFACT CD 9735-2 - Syntax rules
specific to batch EDI, plus batch EDI
service directories
UN/EDIFACT CD 9735-3 - Syntax rules
specific to interactive EDI, plus
interactive EDI service directories
UN/EDIFACT CD 9735-4 - Syntax and
service report message for batch EDI
(Message type - CONTRL)
UN/EDIFACT CD 9735-5 - Security
(authenticity, integrity and non-
repudiation)
UN/EDIFACT CD 9735-6 - Secure
authentication and acknowledgement message
(Message type - AUTACK)
UN/EDIFACT CD 9735-7 - Security
(confidentiality) for batch EDI
UN/EDIFACT CD 9735-8 - Associated
data in UN/EDIFACT data interchange
UN/EDIFACT CD 9735-1 shall be used in combination with either
UN/EDIFACT CD 9735-2
or UN/EDIFACT CD 9735-3.
Electronic data interchange for administration, commerce and
transport (EDIFACT) - Application level syntax rules
Part 8:
Associated data in UN/EDIFACT data interchange
1 Scope
This International Standard specifies syntax rules for the
formatting of messages to be interchanged between computer
application systems.
2 Conformance
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 International Standard.
Devices supporting this International Standard 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 Part 1, and at least either Part 2 or
Part 3 of this International Standard.
When identified in this International Standard, provisions defined
in related standards shall form part of the conformance criteria.
3 Definitions
For the purpose of this International Standard, the definitions in
Part 1 annex A apply.
4 Hierarchical interchange structure for associated data
|
Figure 1 - Hierarchical interchange structure for associated data
4.1 Structures
An interchange may contain either:
ù Messages, or
ù Packages, or
ù Messages and Packages, or
ù Groups containing messages, or
ù Groups containing packages, or
ù Groups containing messages and packages.
However, an interchange may not contain a mixture of groups and
packages, groups and messages, or groups and packages and messages.
4.2 Package content
Only one object at a time may exist between any individual UNO and
UNP envelope.
4.3 Object referencing techniques
With respect to the capability to convey objects within the
interchange structure, there is a requirement to provide adequate
referencing capabilities properly to relate the object and the
associated message.
Within the structure numerous options are available to support
implementation. User preferences will require many techniques for
referring to an object. Accordingly, no user solution is defined.
Any such option of including an object in an interchange would by
definition exclude other potential user solutions.
Within the EDIFACT message a RFF segment will be used to identify
the object identification number attributable to one object. The
object identification number assigned should be unique for a
sufficient time to avoid any confusion. There may be many RFF
segment occurrences used to identify all applicable objects.
Annex A
(normative)
Service directories for associated data
A.1 Segment directory
A.1.1 Segment specification legend:
Function The function of the segment
POS The sequential position number of the stand-alone data
element or composite data element in the segment table
TAG The tag for the data elements contained in the segment. The
tags of all service composite data elements start with the
letter "S", and the tags of all service simple data elements
start with the figure "0"
Name Name of a COMPOSITE DATA ELEMENT in capital letters
Name of a STAND-ALONE DATA ELEMENT in capital letters
Name of a component data element in small letters
S The status of the stand-alone data element or composite data
element in the segment, or of the components in the composite
(where M = Mandatory and C = Conditional)
R The maximum number of occurrences of a stand-alone data
element or composite data element in the segment
Repr. Data value representation of the stand-alone data element or
component data elements in the composite.
a alphabetic characters
n numeric characters
an alphanumeric characters
a3 3 alphabetic characters, fixed length
n3 3 numeric characters, fixed length
an3 3 alphanumeric characters, fixed length
a..3 up to 3 alphabetic characters
n..3 up to 3 numeric characters
an..3 up to 3 alphanumeric characters
Notes Segment note number(s)
A.1.2 Dependency note identifiers
Code Name
D1 One and only one
D2 All or none
D3 One or more
D4 One or none
D5 If first, then all
D6 If first, then at least one
more
D7 If first, then none of the
others
See clause 11.5 in Part 1 for the defintion of the dependency note
identifiers
A.1.3 Index of segments by tag
TAG Name
UNO Object header
UNP Object trailer
A.1.4 Index of segments by name
TAG Name
UNO Object header
UNP Object trailer
A.1.5 Segment specifications
------------------------------------------------------------------------------
UNO OBJECT HEADER
Function: To head, identify and specify an object.
POS TAG Name S R Repr. Notes
010 0800 PACKAGE REFERENCE NUMBER M 1 an..14
020 S020 REFERENCE IDENTIFICATION M 99 1
0813 Reference qualifier M an..3
0802 Reference identification number M an..14
030 S021 OBJECT TYPE IDENTIFICATION M 99 2
0805 Object type qualifier M an..3 3
0807 Object attribute qualifier M an..3 3
0809 Object attribute identification C an..255 3
0808 Object attribute C an..255 3
0051 Controlling agency, coded C an..3
040 S022 STATUS OF THE OBJECT M 1
0810 Length of object in octets M n..18
0070 Sequence of transfers C n..2
0073 First and last transfer C a1
NOTES:
1.The first mandatory occurrence of S020 shall identify the Object
Identification Number. This corresponds to the Object
Identification specified in the applicable message RFF segment.
The second occurrence of S020 shall identify a unique Reference
Number specified in the message associated with the object.
Usage Mandatory.
2.One occurrence of S021 is mandatory and shall be used for file
format identification. (Code values "3" in data element 0805 and
"12" in data element 0807).
3.0805 (Object type qualifier) and 0807 (Object attribute
qualifier) together define the object attribute (0808/0809),
instructing the receiving system on how to process and route the
object.
------------------------------------------------------------------------------
UNP OBJECT TRAILER
Function: To end and check the completeness of an object.
POS TAG Name S R Repr. Notes
010 0810 LENGTH OF OBJECT IN OCTETS M 1 n..18 1
020 0800 PACKAGE REFERENCE NUMBER M 1 an..14 1
NOTES:
1. Shall be identical to the value in the UNO.
------------------------------------------------------------------------------
A.2 Composite data element directory
A.2.1 Composite data element specification legend:
POS The sequential position number of the component data element
in the composite data element
TAG The tag for the component data elements contained in the
composite data element. The tags of all service composite
data elements start with the letter "S", and the tags of all
service simple data elements start with the figure "0"
Name Name of a component data element in small letters
S The status of the component data element in the composite
data element
(where M = Mandatory and C = Conditional)
Repr. Data value representation of the component data elements in
the composite.
a alphabetic characters
n numeric characters
an alphanumeric characters
a3 3 alphabetic characters, fixed length
n3 3 numeric characters, fixed length
an3 3 alphanumeric characters, fixed length
a..3 up to 3 alphabetic characters
n..3 up to 3 numeric characters
an..3 up to 3 alphanumeric characters
Desc. Description of the composite data element
A.2.2 Dependency note identifiers
Code Name
D1 One and only one
D2 All or none
D3 One or more
D4 One or none
D5 If first, then all
D6 If first, then at least one
more
D7 If first, then none of the
others
See clause 11.5 in Part 1 for the defintion of the dependency note
identifiers
A.2.3 Index of composite data elements by tag
TAG Name
S020 Reference identification
S021 Object type identification
S022 Status of the object
A.2.4 Index of composite data elements by name
TAG Name
S021 Object type identification
S020 Reference identification
S022 Status of the object
A.2.5 Composite data element specifications
------------------------------------------------------------------------------
S020 REFERENCE IDENTIFICATION
Desc: To identify the references relating to the object.
POS TAG Name S Repr. Notes
010 0813 Reference qualifier M an..3
020 0802 Reference identification number M an..14
------------------------------------------------------------------------------
S021 OBJECT TYPE IDENTIFICATION
Desc: To identify the attribute related to the object type.
POS TAG Name S Repr. Notes
010 0805 Object type qualifier M an..3
020 0807 Object attribute qualifier M an..3
030 0809 Object attribute identification C an..255 D3(030, 040)
040 0808 Object attribute C an..255 D3(030, 040)
050 0051 Controlling agency, coded C an..3
DEPENDENCY NOTES:
D3(030, 040) = One or more, of 030 (data element 0809) or 040 (data element
0808 shall be present)
------------------------------------------------------------------------------
S022 STATUS OF THE OBJECT
Desc: To identify the length and if required the transfer status of
the object.
POS TAG Name S Repr. Notes
010 0810 Length of object in octets M n..18
020 0070 Sequence of transfers C n..2
030 0073 First and last transfer C a1
--------------------------------------------------------------------
A.3 Simple data element directory
--------------------------------------------------------------------
A.3 Simple data element directory
A.3.1 Simple data element specification legend:
Name Name of a simple data element
Desc. Description of the simple data element
Repr. Data value representation of the simple data element:
a alphabetic characters
n numeric characters
an alphanumeric characters
a3 3 alphabetic characters, fixed length
n3 3 numeric characters, fixed length
an3 3 alphanumeric characters, fixed length
a..3 up to 3 alphabetic characters
n..3 up to 3 numeric characters
an..3 up to 3 alphanumeric characters
A.3.2 Index of simple data elements by tag
TAG Name
0800 Package reference number
0802 Reference identification number
0805 Object type qualifier
0807 Object attribute qualifier
0808 Object attribute
0809 Object attribute identification
0810 Length of object in octets
0813 Reference qualifier
A.3.3 Index of simple data elements by name
TAG Name
0810 Length of object in octets
0808 Object attribute
0809 Object attribute identification
0807 Object attribute qualifier
0805 Object type qualifier
0800 Package reference number
0802 Reference identification number
0813 Reference qualifier
A.3.4 Simple data element specifications
----------------------------------------------------------------------
0800 PACKAGE REFERENCE NUMBER
Desc: Unique package reference number assigned by the sender.
Repr: an..14
----------------------------------------------------------------------
0802 REFERENCE IDENTIFICATION NUMBER
Desc: Reference number to identify a relationship among the
object, message, message group and/or interchange.
Repr: an..14
----------------------------------------------------------------------
0805 OBJECT TYPE QUALIFIER
Desc: Qualifier referring to the type of object.
Repr: an..3
---------------------------------------------------------------------
0807 OBJECT ATTRIBUTE QUALIFIER
Desc: Qualifier referring to the attribute of the object being
described.
Repr: an..3
--------------------------------------------------------------------
0808 OBJECT ATTRIBUTE
Desc: Value of the objects attribute as qualified by 0807.
Repr: an..255
--------------------------------------------------------------------
0809 OBJECT ATTRIBUTE IDENTIFICATION
Desc: Coded identification of the objects attribute as qualified
by 0807.
Repr: an..255
--------------------------------------------------------------------
--------------------------------------------------------------------
0810 LENGTH OF OBJECT IN OCTETS
Desc: Count of the number of octets of the object.
Repr: n..18
Note: The count shall start after the segment terminator of the
UNO and stop with the last octet before the UNP.
--------------------------------------------------------------------
0813 REFERENCE QUALIFIER
Desc: Code giving specific meaning to a reference identification
number.
Repr: an..3
--------------------------------------------------------------------
A.4 Code list directory (Informative)
NOTE: This part of the annex is included for completeness, and
trial use.
The content will be included in the UN/EDIFACT 9735 Service
Code Lists Directory, once this Part (8) is approved.
--------------------------------------------------------------------
0805 OBJECT TYPE QUALIFIER
Desc: Qualifier referring to the type of object.
Repr: an..3
1 Computer environment
2 Security
3 File
4 File block
5 Program
6 Interchange
7 Compression
8 Drawing
9 Filter
10 External standard
11 Character set repertoire
12 Character set encoding
--------------------------------------------------------------------
0807 OBJECT ATTRIBUTE QUALIFIER
Desc: Qualifier referring to the attribute of the object being
described.
Repr: an..3
1 Type
2 Version
3 Release
4 Status
5 Level
6 Technique
7 Text information
8 Identification
9 Name
10 Description
11 Length
12 Format
13 Size
14 Requirement
15 Code page
--------------------------------------------------------------------
--------------------------------------------------------------------
0813 REFERENCE QUALIFIER
Desc: Code giving specific meaning to a reference identification
number.
Repr: an..3
1 Object identification number
2 Application message reference number
--------------------------------------------------------------------
Annex B
(informative)
Object exchange examples
B.1Table showing the use of 0805 - "Object type qualifier" and 0807
- "Object attribute qualifier" to qualify the value in 0808/0809
- "Object Attribute/Object Attribute identification".
Object Composite/Data Object Object Object
information Element Type Attribu Attribu
S021/0807/0809 Qualif te te
ier Qualifi S021/08
S021/0 er 08 or
805 S021/08 S021/08
07 09
Computer Computer 1 1 0809
environment Environment/Type
type
Computer Computer 1 2 0808
environment Environment/Version
version
Computer Computer 1 3 0809
environment Environment/Status
status
Security Level Security/Level 2 5 0809
Code
Security Security/Version 2 2 0808
Version
Security Security/Technique 2 6 0809
Technique
Security Free Security/Text 2 7 0808
Text Info Information
File File/Identification 3 8 0808
identification
by Number
File File/Name 3 9 0808
identification
by Name
File File/Description 3 10 0808
description
File format File/Format 3 12 0809
File version File/Version 3 2 0808
File block type File Block/Type 4 1 0809
File record File/Length 3 11 0808
length
File block File Block/Length 4 11 0808
length
Program ID by Program/Identificat 5 8 0808
Number ion
Program ID by Program/Name 5 9 0808
Name
Program version Program/Version 5 2 0808
Interchange Interchange/Format 6 12 0809
Format
Interchange Interchange/Version 6 2 0808
version
Compression Compression/Techniq 7 6 0809
Technique ue
Drawing Size Drawing/Size 8 13 0809
External Std. External 10 14 0809
Requirement Std./Requirement
Filter Type Filter/Type 9 1 0809
Filter Version Filter/Version 9 2 0808
Filter Code Filter/Code Page 9 15 0809
Page
Character Set Character Set 11 1 0809
Repertoire Repertoire/Type
Character Set Character Set 12 6 0809
Encoding Encoding/Technique
NOTE:Data element 0808 "Object attribute" is used for numbers or
textual information, 0809 "Object attribute identification" is
used for coded values. It is possible that information such as
"Size" could either be transmitted as a coded value using 0809
or as a numeric value using 0808. The table above shows the
preferred method reflecting the results of the analysis to
identify the various object identification used. The table may
be expanded by using any valid combination to express new
requirements.
B.2Examples for using 0805 - "Object type qualifier" and 0807 -
"Object attribute qualifier" to qualify the value in 0808/0809 -
"Object Attribute/Object Attribute identification".
I. To identify the "Filter type" :
0 Object type = 9 (filter)
8 qualifier
0
5
0 Object attribute = 1 (type)
8 qualifier
0
7
0 Object attribute = Holds the actual code
8 identification value to identify the
0 filter type
9
UN/EDIFACT codes values that may be used in
conjunction with 0809 to identify the filter type:
1 Hexadecimal
2 ISO 646 (ASCII), ASCII filter as
described in ISO 10126-1
3 ISO 646 (Baudot), Baudot filter as
described in ISO 10126-1
II. To identify the "Filter version":
08 Object type = 9 (filter)
05 qualifier
08 Object attribute = 2 (version)
07 qualifier
08 Object attribute = Holds the actual
08 filter version number,
such as 2, 3