Information technology — Automatic identification and data capture techniques — Syntax for high-capacity ADC media

ISO/IEC 15434:2006 defines the manner in which data is transferred to high-capacity automatic data capture (ADC) media from a supplier's information system and the manner in which data is transferred to the recipient's information system. It does not define the internal data storage format for specific high-capacity ADC media, nor does it specify the application of data structures provided by a specific data syntax format. The application of the data structure is specified by industry conventions. Users of ADC technologies benefit by being able to receive data in a standard form and by being able to provide data in a standard form. Static ADC technologies such as bar code symbologies, magnetic stripe, optical character recognition, surface acoustical wave (SAW) and Weigand effect typically encode a single field of data. Most applications of these technologies involve the encoding of a single field of data by the supplier of the medium and the subsequent decoding of the data field by the recipient. Encoding single fields of data permits the supplier to perform the encodation from a single field within the supplier's information system. Decoding single fields of data permits the recipient to input this data into a single field in the recipient's information system, in lieu of key entry. High-capacity ADC technologies, such as two-dimensional symbols, RFID transponders, contact memories and smart cards, encode multiple fields of data. These multiple fields are usually parsed by the recipient's information system and then mapped to specific fields of data in the recipient's information system. ISO/IEC 15434:2006 defines the syntax for high-capacity ADC media, so as to enable ADC users to utilize a single mapping utility, regardless of which high-capacity ADC medium is employed. ISO/IEC 15434:2006 specifies a transfer structure, syntax, and coding of messages and data formats when using high-capacity ADC media between trading partners (specifically between suppliers and recipients) and, where applicable, in support of carrier applications, such as bills of lading and carrier sortation and tracking. The data encoded according to ISO/IEC 15434:2006 include data which may be used in the shipping, receiving, and inventory of transport units; data which may be contained within supporting documentation, in paper or electronic form, related to unit loads or transport packages; data which may be used in the sortation and tracking of transport units. ISO/IEC 15434:2006 describes the ISO 646 syntax for automatic data capture. ISO/IEC 15434:2006 is not the controlling specification for data structures (e.g. CII) referenced in ISO/IEC 15434:2006. ISO/IEC 15434:2006 does not supersede or replace any applicable safety or regulatory marking or labelling requirements. It is to be applied in addition to any other mandated labelling requirements.

Technologies de l'information — Techniques automatiques d'identification et de capture des données — Syntaxe pour supports de CAD à haute capacité

General Information

Status
Withdrawn
Publication Date
03-Oct-2006
Withdrawal Date
03-Oct-2006
Current Stage
9599 - Withdrawal of International Standard
Completion Date
27-Feb-2019
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 15434:2006 - Information technology -- Automatic identification and data capture techniques -- Syntax for high-capacity ADC media
English language
17 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15434
Third edition
2006-10-01

Information technology — Automatic
identification and data capture
techniques — Syntax for high-capacity
ADC media
Technologies de l'information — Techniques d'identification et captage
automatique des données — Syntaxe pour supports de CAD à haute
capacité




Reference number
ISO/IEC 15434:2006(E)
©
ISO/IEC 2006

