Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.
Node | Description | Values | Occurs | Example |
---|---|---|---|---|
<CarInformationRQ> | Car information request root element | 1 | ||
@version | Version number. | 0..1 | 1.0 | |
<PickUp> | Pick up group | 1 | ||
<AirportCode/> | Pick up or drop off airport code. | 1 | JFK | |
<Location> | Location group | 1 | ||
<CityCode/> | City code. | 1 | NYC | |
<Category/> | Car location category. Values are: T = Airport terminal O = Off-airport C = City location P = Port X = Rail N = North suburban E = East suburban S = South suburban W = West suburban A = All suburban locations R = Resort location D = default location for the city F = Chauffeur Drive Station * = content of Number element contains complete location code (city code is ignored) | [A] [C] [D] [E] [F] [N] [O] [P] [R] [S] [T] [W] [X] [*] | 1 | T |
<Number/> | Location number. | 1 | 01 | |
</Location> | ||||
<Date/> | Date in ISO 8601 format (yyyy-mm-dd). | 1 | 2002-02-22 | |
<Time/> | Time in ISO 8601 format (hh:mm). | 1 | 14:30 | |
</PickUp> | ||||
<DropOff> | Drop off group | 1 | ||
<AirportCode/> | Pick up or drop off airport code. | 1 | JFK | |
<Location> | Location group | 1 | ||
<CityCode/> | City code. | 1 | NYC | |
<Category/> | Car location category. Values are: T = Airport terminal O = Off-airport C = City location P = Port X = Rail N = North suburban E = East suburban S = South suburban W = West suburban A = All suburban locations R = Resort location D = default location for the city F = Chauffeur Drive Station * = content of Number element contains complete location code (city code is ignored) | [A] [C] [D] [E] [F] [N] [O] [P] [R] [S] [T] [W] [X] [*] | 1 | T |
<Number/> | Location number. | 1 | 01 | |
</Location> | ||||
<Date/> | Date in ISO 8601 format (yyyy-mm-dd). | 1 | 2002-02-22 | |
<Time/> | Time in ISO 8601 format (hh:mm). | 1 | 14:30 | |
</DropOff> | ||||
<CarVendorCode> | Car vendor code. | 1 | ZI | |
@LinkType | Link Type. Values are: GCM = Galileo carmaster only participant GCO = Galileo carmaster only participant secondary GLP = Galileo link partner GLO = Galileo link partner secondary GIA = Galileo inside availability link GIO = Galileo inside availability link secondary ASA = Amadeus standard access ACA= Amadeus complete access ACP= Amadeus complete access plus SDA= Sabre direct connect access SDC= Sabre direct connect sell SOL= Sabre other link type WAP= WebSphereDIR WMP= WebSphereDIR WNA= WebSphereDIR AMADEUS default is ASA | [GCM] [GCO] [GLP] [GLO] [GIA] [GIO] [ASA] [ACA] [ACP] [SDA] [SDC] [SOL] [WAP] [WMP] [WNA] | 0..1 | ASA |
@Source | Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. | 0..1 | 1A, 1V, or other. | |
</CarVendorCode> | ||||
<CarType> | Car type code for car type specific search. GDS use car types defined by standard interline practices and procedures (SIPP) manual. Each car-type code consists of four letters, one letter from each of the following categories : - CLASS - TYPE - SHIFT - AIR CONDITIONING. i.e. ECMR = Economy Class + 2/4 Door Car + Manual Transmisson + Air-Conditioning. You can use asterisks in any position to indicate all. So to search for any car so long as it is automatic, enter: **A* . You can use up to 3 asterisks ( **** not allowed). CLASS: C = Compact E = Economy F = Full Size (4-door) I = Intermediate L = Luxury M = Mini P = Premium S = Standard X = Special TYPE: B = 2-Door C = 2/4 Door D = 4-Door F = 4-Wheel Drive J = All Terrain K = Truck L = Limousine P = Pick Up R = Recreational S = Sports Car T = Convertible V = Van W = Station Wagon X = Special SHIFT: A = Automatic M = Manual AIR CONDITIONING: N = No R = Yes | 1 | ECAR | |
@CodeType | Type of the CarType code. If not specified the specified CarType is handled as SIPP code. For systems that dont support SIPP codes the vendorspecific type must be used instead. Values: SIPP .. SIPP code VS .. vendor specific code | [SIPP] [VS] | 0..1 | |
</CarType> | ||||
<RateOptions> | Rate option group | 1 | ||
@Type | Rate Type. Values are: D = Daily E = Weekend W = Weekly M = Monthly H = Hourly (not supported on Amadeus) | [D] [E] [W] [M] [H] | 0..1 | W |
@Category | Rate category. Values are: A = Association B = Business standard C = Corporate G = Government I = Industry (Travel) K = Package L = Inclusive P = Promotiona R = Credential S = Standard U = Consortium V = Convention X = Negotiated | [A] [B] [C] [G] [I] [K] [L] [P] [R] [S] [U] [V] [X] | 0..1 | S |
@Guarantee | Guarantee rate requested. Values are: Y = Yes N = No | [Y] [N] | 0..1 | Y |
<RateCode/> | Requested rate code. | 1 | STD | |
<CurrencyCode> | 0..1 | |||
</CurrencyCode> | ||||
<CorporateDiscount> | Corporate discount group | 0..1 | ||
<CorporateVendorCode/> | Corporate discount vendor code. | 1 | AXD | |
<DiscountNumber/> | Corporate discount number. | 1 | C0001 | |
</CorporateDiscount> | ||||
<RateQualifier/> | Rate qualifier. | 0..1 | ||
</RateOptions> | ||||
<ReferenceKey/> | Reference data base key. On some GDS/CRS, a reference key provided in a previous response message must be included in CarInformationRS for the request to work. Apollo/Galileo: If previous CarAvailabilityRS contained element Rate/RateID, its value must be included as ReferenceKey here. | 0..1 | 808608317 | |
</CarInformationRQ> |
Column | Description |
---|---|
Node | Name of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath. |
Description | Description of meaning and usage of the node. |
Values | List of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema. |
Occurs | Minimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples: 0..3 Node is optional and may occur up to 3 times. 1..N Node must occur at least one (mandatory) and may occur any number of times. 2 Node must occur exactly twice. |
Example | Example value for the node. |
XML Schema documentation generated with XX/1 server