CarPolicy request message

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.

Root element of request to retrieve car policy information for a particular car vendor location.1
GDS 2-letter code for car rental company. 1 ZI
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.
Car vendor location for which the policy information is requested.1
IATA 3-letter city/airport code for location. In case of non-airport location Category and Number need to be present. 1 NYC
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
Location number used to identify specific rental location within a location category. 1 001
Date in ISO 8601 format (yyyy-mm-dd) for which to return the hours of operation.
Default is current date.

0..1 2007-12-20


NodeName 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.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum 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.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server