1. CARGO XML TASK FORCE
DRAFT TERMS OF REFERENCE
1. Objectives
The objectives of this Task Force are to provide recommendations to the Cargo Business
Processes Panel (CBPP) on XML requirements for transportation messages.
The following messages will be considered:
- Shippers’ Letter of instruction1
o Shipping instructions: Document advising details of cargo and exporter’s
requirement for its physical movement.
o Forwarding instructions: Document issued by a consignor to a freight
forwarder, giving instructions regarding the action to be taken by the freight
forwarder for the forwarding of goods described therein.
- House Waybill
A document made out by an agent / consolidator which specifies the contract
between the shipper and the agent/consolidator for the arrangement of carriage of
goods.2
- Air Waybill
A document made out by or on behalf of the shipper, which evidences the contract
between the shipper and airline(s) for the carriage of cargo over the routes of the
airline(s) 3
- House Manifest
A document containing the same information as a cargo manifest and additional
details on freight amounts, etc.4.
The development of these XML messages will be based as much as possible on existing
messages (e.g. CIMP, IFTMIN).
1 UN/CEFACT United Nations Layout Key for trade Documents 2002, Appendix 1 Definition and descriptions of document names
2 UN/CEFACT United Nations Layout Key for trade Documents 2002, Appendix 1 Definition and descriptions of document names
3 IATA Cargo Services Conference Resolutions Manual, Resolution 660
4 UN/CEFACT United Nations Layout Key for trade Documents 2002, Appendix 1 Definition and descriptions of document names

2. To facilitate electronic data exchange between the stakeholders of the Supply Chain the
Task Force will have the task to:
- Recommend and validate the business data requirements of the standard XML
messages;
- Ensure as much as possible that the business data satisfies multi-modal
requirements;
- Describe commonly associated terms, definitions and codes.
The Task Force shall provide recommendations on the maintenance of the standards.
Note: As part of the analysis the task will have to make recommendation on the possibility
to have one XML message covering more than one message.
2. Composition
2.1 The membership of the Task Force shall comprise a maximum of 25 members.
Ideally, the Task Force will be composed of:
(i) No less than two Shippers,
(ii) No less than two Freight Forwarders,
(iii) No less than two Carriers,
(iv) No less than two Ground Handling Agents,
(v) No less than two Customs Brokers,
(vi) International or National Organizations
2.2 Membership of the Task Force shall reflect as much as possible a fair
representation from the regions of the world in accordance with the following
formula:
(i) The Americas: at least two members,
(ii) Europe, Middle East and Africa: at least two members,
(iii) Asia-Pacific: at least two members.
2.3 The Task Force may invite the participation of experts (e.g. Legal, Security) at the
meetings from time to time.

3. 2.4 Service providers can join the Task Force as observers.
2.5 IATA will convene and support the meetings of the Task Force.
2.6 The CBPP shall appoint the Members of the Task Force drawing from a pool of
individuals nominated by IATA Member airlines, Industry Trade Associations, and
individual organizations falling under the categories set forth in Section 2.1.
3. Rules and Procedures
Meetings
3.1 There will be regular conference calls and possibly Scheduled Meetings of the
Task Force.
3.1.1 IATA may call additional meetings (“Interim Meetings”) at its discretion (e.g.
every quarter), or in accordance with a request from a Member of the Task
Force, provided that IATA shall have first circulated the request to the
members of the Task Force and a majority of the Task Force agrees that the
meeting shall be convened. Interim Meetings may be held by telephone or
videoconference.
3.1.2 At the early stage Members of the Task Force may be requested to
participate in weekly or fortnightly conference calls and in ad-hoc face-to-
face meetings if necessary.
3.2 The quorum for any meeting shall be 50% of the Members.
Recommendations to the CBPP
3.3 The Task Force shall limit its activity to providing recommendations to the CBPP on
XML requirements for cargo transport messages. Importantly, Members will not be
voting on any IATA Industry Standards, Resolutions or Recommended Practices.
3.4 Decisions on the recommendations to the CBPP shall be determined by a two-
thirds consensus of the established Quorum.

4. 4. Roles and Responsibilities
4.1 Each Member of the Task Force shall participate in his or her capacity as an
industry representative.
4.2 Each Representative shall have the following expertise:
(i) Understanding of the needs and benefits to exchange electronic messages in
XML format;
(ii) Business knowledge to identify the required and/or necessary business
information needed in the standard;
(iii) High-level understanding of electronic data exchange mechanism between
trading partners.
4.3 Members shall jointly identify the required and/or necessary business information
needed in the standard
4.4 IATA shall have the responsibility to coordinate meetings of the Task Force
including the preparation of the agenda, reports of the meetings, and arrange for
appropriate support services (for example, legal and technical support).
5. Deliverables
The Task Force will provide recommendations in the following areas:
(i) Message Functional Specifications
(ii) Data Dictionary Specifications (using where feasible international standard code
lists)
(iii) Schemas (based on UN/CEFACT Core Components Library and UN/CEFACT XML
naming and Design rules)*
(iv) Samples*
* Technical experts may be asked to support the development of the schemas and
samples based on the specifications recommended by the Task Force.

5. 6. Reporting
This Task Force shall report to the Cargo Business Processes Panel (CBPP) and shall
consult with the IATA FIATA Consultative Council (IFCC) and the e-freight Central Action
Group (eCAG).
Reports of the meetings including recommendations by the Task Force shall be made
available to all Members of the Task Force.
A dedicated extranet will be set up for the Task Force Members to share information such
as minutes, specifications and supporting materials and to allow on line discussion
through forums.
*********