ota2015a.OTA_HotelInvCountRQ.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 provides the ability to request inventory count details for hotel properties by specific criteria that may include dates, date ranges, rooms and products.
Point of sale object.
Collection of Inventory Count requests criteria.
Provides the criteria to identify the date range and room type inventory to be returned.
A date or range of dates for the rate plan.
Collection of room stay candidates.
Element used to identify available room products.
Indicates the detail of hotel reference information.
Used to search for hotels within a particular market segment. Refer to OpenTravel Code Segment Category Code Type (SEG).
Refer to OpenTravel Code list OpenTravel Code List Property Class Type (PCT).
Refer to OpenTravel Code List Architectural Style Code (ARC).
The level of integration of a property to provide automated transaction information. The lower the number, the higher the integration (e.g., a 1 means the supplier has the highest level of integration automation).
Boolean Flag indicating if overbooking or allocation (defined by BookingLimitMessageType) is requested.
An enumerated type defining the function of the booking limit message. Values: SetLimit (Allocation), AdjustLimit (Overbooking).
The value of this attribute will be a decimal field identifying the maximum number of seconds the responding application has to respond to the request. For example, suppose a client requests 10 OTA 'RatePlanRequestSegment' items but can only wait up to 4.0 seconds max. If only 6 segments were collected within the time-frame, the client would only receive those 6 segments within one response message.
The response to the previous request returns this attribute if there was more data than could be returned in the response. Including the attribute in this request indicates where to begin the next block of data.
Used to specify the source of the data being exchanged as determined by trading partners.