---------------------- Page: 1 ----------------------
ISO/IEC 15434:2006(E)
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/IEC 2006
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.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2006 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 15434:2006(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope .1
2 Normative references .1
3 Terms, definitions and documentation notation conventions.2
3.1 Terms and definitions .2
3.2 Documentation notation conventions .2
4 Message format.2
4.1 Message Envelope.3
4.1.1 Message Header.3
4.1.2 Message Trailer.4
4.2 Format Envelope.4
4.2.1 Format Header.4
4.2.2 Format Header “00” - Reserved format .6
4.2.3 Format Header “01” - Transportation .6
4.2.4 Format Header “02” - Complete EDI message / transaction .6
4.2.5 Format Header “03” - Structured data using ASC X12 segments .6
4.2.6 Format Header “04” - Structured data using UN/EDIFACT segments .7
4.2.7 Format Header “05” - Data using GS1 Application Identifiers.7
4.2.8 Format Header “06” - Data using ASC MH 10 Data Identifiers.7
4.2.9 Format Header “07” - Free form text data .8
4.2.10 Format Header “08” - Structured data using CII syntax rules .8
4.2.11 Format Header “09” - Binary data.8
4.2.12 Format Header (“10”- “11”) - Reserved formats.8
4.2.13 Format Header “12” - Data using Text Element Identifiers .9
4.2.14 Format Header (“13”-“99”) - Reserved formats.9
4.2.15 Format Trailer.9
4.3 Data format .9
4.3.1 Format “00” (Reserved) .9
4.3.2 Format “01” Carrier sortation and tracking (Transportation) .10
4.3.3 Format “02” (Complete EDI message / transaction) .12
4.3.4 Format “03” (Structured data using ASC X12 segments) .12
4.3.5 Format “04” (Structured data using UN/EDIFACT segments) .12
4.3.6 Format “05” (Using GS1 Application Identifiers) .13
4.3.7 Format “06” (Using ASC MH 10 Data Identifiers) .13
4.3.8 Format “07” (Free form text format) .13
4.3.9 Format “08” (Structured data using CII syntax rules).13
4.3.10 Format “09” (Binary data) .13
4.3.11 Format “10”-“11” (Reserved).14
4.3.12 Format “12” (Using Text Element Identifiers).14
4.3.13 Format “13”-“99” (Reserved).14
5 Maintenance .14
Annex A (normative) Subset of ISO 646 (Table of hexadecimal and decimal values) .16
Bibliography .17

© ISO/IEC 2006 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 15434:2006(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 15434 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.
This third edition cancels and replaces the second edition (ISO/IEC 15434:2005), which has been technically
revised.

iv © ISO/IEC 2006 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 15434:2006(E)
Introduction
This International Standard defines the manner in which data is transferred to high-capacity automatic data
capture (ADC) media from a supplier’s information system and the manner in which data is transferred to the
recipient’s information system. This International Standard does not define the internal data storage format for
specific high-capacity ADC media. This International Standard does not specify the application of data
structures provided by a specific data syntax format. The application of the data structure is specified by
industry conventions.
Users of ADC technologies benefit by being able to receive data in a standard form and by being able to
provide data in a standard form. Static ADC technologies such as bar code symbologies, magnetic stripe,
optical character recognition, surface acoustical wave (SAW) and Weigand effect typically encode a single
field of data. Most applications of these technologies involve the encoding of a single field of data by the
supplier of the medium and the subsequent decoding of the data field by the recipient. Encoding single fields
of data permits the supplier to perform the encodation from a single field within the supplier’s information
system. Decoding single fields of data permits the recipient to input this data into a single field in the
recipient’s information system, in lieu of key entry.
High-capacity ADC technologies, such as two-dimensional symbols, RFID transponders, contact memories
and smart cards, encode multiple fields of data. These multiple fields are usually parsed by the recipient’s
information system and then mapped to specific fields of data in the recipient’s information system. This
International Standard defines the syntax for high-capacity ADC media, so as to enable ADC users to utilize a
single mapping utility, regardless of which high-capacity ADC medium is employed.

© ISO/IEC 2006 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 15434:2006(E)

Information technology — Automatic identification and data
capture techniques — Syntax for high-capacity ADC media
1 Scope
This International Standard specifies a transfer structure, syntax, and coding of messages and data formats
when using high-capacity ADC media between trading partners (specifically between suppliers and recipients)
and, where applicable, in support of carrier applications, such as bills of lading, and carrier sortation and
tracking.
The data encoded according to this International Standard include
⎯ data which may be used in the shipping, receiving and inventory of transport units;
⎯ data which may be contained within supporting documentation, in paper or electronic form, related to
unit loads or transport packages;
⎯ data which may be used in the sortation and tracking of transport units.
This International Standard describes the ISO 646 syntax for automatic data capture.
This International Standard is not the controlling specification for data structures (e.g. CII) referenced in this
International Standard.
This International Standard does not supersede or replace any applicable safety or regulatory marking or
labelling requirements. This International Standard is to be applied in addition to any other mandated labelling
requirements.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 646, Information technology — ISO 7-bit coded character set for information interchange
ISO/IEC 19762 (all parts), Information technology — Automatic identification and data capture (AIDC)
techniques — Harmonized vocabulary
ANS MH10.8.2, ASC MH 10 Data Identifiers and Application Identifiers
ANS MH10.8.3, ASC MH 10 Syntax for high capacity ADC media
ANS X12, Electronic Data Interchange
CII Syntax Rule (Vers 3.00), CII Syntax Rule Specifications (3.00) (Electronic Data Interchange — Japan)
GS1 General Specification, GS1
ATA Common Support Data Dictionary (CSDD), Air Transport Association
© ISO/IEC 2006 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/IEC 15434:2006(E)
3 Terms, definitions and documentation notation conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 (all parts) apply.
3.2 Documentation notation conventions
This International Standard uses the following typographical conventions in message examples.
a) BOLD, ALL CAPITALS Text that must be entered exactly as it appears.
E
F G U R
(In this International Standard, , , , , O are used to represent
S S S S T
non-printable special characters. The ISO 646 representation of special
characters used in this International Standard can be found in Annex A.)
b) italic, lower case Variable Parameters. The user must supply an appropriate value. In
some cases default values are recommended in this International
Standard.
4 Message format
This clause defines how data shall be transferred from a High Capacity ADC Media reading device to the
user's application software.
To allow multiple data Formats to be contained within a data stream, a two level structure of enveloping is
employed. The outermost layer of the message is a Message Envelope that defines the beginning and end of
the message. Within the Message Envelope are one or more Format Envelopes that contain the data (see
Figure 1). Multiple formats in a single message should only be employed with bi-lateral agreements of the
trading partners.
The Message Envelope shall consist of
• a Message Header,
• one or more Format Envelope(s), and
• a Message Trailer (when required).
Each Format Envelope within the Message Envelope shall consist of
• a Format Header,
• data, formatted according to the rules defined for that Format, and
• a Format Trailer (when required).
2 © ISO/IEC 2006 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 15434:2006(E)

