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 |
|---|---|---|---|---|
<CarMakesRS> | Car makes response root element | 1 | ||
@version | Version number. | 0..1 | 1.0 | |
<InfoGroup> | Error and information group | 0..1 | ||
<ForInfo> | Information group | 0..N | ||
@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. | |
@SourceRef | PNR Record Locator associated to Source attribute. | 0..1 | ||
@Code | A code to uniquely identify a specific type of ForInfo message. Currently not returned for most ForInfo messages. | 0..1 | I00001 | |
@Lang | ISO language code. A two letter code as defined by ISO-639-1. | 0..1 | de | |
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
</ForInfo> | ||||
<Error> | Error group | 0..N | ||
@ErrorType | Type of error. | 1 | Air | |
@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. | |
@SourceRef | PNR Record Locator associated to Source attribute. | 0..1 | ||
<Code/> | Error code or equipment type code. | 1 | 0104 (error code), 747 (equipment code) | |
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
<UnderlyingError> | Errors of the backend system can be returned here. | 0..N | ||
@Code | error code of the backend system. | 0..1 | ||
<Text/> | Information text or error text. | 0..N | Free flow text. Example: Invalid flight number | |
</UnderlyingError> | ||||
</Error> | ||||
<BackOffice> | Generic back office response container. Serves as a placeholder for any context specific content. | 0..1 | ||
</BackOffice> | ||||
</InfoGroup> | ||||
<CarVendorCode/> | Car vendor code. | 1 | ZE | |
<CarVendorName/> | Car vendor name. | 1 | Hertz | |
<CityName/> | City name. | 1 | Miami | |
<AddressGroup> | Address group | 0..1 | ||
<LocationName/> | Location name. | 0..1 | Miami International Airport | |
<Address/> | Location address. | 0..1 | 154 Airport Blvd | |
<City/> | City. | 0..1 | Miami | |
<StateCode/> | State. | 0..1 | FL | |
<PostalCode/> | Postal code or zip code. | 0..1 | 33126 | |
<CountryCode/> | Country code. | 0..1 | US | |
<AddressText/> | Free flow address text information. | 0..N | 5301 Blue Lagoon Drive, Miami, FL 33126 | |
</AddressGroup> | ||||
<ContactNumbers> | Phone numbers group | 0..1 | ||
<Phone/> | Location phone number. | 1 | 305-323-1800 | |
<Fax/> | Fax number. | 0..1 | 305-323-1818 | |
<Emergency/> | Emergency phone number. | 0..1 | 1-800-654-3131 | |
</ContactNumbers> | ||||
<Information> | Information group | 0..1 | ||
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
</Information> | ||||
<OptionalEquipment/> | DEPRECATED in favor of OTA-code based AvailableEquipment element. Equipment type. | [ABG] [ABS] [AIR] [ATD] [BBS] [BST] [BYC] [CAL] [CAM] [CBR] [CBS] [CCL] [CCT] [CDD] [CLS] [CSB] [CSI] [CST] [DAB] [DSL] [DVD] [FMR] [FRT] [HCH] [HCL] [HCR] [ICS] [LDP] [LFA] [LFF] [LUG] [NSK] [NVP] [NVS] [PAB] [PAS] [PAX] [PDL] [PHN] [PWS] [RAD] [RSB] [SBE] [SBR] [SIX] [SKI] [SKR] [SKV] [SNO] [SNT] [SRC] [STR] [SUR] [TAP] [TEL] [TOL] [TRH] [TSW] [TVI] [VCR] [WIN] | 0..N | SKR |
<AvailableEquipment> | 0..1 | |||
<Equipment> | An optional equipment available for this offer. | 1..N | ||
@Type | OTA code type EQP .. equipment type VS .. vendor specific code | [EQP] [VS] | 0..1 | |
@Code | OTA code to specify the type of optional equipment. | 0..1 | ||
@Quantity | Number of equipment items | 0..1 | ||
@Description | Textual description of the optional equipment. | 0..1 | SKI RACK | |
</Equipment> | ||||
</AvailableEquipment> | ||||
<CarMakes> | Car information group | 1..N | ||
<CarType/> | Car type. | 1 | ECAR | |
<Class/> | Car class. | 0..1 | A | |
<Make/> | Car make or model. | 1 | Hyundai Accent | |
<Capacity/> | Passenger capacity. | 1 | 4 | |
<Doors/> | Number of doors. | 1 | 2-4 | |
</CarMakes> | ||||
<MoreCarsToken/> | Token used to request more cars in the subsequent car list request.Or number of more available tokens. | 0..1 | 1-1367258029-366043017-11-N or Y. 5 (number of more available tokens) | |
</CarMakesRS> |
| 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