ota2015a.OTA_TourActivityAvailRQ.xsd Maven / Gradle / Ivy
ALL SCHEMA FILES IN THE OPENTRAVEL ALLIANCE SPECIFICATION ARE MADE AVAILABLE ACCORDING TO THE TERMS DEFINED BY THE OPENTRAVEL LICENSE AGREEMENT AT http://www.opentravel.org/Specifications/Default.aspx.
This message is used to request availability for a day tour and/or activity selected by the customer. Note that the tour and/or activity code is known to the availability system, e.g. a unique ID and/or name is being passed in the request in addition to date/ time, customer types and counts.
Point of sale information for the initiator of the availability request.
Information that may directly impact how the receiving system processes the request message.
A positive integer value that indicates the maximum number of responses desired in the return.
The Tour/Activity response message may return a value in this element if there is additional data available that is not contained in the response message. The text value should be echoed in this request to indicate where to begin the next block of data.
Identification of the language used for any descriptive information.
The requested display currency in ISO 4217 encoding.
(Reference): http://www.opentraveldevelopersnetwork.com/Supported_ISO_Standards.php
(More Info): http://www.opentraveldevelopersnetwork.com/2012A_SchemaDoc/DisplayCurrency
The requested pricing currency in ISO 4217 encoding.
CAD = Canadian Dollar | USD = United States Dollar | EUR = Euro
http://www.opentraveldevelopersnetwork.com/Supported_ISO_Standards.php
The ISO 4217 standard "minor unit" for the number of decimal places for a the display and pricing currency.
The ISO 4217 standard "minor unit" is typically used when the amount provided includes the minor unit of currency without a decimal point (e.g., USD 8500 needs DecimalPlaces="2" to represent $85).
If TRUE, tours and activities that do meet all specified criteria should be returned.
Criteria for a tour/ activity availability request.
Core identifying information for the tour(s)/activity(s) which availability is being requested for.
Physically challenged accessibility preferences. NOT ALL TOUR/ ACTIVITY RESERVATION SYSTEMS CAN DETERMINE AVAILABILITY BASED ON ACCESSIBILITY CRITERIA. Check with your trading partner before implementing this functionality.
Promotion codes and discount program information that may influence availability.
One or more promotion codes for promotional pricing.
Up to 9 may be specified for each participant category and/ or group.
Discount program information.
The company name associated with the discount program.
The name of a discount program, e.g. "Day Pass" or "Gold Card".
A description of the discount program.
A unique ID (that is assigned elsewhere in the message) that associates a participant category with other information.
A unique ID (that is assigned elsewhere in the message) that associates a group with other information.
Physical address, region and geocoding tour/ activity location information.
Negotiated rate information that may influence availability.
The requested start date(s) and optional time(s) of the tour/ activity search period.
Up to nine date/time combinations may be requested.
Note that for each start or end period date, up to 5 times may also be requested.
Note that the @Duration attribute should not be used.
The requested start time. Up to 5 may be specified for each requested date.
The date of the tour/ activity.
A choice between specifying participant quantity/ category and/or group information.
Specifies the number of participants and optionally the participant category.
The number of free child places being requested.
Group information for which availability is being requested.
A group name that participant(s) are associated with.
A unique identifier for a group that may be used elsewhere in this message.
The minimum quantity of participants in a group.
The maximum quantity of participants in a group.
The actual quantity of participants in a group.
A group code that participant(s) are associated with.
Multimodal offer influencers.