Figure 1 — Enveloping Structure
Note: Annex A shows the decimal and hexadecimal values of ASCII characters used in this International Standard.
4.1 Message Envelope
The Message Envelope defines the start and end of the data contained within the data stream, and provides
the following functions:
• indication that the message contained within this media is formatted in compliance with the rules of this
International Standard;
• indicates the character which has been defined to separate Formats within this Message;
• provides a unique character to indicate the end of the Message.
The structure within a data stream is as follows:
a Message, containing one or more Formats;
 a Format, containing one or more Segments;
  a Segment, containing one or more Data Elements;
  a Data Element (Field), potentially containing one or more Sub-elements (Sub-fields).
4.1.1 Message Header
The Message Header consists of two parts:
• the three character Compliance Indicator, and
• the Format Trailer Character.
1) R
The complete Message Header is: [ )>
S

1) An artificial “space” character has been added between the “[” and “)” characters so as to not be misinterpreted as the
alphabetic character “D”.
© ISO/IEC 2006 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/IEC 15434:2006(E)
4.1.1.1 Compliance Indicator
The Compliance Indicator shall be the first three characters in the Message Header. The Compliance Indicator
shall be [)> (left bracket, right parenthesis, and greater than). See Annex A for a table of ASCII decimal and
hexadecimal values used in this International Standard.
4.1.1.2 Format Trailer Character
The Format Trailer Character shall be the fourth character in the Message Header. The Format Trailer
R
Character shall be the non-printable ASCII character “ ” (see Annex A). The Format Trailer Character is used
S
throughout the message to indicate the end of a data Format envelope (see 4.2.15).
4.1.2 Message Trailer
The Message Trailer identifies the end of the message within the data stream. The Message Trailer shall be
E
the End Of Transaction character, “ O ” (see Annex A). The Message Trailer character shall not be used
T
E
elsewhere in the message except in Format “09” (binary data) where the “ O ” character may appear.
T
The Message Trailer shall not be used with Formats “02” (Complete EDI message / transaction) and “08”
(Structured data using CII Syntax Rules).
4.2 Format Envelope
The Format Envelope defines the start and end of data in a given Format and provides the following functions:
• identifies the data Format used within the envelope;
• defines the character(s) used to separate the Segments, Data Elements (Fields), and Sub-elements
(Sub-fields) within this data Format;
• indicates any applicable date, release, or control information.
4.2.1 Format Header
A Format Header shall consist of two parts:
• a Format Indicator (a two-digit numeric identifier which identifies the rules governing the Format);
• variable data (if any) which defines the separators used and version and release, date, or control
 information of the applicable standards.
Table 1 lists the Format Indicators and variable data associated with the Format Header.
4 © ISO/IEC 2006 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 15434:2006(E)
Table 1 — Format header table Showing associated separators
Format Format
Variable Header Data Format Description
Indicator Trailer
00  Reserved for future use
G R
vv
01 Transportation
S S
02  Complete EDI message / transaction
F G U R
vvvrrr
03 Structured data using ANSI ASC X12 Segments
S S S S
F G U R
vvvrrr
04 Structured data using UN/EDIFACT Segments
S S S S
G R

