Travel Codes Translator eBL

The Travel Codes Translator eBL provides translation for Galileo’s local data, which is a collection of data that provides mappings between travel-industry names and codes recognized by the Apollo and Galileo CRSs. These mappings include information for data such as air, car, and hotel vendors; cities and airports; classes of service; and meal types.

CRSs process only coded forms of many types of data and these coded forms are necessary to communicate with the CRS. Translating human-readable text into CRS codes is called encoding. Translating CRS codes into human-readable text is called decoding. These codes are also used to maintain relationships between types of data, such as cities, states, and countries.

While some types of local data, such as city and airport codes, are standardized, other types of local data are obtained directly from travel vendors. Because these codes change on a regular basis, the Travel Codes Translator eBL allows for more efficient translation of local data. A number of Galileo Web Services interface directly with the Travel Codes Translator eBL to automatically translate CRS data. Currently, the Itinerary eBL and Flight Information eBL use the Travel Codes Translator eBL to decode travel information returned from the CRS.

Travel Codes Translator eBL uses a database to map codes to human-readable text. No calls to CRS transactions are necessary.

Help Contents

The Travel Codes Translator eBL help contains the following topics:

• Encode Overview – Explains how to translate human-readable text into codes necessary for the CRS. Also describes the two types of search capabilities.

• Decode Overview – Explains how to translate CRS codes into human-readable text.

• Supported Translation Categories – Specifies which travel categories are supported for encoding and decoding.

• Supported Languages – Specifies which languages are supported.

• Sample Requests and Responses – Provides sample requests and responses for encoding and decoding.