A placeholder in the schema to allow for additional elements and attributes to be included if required, per Trading Partner Agreement (TPA).
value="Inherit" Permission for sharing data for marketing purposes.
Formatted text content and an associated item or sequence number.
When true a written confirmation was requested and will be sent.
A collection of hotel reservations.
A URL for this paragraph.
Identifies the last software system or person to modify a record.
The telephone number associated with the delivery address.
This indicates where this message falls within a sequence of messages.
The name to which the confirmation should be addressed.
When true, indicates a default value should be used.
Textual information, which may be formatted as a line of information, or unformatted, as a paragraph of text.
Identifes the primary language preference for the message. The human language is identified by ISO 639 codes.
Hotel Reservation Notif Request supports the functionality of updating other systems with reservation data. The message assumes a push model, with the originating system pushing the data to another system. The originating system would usually be a booking source, such as a Global Distribution System (GDS), a Central Reservation System (CRS) or some other agent of the hotel.
The language in which the confirmation should be provided.
To indicate a confirmation is to be sent for this batch of reservations.
The sequence number for the paragraph.
A collection of routing hops.
Time stamp of last modification.
value="Inherit" Permission for sharing data for synchronization of information held by other travel service providers.
For all OTA versioned messages, the version of the message is indicated by a decimal value.
Date an item will be purged from a database (e.g., from a live database to an archive).
Indicates the creation date and time of the message in UTC using the following format specified by ISO 8601; YYYY-MM-DDThh:mm:ssZ with time values using the 24 hour clock (e.g. 20 November 2003, 1:59:38 pm UTC becomes 2003-11-20T13:59:38Z).
An email address to which the confirmation should be sent.
Used to indicate whether the request is for the Test or Production system.
Defines the purpose of the e-mail address (e.g. personal, business, listserve). Refer to OTA Code List Email Address Type (EAT).
The time until a hold is released.
When true, indicates the message is being re-sent after a failure. It is recommended that this attribute is used (i.e., set to TRUE) only when a message is retransmitted.
Used to identify the sequence number of the transaction as assigned by the sending system; allows for an application to process messages in a certain order or to request a resynchronization of messages in the event that a system has been off-line and needs to retrieve messages that were missed.
To specify the type of action requested when more than one function could be handled by the message.
A reference for additional message identification, assigned by the requesting host system. When a request message includes an echo token the corresponding response message MUST include an echo token with an identical value.
Formatted text content.
Additional data that will be sent with the confirmation. This could be used to include a map, pictures, or any other information that the reservation source wishes to include with the confirmation
In many cases the description repeats, this will allow you to define the information that is being sent, typically used when multiple occurrences of ParagraphType are being sent.
The mailing address to which the confirmation should be delivered.
ID of creator. The creator could be a software system identifier or an identifier of an employee resposible for the creation.
Used elsewhere in the message to reference this specific email address.
An image for this paragraph.
Time stamp of the creation.
Identifies the alternate language for a customer or message. The human language is identified by ISO 639 codes.
A unique identifier to relate all messages within a transaction (e.g. this would be sent in all request and response messages that are part of an on-going transaction).