05 Data using GS1 Application Identifiers
S S
G R
2)

06 Data using ASC MH 10 Data Identifiers
S S
R

07 Free form text
S
08 vvvvrrnn Structured data using CII Syntax Rules
Binary data (file type) (compression technique) (number
G G G G R
ttt.t ccc.c nnn.n
09
S S S S S
of bytes)
10-11  Reserved for future use
G R

12 Structured data following Text Element Identifier rules
S S
12-99  Reserved for future use

Note 1: vv  represents the two-digit version of Format “01” being used
R
Note 2:   represents the Format Trailer character (see 4.2.15).
S
F
Note 3:  represents the Segment Terminator (see 4.2.1.1.1).
S
G
Note 4:  represents the Data Element Separator (see 4.2.1.1.2).
S
U
Note 5:  represents the Sub-Element Separator (see 4.2.1.1.3).
S
Note 6: vvvrrr  represents the three digit Version (vvv) followed by the three digit Release (rrr) (see 4.2.5).
Note 7: vvvvrrnn represents the four digit Version (vvvv) followed by the two digit Release (rr) followed by the
  two digit Edition indicator (nn) (see 4.2.10).
Note 8: ttt.t  represents the file type name (see 4.2.11).
Note 9: ccc.c  represents the compression technique name (see 4.2.11).
Note 10: nnn.n represents the number of bytes (see 4.2.11).

2) Previously known as FACT Data Identifiers.
© ISO/IEC 2006 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/IEC 15434:2006(E)
4.2.1.1 Separators and terminators
The Separators and Terminators are an integral part of the data stream. The Separator and Terminator
characters shall not be used in non-binary data elsewhere in the message. For binary data strings (Format
“09”) special considerations apply (see 4.2.11).
4.2.1.1.1 Segment Terminator
Each segment in Format “03” shall be terminated by the Segment Terminator character, the non-printable
F
character “ ” (see Annex A).
S
4.2.1.1.2 Data Element Separator
Data elements in Formats “01,” “03,” “05,” and “06” shall be separated by the Data Element Separator, the
G
non-printable character “ ” (see Annex A).
S
4.2.1.1.3 Sub-element Separator
Sub-elements in Format “03” shall be terminated by the Sub-element Separator character, the non-printable
U
character “ ”, (see Annex A).
S
4.2.2 Format Header “00” - Reserved format
Format header “00” is reserved for future assignment by the maintenance body of this International Standard.
4.2.3 Format Header “01” - Transportation
The Format Header shall be represented as
G
01 vv
S
where
G
• is the Data Element Separator to be used between Data Elements;
S
• vv represents the two-digit version assigned by the maintenance body of this International
 Standard.
4.2.4 Format Header “02” - Complete EDI message / transaction
The Format Header shall be represented as
02
There is no variable header data for this data Format (see 4.3.3).
4.2.5 Format Header “03” - Structured data using ASC X12 segments
The Format Header shall be represented as
F G U
03vvvrrr
S S S


6 © ISO/IEC 2006 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 15434:2006(E)
where
• vvvrrr represents the three-digit Version (vvv) and three-digit Release (rrr) indicator for the drafts of

ASC X12 used;
F
• is the Segment Terminator to be used to indicate the end of an EDI segment;
S
G
• is the Data Element Separator to be used between EDI Data Elements;
S
U
• is the Sub-element Separator to be used between EDI Sub-elements in a Composite Data
S
Element.
Format Header “03” employs ANSI ASC X12 segments, used in North America. For international trade Format
Header “04” should be used. Format “03” is intended for use within North America only.
4.2.6 Format Header “04” - Structured data using UN/EDIFACT segments
The Format Header shall be represented as
F G U
04vvvrrr
S S S
where
• vvvrrr represents the three-digit Version (vvv) and three-digit Release (rrr) indicator for the

