TimeInformation response 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.

NodeDescriptionValuesOccursExample
<TimeInformationRS>
Time information response root element1
@version
Version number. 0..1 1.0
<InfoGroup>
Error and information group0..1
<ForInfo>
Information group0..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
<Text/>
Information text or error text. 1..N Free flow text. Example: Invalid flight number
</ForInfo>
<Error>
Error group0..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>
<LocalInfo>
A LocalInfo element is returned for every LocalInfo element in the request *except* for LocalInfo elements for which XX/1 failed to optain the requested information. 0..N
@DaylightSavingUnknown
When UTC time and date were requested for a local time and date it is necessary to know whether the local time is daylight saving or standard time to be able to perform a proper conversion to UTC.

If there is no information available whether daylight saving applies to the requested local time and date, the UTC time and date are determined assuming standard local time and date. In that case the attribute DaylightSavingUnknown is returned with value "Y" to indicate that the UTCTime and UTCDate values may be wrong by the time difference between daylight saving and standard time (in most cases 1 hour).

[Y] 0..1 Y
<Time/>
Local time in ISO 8601 format (hh:mm). If LocalInfo was requested with Time and Date, the Time returned is the requested local time. If LocalInfo was requested without Date and Time, the Time returned is the current local time.

1 06:30
<Date/>
Local date in ISO 8601 format (yyyy-mm-dd). If LocalInfo was requested with Time and Date, the Date returned is the requested local date. If LocalInfo was requested without Date and Time, the Date returned is the current local date.

1 2002-02-02
<CityCode/>
City code for which information was requested. For GDS/CRS for which it is supported to request mutiple LocalInfo elements at once the CityCode is always returned.

0..1 BKK
<UTCTime/>
If LocalInfo was requested with local Time and Date and conversion to UTC is supported for the GDS/CRS, UTCTime returns the UTC time in ISO 8601 format (hh:mm) which corresponds to the specified local time.

0..1 06:30
<UTCDate/>
If LocalInfo was requested with local Time and Date and conversion to UTC is supported for the GDS/CRS, UTCDate returns the UTC date in ISO 8601 format (yyyy-mm-dd) which corresponds to the specified local date and time.

0..1 2002-02-02
</LocalInfo>
</TimeInformationRS>

Legend

ColumnDescription
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