UN/EDIFACT level used;
F
• is the Segment Terminator to be used to indicate the end of an EDI segment;
S
G
• is the Data Element Separator to be used between EDI Data Elements;
S
U
• is the Sub-element Separator to be used between EDI Sub-elements in a Composite Data
S
Element.
4.2.7 Format Header “05” - Data using GS1 Application Identifiers
The Format Header shall be represented as
G
05
S
where
G
• is the Data Element Separator to be used between data Fields.
S
4.2.8 Format Header “06” - Data using ASC MH 10 Data Identifiers
The Format Header shall be represented as
G
06
S
where
G
• is the Data Element Separator to be used between data Fields.
S
© ISO/IEC 2006 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/IEC 15434:2006(E)
4.2.9 Format Header “07” - Free form text data
The Format Header shall be represented as
07
There is no variable header data for this data Format (see 4.3.8).
4.2.10 Format Header “08” - Structured data using CII syntax rules
The Format Header shall be represented as
08vvvvrrnn
where
• vvvvrrnn represents the four-digit Version (vvvv) , two-digit Release (rr), and two-digit edition (nn)

indicator for the CII level used. This equates to the BPID in CII Syntax Rules (see 4.3.9).
Format Header “08” employs CII syntax rules, used in Japan. For international trade Format Header “04”
should be used. Format “08” is intended for use within Japan only.
4.2.11 Format Header “09” - Binary data
The Format Header shall be represented as
G G G G
09 ttt.t ccc.c nnn.n
S S S S
where
G
• is the Data Element Separator to be used between Fields in this header and at the end of the
S
last data field.
• ttt.t represents the identification of the binary file type, e.g., JPEG, TIFF, PCX, BMP, CSV, CGM,
GIF. This field is a variable length of 1-30 characters (including version if applicable). This
G
field shall be terminated by the “ ” character. The binary file type and the means by which to
S
represent the binary file type should be mutually agreed upon between the trading partners.
• ccc.c represents the compression technique employed. This field is a variable length of 0-30
characters. If no compression is used, this field shall be left blank. In any case this field shall
G
be terminated by the “ ” character. The compression technique and the means by which to
S
represent the compression technique should be mutually agreed upon between the trading
partners.
• nnn.n represents the number of bytes in the binary message. This field is a variable length field of 1-
15 digits. The count does not include the length of the data format header or the data format
G
trailer. This field shall be terminated by the “ ” character, which is not part of the byte count.
S
4.2.12 Format Header (“10”- “11”) - Reserved formats
Format headers “10” - “11” are reserved for future assignment by the maintenance body for this International
Standard.
8 © ISO/IEC 2006 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC 15434:2006(E)
4.2.13 Format Header “12” - Data using Text Element Identifiers
The Format Header shall be represented as
G
12
S
where
G
• is the Data Element Separator to be used between data fields.
S
4.2.14 Format Header (“13”-“99”) - Reserved formats
Format headers “13” - “99” are reserved for future assignment by the maintenance body for this International
Standard.
4.2.15 Format Trailer
The Format Trailer identifies the end of a Format Envelope. The Format Trailer shall consist of the Format
R
Trailer Character, the non-printable ASCII character “ ” (see Annex A). The Format Trailer Character shall
S
not be used in non-binary data elsewhere in the Message.
The Format Trailer shall not be used with Formats “02” (Complete EDI message / transaction) and “08” (CII -
Complete Message).
4.3 Data format
Within a given Format Envelope, the data shall be formatted using one and only one of the following methods.
• Transportation.
• Complete EDI Message / Transaction (ASC X12, UN/EDIFACT or CII standard).
• Structured Text (ASC X12 or UN/EDIFACT subset).
• Data structured using the rules of GS1 Application Identifiers.
• Data structured using the rules of ASC MH 10 Data Identifiers.
• Free form text.
• CII Message Record without Message-group header and trailer.
• Binary Data.
• Data structured using the rules of Text Element Identifiers.
If more than one Format is included in a Message, Format “01”, if used, shall be the first Format in the
Message.
4.3.1 Format “00” (Reserved)
This Format type is reserved for future assignment and should not be used prior to the issuance of a revision
or draft standard for trial use of this document.
© ISO/IEC 2006 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO/IEC 15434:2006(E)
4.3.2 Format “01” Carrier sortation and tracking (Transportation)
Format “01” consists of two areas: the first is mandatory data which is common to all carrier sortation and
tracking applications, the second area is optional data which may be useful to specific applications between
trading partners.
The organization controlling the data structure within this format is identified through the version indicator in
the Format Header. At the time that this International Standard was published the following versions had been
identified.
• Version “02” - Formatted according to the rules of ASC MH10/SC 8 (using measurement qualifiers of
pounds [“LB”] and kilograms [“KG”]).
• Version “06” - Formatted according to the rules of the International Air Transport Association (I
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.